slos-and-triggers Eval
======================

Status: review
Score: 65/100
Risk: medium
Decision: manual_review
Policy: review
Reason: Test manually in an isolated workspace and compare against safer alternatives.

Install:
npx skills add honeycombio/agent-skill --skill slos-and-triggers

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: 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.
- PASS License clarity: MIT
- WARN Permission surface: filesystem or document access, network or browser access

Warnings:
- Trust score: Potentially useful, but at least one trust signal needs human inspection.
- Audit score: Needs review
- Agent safety gate: Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
- Permission surface: filesystem or document access, network or browser access
- Permission surface may require sandboxing
- The SKILL.md uses `${CLAUDE_PLUGIN_ROOT}` for reference file paths, which may be confusing in non-Claude or generic agent environments; the variable is not explained.
- The statement that 'Compliance at 0%' is likely a misconfigured SLI is too absolute: a newly created SLO before backfill, or an SLO with no matching events, can also show 0% compliance.
- The skill provides good action heuristics but does not specify a consistent output format for agent responses, such as how to summarize SLO status, budget burn, and recommended actions to the user.
- Low GitHub adoption signal
- Quality score needs review
- Permission surface needs review: filesystem or document access, network or browser access
- GitHub adoption: 22 GitHub stars

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
- The SKILL.md uses `${CLAUDE_PLUGIN_ROOT}` for reference file paths, which may be confusing in non-Claude or generic agent environments; the variable is not explained.
- No OpenAgentSkill engagement data yet
- Permission surface may require sandboxing
- The statement that 'Compliance at 0%' is likely a misconfigured SLI is too absolute: a newly created SLO before backfill, or an SLO with no matching events, can also show 0% compliance.
- The skill provides good action heuristics but does not specify a consistent output format for agent responses, such as how to summarize SLO status, budget burn, and recommended actions to the user.

URLs:
- Skill: https://www.openagentskill.com/skills/honeycombio-slos-and-triggers
- Audit: https://www.openagentskill.com/skills/honeycombio-slos-and-triggers/audit
- JSON: https://www.openagentskill.com/api/agent/evals?slug=honeycombio-slos-and-triggers