Comments
Code comments and annotations
xiaohongshu-mcp
by tclawde
Xiaohongshu MCP Skill - Full automation solution with login fix. Features: (1) Login management, (2) Search, publish, interact, (3) Complete MCP protocol support (13 tools), (4) Comment strategy. Built-in Feishu notification, iflow integration. Triggers: xiaohongshu, rednote, 小红书 automation.
by AutumnsGrove
"Comprehensive PDF manipulation, extraction, and generation with support for text extraction, form filling, merging, splitting, annotations, and creation. Use when working with .pdf files for: (1) Extracting text and tables, (2) Filling PDF forms, (3) Merging/splitting PDFs, (4) Creating PDFs programmatically, (5) Adding watermarks/annotations, (6) PDF metadata management"
query-optimizer
by CuriousLearner
Analyze and optimize SQL queries for better performance and efficiency.
documentation-generator
by CuriousLearner
Auto-generate JSDoc, docstrings, README files, and API documentation.
documenting-library-guides
by MrPointer
Create user-facing documentation for libraries — the kind of docs you'd find on a static documentation site. Guides readers through the library with an engaging, conversational tone, real code examples drawn from the actual codebase, and a navigable site-like structure. Use when (1) a library has no user-facing docs beyond inline code comments, (2) existing docs are API references with no narrative guidance, (3) users need task-oriented guides to accomplish common goals, or (4) a library's docs need restructuring into a browsable, site-ready format.
reddit-community-builder
by aibangjuxin
You are a genuine and strategic Reddit Community Builder. You understand that Reddit is not a place for traditional marketing. You are an expert at providing value, fostering discussions, and building trust within niche subreddit communities. You know the rules (both written and unwritten) of different subreddits and respect their culture.
support-responder
by aibangjuxin
You are a patient, empathetic, and knowledgeable Support Responder. You are an expert on the product and can clearly explain complex features in simple terms. Your primary goal is to solve the customer's problem quickly and leave them feeling heard, valued, and satisfied.
jira-comment
by MichaelVessia
Comment on a Jira ticket on Michael's behalf, clearly attributed as AI-generated. Use when asked to leave a comment or reply on Jira.
gh-comment
by MichaelVessia
Comment on a GitHub PR or issue on Michael's behalf, clearly attributed as AI-generated. Use when asked to leave a comment, reply, or respond on GitHub.
documenting-architecture
by MrPointer
Document system architecture, design decisions, layer boundaries, and how components connect and communicate. Use when (1) a project's architecture is undocumented, (2) agents can't figure out how the system fits together, (3) after major refactoring that changed system structure, or (4) onboarding developers who need to understand the big picture. References domain concepts — never redefines them.
python-types-contracts
by ahgraber
Use when defining or evolving public interfaces, schema boundaries, or pydantic usage in Python. Also use when annotations are missing on public APIs, pydantic models appear everywhere instead of at trust boundaries, contract changes lack migration guidance, or Any/object types are overused across module boundaries.
documentation-templates
by benshapyro
Generates README files, API documentation, and inline code comments following best practices. Use when creating project documentation, writing READMEs, documenting APIs, or explaining complex code.
failure-taxonomy
by maragudk
Build a structured taxonomy of failure modes from open-coded trace annotations. Use this skill whenever the user has freeform annotations from reviewing LLM traces and wants to cluster them into a coherent, non-overlapping set of binary failure categories (axial coding). Also use when the user mentions "failure modes", "error taxonomy", "axial coding", "cluster annotations", "categorize errors", "failure analysis", or wants to go from raw observation notes to structured evaluation criteria. This skill covers the full pipeline: grouping open codes, defining failure modes, re-labeling traces, and quantifying error rates.
mail-contacts
by aashari
Extract contacts and build a communication directory from email history. Find email addresses, frequency of contact, and relationship strength. Use when user wants to find someone's email address, see all contacts, or understand their communication network. Arguments: optional person name, company, domain, or "top contacts" / "recent contacts".
coding-conventions
by richfrem
Coding conventions and documentation standards across Python, TypeScript/JavaScript, and C#/.NET codebases. Use when: (1) writing new code files or functions, (2) reviewing code for style and documentation compliance, (3) adding file headers or docstrings, (4) creating new tools that need inventory registration, (5) refactoring code that exceeds complexity thresholds, (6) setting up module structure. Covers file headers, function documentation, naming conventions, and tool inventory integration.
mapkit
by ios-agent
"Help developers integrate Apple MapKit into iOS/macOS apps. Use this skill when users ask to add a map to their app, display maps, show user location on a map, add markers/pins/annotations, implement map clustering, get directions/routing between locations, search for places/points of interest, implement MapKit features, work with MKMapView, SwiftUI Map, MKAnnotation, MKOverlay, MKDirections, MKLocalSearch, or any MapKit-related development task."
Schema
by andrueandersoncs
This skill should be used when the user asks about "Effect Schema", "Schema.Struct", "Schema.decodeUnknown", "data validation", "parsing", "Schema.transform", "Schema filters", "Schema annotations", "JSON Schema", "Schema.Class", "Schema branded types", "encoding", "decoding", "Schema.parseJson", or needs to understand how Effect handles data validation and transformation.
inline-documentation
by troykelly
Use when writing code - ensure complete JSDoc, docstrings, and inline comments assuming documentation will be generated from code
code-documentation
by ilude
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.
gene-database
by hxk622
Query NCBI Gene via E-utilities/Datasets API. Search by symbol/ID, retrieve gene info (RefSeqs, GO, locations, phenotypes), batch lookups, for gene annotation and functional analysis.
anndata
by hxk622
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
development-philosophy
by ilude
Personal development philosophy emphasizing experiment-driven, fail-fast approach. Activate when planning implementations, reviewing code architecture, making design decisions, or when user asks to apply development principles. Guides against over-engineering and towards solving real problems with simple solutions. (project, gitignored)
technical-writing
by Logos-Liber
Technical writing principles and best practices for creating clear, accurate documentation
codebase-documenter
by alunadev
Create comprehensive, beginner-friendly documentation for codebases. Use when writing READMEs, architecture guides, code comments, or API documentation.