Product & Planning

conn-castle Skill

Audit agent memory files (ISSUES, BACKLOG, DECISIONS, COMMANDS, CONTEXT) for structure, staleness, placement, consistency, and DECISIONS.md bloat; fix accepted findings.

evanklem Skill

Conversational bug discovery → issue draft. Light listening, background exploration, scope assessment. Asks before gh issue create — never auto-files. Use when conducting a QA session, triaging user-reported issues, or filing bugs.

evanklem Skill

Synthesize a PRD (Product Requirements Document) for a big new feature. Synthesis (not interview) — uses existing project context and explicit ADRs. Asks before gh issue create. Use when scoping a substantial new feature in PRD shape (e.g., before a sprint).

compozy Bundle

Runs an optional cross-LLM peer review of a spec (TechSpec, design doc, RFC, or detailed PRD) via `compozy exec` and requires the reviewer to write one scoped Markdown findings artifact for user-directed incorporation. The reviewer runtime is configurable through --ide / --model / --reasoning (defaults claude / opus / xhigh). Project-agnostic: works in any repo, auto-discovers project rule files (CLAUDE.md, AGENTS.md, .cursor/rules, CONTRIBUTING.md), and writes artifacts to --out, an auto-detected .compozy/tasks/<slug>/qa/ layout, or a .peer-reviews/<timestamp>/ fallback. Use when a spec draft has already been approved by the user and they want an external review round, especially for autonomy/network/security/migration-impacting designs. Do not use for implementation/diff review (use impl-peer-review), automatic approval gates, or auto-looped review cycles.

0xatd Skill

Manage Venice x402 wallet credits. Covers POST /x402/top-up (payment discovery + signed USDC settlement), GET /x402/balance/{walletAddress}, GET /x402/transactions/{walletAddress}, USDC on Base (chain 8453), minimum $5 top-up, transaction types TOP_UP/CHARGE/REFUND, and the x402 v2 PAYMENT-REQUIRED response shape returned by all inference endpoints.

aaron-he-zhu Skill

`rank-tracker` has moved

aaron-he-zhu Skill

`serp-analysis` has moved

caseyrtalbot Skill

Initiate a new Forge workflow. Creates .forge/ state and begins the discovery phase. User-invoked only: do not auto-trigger.

caseyrtalbot Skill

Use when starting any new feature, change, or project. Collaboratively refines what to build through structured questions before any design or code begins. Phase: DISCOVERY.

caufieldz Bundle

当用户提到「PPT」「宣讲材料」「SOP 手册」「多 Tab 信息文档」时触发，产物为 HTML 多 Tab 信息文档。「方案文档」走 prd skill（方案型项目）。

caufieldz Bundle

当用户提到「PRD」「需求文档」时触发。基于 IMAP / 原型输出 PRD 亦触发。 PRD 形态为 md（含本地截图，推 Confluence 时脚本自动上传图片）。

caufieldz Bundle

「流程图 / 泳道图 / 审批流 / 状态机」触发。输出 .svg + .png 供 PRD / IMAP / PPT / 架构图 `<img>` 引用。

caufieldz Bundle

当用户提到「原型」「可交互原型」「prototype」时触发。PRD / IMAP 完成后可转为可交互版本。

caufieldz Bundle

当用户说「code review / 审代码 / 过一遍代码 / 提交前审一下 / 看看我这次改的」时触发。 改完 scripts/ · .claude/hooks/ · .claude/skills/*/scripts/ · projects/*/scripts/ 想在 commit 前收口亦触发。 「审计 / 诊断」不触发（走 workspace-audit）；PRD 产出物一致性不触发（走 cross-check）。

caufieldz Bundle

当 PRD 完成后最终交付前验收，或用户说「拉通检查」「校验一下」「检查一致性」「reader test」时触发。 7 维结构性校验已脚本化（PRD 写入自动跑），本 skill 保留两件脚本替代不了的事：① 多 ❌ 项的修复优先级编排 ② Reader Testing 评审实践。

caufieldz Bundle

