Skill UI

This skill addresses the common problem of documentation decay in long-lived software projects. It establishes a canonical governance layer by assigning four non-overlapping roles—Constitution, Map, Status, and History—to existing documentation. By linking these roles to the active agent harness, it prevents documentation drift, ensuring that all project information remains accurate, authoritative, and contextually linked to the current codebase, making it ideal for the maintenance phase.

Reviews GitHub pull requests in the googleapis/mcp-toolbox repo against the team's reviewer checklist: title conventions, linked issues, logic errors, edge cases, breaking changes, tests, docs, security, and new dependencies, then proposes a paste-ready verdict for the maintainer.

Reviews a pull request and posts one consolidated GitHub review with inline comments via the gh CLI. Runs the repo's own checks first, verifies external claims against official docs, then reports correctness, security, and structural findings—each backed by evidence and gated for noise.

Run a read-only audit to detect documentation drift against code, APIs, and configurations. Identifies stale, missing, or inconsistent docs across READMEs, API docs, and user guides. Compares documentation claims with actual implementation to ensure accuracy without modifying files.

Master API documentation with OpenAPI 3.1, AI-powered tools, and modern developer experience practices. Create interactive docs, generate SDKs, and build comprehensive developer portals.

This skill interviews users to extract project vision, decisions, and preferences into durable documentation like README and ADRs. It follows a structured loop: checking existing docs, asking varied questions, and updating documents after every answer. The goal is to save user judgment and knowledge into clear markdown files. It ensures consistency and captures the project's core identity through back-and-forth interaction.

Orchestrates maintenance workflows for the brooks-lint plugin, running a sequential subagent pipeline (author, eval, QA, trigger-audit, release) to add or edit skills, refresh eval suites, keep manifests and docs in sync, and audit trigger boundaries. Ensures quality gates and consistency across the repository.

Automates Coda document and data workflows through Rube MCP/Composio, covering searches, tables, formulas, exports, permissions, sharing, and publishing so bots can manage docs without manual API fiddling.

This skill specializes in creating comprehensive and maintainable documentation directly from codebases. It generates API docs, architecture diagrams, user guides, and technical references using AI analysis. Ideal for building documentation pipelines, standardizing docs across repositories, and ensuring living documentation stays synchronized with code changes while adhering to industry best practices.

Automatically fetch latest library/framework documentation for Claude Code via Context7 API. Use for up-to-date docs on React, Next.js, Prisma, or any popular library.

Generate professional, ATS-optimized CVs for FlowCV, Canva, Google Docs, or Word. Handles multi-source merging, JD targeting, seniority adaptation, and humanized rewriting. Outputs paste-ready text with an ATS flaw report and improvement suggestions.

Use the DBX CLI to inspect DBX-managed database connections, explore schemas, run bounded read-only queries, generate DBML or schema docs, and open tables in DBX Desktop. Includes strict safety gates for writes and DDL.