Technical Writing

Auto-load when writing TypeScript code. Provides patterns for type safety, async handling, and modern TypeScript idioms.

dbt best practices for models, tests, documentation, and project organization.

Write detailed product and technical specification documents for OrbitCove. Use when creating PRDs, architecture docs, data models, or UX flows.

Extracts C++ code snippets, lists classes and functions, and provides source code references for comprehensive C++ codebase analysis. This skill should be used when analyzing any C++ source files to understand code structure, extract reusable components, and generate structured documentation.

Web and code search with Exa MCP. Use for current documentation, API references, code examples, latest library info, or when the user mentions "exa", "web search", "docs", or "current API".

Package custom skills into versioned distributable ZIP files with installation and user documentation. Use when preparing a skill for sharing, distribution, or archival. Supports semantic versioning, automatic documentation generation, and version management.

Write clear, developer-focused documentation including README files, API docs, architecture decision records, code comments, and user guides. Use for documentation tasks, markdown files (.md), or improving existing docs.

Investigate platform incidents, perform RCA, create incident documentation, and follow alert runbooks in the Kagenti platform

Invoke Gemini CLI as a partner AI developer for tasks benefiting from its 1M token context window or a second opinion. Use when analyzing large codebases, generating documentation, getting alternative perspectives, researching topics with web search, or creating UI wireframes/components. Gemini has read/write/edit/shell/web search capabilities like Claude.

Use when writing systematic review manuscript sections following PRISMA 2020 guidelines. Covers abstract, introduction, methods, results, and discussion drafting for medical journals. Invoke for academic writing assistance.

Draft GitHub issues as YAML files from plans or requirements. Use this skill when:- User says "draft issues" or "create issue draft", or suggests refinements to the draft issues- Converting plans/requirements into GitHub issue format- User provides a plan file path (docs/plans/*.md)- Need to structure multiple related issues with parent-child relationshipsGenerates YAML files in tmp/issues/ for review before publishing to GitHub.

This skill should be used when validating user prompts, plans, or requests before execution. It conducts independent validation, questions assumptions, references official sources and documentation, identifies potential issues, and presents revised recommendations to ensure accuracy and completeness.

Expert knowledge for Technology Layer modeling in Documentation Robotics

Documentation organization, maintenance, and cleanup.USE WHEN: organizing docs, cleaning project root, updating documentation,checking for redundancy, maintaining docs structure.NOT FOR: technical implementation (use relevant technical skill).Examples:<example>Context: User added documentation to wrong location.user: "I added a new API doc file to the root directory"assistant: "I'll use docs-keeper to organize it in the proper docs/ location."<commentary>File organization is docs-keeper responsibility.</commentary></example><example>Context: User needs to update docs after code changes.user: "I modified the auth system and need to update the docs"assistant: "I'll use docs-keeper to update the authentication documentation."<commentary>Documentation updates are docs-keeper responsibility.</commentary></example>

Use when spec is complete and you need detailed implementation tasks for LLM agents. Creates execution plans with exact file paths, complete code examples, and verification steps. Triggers: 'write plan', 'execution plan', 'implementation plan', 'break down into tasks', 'detailed steps'.

This skill should be used when agents need to provide clickable code references to users in reports, investigations, or bug findings. It ensures file references use the simple path:line_number format that Claude Code automatically converts to clickable links. Do not use for general documentation or conceptual explanations.

Implement robust error handling with user-friendly messages, fail-fast validation, specific exception types, and proper resource cleanup across the application. Use this skill when writing try-catch blocks, throwing or catching exceptions, implementing error boundaries, handling API errors, or managing error states in any part of the codebase. Apply this skill when validating inputs early (fail fast), providing clear actionable error messages to users without exposing security details, using specific exception types rather than generic errors, implementing centralized error handling at appropriate boundaries, designing for graceful degradation, implementing retry logic with exponential backoff, or ensuring resources are cleaned up in finally blocks. This skill ensures errors are caught and handled appropriately, user experience remains positive even when errors occur, security is maintained by not leaking sensitive information, and systems continue operating or degrade gracefully when non-critical services fa

Help and documentation for Idea to MVP plugin.Use when: user asks about building MVPs, vibe coding, or available commands.Triggers: "help", "what can you do", "mvp help", "how to build".

Guided workflow for creating new Claude Code Skills with proper structure, documentation, templates, subagents, and hooks. Use this when the user wants to create a new skill or asks you to build tooling/automation. Ensures skills follow official conventions and are production-ready.

PRISMA-compliant manuscript drafting for systematic reviews