当用户提到「操作手册 / 使用手册 / 用户手册 / 帮助中心文章 / 带截图的 SOP 手册」时触发。 「营销稿 / 宣发稿 / 上线宣传 / 推广文案」亦触发（走 promo- 模式，两者同为面向用户的上线交付物）。 丢一份现有手册 / 营销稿要改版亦触发。「告警 SOP / 监控值班手册」不触发（那是 prd- 应急 runbook，另一物种）。

charliecpeterson Bundle

Slow, exhaustive planning sessions: question the user one decision at a time until requirements are fully confirmed, then optionally chain into research scouts, a readiness audit, an architecture draft, and a staged roadmap. Trigger on "help me plan", "let's design", "I want to build", "deep planner", or /plan. Built-in plan mode is the lightweight alternative; this is the opt-in careful path.

cyanluna-git Skill

Refine backlog requirements through structured user interview. Turns rough task descriptions into concrete, actionable requirements with goal, scope, acceptance criteria, and edge cases.

firatcand Bundle

Use when the user is working a B2B SaaS deal from qualified opportunity to closed-won — preparing discovery calls, structuring demos or POCs, handling a specific objection, qualifying with MEDDIC/MEDDPICC/SPICED, building mutual action plans, navigating negotiation or procurement, or reviewing pipeline health, forecast accuracy, and deal velocity. Not for finding or prospecting new leads (use prospecting) or upstream positioning (use product-position).

firatcand Bundle

Use when the user needs to scope, write, or audit a product spec — a PRD, feature spec, user stories, acceptance criteria, or a "spec this out"/"break this into stories"/"definition of done" request — or wants an existing spec reviewed for gaps and anti-patterns. Triggers whenever a feature idea needs to become structured requirements that align a team on what to build. For the analytics behind success metrics, use data-analysis; for the technical design, use software-architect.

flingjie Bundle

ALWAYS use this skill when the user wants to find, discover, search for, evaluate, compare, or track GitHub repositories — even if they don't explicitly say "trending" or "discover." Covers: discovering trending repos in any domain, searching for open-source tools by topic, evaluating individual repo quality (deep-dive), comparing repos side-by-side, tracking repos over time with watches, checking for new/updated repos since last scan, and any request that involves finding or assessing GitHub projects. Trigger phrases include "find me X repos", "trending repos in Y", "what's hot in Z", "discover X tools", "evaluate this repo", "compare top 3", "which repo is better for X", "I need a tool that does X", "track these repos", "check my watches", "what changed since last scan", "re-scan my watches", and any mention of repo-trend, repo discovery, or repo scout. Uses three-tier evaluation: quick API scan for discovery → full checklist for assessment → deep Claude reasoning for strategic recommendations. Pure gh CLI

flingjie Bundle

Cross-source concept lifecycle radar that turns weak signals into validated, falsifiable builds. Use when the user wants to track an idea from a hunch to evidence across multiple sources ("validate an idea", "weak signals to validated builds", "hypothesis and evidence", "should I build or drop this", "concept radar", "track this concept", "cross-source signal", "雷达", "验证一个想法"), or asks to capture, scan, verify, review, build, or source-audit a concept. Owns cross-source synthesis and the Inbox → Watch → Verify → Build/Drop lifecycle. Single-source requests route to the specialist skills instead: X-only learning → twitter-learning, Reddit-only pain discovery → reddit-opportunity, GitHub-only discovery → repo-trend. X reply/engagement and customer outreach are out of scope for this project. Deterministic schemas, persistence, scoring, and gates live in the Python CLI; this skill orchestrates retrieval and semantic judgment through validated JSON contracts.

gjalla Skill

Design to accommodates the system's likely future, not just its present state. This is "temporal design" — reasoning about how today's implementation interacts with tomorrow's roadmap and evolving requirements. Use this skill when making decisions during implementation: where to place abstractions, how to structure interfaces, when to make something configurable vs. hardcoded. Triggers when you're choosing between approaches and the difference between them is how well they'll hold up over time.

gnurio Skill

Review existing requirements or convert raw context into requirements that meet 18 quality characteristics (unambiguous, clear, cohesive, consistent, conformant, current, modifiable, traceable, relevant, unique, categorised, complete, correct, concise, testable, implementation-independent, owned, feasible). Use whenever the user mentions requirements, PRDs, specs, user stories, acceptance criteria, requirements review, requirements audit, BRD, FRD, requirements quality, requirements catalogue, requirements traceability, "are my requirements any good", "turn this into requirements", "make these requirements better", or shares meeting notes, interview transcripts, stakeholder input, or feature ideas that need to be formalised. Trigger even when the user does not use the word "requirement" if the artifact they share is functionally a requirement (e.g., "the system should let users export to PDF", "we need a way for admins to revoke access").

