From agent-tools
When you notice something wrong or suboptimal in a skill or agent definition -- file a GitHub issue on joshrotenberg/agent-tools rather than silently proceeding.
How this skill is triggered — by the user, by Claude, or both
Slash command
/agent-tools:agent-feedbackThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
When an agent detects a problem in a skill or agent definition during
When an agent detects a problem in a skill or agent definition during real use, that observation is valuable. This skill describes when and how to file a GitHub issue so it isn't lost.
File an issue when you notice:
Do NOT file for stylistic preferences or minor wording nits.
File when either condition is true:
If neither condition applies, continue without filing.
fix: <skill-name> -- <one-line description>
feat: <skill-name> -- <one-line description>
Use fix: for incorrect or outdated instructions. Use feat: for missing coverage of a real situation.
Examples:
fix: sandbox-preflight -- blocked tool check silently no-ops when gh is missing
feat: orchestration-prompt-template -- no guidance for runner prompt when issue has no acceptance criteria
gh issue create \
--repo joshrotenberg/agent-tools \
--title "fix: <skill-name> -- <one-line description>" \
--body "$(cat <<'EOF'
**What the skill says**
<quote or paraphrase>
**What actually happened / what is missing**
<specific description>
**Suggested fix or question**
<proposed change or question>
EOF
)"
Add relevant labels with --label to match the severity and component of the observation.
Available labels: skills, agents, ci, docs, fix, feat, field-feedback, p1, p2, p3.
Example: --label "skills,fix,p2" for a skill bug of moderate severity.
Check for duplicates before filing:
gh issue list --repo joshrotenberg/agent-tools --state open
Don't bundle multiple unrelated findings into one issue. If you have two distinct observations, file two issues.
Continue the current task. Do not wait for the issue to be resolved. Include the issue URL in your return summary to the dispatcher or human.
gh issue listfield-feedback -- for wrapper bugs, sandbox gaps, unexpected
dispatch behaviors, and findings that route to repos other than joshrotenberg/agent-toolsrunner-issue-authority -- gh issue view as the authoritative
source for task inputspiral-diagnosis -- when a dispatched session is stuck
(a different kind of feedback loop)npx claudepluginhub joshrotenberg/agent-tools --plugin agent-toolsCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.