coding-standards Eval
=====================

Status: failed
Score: 77/100
Risk: high
Decision: do_not_auto_install
Policy: block
Reason: Permission surface: secrets or environment access, filesystem or document access

Install:
npx skills add affaan-m/ECC --skill coding-standards

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
- WARN Trust score: Good trust signals with a few areas worth checking before rollout.
- WARN Audit score: Needs review
- WARN Agent safety gate: Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
- PASS License clarity: MIT
- FAIL Permission surface: secrets or environment access, filesystem or document access

Warnings:
- Trust score: Good trust signals with a few areas worth checking before rollout.
- Audit score: Needs review
- Agent safety gate: Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
- High-risk permission hints: Secrets or environment access
- Dependency or permission surface needs review
- Permission surface may require sandboxing
- Financial research output is not financial advice; require human review before any live investment decision
- SKILL.md contains React, Next.js, API design, and Supabase-specific examples that overlap with the stated scope boundaries, which say to use frontend-patterns and backend-patterns for framework-specific guidance.
- The skill claims to be a baseline cross-project standard but includes framework-specific file structures and libraries, which may cause agents to apply them outside the intended context.
- No explicit setup or invocation details are included, though this is largely a knowledge-based skill and does not require installation.
- Financial research output is not financial advice; require human review before any live investment decision.
- Permission surface needs review: secrets or environment access, filesystem or document access

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
- SKILL.md contains React, Next.js, API design, and Supabase-specific examples that overlap with the stated scope boundaries, which say to use frontend-patterns and backend-patterns for framework-specific guidance.
- High-risk permission hints: Secrets or environment access
- Dependency or permission surface needs review
- Permission surface may require sandboxing
- Financial research output is not financial advice; require human review before any live investment decision
- The skill claims to be a baseline cross-project standard but includes framework-specific file structures and libraries, which may cause agents to apply them outside the intended context.

URLs:
- Skill: https://www.openagentskill.com/skills/affaan-m-coding-standards
- Audit: https://www.openagentskill.com/skills/affaan-m-coding-standards/audit
- JSON: https://www.openagentskill.com/api/agent/evals?slug=affaan-m-coding-standards