Star200+

Pre-install eval

context-fundamentals 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
61
Eval report
59
Trust
69
Audit
41
Agent safety

do not auto install

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

Required gates

Checks an agent must pass before install

Open JSON

Task fit

94

pass

Task wording matches this skill metadata.

  • Evaluate context-fundamentals before installing it in an agent workflow
  • automation
  • RAG and knowledge workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add shipshitdev/skills --skill context-fundamentals

Install command safety

92

pass

standard package or runtime install path

  • npx skills add shipshitdev/skills --skill context-fundamentals

Trust score

59

fail

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

  • Manual review
  • 33 GitHub stars
  • Unknown

Audit score

69

warn

Needs review

  • License is unclear

Agent safety gate

41

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

46

fail

secrets or environment access, filesystem or document 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
  • Low GitHub adoption signal
  • Repository license is listed as 'Unknown' in GitHub, but skill metadata and README explicitly state MIT and reference the upstream MIT license. This is a minor compliance ambiguity that should be resolved by confirming/updating the repository license.
  • No OpenAgentSkill engagement data yet
  • High-risk permission hints: Secrets or environment access

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

warn

70

Public metadata needs stronger README/SKILL.md context

Recent maintenance

pass

100

2d since push

Alternatives available

pass

82

Alternative skills are available for comparison.