Skill Issue Reporter

Report issues with skills to the centralized tracker at psylch/skill-issues.

When to use

When you encounter a problem while using a skill:

The skill's instructions don't match reality (outdated paths, missing tools)
The skill's design doesn't fit the actual use case
A script or command from the skill fails
The skill is missing a capability it should have

Workflow

1. Identify the skill

Determine which skill has the issue. Use the skill's name from its SKILL.md frontmatter (e.g., better-agent-browser, tech-research, ch-project-context).

2. Compose the issue

Write a title and body with whatever context is most useful. You have the richest context right now — include what matters:

What you were trying to do
What went wrong or felt wrong
Relevant error messages, file paths, or commands
Your assessment of whether it's a bug, design flaw, or suggestion

No fixed template. Organize the information however makes the problem clearest.

3. Submit

Run this command via Bash:

gh issue create -R psylch/skill-issues \
  --label "skill:<SKILL_NAME>" \
  --title "<TITLE>" \
  --body "$(cat <<'EOF'
<BODY>

---
Source project: <current project name or path>
EOF
)"

Optionally add a type label: --label bug, --label suggestion, or --label design-flaw.

4. Confirm

After creating, note the issue URL in your response so the user (or future CIO session) can find it.

Notes

The gh CLI must be authenticated (it almost always is in this environment)
Don't worry about duplicate detection — issue volume is low, CIO deduplicates manually
Include a "Source project" line at the bottom so CIO knows where to look for context