verify-known-issues
Verify claims about known issues in libraries or tools. Use when about to state something is a "known issue", "known bug", or "known limitation".
Profile →npx skills add majiayu000/claude-skill-registry --skill verify-known-issues-beshkenadze-claude-skills-market-2 --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Verify Known Issues ## Trigger This skill activates when Claude is about to say ANY of these patterns: - "This is a known issue with..." - "This is a known bug in..." - "This is a known limitation of..." - "This is a known problem with..." - "There's a known issue..." - "This is a documented issue..." - "This is a common issue with..." - "This is a recognized bug..." ## Overview Claude may hallucinate "known issues" that don't exist. Claims about external software bugs, library limitations, or platform issues MUST be verified before stating them as fact. ## Required Workflow ### Step 1: STOP Before Claiming Do NOT write "This is a known issue" until verification is complete. ### Step 2: Web Search Verification Use WebSearch to find evidence: ``` Search queries to try: - "[library/tool name] [error message] known issue" - "[library/tool name] [behavior] bug github" - "[library/tool name] [version] issue" - "site:github.com [library] [error] issue" ``` ### Step 3: Evaluate Evidence Evidence MUST include at least ONE of: - GitHub issue with multiple confirmations - Official documentation mentioning the limitation - Stack Overflow answer with significant upvotes - Official bug tracke
- Trigger
- Overview
- Required Workflow
- Step 1: STOP Before Claiming
- Step 2: Web Search Verification
- Step 3: Evaluate Evidence
- Step 4: Sub-Agent Consensus
- Step 5: Report with Citations
- Decision Tree
- Examples
- BAD (Before This Skill)
- GOOD (After This Skill)
- Exceptions
- Anti-Patterns
What does the verify-known-issues skill do?
Verify claims about known issues in libraries or tools. Use when about to state something is a "known issue", "known bug", or "known limitation".
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill verify-known-issues-beshkenadze-claude-skills-market-2 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.