OpenAgentSkill
GitHub200+

Pre-install eval

content-strategy 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
70
Eval report
71
Trust
77
Audit
53
Agent 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 content-strategy before installing it in an agent workflow
  • core
  • Content automation workflows; Claude Code teams; teams that value GitHub adoption signals

Install path

92

pass

Install handoff is available.

  • npx skills add aitytech/agentkits-marketing --skill content-strategy

Install command safety

92

pass

standard package or runtime install path

  • npx skills add aitytech/agentkits-marketing --skill content-strategy

Trust score

71

warn

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

  • Manual review
  • 596 GitHub stars
  • MIT

Audit score

77

warn

Needs review

  • Financial research output is not financial advice; require human review before any live investment decision

Agent safety gate

53

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

86

pass

MIT

  • MIT

Permission surface

74

warn

secrets or environment access

  • 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
  • production agents without a repository review
  • SKILL.md declares output_schema: content-plan but does not define the schema or provide an example content-plan output.
  • High-risk permission hints: Secrets or environment access
  • Financial research output is not financial advice; require human review before any live investment decision
  • The skill references prerequisites such as marketing-fundamentals, but those dependencies are not included or explained within the skill bundle.

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

86

Metadata includes enough usage and workflow context

Recent maintenance

pass

88

2mo since push

Alternatives available

pass

82

Alternative skills are available for comparison.