" \ --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

# Skill Issue > Report skill bugs, design flaws, or suggestions to the centralized issue tracker. Use when a skill doesn't work as expected, has a design problem, or could be improved. Triggers: 'report skill issue', 'skill bug', 'skill problem', 'skill-issue', '上报skill问题', 'skill设计问题' - Skill: `psylch/skill-issue` (Agent Skill) - Install (CLI): `npx skillmds@latest add psylch/skill-issue` - Raw SKILL.md: https://api.skillmd.com/api/skills/psylch/skill-issue/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Docs & Writing - Author: psylch (https://skillmd.com/u/psylch) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/psylch/skill-issue --- # 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 Auto-detect: look back in your conversation for the most recent `Skill` tool invocation — its `skill` parameter is the skill name. If the issue was triggered by a script, check the script path for `skills//`. If auto-detection fails, ask the user or infer from context. The name must match the skill's SKILL.md frontmatter `name` field (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: ```bash gh issue create -R psylch/skill-issues \ --label "skill:" \ --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