Pre-install eval
source-command-choose-desktop-stack 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.
manual review
Test manually in an isolated workspace and compare against safer alternatives.
Required gates
Checks an agent must pass before install
Task fit
84
Task wording matches this skill metadata.
- Evaluate source-command-choose-desktop-stack before installing it in an agent workflow
- other
- Coding agents workflows; Claude Code teams; builders willing to evaluate younger projects
Install path
92
Install handoff is available.
- npx skills add legioncodeinc/vibe-coding-tools --skill source-command-choose-desktop-stack
Install command safety
92
standard package or runtime install path
- npx skills add legioncodeinc/vibe-coding-tools --skill source-command-choose-desktop-stack
Trust score
75
Good trust signals with a few areas worth checking before rollout.
- Strong shortlist
- 88 GitHub stars
- AGPL-3.0-or-later
Audit score
77
Needs review
- AI review approval is missing
Agent safety gate
53
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: Shell or command execution
License clarity
86
AGPL-3.0-or-later
- AGPL-3.0-or-later
Permission surface
76
shell or command execution
- Shell or command execution: high
- Network access: medium
Validation plan
What the agent should do next
- 1Inspect repository, README/SKILL.md, license, and recent commits before production use.
- 2Install in an isolated workspace or sandbox with no production secrets available.
- 3Run the smallest representative task and record files touched, commands run, network access, and outputs.
- 4Compare the selected skill against at least one alternative when the eval status is review or failed.
- 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
- high-compliance environments without internal security review
- No major risk signals from current metadata
- High-risk permission hints: Shell or command execution
- AI review approval is missing
- Quality score needs review
Supporting checks
Trust signals behind the decision
README/SKILL.md completeness
warn76
Public metadata needs stronger README/SKILL.md context
Recent maintenance
pass100
2d since push
Alternatives available
pass82
Alternative skills are available for comparison.