context-fundamentals Eval
=========================

Status: failed
Score: 61/100
Risk: high
Decision: do_not_auto_install
Policy: block
Reason: Trust score: Potentially useful, but at least one trust signal needs human inspection.

Install:
npx skills add shipshitdev/skills --skill context-fundamentals

Required checks:
- PASS Task fit: Task wording matches this skill metadata.
- PASS Install path: Install handoff is available.
- PASS Install command safety: standard package or runtime install path
- FAIL Trust score: Potentially useful, but at least one trust signal needs human inspection.
- WARN Audit score: Needs review
- WARN Agent safety gate: Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
- WARN License clarity: Unknown
- FAIL Permission surface: secrets or environment access, filesystem or document access

Warnings:
- Audit score: Needs review
- Agent safety gate: Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
- README/SKILL.md completeness: Public metadata needs stronger README/SKILL.md context
- License clarity: Unknown
- High-risk permission hints: Secrets or environment access
- License is unclear
- Permission surface may require sandboxing
- 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.
- SKILL.md contains cross-references to non-vendored skills (context-degradation, context-optimization) that are not present in this bundle. The README notes these were intentionally removed from routing, but the references in the body remain and could confuse an agent.
- The included Python script (context_manager.py) is a utility with token estimation heuristics; it is not production-grade and may be used by an agent without proper validation. This is not a security risk but could lead to inaccurate context handling if used in operational settings.
- Low GitHub adoption signal
- Quality score needs review

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

Do not use when:
- 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
- License is unclear
- Permission surface may require sandboxing

URLs:
- Skill: https://www.openagentskill.com/skills/shipshitdev-context-fundamentals
- Audit: https://www.openagentskill.com/skills/shipshitdev-context-fundamentals/audit
- JSON: https://www.openagentskill.com/api/agent/evals?slug=shipshitdev-context-fundamentals