注释
代码注释与标注
reddit-intel
SamCuipogobongo
Reddit competitive intelligence for any product. Discovers keywords, finds relevant communities, searches for posts with pain points, and analyzes comments to extract competitor mentions, real user language, and unmet needs. Runs 4 incremental steps: expand-keywords / expand-subreddits / find-posts / analyze-comments. Also: init (first-time setup). Each run: read JSONL → search → dedup-append → re-render Markdown. Requires: Exa MCP server for Reddit search. Usage: /reddit-intel step-name
clarify
diskd-ai
Clarify redmine task skill
triage
tt-a1i
Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.
yc-product-hunt-launch
imsurajj
Write all copy needed for a successful Product Hunt launch: tagline, description, first comment, and maker comment. Use when the user asks to launch on Product Hunt, write PH copy, or prepare a launch post.
masm-doc-comments
tomevault-io
Enforce doc comment conventions for Miden Assembly (.masm) procedures. Use when editing, reviewing, or creating .masm procedures, especially when documenting inputs, outputs, panic conditions, or invocation types. Use when this capability is needed.
scgpt
HughYau
Embed and annotate single-cell expression data with scGPT, a foundation model for single-cell biology. Use this skill when: (1) Producing cell embeddings from an AnnData for clustering/integration, (2) Zero-shot or fine-tuned cell-type annotation, (3) Gene-level representation for perturbation/GRN tasks. For probabilistic single-cell models (scVI etc.), use the scvi-tools library.
run-tasks
kbrdn1
Execute GitHub issues or task files with full EPCT workflow and PR creation
coding-standards
Sylla-BV
This skill should be used when the user asks about "Python coding standards", "Python code style", "type hints", "type annotations", "Optional vs union", "T None", "mypy", "black", "isort", "flake8", "ruff", "Pydantic models", "ConfigDict", "async patterns", "asyncio", "structlog", "error handling in Python", "Python naming conventions", "snake_case", "reviewing a Python PR", "does this pass Python code review", "BaseHarvester", "Dramatiq actors", "pydantic-settings", "pytest conventions", or wants to know whether code follows Sylla's Python data-engine repository standards.
community-management-playbook
mohitagw15856
"Build a community management playbook for a brand's social media channels. Use when asked to create guidelines for managing comments, DMs, and community interactions, define a moderation policy, or build response frameworks for social media community managers. Produces a complete playbook with response templates, escalation paths, moderation rules, and tone guidelines."
bd-record
TeamWiseFlow
当执行 BD（商务拓展）任务时维护 SQLite 追踪数据库，记录已探索的创作者（模式一）和已互动的帖子（模式二），避免重复追踪和重复互动。
academic-paper
lovits
"12-agent academic paper writing pipeline. 11 modes (full/plan/outline/revision/revision-coach/abstract/lit-review/format-convert/citation-check/disclosure/rebuttal-audit). 6 paper types, 5 citation formats, bilingual abstracts, LaTeX/DOCX-via-Pandoc/PDF output. Style Calibration + Writing Quality Check + Anti-Patterns with IRON RULE markers. Triggers: write paper, academic paper, guide my paper, parse reviews, audit my rebuttal, check my response draft, AI disclosure, 寫論文, 學術論文, 引導我寫論文, 審查意見, 評估回覆, 논문 작성, 초록 작성, 논문 수정, 논문 계획을 도와줘, 심사 의견 반영, 답변서 점검, AI 사용 고지."
feishu-inout
kristencacogenic360
Read/write Feishu/Lark cloud documents, send/search messages, manage calendar/meetings, operate bitable (multi-dimensional tables), and manage group chats via the official Remote MCP service and Open APIs. Works with Claude Code, Cursor, Codex, OpenCode, OpenClaw, and other AI coding agents. Trigger this skill when the user mentions Feishu, Lark, cloud docs, read/search/create documents, messaging, sending messages, meeting, calendar, bitable, multi-dimensional table, 多维表格, 日历, 会议, create group, 创建群, or provides a Feishu/Lark document URL.
explaining-code
odewahn
Explains code with visual diagrams and analogies. Use when explaining how code works, teaching about a codebase, or when the user asks "how does this work?"
skool-headless-reader
IgorGanapolsky
Read, monitor, and analyze Skool communities or posts headlessly for lead discovery, customer pain, acquisition opportunities, or ThumbGate revenue research without blocking the user's browser.
mission-control
ggaegule-commits
Kanban-style task management dashboard for AI assistants. Manage tasks via CLI or dashboard UI. Use when user mentions tasks, kanban, task board, mission control, or wants to track work items with status columns (backlog, in progress, review, done).
codebase-guard
0xlic
"Identify, use, and maintain guard: comments in a codebase. Use when an agent reads guard comments while exploring code, when a user correction after model misunderstanding should become a trusted code fact, or when existing guard facts conflict with code changes or user requirements."
r-package-check
pedrohcgs
Run the full R package release gate — regenerate docs, run the test suite, run R CMD check --as-cran, and triage every ERROR / WARNING / NOTE against CRAN policy before a release or submission. Use when the user says "check my R package", "R CMD check", "is this package CRAN-ready", "run devtools::check", "prepare for CRAN submission", or points at a directory containing a DESCRIPTION file. Produces a check report + CRAN-submission checklist in quality_reports/.
Music Listener
naohainezha
If the user is sharing their own music, be encouraging but honest.
doc-author
mintlify
Write, edit, and maintain documentation. Use for collaborative drafting, autonomous writing, or improving existing docs. Defaults to collaborative mode where the human makes final decisions. Built by Mintlify.
architecture-simplicity
youlianvr
'Use when the user wants to: design/redesign modules and layers, choose between a library and own code, understand why a project became a god-file, add an abstraction "for growth," update a DB schema without data loss, or during architecture review. Covers: YAGNI until second need, stdlib-first, modules by change reason, shared core + thin adapters, config outside repo + defaults in code, schema evolution without DROP, provider fallback chain, non-representable invalid states, dead code removal. Do not use for money (money-path-safety), hardening (hardening-observability), or refactoring (agent-refactor-safety).'
finalize-step-review-retrospective
cuioss
Finalize-phase wrapper that compares the PR's automated and human reviewers — a deterministic per-reviewer metrics pass (raw vs actionable vs meta comments, resolution buckets, %-resolved-as-fixed) augmented by an LLM qualitative quality judgment and a comparative verdict, persisted as a review-retrospective artifact
pr-walkthrough
warpdotdev
Generate a static interactive D3 walkthrough of a pull request. Use when the user wants a zoomable PR map, graph/canvas PR orientation, or alternate visualization of PR system components, data flow, code dependencies, and user actions.
coding-style
youlianvr
"Core principles for clean, maintainable, minimal code generation. Merged 2026-08-09 from coding-style.md + andrej-karpathy-skills.md + karpathy-coder + minimalist; extended 2026-08-15 with reviewed ponytail mechanics (DietrichGebert/ponytail, MIT) and the code-simplifier over-simplification guard (Anthropic claude-plugins-official). Enforces Karpathy's 4 principles (think before coding, simplicity first, surgical changes, goal-driven execution), the Minimalist Efficiency Ladder (YAGNI → reuse → stdlib → native → existing deps → one-liner → minimum code), clean-deletion rules, lazy-senior intensity levels (lite/full/ultra), trade-off markers, compressed output format, and a clarity-over-brevity guard against over-simplification. Use when writing, reviewing, or committing code; when the user asks for efficient code, fewer dependencies, YAGNI, 'don't overcomplicate', a 'karpathy check', or before claiming a diff is good."
ci-fix
dotnet
Common safety and triage protocol for .NET MAUI CI-fixer workflows. Use whenever investigating, creating, or advancing a [ci-fix] or [ci-fix-net11] pull request from a ci-scan issue, including frozen ownership snapshots, Continue/Watch/Stop/Skip classification, manual single-issue dispatches, and scheduled sweeps.