documents▌

Generates and validates technical documentation across docstrings, API specs, and developer guides. \n \n Supports multiple docstring formats (Google, NumPy, Sphinx for Python; JSDoc for TypeScript) and API specification standards (OpenAPI, AsyncAPI, gRPC) \n Includes validation workflows for each format: doctest/pytest for Python, TypeScript compilation checks, and Redocly linting for OpenAPI specs \n Covers inline code documentation, interactive API portals, documentation site generation, and

Create, edit, analyze, and redline Word documents with full format and tracked-change support. \n \n Three distinct workflows: text extraction via pandoc, document creation using docx-js, and editing via the Python Document library with OOXML manipulation \n Redlining workflow for tracked changes with batching strategy, minimal-edit principles, and comprehensive verification to ensure professional document review \n Raw XML access for comments, complex formatting, embedded media, and metadata th

Read, write, and manage comments in Feishu documents with markdown support and block-level operations. \n \n Supports full document lifecycle: read plain text, write/append markdown content, create new documents, and manage individual blocks (get, update, delete) \n Comment operations include listing document and block-level comments, retrieving single comments, and creating global comments with pagination support \n Structured content (tables, images, code blocks) accessible via list_blocks act

Document conversion, extraction, OCR, redaction, signing, and form-filling via the Nutrient DWS API. \n \n Converts between 15+ formats including PDF, DOCX, XLSX, PPTX, HTML, and images (JPG, PNG, TIFF, WebP, SVG, and more) \n Extracts plain text and tables from documents; OCR supports 100+ languages for scanned PDFs and images \n Redacts PII using preset patterns (SSN, email, credit card, phone, date, URL, IP, MAC address, ZIP code, VIN) or custom regex \n Adds watermarks, applies digital CMS s

Automatically regenerates marketplace documentation files from Jinja2 templates and catalog data. \n \n Generates four synchronized documentation files (agents.md, agent-skills.md, plugins.md, usage.md) by reading marketplace.json and plugin metadata \n Provides Python script with command-line options for full generation, selective file output, dry-run mode, and custom path configuration \n Includes pre-built Jinja2 templates with access to comprehensive context: plugins organized by category, i

Share a Google Doc with collaborators and send them notification emails. \n \n Combines three Google Workspace skills (Drive, Docs, Gmail) to locate documents, grant editor access, and notify recipients in sequence \n Automates the workflow of finding docs by name, adding collaborators with write permissions, and emailing them the share link \n Requires gws-drive , gws-docs , and gws-gmail skills to be loaded before execution \n

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

Complete workflow for adding documentation for a new AI provider.

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