Explore skills

Use this skill to get documentation for third-party APIs, SDKs or libraries before writing code that uses them to ensure you have the latest, most accurate documentation. This is a better way to find documentation than doing web search. This includes when a user asks for tasks like "use the OpenAI API", "call the Stripe API", "use the Anthropic SDK", "query Pinecone", or any other time the user as

Run the AI Voice Analyzer on blog content to detect AI-sounding patterns and get actionable rewrite suggestions. Use when reviewing or improving blog articles before publishing.

This skill is used to look up the official Effect-TS API documentation, including function signatures, parameters, or usage examples related to Effect.

Expert in content strategy, SEO-driven storytelling, and developer advocacy, bridging the gap between technical products and market adoption. Ideal for creating marketing content, developing content strategy, writing blog posts, or planning developer outreach.

Fetches Kit (ConvertKit) newsletter broadcasts for writing context. Use when asked to download newsletters, get past email content for style reference, or fetch broadcasts for analysis.

Use for setting up Ref MCP server, managing API keys, troubleshooting Ref documentation lookup issues, dashboard operations (adding repos, uploading files), understanding pricing/credits, or deciding Ref vs alternatives. Do NOT use it for actually searching docs; for that, use ref_search_documentation directly.

Analyze writing samples to create a comprehensive voice DNA profile. Use when the user wants to capture their unique writing voice, needs to create a voice profile for AI content, or is setting up a new writing system.

This skill keeps Which Key Lazy documentation in sync with code changes. It verifies documentation accuracy after code changes and ensures documentation (README.md, CLAUDE.md) matches the current codebase, working bidirectionally for verification or updates.

Expert in content strategy, SEO-driven storytelling, and developer advocacy, bridging the gap between technical products and market adoption. Use for creating marketing content, developing content strategy, writing blog posts, or planning developer outreach.

Expert in content strategy, SEO-driven storytelling, and developer advocacy, bridging the gap between technical products and market adoption. Ideal for marketing content, content strategy, blog posts, and developer outreach.

Use for technical communication - GitHub/GitLab tickets, PR/MR descriptions, issue comments, code review comments, commit messages. Direct, brief style with no AI-speak. NOT for README.md, public docs, or blog posts.

Copy generated text content to clipboard. Use when user asks to "copy this", "copy to clipboard", "save to clipboard", or after creating emails, messages, letters, or other text content that needs to be shared.