harzva Skill

Use when working on learn-likecc and the task involves new requirements, roadmap updates, README updates, git commits, GitHub Pages updates, or release/version changes. Ensures every new requirement is written into plan files, unfinished work remains in TODO sections, and release/git/pages handling follows the repo workflow without the user needing to restate it each time.

ibm Skill

End-to-end workflow to examine and summarise an ado discoveryspace — fetch space YAML, describe entity and measurement space structure, assess sampling coverage, export measurement data, and find related resources. Use when the user asks to inspect, summarise, debug, or analyse a discoveryspace; wants to understand dimensions, experiments used in a space, or sampling coverage; provides a space ID or asks to use --use-latest for the current space.

jianyun8023 Bundle

Use when editing `.alloy` files, configuring Grafana Alloy pipelines, or debugging log collection and relabeling behavior. Covers HCL syntax, common Loki/Prometheus components, processing stages, Docker discovery, and FnOS-specific patterns.

lawwu Skill

Create a visual presentation demonstrating business value of a trained model using showboat. Use after evaluation and explainability to synthesize findings into a stakeholder-ready demo. Invoke when asked to show business value, create a model presentation, generate a demo, or produce a stakeholder report.

linuxfoundation Skill

Repo-owned code-review brain for local pre-PR review on lfx-v2-newsletter-service. Audits the reviewed change against this repo's written rule surface — CLAUDE.md, the repo-local skills, and the service-owned contract docs — and returns an ordinary Markdown review in which every finding quotes a repo rule verbatim. Loaded directly by the `lfx-local-review` launcher through the `local-code-review` discovery alias; not a skill a developer invokes by hand.

linuxfoundation Skill

Repo-owned learnings review brain for local pre-PR review on lfx-v2-newsletter-service. Matches the reviewed change against the empirical pattern knowledge base in docs/reviews/knowledge-base/ — patterns extracted from real past PR review comments on this repo — and returns an ordinary Markdown review in which every finding quotes a KB pattern entry. Loaded directly by the `lfx-local-review` launcher through the `local-learnings-review` discovery alias; not a skill a developer invokes by hand.

lucaswall Skill

Deep research and discussion of a roadmap feature or new idea. Gathers extensive context from codebase, web, APIs, MCPs, and project history, then presents a concise analysis report for interactive discussion. After discussion, handles the outcome — write a feature spec to the roadmap, move to backlog, create an inline plan, modify, or drop. Use when user says "roadmap", "pull from roadmap", "push to roadmap", "add to roadmap", "analyze this feature", "research this idea", or wants to evaluate a feature.

lucaswall Bundle

Audits codebase using an agent team with 3 domain-specialized reviewers (security, reliability, quality). Triages open Sentry issues (creates Linear issues for real bugs, resolves/ignores noise). Creates Linear issues in Backlog state for findings. Use when user says "audit", "find bugs", "check security", "review codebase", or "team audit". Higher token cost, faster and deeper analysis. Falls back to single-agent mode if agent teams unavailable.

lucaswall Bundle

Create TDD implementation plans from direct feature requests. Use when user provides a task description like "add X feature", "create Y function", or "implement Z". Creates Linear issues in Todo state. Faster than plan-backlog for ad-hoc requests that don't need backlog tracking.

lucaswall Bundle

Plan Backlog Skill

lucaswall Skill

Add issues to Linear Backlog from free-form input. Use when user says "add to backlog", "create backlog issues", "track this", or describes tasks/improvements/bugs to add. Interprets user's ideas, investigation findings, or conversation context into well-structured Backlog issues. Can process multiple items at once.

lucaswall Skill

Refine vague Linear Backlog issues into well-specified, actionable items. Use when user says "refine backlog", "refine PROJ-123", "improve backlog items", or "clarify issues". Fetches Backlog issues, analyzes gaps, asks clarifying questions, and updates Linear after user confirms.