brainstorm-beagle Eval
======================

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

Install:
npx skills add existential-birds/beagle --skill brainstorm-beagle

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: Apache-2.0
- WARN Permission surface: shell or command execution, filesystem or document 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: shell or command execution, filesystem or document access
- High-risk permission hints: Shell or command execution
- Financial research output is not financial advice; require human review before any live investment decision
- Path inconsistency: SKILL.md says the spec is saved to `.beagle/concepts/<slug>/spec.md`, but references/spec-template.md says save to `docs/specs/YYYY-MM-DD-<topic>.md`. This could cause agents to write specs to inconsistent locations.
- SKILL.md does not explicitly document operational limitations such as what to do if the user provides insufficient context, how to handle conflicting requirements, or when to stop asking questions. The workflow is clear but edge-case behavior is underspecified.
- Financial research output is not financial advice; require human review before any live investment decision.
- Quality score needs review
- GitHub adoption: 80 GitHub stars
- Stars/forks activity: 80 stars, 8 forks; issue activity unavailable in current metadata

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
- Path inconsistency: SKILL.md says the spec is saved to `.beagle/concepts/<slug>/spec.md`, but references/spec-template.md says save to `docs/specs/YYYY-MM-DD-<topic>.md`. This could cause agents to write specs to inconsistent locations.
- No OpenAgentSkill engagement data yet
- High-risk permission hints: Shell or command execution
- Financial research output is not financial advice; require human review before any live investment decision
- SKILL.md does not explicitly document operational limitations such as what to do if the user provides insufficient context, how to handle conflicting requirements, or when to stop asking questions. The workflow is clear but edge-case behavior is underspecified.
- Financial research output is not financial advice; require human review before any live investment decision.

URLs:
- Skill: https://www.openagentskill.com/skills/existential-birds-brainstorm-beagle
- Audit: https://www.openagentskill.com/skills/existential-birds-brainstorm-beagle/audit
- JSON: https://www.openagentskill.com/api/agent/evals?slug=existential-birds-brainstorm-beagle