aceternity-ui
100+ animated React components (Aceternity UI) for Next.js with Tailwind. Use for hero sections, parallax, 3D effects, or encountering animation, shadcn CLI…
[TODO: Write comprehensive description in third-person. Start with "This skill provides..." or "This skill should be used when..."] [TODO: Add "Use when" scenarios - specific situations where Claude should use this skill] [TODO: Add keywords - technologies, use cases, error
$ npx -y skills add secondsky/claude-skills --skill skill-name --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/skill-nameContext preview
The summary Claude sees to decide when to auto-load this skill.
[TODO: Write comprehensive description in third-person. Start with "This skill provides..." or "This skill should be used when..."] [TODO: Add "Use when" scenarios - specific situations where Claude should use this skill] [TODO: Add keywords - technologies, use cases, error
name: [TODO: lowercase-hyphen-case-name] description: | [TODO: Write comprehensive description in third-person. Start with "This skill provides..." or "This skill should be used when..."] [TODO: Add "Use when" scenarios - specific situations where Claude should use this skill] [TODO: Add keywords - technologies, use cases, error messages that should trigger this skill] license: MIT
**Status**: [TODO: Production Ready / Beta / Experimental] **Last Updated**: [TODO: YYYY-MM-DD] **Dependencies**: [TODO: List prerequisite skills or tools, or write "None"] **Latest Versions**: [TODO: package@version, package2@version]
---
[TODO: Provide clear, actionable instructions]
# [TODO: Example command]
**Why this matters:**
[TODO: Continue with step-by-step instructions]
// [TODO: Code example with comments]
**CRITICAL:**
[TODO: Keep going until setup is complete]
---
[TODO: Detailed instructions]
[TODO: Code examples, configurations, etc.]
**Key Points:**
[TODO: Continue with detailed steps]
---
✅ [TODO: Best practice #1] ✅ [TODO: Best practice #2] ✅ [TODO: Best practice #3]
❌ [TODO: Anti-pattern #1] ❌ [TODO: Anti-pattern #2] ❌ [TODO: Anti-pattern #3]
---
This skill prevents **[TODO: number]** documented issues:
**Error**: [TODO: Exact error message or description] **Source**: [TODO: GitHub issue link, Stack Overflow link, or official docs] **Why It Happens**: [TODO: Root cause] **Prevention**: [TODO: How this skill fixes it]
[TODO: Repeat pattern for each issue]
---
[TODO: Complete, working configuration file]
**Why these settings:**
---
// [TODO: Code example]
**When to use**: [TODO: Specific scenarios]
[TODO: More examples]
---
[TODO: Only include this section if you have scripts/, references/, or assets/]
[TODO: List and explain any executable scripts]
**Example Usage:**
./scripts/[TODO: script-name].sh
[TODO: List documentation files that Claude can load when needed]
**When Claude should load these**: [TODO: Specific scenarios]
[TODO: List template files, images, etc. that get used in output]
---
[TODO: Deep dive into complex scenarios]
[TODO: Additional advanced content]
---
**Required**:
**Optional**:
---
---
{
"dependencies": {
"[TODO: package]": "^[TODO: version]"
},
"devDependencies": {
"[TODO: package]": "^[TODO: version]"
}
}---
[TODO: Optional - provide evidence of production usage]
This skill is based on [TODO: project name]:
---
**Solution**: [TODO: How to fix]
**Solution**: [TODO: How to fix]
---
Use this checklist to verify your setup:
---
**Questions? Issues?**
1. Check [TODO: reference/common-issues.md] if you created one 2. Verify all steps in the setup process 3. Check official docs: [TODO: URL] 4. Ensure [TODO: critical requirement] is configured
---
1. **Search for [TODO:**** - Replace every [TODO: ...] with actual content 2. **Delete this section** when done 3. **Remove sections** that don't apply to your skill 4. **Add sections** as needed for your specific use case 5. **Test everything** before committing 6. **Verify against** ONE_PAGE_CHECKLIST.md
**Key Reminders:**
**Example Good Description:**
description: | This skill provides comprehensive knowledge for building React applications with Vite and TypeScript. It should be used when scaffolding new Vite projects, configuring TypeScrip
145 production-ready skills for Claude Code CLI 🔌 Platform / Harness Support These plugins ship as Claude Code marketplace plugins (.claude-plugin/ manifests) and Codex CLI plugins (.codex-plugin/ manifests).
Repo: secondsky/claude-skills
100+ animated React components (Aceternity UI) for Next.js with Tailwind. Use for hero sections, parallax, 3D effects, or encountering animation, shadcn CLI…
Secure API authentication with JWT, OAuth 2.0, API keys. Use for authentication systems, third-party integrations, service-to-service communication, or…
Creates comprehensive API changelogs documenting breaking changes, deprecations, and migration strategies for API consumers. Use when managing API versions,…
Verifies API contracts between services using consumer-driven contracts, schema validation, and tools like Pact. Use when testing microservices communication,…
Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs,…
Implements standardized API error responses with proper status codes, logging, and user-friendly messages. Use when building production APIs, implementing…