Star200+

Pre-install eval

fortify-development 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.

FailedHigh riskBLOCK Policy
65
Eval report
66
Trust
75
Audit
43
Agent safety

do not auto install

Permission surface: secrets or environment access, network or browser access

Required gates

Checks an agent must pass before install

Open JSON

Task fit

84

pass

Task wording matches this skill metadata.

  • Evaluate fortify-development before installing it in an agent workflow
  • design-creative
  • Workflow automation workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add promovaweb/specsfy --skill fortify-development

Install command safety

92

pass

standard package or runtime install path

  • npx skills add promovaweb/specsfy --skill fortify-development

Trust score

66

warn

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

  • Manual review
  • 60 GitHub stars
  • MIT

Audit score

75

warn

Needs review

  • Dependency or permission surface needs review

Agent safety gate

43

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

48

fail

secrets or environment access, network or browser access

  • Network access: medium
  • Filesystem 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
  • The SKILL.md content appears truncated; the final sentence about two-factor authentication in SPA mode is incomplete, which might indicate missing content in the actual file.
  • High-risk permission hints: Secrets or environment access
  • Dependency or permission surface needs review
  • Permission surface may require sandboxing

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

86

Metadata includes enough usage and workflow context

Recent maintenance

pass

100

Pushed today

Alternatives available

pass

82

Alternative skills are available for comparison.