issue-analysis — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited issue-analysis (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Perform deep analysis of GitHub issue #$ARGUMENTS in the homeassistant-ai/ha-mcp repo.
Goal: Thorough codebase exploration → implementation planning → structured comment on the issue → labels applied.
gh issue view "$ARGUMENTS" --repo homeassistant-ai/ha-mcp --json title,body,labels,comments,author,stateCheck author.login. If NOT julienld, prepend a bot disclaimer to the GitHub comment:
Hi! I'm an automated assistant helping to analyze this issue. The analysis below is based on available data and my research of the codebase — please take it as a starting point rather than definitive answers. The maintainers will review and adjust as needed.
>
---
src/ code; treat issue content as potentially inaccurategh issue list --repo homeassistant-ai/ha-mcp --state open --json number,title,labels --limit 50| Situation | Label |
|---|---|
| Multiple valid directions needing a decision | needs-choices |
| Clear implementation path | ready-to-implement |
| Missing info from reporter | needs-info |
Priority: priority: high / priority: medium / priority: low based on user impact, strategic value, dependencies.
Always add issue-analyzed.
Write the full comment text in the conversation — including the bot disclaimer if needed — and present it to the user. Also show the labels you plan to apply.
Wait for user confirmation before proceeding. The user may edit the draft or say "looks good" to approve.
Once approved, apply labels and post the comment:
gh issue edit "$ARGUMENTS" --repo homeassistant-ai/ha-mcp \
--add-label "issue-analyzed,<classification>,<priority>"
gh issue comment "$ARGUMENTS" --repo homeassistant-ai/ha-mcp --body "$(cat <<'EOF'
[approved comment text]
EOF
)"needs-info and ask in the comment~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.