Results for “docs”

Retrieve up-to-date library, framework, and project documentation using scripts + MCP tools (Context7, Context Hub) with intelligent fallback. Use this skill whenever the user or agent needs documentation for any library, framework, API, SDK, or internal project spec. Triggers on "docs for [X]", "how does [library] work", "find documentation", "API reference for", "look up [feature] in [library]", "latest docs", "what's the API for", "find our [internal spec]", or any request that requires current, accurate documentation rather than relying on training data. Always prefer this skill over raw WebSearch for documentation retrieval — it returns structured, context-efficient results.

The English summary is being prepared. Showing the original description.

docs (editable docs people share and comment on; the default for any document, named as a doc or not: a document, report, proposal, resume, cover letter, letter, contract, policy, form, template, worksheet, essay, handbook, guide, how-to, cheat sheet, SOP or other writing to keep, share, collaborate on, send, submit, print or sign; a doc exports to Word, PDF, Markdown or Google Docs, so needing a file to send, attach, upload, submit or print is no reason to pick Word, and a file nobody asked for is a doc, not Word; a plan, comparison, summary or notes asked in chat stays in chat; a pasted claude.ai artifact link may be a doc: check with docs tools first; Word or another file format named, tracked changes wanted, or a .docx to change or use as a template → that format's skill): making one → if no docs-connector instructions are in context, call its `guide` (topic.instructions) first; then create the doc (headings only, no body) before any search, file read or plan, even with files attached.

The English summary is being prepared. Showing the original description.

The procedure for every doc change in common-docs or a repo's CLAUDE.md, FEATURE.md or SKILL.md. Use when creating, editing, moving or deleting a doc, finding duplicate or disagreeing docs, planting a repo pointer, consolidating a node, or on /docs and the daily docs-steward run.

The English summary is being prepared. Showing the original description.

Manage Google Workspace tasks through a command-line tool. Search and send Gmail messages, manage Calendar events, find Drive files, list contacts, update Sheets data, and read or export Docs.

• Searching recent emails and drafting replies
• Creating or updating calendar events
• Finding files and listing contacts

Find, inspect, summarize, and update documents, spreadsheets, and presentations across Google Drive, Docs, Sheets, and Slides. Consolidate plans and trackers, clean shared files, and identify duplicates or outdated materials within a connected workflow.

• Finding and condensing the current planning document
• Cleaning and restructuring a shared customer spreadsheet
• Importing and tidying a presentation in Google Slides

Create and edit Remotion documentation with consistent API pages, code examples, version labels, and compatibility information. The skill also guides sidebar placement and preview card generation when adding or updating pages.

• Add a documentation page for a public API
• Standardize code examples and parameter descriptions
• Review version labels and compatibility information

Add browser WebCodecs bugs to the Remotion Mediabunny documentation. It checks the linked issue’s title, filing date, reporter, and resolution, then adds a table row while preserving the existing format.

• Adding a Chromium bug to the documentation
• Recording WebKit or Firefox issues
• Checking reporter details and fix status before adding a row

Maintain Cherry Studio documentation by checking it against source code, placing facts in appropriate files, and removing duplication. Review documentation affected by code changes and keep relevant English and Chinese counterparts aligned.

• Organizing READMEs and reference documentation
• Reviewing documentation affected by code changes
• Checking comments and agent instructions against code

Write or revise system architecture documents, design decision records, and engineering references. Use concrete examples and clear explanations of design choices to make documents useful both to newcomers and to developers needing precise details.

• Documenting how a subsystem works
• Rewriting design documents for new team members
• Explaining architecture decisions within the document

Find a Gmail message and save its body in a Google Doc, together with the sender and subject. Use it to archive important correspondence or keep an email available as a reference document.

• Archiving important emails as documents
• Saving messages with sender and subject details
• Keeping email content for later reference

Set brand styling from a website link or a plain-language description, preview it on a sample page, and save preferred delivery formats so future plugin pages and documents follow the chosen look and format.

• Set brand styling from a website link
• Update colors and logos after rebranding
• Preview report styling before saving

Audits Mastra documentation against repository source and canonical writing guidance. Checks examples in context, API reference coverage, and targeted automated results, then produces an evidence-based report with findings and limitations without editing files.

• Auditing every changed documentation page in a pull request
• Checking code examples against source and surrounding explanations
• Finding missing or incorrect API reference details

Draft responses to requests for proposals and sales questionnaires using approved past answers and product documentation. Organize answers in Google Docs, flag uncertain questions, and prepare an unsent Gmail reply for human review and submission.

• Preparing a first draft of a sales proposal questionnaire
• Reusing approved answers about pricing and support
• Identifying questions that need human review

Review a new contract against standard company positions, summarize its terms, and flag deviations clause by clause. Draft replacement wording as Docs suggestions and share a legal summary in Slack, with every proposed change awaiting a lawyer's approval.

• Preparing an initial review of a newly received contract
• Checking liability, renewal, payment, and other standard terms
• Drafting clause replacements for a lawyer to review

Review newly added comments, docstrings, and changelog entries so future readers can understand the current code. Revise development history, redundant explanations, and unclear shorthand while preserving constraints that the code cannot explain on its own.

• Review comments before committing
• Check prose added across a branch
• Clarify function documentation for future readers

Update documentation to match source changes on the current branch. Map changed files to existing pages, verify behavior against the code, revise affected references and examples, and report missing documentation using repository-specific mapping rules.

• Updating API documentation after code changes
• Fixing guides and examples affected by renamed parameters
• Finding missing documentation pages or sections

Create and maintain code comments, API specifications, documentation sites, and user guides. Apply consistent formats, document parameters and errors, validate code examples, and report which parts of the code have been documented.

• Add explanations to public functions and classes
• Create API specifications and reference pages
• Build a documentation site

Automate Google Workspace tasks through a command-line tool: read email, calendars, files, documents, and spreadsheet data, or make requested updates. Inspect authentication, return structured JSON data, and restrict allowed operations for agent workflows.

• Retrieve email, calendar, and file information
• Update Google Docs and Google Sheets
• Check authentication and diagnose access problems

Guide visual changes to an existing documentation site and landing page. Apply defined limits for text width, spacing, navigation, and color so layout updates preserve readable content and a consistent visual style.

• Adjusting documentation page width and spacing
• Choosing where to place a new navigation link
• Updating landing page colors and typography

Find and fix the docs and agent guidance that a branch makes stale - agent skills and their reference files, AGENTS.md and .agents/*.md prompts, READMEs, docs/ folders, and code-adjacent docs that name a changed path, command, symbol, env var, setting, endpoint or behaviour. Use before opening a PR, before pushing new commits to an open PR, and when asked to update docs or skills after a change. The open-pr skill runs it every time.

The English summary is being prepared. Showing the original description.

Audit the developer experience of a product, SDK, docs site, or SKILL.md by dropping multiple Claude subagents at it with only a tiny task prompt and real tools (WebFetch, Bash, Write). Agents must discover the docs themselves, install deps, ask for credentials if needed, and attempt real execution. The skill captures each agent's trace — tool calls, retries, wall time, errors — and scores on Setup Friction, Speed, Efficiency, Error Recovery, and Doc Quality, then emits an HTML report with an A–F grade and concrete fixes. Use when the user asks to audit agent experience, test a skill, audit docs for agents, check if a SDK is agent-friendly, validate a SKILL.md, measure agent DX, or benchmark how painful onboarding is for an AI agent. Triggers: 'audit agent experience', 'test this skill', 'audit docs for agents', 'is my SDK agent-friendly', 'run a DX audit', 'agent experience test', 'test my docs', 'how do agents do with my product'.

The English summary is being prepared. Showing the original description.

SUPERSEDED by /claudex-loop (formerly /crucible; its docs-aware mode covers this variant) — prefer that skill unless you explicitly want this one. Two-act plan hardening with living documentation. ACT 1 (you ↔ Claude) — Claude interviews you relentlessly about a plan, one question at a time, challenging it against your project's existing domain model and glossary (CONTEXT.md), sharpening fuzzy terms, stress-testing with concrete scenarios, cross-referencing code, and updating CONTEXT.md + ADRs inline as decisions crystallise. ACT 2 (Claude ↔ Codex) — Claude writes the locked plan to PLAN.md and OpenAI Codex adversarially reviews it in a read-only sandbox (VERDICT:APPROVED/REVISE), Claude revises and re-submits to the SAME Codex session until APPROVED or a MAX_ROUNDS cap, then you sign off before any code. Use when the user says "/grill-with-docs-codex", "grill me against the docs then have codex review", "stress-test this against our domain model then get a second model on it", or is about to build something high-stakes in a project with established terminology/ADRs and wants alignment, documentation, AND a cross-model sanity check. Builds on Matt Pocock's grill-with-docs (MIT). NOT for reviewing already-written code (use /codex:review) and NOT for trivial changes.

The English summary is being prepared. Showing the original description.

House style for user-facing documentation — voice, scope, structure, and what to leave out. Use this skill whenever writing, editing, or reviewing anything a user reads to learn how to use a tool — help center articles, getting-started guides, tutorials, feature docs, README usage sections, in-app help, release notes, or FAQ entries. Trigger it even when the request is phrased plainly — "document this feature", "write docs for X", "explain this to users", "write a README for this library", "turn these notes into a guide" — and even when no style guidelines are mentioned. Also use it to review existing docs for tone, bloat, or leaked implementation detail. Do not use it for internal engineering docs, architecture write-ups, RFCs, or code comments.

The English summary is being prepared. Showing the original description.

Generate project documentation from codebase analysis — ARCHITECTURE.md, API_ENDPOINTS.md, DATABASE_SCHEMA.md. Reads source code, schema files, routes, and config to produce accurate, structured docs. Use when starting a project, onboarding contributors, or when docs are missing or stale. Triggers: 'generate docs', 'document architecture', 'create api docs', 'document schema', 'project documentation', 'write architecture doc'.

The English summary is being prepared. Showing the original description.