Verify claims about known issues in libraries or tools. Use when about to state something is a "known issue", "known bug", or "known limitation".
/plugin marketplace add beshkenadze/claude-skills-marketplace/plugin install beshkenadze-skills-marketplace@beshkenadze/claude-skills-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
This skill activates when Claude is about to say ANY of these patterns:
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.
Do NOT write "This is a known issue" until verification is complete.
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"
Evidence MUST include at least ONE of:
Launch a verification agent to review the evidence:
Use Task tool with subagent_type="general-purpose":
- Provide the claim you want to make
- Provide the evidence URLs found
- Ask: "Does this evidence support claiming this is a 'known issue'?"
If verified, state the claim WITH citations:
This is a known issue with [X].
Evidence:
- [GitHub Issue #123](url) - Reported by N users
- [Official docs](url) - Documents this limitation
If NOT verified, rephrase:
I encountered [behavior]. I couldn't find documentation
confirming this is a known issue, so it may be:
- A configuration problem
- An edge case
- A misunderstanding on my part
Let me investigate further...
About to claim "known issue"?
│
▼
┌─────────────────────────────┐
│ STOP - Do not write claim │
└─────────────────────────────┘
│
▼
┌─────────────────────────────┐
│ WebSearch for evidence │
│ (3+ different queries) │
└─────────────────────────────┘
│
▼
Found credible sources?
│
├─► NO ──► Rephrase as observation, not fact
│
▼ YES
┌─────────────────────────────┐
│ Launch verification agent │
│ with evidence context │
└─────────────────────────────┘
│
▼
Agent confirms?
│
├─► NO ──► Rephrase as observation
│
▼ YES
┌─────────────────────────────┐
│ State claim WITH citations │
└─────────────────────────────┘
Claude: "This is a known issue with Python 3.14's asyncio
module where get_event_loop() is deprecated."
No evidence provided. May be hallucinated.
Claude: Let me verify this before claiming it's a known issue...
[WebSearch: "python 3.14 asyncio get_event_loop deprecated"]
Found:
- PEP 594: Confirms deprecation
- Python docs: Documents new pattern
- GitHub cpython#12345: Migration guide
[Verification agent confirms evidence]
Claude: "This is a known issue with Python 3.14 -
`get_event_loop()` was deprecated per PEP 594.
Evidence: [PEP 594](url), [Python Docs](url)
The fix is to use `asyncio.run()` or create an explicit loop."
This skill does NOT apply to:
| Don't | Do |
|---|---|
| "This is a known issue" (no source) | Search first, cite sources |
| Skip verification for "obvious" bugs | All external claims need evidence |
| Cite memory alone | Fresh search required |
| Single unverified source | Multiple sources or official docs |
| Trust outdated information | Check issue is still open/relevant |
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.