2.5K skills · sorted by relevance
Maintain Composio's documentation site and record documentation decisions. Work on content, Fumadocs configuration, changelogs, automation prompts, and review guidance, including ADR-style records that capture decisions and their rationale.
Translate an English MkDocs documentation set into a chosen language while preserving folder structure and Markdown formatting. Update shared content references, navigation labels, notice labels, and language configuration, and check that every source file has been translated.
Automate Docsumo operations through Rube MCP, a connection for agent tools. The skill discovers available actions, checks account connectivity, and uses current input requirements to execute supported tasks through Composio.
Read, create, and revise Google Docs through a dedicated command-line tool. For formatted documents, prepare a styled Word file, upload it to Google Docs, and check the resulting content and formatting.
Write, revise, and review beads user documentation using consistent terminology, explanations, diagrams, and navigation. Follow project rules for generated pages and release alignment, with checks for links, freshness, and documentation consistency.
Automate Docsumo operations through Rube MCP, a connection for agent tools. The skill discovers available actions, checks account connectivity, and uses current input requirements to execute supported tasks through Composio.
Review, improve, rewrite, or draft Storybook documentation in /docs. Assess each page’s purpose, audience, structure, and examples, then make suitable edits or provide a content plan, with formatting checks after changes.
Run Algodocs operations through Rube MCP, a connection for agent tools. The skill discovers available actions, checks authentication status, and uses the required input fields to execute tasks or organize bulk operations.
Create editable documents for sharing and comments, including reports, proposals, resumes, and guides. Use the docs connector to prepare documents that can be exported to Word, PDF, Markdown, or Google Docs.
Run Algodocs operations through Rube MCP, a connection for agent tools. The skill discovers available actions, checks authentication status, and uses the required input fields to execute tasks or organize bulk operations.
Review recent Git commits to find changes that affect users, then update the relevant documentation pages. Identify missing pages, explain changed behavior or migration steps, and validate the resulting documentation with the project's build tools.
MkDocs documentation project reference covering CLI commands, mkdocs.yml configuration, Material theme setup, and plugin integration. Bundled references include complete CLI parameters, all mkdocs.yml settings with valid values, Material theme customization options, and plugin configs for mkdocstrings, mermaid2, mkdocs-gen-files, mkdocs-literate-nav, and mkdocs-typer2. Use when initializing a MkDocs site, configuring mkdocs.yml, customizing the Material theme, integrating plugins, building static docs from Markdown, or generating API documentation from Python docstrings.
The English summary is being prepared. Showing the original description.
Run Docsbot AI operations through Rube MCP, a connection for agent tools. The skill provides a workflow for discovering supported actions, verifying an active connection, and executing operations with current tool inputs, including bulk processing guidance.
Run Docsbot AI operations through Rube MCP, a connection for agent tools. The skill provides a workflow for discovering supported actions, verifying an active connection, and executing operations with current tool inputs, including bulk processing guidance.
Generate and maintain AI-readable markdown documentation for a codebase in docs/. Use this skill whenever the user asks to document their codebase, generate project docs, create architecture docs, update documentation after code changes, build a knowledge base for AI agents, create onboarding docs, map out a codebase, or explain a project structure. Also trigger when users say things like "document this repo", "create docs for my project", "update the docs", "write architecture documentation", "help AI understand my code", "generate a codebase overview", or "maintain docs". This skill is specifically about creating structured markdown files in a docs/ directory that serve as a knowledge base — NOT about writing inline code comments, README files, or API reference docs from docstrings.
The English summary is being prepared. Showing the original description.
Regenerate and commit Class S site-served artifacts after registry changes, then sync documentation across the main repo and the adjacent wiki. Use this skill when: you've changed registry/nodes/, registry/named/, or named-skills.json and need to regenerate docs/graph/* so the live website reflects the update; CI Guard E (docs-cohesion.yml) is failing because Class S artifacts are out of date; someone says "sync the docs", "regenerate docs", "run gaia dev docs", "update the site graph", "commit the Class S artifacts", "website is stale", or "update the wiki"; or you're finishing a registry PR and need to ensure docs/graph/gaia.json, docs/graph/gaia.gexf, docs/graph/gaia.svg, and docs/graph/named/index.json are committed alongside the source change. Also covers updating README.md, docs/index.html, and mirroring changes to the adjacent wiki repo at ../gaia-wiki.
The English summary is being prepared. Showing the original description.
Comprehensive guide for building, configuring, customizing, and deploying Docsify documentation sites. Use when the user wants to (1) initialize a new Docsify site, (2) add or organize Markdown pages, sidebars, navbars, or cover pages, (3) configure `window.$docsify` options, (4) customize themes / CSS variables / fonts, (5) install built-in or third-party Docsify plugins (search, GA, emoji, zoom, copy-code, comments, pagination, tabs, etc.), (6) write a custom Docsify plugin using lifecycle hooks, (7) use Docsify Markdown helpers (callouts, link attributes, image attributes, heading IDs, task lists, embed files with `:include`), (8) deploy to GitHub Pages, GitLab Pages, Netlify, Vercel, Firebase, Docker, Nginx, etc., (9) enable PWA / offline mode, virtual routes, or Vue compatibility, or (10) upgrade a Docsify site from v4 to v5. Triggers on mentions of "docsify", "_sidebar.md", "_navbar.md", "_coverpage.md", "$docsify", or `docsify-cli`.
The English summary is being prepared. Showing the original description.
Write, restructure, or review documentation — tutorials, how-to guides, reference pages, concept/explanation docs, API references, READMEs, changelogs, release notes, and troubleshooting guides. Distills documentation craft from Mintlify's guides (compiled from technical writers at Stripe, GitHub, Amplitude, and Anaconda), the Diátaxis framework (including the compass and per-type voice), the Google and Microsoft style guides, Every Page Is Page One, Write the Docs, and Docs for Developers: audience analysis, content-type selection, style and word-level rules, procedure writing, structure for humans and AI agents, code-example standards, page templates (templates.md), mechanical enforcement and llms.txt (mechanics.md), maintenance, and success metrics. Use this skill when the user asks to "write docs", "document this feature", "improve this page", "review these docs", "write a tutorial / how-to / reference page", "structure the docs", "write API documentation", "write a README / changelog", or when authoring any file under a `docs/` tree. For SKMTC docs specifically, this skill governs the *craft* (what makes the page good); the content split between skills, `llms.md`, and the docs tree is governed by `docs/skills/README.md`. Distinct from `skmtc-retro` (captures observations about work) and the `skmtc-*` operational skills (guide doing the work) — this skill guides writing *about* the work for readers.
The English summary is being prepared. Showing the original description.
List the files in a Google Drive folder and download them individually. The workflow also covers exporting Google Docs as PDF files for a local copy of the documents.
Read and update Google Docs through gws commands. Create blank documents, retrieve the latest version, append text, or apply multiple updates together, using command help and schema information to check the required inputs.
Review local code changes with git diff and update the matching pages under docs/. Keep commands, settings, examples, and navigation aligned with current behavior so readers can understand the changes without reading the code.
Create and edit Google Docs while preserving requested structure, formatting, tabs, and tables. Adapt templates using current source information, update links and smart chips, and check that the finished document covers the requested content.
Use when a project has no docs/ directory or needs initial documentation generated from codebase analysis. Triggers on "init docs", "create documentation", "generate docs", "docs init", or when docs/ is empty. Do NOT use for updating existing docs (use mk:document-release).
The English summary is being prepared. Showing the original description.
Create and revise shared documents in Claude Docs, where people and Claude can edit together. The skill guides document creation, targeted changes, and comment replies through the connector, with updates appearing live to readers.