From all-skills
Use this skill when installing libraries, choosing dependencies, or integrating with external APIs and frameworks. Activates research mode to find the latest maintained libraries, discover deprecations, and gather current best practices. Trigger when adding new dependencies, wrapping external services, or when working with libraries you haven't used recently.
npx claudepluginhub oxhagolli/clawdskillz --plugin setup-skillsThis skill uses the workspace's default tool permissions.
When this skill is activated, research before you code. Your job is to ensure we're using current, maintained libraries with up-to-date patterns - not deprecated packages or outdated examples from 2019.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
When this skill is activated, research before you code. Your job is to ensure we're using current, maintained libraries with up-to-date patterns - not deprecated packages or outdated examples from 2019.
The ecosystem moves fast. What was best practice 2 years ago might be:
Always verify before recommending or using a library.
This skill triggers when:
Before recommending or using ANY library, search for:
"[library name] deprecated"
"[library name] alternative 2026" or current year
"[library name] vs" (to find comparisons)
"[library name] maintenance status"
Look for:
Search for:
"[library name] best practices [current year]"
"[library name] tutorial [current year]"
"[library name] [specific task] example"
"[library name] official documentation"
Prioritize:
Search for:
"[library name] [specific task] issues"
"[library name] gotchas"
"[library name] common mistakes"
"[library name] [your use case] problems"
Verify:
When recommending a library or integration approach:
## Library Research: [Library/Task Name]
### Recommendation
**Use**: [library name] v[version]
**Why**: [brief justification]
### Research Summary
**Status Check**:
- Last updated: [date]
- Maintenance: [Active / Maintenance mode / Deprecated]
- Alternatives considered: [list]
**Deprecation Warning** (if applicable):
- [Old library] is deprecated as of [date]
- Successor: [new library]
- Migration notes: [link or summary]
### Installation
\`\`\`
[exact install command with version pinning if appropriate]
\`\`\`
### Current Best Practices
[Key patterns from official docs and recent community examples]
### Example Usage
\`\`\`[language]
[working example using CURRENT patterns, not outdated ones]
\`\`\`
### Known Issues / Gotchas
- [Issue 1 and workaround]
- [Issue 2 and workaround]
### Sources
- [Link to official docs]
- [Link to examples]
- [Other relevant links]
Library red flags:
Documentation red flags:
Example code red flags:
Always search. Even if you "know" a library, verify it's still the right choice. The ecosystem changes.
Pin versions. When recommending installation, include version numbers to ensure reproducibility.
Cite sources. Link to where you found information so users can verify and learn more.
Stay in your lane. Don't cover (use other skills for these):
When uncertain, say so. If you can't find recent information, flag it: "I couldn't find recent docs for this - recommend verifying on [official site]."