psylch/skill-issue-skill · Archived
Report skill bugs, design flaws, or suggestions to the centralized issue tracker.
npx skills add psylch/skill-issue-skill --skill skill-issue
This repository is archived — consider an actively maintained alternative.
Helps users discover and install agent skills when they ask questions like "how do I do X", "fi…
3.3M installsCreate new skills, modify and improve existing skills, and measure skill performance. Use when …
375.6K installsReplace with description of the skill and when Claude should use it.
64K installsRelated neighbors and high-traction skills in the same topics — useful to compare before installing.
Guidance for distinctive, intentional visual design when building new UI or reshaping an existi…
866.4K installsBrowser automation CLI for AI agents. Use when the user needs to interact with websites, includ…
810.4K installsReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…
617.3K installsBuild, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …
576.5K installsDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …
568.9K installsDeclared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
main
Files included with this skill beyond the listing page.
SKILL.md
2,318 B
SUMMARY.md
304 B
Report issues with skills to the centralized tracker at psylch/skill-issues.
When you encounter a problem while using a 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/<name>/.
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).
Write a title and body with whatever context is most useful. You have the richest context right now — include what matters:
No fixed template. Organize the information however makes the problem clearest.
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.
After creating, note the issue URL in your response so the user (or future CIO session) can find it.
gh CLI must be authenticated (it almost always is in this environment)