Comments
Code comments and annotations
ljg-explain-concept
by lijigang
Deep concept anatomist that deconstructs any concept through 8 exploration dimensions (history, dialectics, phenomenology, linguistics, formalization, existentialism, aesthetics, meta-philosophy) and compresses insights into an epiphany. Use when user asks to explain, dissect, or deeply understand a concept, term, or idea. Produces org-mode output.
implementation-guide
by nbbaier
Generate comprehensive implementation guides for coding tasks instead of writing code directly. Use when the user requests detailed implementation documentation, step-by-step development guides, or when they want to implement features themselves using tools like Cursor. Creates exhaustive guides with background context, architecture decisions, milestones with verification points, and rationale for a "build-it-yourself" workflow.
agentskill
by airscripts
Analyze a code repository and synthesize an AGENTS.md.
audit-prep-assistant
by runkids
Prepares codebases for security review using Trail of Bits' checklist. Helps set review goals, runs static analysis tools, increases test coverage, removes dead code, ensures accessibility, and generates documentation (flowcharts, user stories, inline comments).
feynman
by neurofoo
Feynman Technique for deep learning—explain a concept simply, identify gaps, fill them, then refine. Use when learning something new, testing understanding, or preparing to teach.
moscow
by neurofoo
MoSCoW prioritization categorizing items as Must have, Should have, Could have, or Won't have. Use for scope definition, feature prioritization, or when everything feels equally important.
wemp-operator
by IanShaw027
"微信公众号自动化运营。触发词：采集热点、公众号日报、周报、检查评论、回复评论、生成文章。依赖 wemp skill。"
documentation-templates
by xenitV1
Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.
critical-reasoning
by andrewgleave
Apply critical rationalist epistemology (Popper, Deutsch) to evaluate reasoning, identify errors, and refine understanding. Use when the user explicitly requests help with reasoning - phrases like "help me think this through", "does this make sense", "any flaws in this", "what am I missing", "critique this", "is this reasoning sound", "stress test this idea", "devil's advocate", or any request to evaluate arguments, identify logical problems, or improve thinking. Also use when errors in reasoning are significant enough to materially affect the user's goals, even if not explicitly requested.
phase-3-outline
by cuioss
Two-lane solution outline creation - light lane for bounded localized changes, deep lane for codebase-wide discovery
reddit-skills
by beggarticksarthurtatum121
Reddit automation skill collection. Supports authentication, content publishing, search & discovery, social interactions, and compound operations. Triggered when a user asks to operate Reddit (post, search, comment, login, analyze, upvote, save).
luau-type-expert
by dig1t
Professional Luau type-checking and clean code specialist for Roblox development. Use this skill when: - Writing or reviewing Luau code that needs proper type annotations - Fixing type errors from luau-lsp or luau-analyze - Converting untyped Lua/Luau to strictly typed code - Designing type-safe APIs, modules, or data structures - Understanding Luau type system features (generics, unions, intersections, refinements) - Optimizing code for luau-lsp compatibility - Setting up --!strict mode compliance - Creating type definitions (.d.luau files) - Debugging "Type X is not compatible with Y" errors - Writing metatables with proper type support Triggers: "type error", "type annotation", "luau types", "strict mode", "--!strict", "type checking", "luau-lsp", "type mismatch", "generic type", "union type", "type narrowing", "type refinement", "type cast", "export type", "typeof"
cpp-api-documentation
by sentenz
Adds Doxygen-compatible documentation comments to C++ header files. Use this skill exclusively for adding or improving API documentation in existing header files (.hpp, .h). Do NOT create new resource files such as Doxyfile, scripts, or README files.
deep-work
by petekp
Structured development workflow that separates research, planning, and implementation into distinct phases with persistent markdown artifacts. Use when starting any non-trivial feature, refactor, bug investigation, or codebase change. Trigger on: "deep work", "research and plan", "plan before coding", "write a plan", "research this codebase", "don't code yet", "understand then implement", or when the user wants a disciplined approach to a complex task. Also use when the user says "research", "plan", "annotate", "implement the plan", or references research.md/plan.md artifacts.
hinge-profile-optimizer
by b1rdmania
Improve a Hinge dating profile through research-backed screenshot audits, photo selection and ordering, conversational discovery, prompt and caption writing, settings review, or post-launch troubleshooting. Use for a full profile rebuild or a focused request about photos, copy, positioning, match quality, or profile performance.
literate-docs
by ssiumha
Adds docstrings, comments, and WHY/DECISION tags to code. Use when documenting functions/classes with language-specific standards (JSDoc, PEP 257, GoDoc).
claris-filemaker-pro
by CadenceUX
REFERENCE skill — FileMaker Pro script steps, calculation functions, and custom functions ONLY. Use for: syntax lookups, function parameters, usage examples, and live doc fetches across all 368 built-in functions (If, Case, Let, While, ExecuteSQL, JSON, AI/embedding, Persistent Data), all 215 script steps (including FM 26 PDF Files and Persistent Data categories), Data API (REST), SQL/ExecuteSQL, WebDirect, FileMaker Go, error codes, and custom function patterns. Not a platform administration guide. Out of scope: FileMaker Server admin, Claris Connect, Claris Studio, ODBC/JDBC deep configuration. Trigger on any FileMaker function name — even inside code, a calc field, or a script. Always check local reference files first for format, doc_url, and originated_in_version before fetching live docs. Prefer live doc fetches over training data — Claris docs are versioned and frequently updated.
code-review-python
by ssiumha
Python type hints and typing review checklist. Injected into code-reviewer agent for Python projects. Use when reviewing Python code for type safety or auditing type annotations.
reddit-reader
by brisyramshere
通过 Reddit OAuth2 API 搜索和阅读 Reddit 帖子、评论和子版块内容。当用户要求搜索 Reddit 讨论、浏览子版块帖子、阅读 Reddit 帖子内容和评论、了解 Reddit 社区对某个话题的看法时使用此 skill。支持按时间范围和排序方式筛选，支持读取完整帖子正文和嵌套评论树。
doc-hunter-go
by skyosev
Audit Go code for missing documentation where the "why" is not obvious — obscure calculations, non-trivial business rules, surprising behavior, implicit constraints, workarounds, and missing godoc on exported symbols. Finds where a comment would save the next reader significant time. Use when: reviewing Go code for long-term maintainability, onboarding new team members, auditing undocumented business logic, or preparing code for handoff.
documenting-code-comments
by third774
Standards for writing self-documenting code and best practices for when to write (and avoid) code comments. Use when auditing, cleaning up, or improving inline code documentation.
doc-hunter-ts
by skyosev
Audit TypeScript code for missing inline documentation where the "why" is not obvious — obscure calculations, non-trivial business rules, surprising behavior, implicit constraints, and workarounds. Finds where a comment would save the next reader significant time. Use when: reviewing TypeScript code for long-term maintainability, onboarding new team members, auditing undocumented business logic, or preparing code for handoff.
cron-scheduler
by AIDotNet
解析、验证和解释cron表达式，计算下次运行时间。
documentation-writer
by AIDotNet
生成全面的文档，包括README文件、API文档、代码注释（JSDoc、docstrings、XML）和架构文档。