docs▌

Query OpenAI's official developer documentation via MCP server for API, SDK, and platform guidance. \n \n Search and fetch docs on OpenAI APIs (Chat Completions, Realtime, Responses), SDKs, ChatGPT Apps, Codex, and migrations using a CLI wrapper around the OpenAI Docs MCP server \n Includes subcommands for discovery ( search , list ), retrieval ( fetch ), and schema inspection ( endpoints , openapi ) \n Supports optional anchors for fetching specific doc sections and code sample generation in mu

XML documentation standards and patterns for C# public APIs and members. \n \n Use <summary> for one-sentence descriptions starting with a present-tense verb, and <remarks> for implementation details, usage notes, or additional context \n Employ specific tags for different member types: <param> and <returns> for methods, <value> for properties, <typeparam> for generics, and <exception cref> for thrown exceptions \n Follow prescribed wording patterns for Boolean

Automatically capture solved problems as searchable documentation with category-based organization and YAML validation. \n \n Auto-triggers after confirmation phrases like \"that worked\" or \"it's fixed\"; documents non-trivial problems with investigation history, root cause, and prevention guidance \n Enforces strict YAML frontmatter validation against enum-defined problem types and severity levels before file creation \n Organizes solutions into category directories (e.g., docs/solutions/perf

Fetch up-to-date Railway documentation to answer questions accurately.

Guided workflow for updating Next.js documentation based on code changes and PR reviews. \n \n Analyzes git diffs to identify affected documentation files using a code-to-docs mapping reference \n Provides templates and conventions for scaffolding new feature docs (components, functions, config, guides, file conventions) \n Walks through step-by-step updates to existing documentation with user confirmation before each change \n Includes validation checklist and linting commands to ensure formatt

Read and write Google Docs through the Google Workspace API. \n \n Supports three core operations: create (new blank documents), get (retrieve document content), and batchUpdate (apply multiple validated updates in a single request) \n Uses a schema-driven CLI with gws schema inspection to discover required parameters, types, and defaults before executing commands \n Requires Google Workspace authentication and shared security rules documented in gws-shared/SKILL.md \n Includes a helper command

Category: test

Automates the process of keeping project documentation synchronized with codebase changes. This skill analyzes git differences between the current working branch and the last released version, then intelligently updates relevant documentation files.

Browse a running web app, screenshot every screen, and produce documentation good enough to publish. Not a screenshot dump — a structured guide that teaches someone how to use the app.

✅ Use this skill when: