Skill UI

A comprehensive three-column layout template designed for high-readability technical documentation, such as API references, tutorials, and guides. It features a sticky side navigation, main article body with support for code blocks and callouts, and a scroll-spy Table of Contents (TOC). Includes search and version control.

An interactive skill designed to interview users to capture project vision, core decisions, and technical preferences. It systematically converts raw discussions into structured documentation, maintaining the project's history in ADRs (Architectural Decision Records) and its overarching goal in the README.

Automatically generates comprehensive API documentation from existing TypeScript or JavaScript source code. It scans public exports, parses detailed JSDoc annotations (including parameters, returns, and throws), and can generate standardized OpenAPI 3.0 specifications for HTTP endpoints, ensuring robust and up-to-date API references.

This skill guides the operation, consolidation, and maintenance of complex working systems within Google Workspace (Docs, Sheets, Slides). It emphasizes treating files as integrated systems—such as trackers or planning hubs—requiring careful inspection, precise edits, and structural cleanup rather than simple content rewriting. Use it for consolidating scattered data, cleaning shared spreadsheets, or ensuring the correct canonical version of a document is utilized.

Reconcile code, docs, rules, memory, and workspace residue so the next session starts from one current source of truth. Best for project handoff, stale documentation, and closing out knowledge drift.

This skill converts Microsoft Word documents (.docx) into Markdown format. It is essential for accurately analyzing, summarizing, or extracting data from proprietary Word files, as direct parsing is unreliable. It supports single files, batch processing of folders, and is designed to coordinate with sibling skills (PDF and Excel) when handling mixed document types to ensure no data is skipped.

Creates task-oriented technical documentation with progressive disclosure for READMEs, API docs, architecture docs, and markdown. Also generates formal security reports (reverse engineering, penetration testing, CTF, malware/APT analysis) in the user's project directory with Evidence-Finding-Path chain.

Converts books, documentation folders, and source collections (PDF, EPUB, DOCX, HTML, Markdown, RST, etc.) into structured agent skills. Extracts named frameworks, principles, techniques, and anti-patterns into a master SKILL.md plus chapter files, glossary, patterns, and a decision cheatsheet. Ideal for turning internal docs or standards into reusable knowledge bases or packaging compiled skills as plugins.

Captures a short user pitch, then drafts a product overview (PRD.md) and technical design (ARCHITECTURE.md) for a third-party .ppmplugin native control. Walks through every operation's iOS and Android implementation strategy with opinionated recommendations and iterates with the user until approval. The resulting docs serve as the source of truth for downstream code-generation skills.

This skill helps legal professionals set up a personalized, structured Legal Guidance Vault. It guides the user through an interview of their entire digital tool stack (email, calendar, docs, etc.) to ensure all sources are covered. It generates a standardized, reusable prompt template for archiving privileged legal advice, making it searchable by topic, person, or product in future sessions.

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.