@gigsmart/haiku-report
ASubmit feedback or a bug report to the H·AI·K·U team
Install
agr install @gigsmart/haiku-report --target claudeWrites 1 file into .claude/skills/, pinned to git-a0152174.
- .claude/skills/haiku-report/SKILL.md
Document
name: haiku-report description: Submit feedback or a bug report to the H·AI·K·U team
Feedback
- Ask the user what feedback they'd like to share — what happened, what they expected, and any steps to reproduce.
- Summarize their feedback into a clear, actionable issue report. Do NOT submit their words verbatim — synthesize it into a structured summary with context (what they were doing, what went wrong, what the expected behavior was).
- Ask the user if the summary looks good before submitting.
- Call
haiku_reportwith the synthesizedmessage. Optionally includecontact_emailandnameif the user provides them.
Trustgrade A
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- passLicense
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-a0152174fd312026-07-31