Pre-install eval
azure-troubleshooting 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.
do not auto install
Trust score: Potentially useful, but at least one trust signal needs human inspection.
Required gates
Checks an agent must pass before install
Task fit
84
Task wording matches this skill metadata.
- Evaluate azure-troubleshooting before installing it in an agent workflow
- research
- Research agents workflows; Claude Code teams; builders willing to evaluate younger projects
Install path
92
Install handoff is available.
- npx skills add aktsmm/Agent-Skills --skill azure-troubleshooting
Install command safety
92
standard package or runtime install path
- npx skills add aktsmm/Agent-Skills --skill azure-troubleshooting
Trust score
59
Potentially useful, but at least one trust signal needs human inspection.
- Manual review
- 25 GitHub stars
- CC BY-NC-SA 4.0
Audit score
67
Needs review
- License restricts commercial reuse
Agent safety gate
19
This skill should not be selected by an agent without explicit human security review.
- Do not auto-install. Inspect the source, dependencies, and permission surface first.
- Metadata combines secrets access with shell or command execution
License clarity
58
CC BY-NC-SA 4.0
- CC BY-NC-SA 4.0
Permission surface
18
secrets or environment access, shell or command execution
- Shell or command execution: high
- Browser automation: medium
- 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
- production agents without a repository review
- Low GitHub adoption signal
- The skill is primarily written in Japanese, which may limit accessibility for non-Japanese-speaking users.
- High-risk permission hints: Shell or command execution, Secrets or environment access
- License restricts commercial reuse
Supporting checks
Trust signals behind the decision
README/SKILL.md completeness
pass86
Metadata includes enough usage and workflow context
Recent maintenance
pass88
2mo since push
Alternatives available
pass82
Alternative skills are available for comparison.