Discover tools technical docs skills, compare source repositories and read the instructions for each workflow.
Creates or updates README.md files following GitHub best practices with badges, visual hierarchy, and comprehensive documentation. Use when asked to "create a README", "generate documentation", "write a README...
Only provide concepts and documentation
Guide for developing the API service using Python, FastAPI, Pydantic, and Docker. Use this when creating or modifying API endpoints, models, routers, or backend logic.
Guidelines and templates for creating and updating repository documentation following the LLM Documentation Protocol. Use when adding or modifying workflow or file docs, updating `docs/INDEX.md`, or reviewing P...
Comprehensive guide for writing technical documentation
Run GPT-5.2 Codex (gpt-5.2-codex high) via OpenAI Codex CLI to review code for bugs, issues, and architecture problems. Use when the user wants a second opinion on code, requests a code review from an external...
Provides guidance and explanations on Python code structure, organization, and architectural patterns tailored for students and beginners.
This skill manages all documentation for the Synapse A2A project. It should be used when code changes require documentation updates, when checking documentation consistency, or when manually invoked via /synaps...
Guide user through support platform setup. Use when user says "set up", "configure", "I'm on step X", or provides API keys/credentials.
Annotation and documentation protocol for rapid-iteration projects (“vibe coding”). Enforces Google Docstring Style plus comment-as-contract: consistency with signatures/types, explicit pre/post-conditions, uni...
Review, create, or update docs/manual.md with user documentation for the product
Review, create, or update README.md to match organizational standards with accurate project-specific content
Review, create, or update docs/architecture.md to match organizational standards with accurate technical content
Generate code documentation, API docs, and technical guides. Use when documenting code, creating API documentation, writing technical specs, or when the user mentions "document", "docs", "README", "API docs", "...
Generate code documentation, API docs, and technical guides. Use when documenting code, creating API documentation, writing technical specs, or when the user mentions "document", "docs", "README", "API docs", "...
Produce a feature/component documentation that adheres to repo standards.
Create and improve product documentation for Viya TMS. Supports user guides, feature docs, API references, and release notes with consistent style and structure.
Writing clear, user-facing documentation for non-technical users. Use when creating in-app docs, help content, or feature documentation.
Update documentation after code changes. Use when API endpoints, database schema, backend/frontend structure, or block definitions have been modified.
Auto-generate structured dev journal entries from conversation context. Triggers on "dev journal", "generate journal", "journal this session", "log this session", or end-of-session journaling requests. Scans th...
Require comprehensive WHY/WHEN/HOW documentation for all functions. Apply when writing functions, classes, or complex logic to explain purpose, usage context, and implementation approach.
Searching internet for technical documentation using llms.txt standard, GitHub repositories via Repomix, and parallel exploration. Use when user needs: (1) Latest documentation for libraries/frameworks, (2) Doc...
Use this agent when researching external best practices, documentation, and examples for any technology, framework, or development practice. Specializes in gathering information from official documentation, com...
Use this agent when needing to gather comprehensive documentation and best practices for specific frameworks, libraries, or dependencies in a project. Specializes in fetching official documentation, exploring s...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.