Comments
Code comments and annotations
open-taskboard
by 1648298170
管理 opencode Taskboard 的任务：查看、拆解、领取、跟踪任务状态。Use when the user asks to 看任务/拆解任务/拆分需求/更新任务状态/领取任务, or when starting work that should be tracked on the taskboard.
agent-instantiation
by The-Interdependency
Methodology for instantiating, forking, running, merging, and retiring agents in the a0 platform and its near-identical mirror a0ucns. Load this when adding or changing a sub-agent spawn path, a PCNA instance fork/merge, an agent definition or naming scheme, spawn caps or approval gating, an agent run/log table, a heartbeat-driven agent task, or a checkpoint of agent state. Use it before writing any code that creates, addresses, schedules, or tears down an agent or sub-agent, so the new code follows the platform's existing lifecycle, fork/merge, identity, and gating contracts rather than inventing a parallel one. NOTE: a0-betatest (a0p) has diverged to a different per-user CRUD + native-ZFAE instancing model — this skill's spawn/fork/merge sequence does NOT apply there; see "a0-betatest divergence".
walkthrough
by victorlga
Guided, navigable walkthrough of a branch or PR. Builds an interactive page where you click into functions like go-to-definition in vim, back out along the same path, and read AI explanations built from context to code at every step. Use when the user wants to understand what a branch or PR changed and the code around it, asks for a walkthrough or explanation of a diff, or needs to review changes an agent made.
assess-issue
by hoopit
Decide whether one issue is worth fixing — price the fix, measure the harm against live data, then close it with the findings or ship it.
yc-product-hunt-launch
by 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.
Monitor Polymarket
by Atrium-Hermes
Monitor specific prediction markets for 24h price moves, volume changes, and fresh comments
using-agent-skills
by MGallo-Code
Discovers and invokes agent skills. Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked.
flow-board
by pmcfadin
Report status across all in-flight CQLite delivery work — render the shared GitHub Project claim board (item, status, assignee, priority) with drift + abandoned-claim reconciliation, then surface and drive the single furthest-along item waiting on the owner (a green PR to merge, a spec to approve), or offer a claim-aware pick-list. Use when the owner asks "where do things stand", "what's next", "unblock me", or "what needs me".
masm-doc-comments
by 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.
portfolio-analyst
by Kosmos-7
Analyste personnel pour décisions d'investissement. Score consistant des titres (qualité + valorisation + timing + analystes, scoring v3), discipline de vente anti-disposition, frameworks de décision (pre-mortem, second-level thinking, base rates), détection de biais cognitifs. Pour questions du type "dois-je acheter X", "j'hésite sur Y", "le marché va...", "j'ai vendu trop tôt", "fais-moi un point sur mon portefeuille". Triggers FR/EN multiples — voir section dédiée.
coding-standards
by 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.
academic-paper
by 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 사용 고지."
explain-diff
by alex-jordan547
"Create a rich self-contained HTML explanation of a code change, diff, branch, commit, PR, or worker implementation. Use when the user asks to explain code changes, wants to understand what an agent changed, needs a reviewable handoff artifact, or when an orchestrator/worker is asked to invoke /explain-diff for a substantial change."
dependabot-merge
by shoji9x9
Dependabot が作成した PR のレビューとマージを gh で標準化するスキル。PR URL / PR 番号で 1 件、--all または無指定で open な全 Dependabot PR を対象にする。CI 成功の確認 → 更新内容（changelog/release notes）からマージ影響の確認 → 判断を PR コメントに記録 → 問題なければマージ、までを進める。特に 0.x（<1.0）依存はマイナー更新でも破壊的変更があり得るため影響を確認してから扱う。「Dependabot の PR をマージして」「依存更新 PR を確認してマージ」「dependabot-merge」「dependabot の PR を全部見て」や、--all を伴う依頼で必ず発動する。依存更新 PR を 1 件ずつ影響判断してからマージする。
feishu-inout
by 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
by 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?"
orchestrator-dispatch-loop
by simnova
The CEO-side board loop — plant a RED, probe it, commit, dispatch, verify, integrate, close. Exact signatures and the traps that cost real time. Read before dispatching or harvesting a slice; the worker-side contract is delegated-worker-contract.
mission-control
by 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).
secpal-pr-review
by SecPal
Process completed review feedback for one named SecPal repository and pull request after an explicit remediation request, or handle explicitly named fixed-thread resolution-only requests after the findings were validated, committed, and pushed. Do not use for generic review, PR creation, review requests, CI-only debugging, ordinary implementation, or merge-only work.
codebase-guard
by 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."
ponytail
by SnipeBoss
Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", and whenever they complain about over-engineering, bloat, boilerplate, or unnecessary dependencies.
incident-response
by OldBoy405
How this team handles a production incident issue — what to establish before proposing a fix, and what an agent may and may not do on its own.
data-visualization
by nachopalmeri
"Data visualization with chart selection, color theory, and annotation best practices. Covers chart types (bar, line, scatter, heatmap), axes rules, and storytelling with data. Use for: charts, graphs, dashboards, reports, presentations, infographics, data stories. Triggers: data visualization, chart, graph, data chart, bar chart, line chart, scatter plot, data viz, visualization, dashboard chart, infographic data, data presentation, chart design, plot, heatmap, pie chart alternative"
cleanup
by YashuLanki
Use when asked to clean up the repo — remove dead files, folders, docs, config constants, imports, or stale doc sections left behind by earlier work. Also for "what's dead in here?", "tidy this up", or after a large refactor.