Star0

Pre-install eval

Tiktok Signature eval report.

A machine-readable install decision for agents: task fit, Trust Score, Audit Score, install safety, permission surface, and a concrete validation plan before this skill touches a workspace.

Needs reviewMEDIUM RISKREVIEW POLICY
69
Eval
71
Trust
77
Audit
49
Safety

manual review

Test manually in an isolated workspace and compare against safer alternatives.

Required gates

Checks an agent must pass before install

Open JSON

Task fit

84

pass

Task wording matches this skill metadata.

  • Evaluate Tiktok Signature before installing it in an agent workflow
  • browser-automation
  • Browser automation workflows; Claude Code teams; teams that value GitHub adoption signals

Install path

92

pass

Install handoff is available.

  • npx skills add carcabot/tiktok-signature

Install command safety

92

pass

standard package or runtime install path

  • npx skills add carcabot/tiktok-signature

Trust score

71

warn

Potentially useful, but at least one trust signal needs human inspection.

  • Manual review
  • 981 GitHub stars
  • Unknown

Audit score

77

warn

Needs review

  • License is unclear

Agent safety gate

49

warn

Sparse or mixed signals. Useful for discovery, but not for autonomous installation.

  • Test manually in an isolated workspace and compare against safer alternatives.
  • High-risk permission hints: Secrets or environment access

License clarity

42

warn

Unknown

  • Unknown

Permission surface

60

warn

secrets or environment access, network or browser access

  • Browser automation: medium
  • Network access: medium
  • Secrets or environment access: high

Validation plan

What the agent should do next

  1. 1Inspect repository, README/SKILL.md, license, and recent commits before production use.
  2. 2Install in an isolated workspace or sandbox with no production secrets available.
  3. 3Run the smallest representative task and record files touched, commands run, network access, and outputs.
  4. 4Compare the selected skill against at least one alternative when the eval status is review or failed.
  5. 5Promote only after the agent reports a successful verification result and unresolved warnings are accepted.

Do not use when

Conditions that require another skill

  • teams that need a vendor-supported SLA
  • high-compliance environments without internal security review
  • No major risk signals from current metadata
  • High-risk permission hints: Secrets or environment access
  • License is unclear
  • Permission surface may require sandboxing

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

fail

50

Public metadata needs stronger README/SKILL.md context

Recent maintenance

pass

88

1mo since push

Alternatives available

pass

82

Alternative skills are available for comparison.