Loading...
Loading...
Found 38 Skills
Python code style, linting, formatting, naming conventions, and documentation standards. Use when writing new code, reviewing style, configuring linters, writing docstrings, or establishing project standards.
Write, fix, and standardize Python docstrings in Google style. Use whenever the user asks to add or improve docstrings, convert mixed docstrings to Google format, add missing Args/Returns/Raises/Attributes/Example sections, or make docstrings concise and API-focused.
Use when adding docstrings, creating API documentation, or building documentation sites. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, tutorials, user guides.
Guidelines for self-explanatory code and meaningful documentation. Activate when working with comments, docstrings, documentation, code clarity, API documentation, JSDoc, or discussing code commenting strategies. Guides on why over what, anti-patterns, decision frameworks, and language-specific examples.
Register and implement PydanticAI tools with proper context handling, type annotations, and docstrings. Use when adding tool capabilities to agents, implementing function calling, or creating agent actions.
Detect AI-generated writing patterns in developer text — docs, docstrings, commit messages, PR descriptions, and code comments. Use when reviewing any text artifact for authenticity and clarity.
Audits and enhances API documentation for FastAPI and REST endpoints. Identifies missing descriptions, incomplete response codes, missing examples, and generates enhanced docstrings, Pydantic model examples, and OpenAPI spec improvements. Triggers on: "generate API docs", "document this API", "OpenAPI for", "add examples to", "improve docstrings", "API documentation audit", "FastAPI docs", "document endpoints", "API reference", "swagger docs", "REST API docs", "endpoint documentation", "response documentation". Use this skill when API endpoints need documentation or documentation audit.
Comprehensive Python programming guidelines based on Google's Python Style Guide. Use when you needs to write Python code, review Python code for style issues, refactor Python code, or provide Python programming guidance. Covers language rules (imports, exceptions, type annotations), style rules (naming conventions, formatting, docstrings), and best practices for clean, maintainable Python code.
Write comprehensive code documentation including JSDoc, Python docstrings, inline comments, function documentation, and API comments. Use when documenting code, writing docstrings, or creating inline documentation.
Expert at writing high-quality documentation for code, APIs, and projects. Auto-invokes when generating docstrings, creating README files, writing API documentation, adding code comments, or producing any technical documentation. Provides language-specific templates and best practices for effective documentation writing.
Use this skill when working with the mcp-skill CLI to create generated MCP app wrappers, list available generated apps, list functions for a specific app, inspect a generated function signature and docstring, or understand how to call generated apps from async Python.
Analyzes code comments for accuracy, completeness, and long-term maintainability. Identifies misleading comments, comment rot, and documentation gaps. Triggers: After adding documentation, before finalizing a PR, when reviewing comments. Examples: - "Check if the comments are accurate" -> verifies comments match code behavior - "Review the documentation I added" -> analyzes new comments for quality - "Analyze comments for technical debt" -> finds outdated or misleading comments - "Are my docstrings correct?" -> validates documentation accuracy