Loading...
Loading...
Found 3,197 Skills
Configure and run openapi-format CLI workflows for OpenAPI/AsyncAPI documents. Use when you need to sort fields, filter operations/tags/flags/content, change casing, generate operationIds, apply overlays, convert OpenAPI versions (3.0/3.1 to 3.1/3.2), rename titles, split specs, bundle refs, or manage .openapiformatrc/--configFile driven formatting pipelines with minimal config overrides.
Create, edit, and refine agent skills through co-development and eval loops. Use for ANY question about skills or request to create/modify them.
Best practices for organizing project folders, file naming conventions, and directory structure standards for research and development projects
Visualize and document pplx-sdk system architecture with Mermaid diagrams — layer maps, data flow, dependency graphs, sequence diagrams, and component relationships. Use when designing new features, onboarding, or documenting how the system works.
This skill should be used after creating or modifying skills to update the main README.md file. It scans all skills in ~/.claude/skills/, extracts metadata from SKILL.md files, and regenerates the README with categorized skill listings. Triggers on requests mentioning "update skills readme", "refresh skills list", or after adding new skills.
Automatically sync Agents.md, claude.md and gemini.md files in the project to maintain content consistency. Supports automatic monitoring and manual triggering.
Create and manage Mermaid architecture diagrams with automatic SVG generation
Extract a shareable runnable template under templates/NNN-slug/ from a real project: copy + de-brand + remove secrets + add env examples + docs, with minimal refactors. Use when you have a working project and want to turn it into a template.
Convert meeting discussions into clear, actionable notes with tasks, decisions, and follow-ups fo...
Conduct Neovim configuration research using plugin docs and codebase exploration. Invoke for neovim research tasks.
Turn vague ideas into a validated design/spec through structured brainstorming. Use before any creative work (new features, UI/components, behavior changes, refactors) and whenever a user asks to brainstorm, define requirements, propose approaches, or write a design doc.
Create a new skill that uses an MCP server, following best practices from the MCP CLI guide. Use when user wants to create a skill for a new MCP server or integrate MCP functionality into a skill.