Product & Planning

claudekit Bundle

Fast codebase scouting using parallel agents. Use for file discovery, task context gathering, quick searches across directories. Supports internal (Explore) and external (Gemini/OpenCode) agents.

yichengyang-ethan Skill

用于先搞清楚“有哪些数据可看、怎么搜索目标市场、怎么落地数据样本”的技能。只做数据发现与取数，不做策略假设。

arenukvern Bundle

Critically analyze whether a product, repo, skill, plugin, harness, or architecture vision still fits the real application, user intent, implementation, evidence, and likely future direction. Use when asked to assess vision vs application, predict future fit, critique roadmap direction, analyze strategic intent, or decide whether to keep, refine, pivot, or kill a plan.

konecty Bundle

All Konecty CRM data operations through the Konecty user MCP server: find/search/filter records, cross-module queries and aggregations, create records, update records (fetch-first with _updatedAt), delete records (preview + confirm), upload/download/delete files, session login, and module/field discovery. Use when user wants to: buscar registros, pesquisar, listar, filtrar dados, criar registro, inserir dado, criar contato/oportunidade/atividade, atualizar, editar, modificar registro, deletar, remover, apagar registro, fazer upload, anexar arquivo, enviar imagem, listar módulos, descobrir campos, consultar o CRM, search records, create record, update, delete, upload file, discover fields, query CRM data. Requires the konecty MCP server connected (see konecty-setup). Do NOT use for metadata/schema ops (documents, lists, views, access, hooks, namespace) — use konecty-meta; do NOT use for connecting/configuring the MCP server — use konecty-setup.

zhangliang0115 Skill

Write, structure, and publish a SKILL.md skill that works across every harness — Claude Code, DeepSeek Harness (dsh), Codex CLI, Gemini CLI, Copilot, Cursor — including the cross-agent gotchas generic guides miss: tier shadowing between project and user roots, discovery rules, and trigger-description design. Use when creating a new skill, fixing a skill that fails to load in some agents, or preparing a skill repo for distribution.

zhangliang0115 Skill

Audit whether an agent skill works across every harness (Claude Code, DeepSeek Harness dsh, Codex, Gemini CLI, Copilot, Cursor) before publishing or after a "my skill loads in Claude but not in dsh" report. Checks name collisions across roots, tier shadowing, discovery rules, and trigger quality per agent.

enocgit Skill

Orchestrates an end-to-end, plan-gated software build pipeline: routes each stage to the right skill while enforcing human approval gates. Covers discovery, PRD, stress-test, architecture, API contracts, decomposition, implementation, QA, review, landing, and retro. The single entry point for the workflow. Use when the user wants to build a feature or product the disciplined way, start or resume structured development, asks "what stage are we at" / "what's next", or says "start the sdlc" / "run the pipeline".

enocgit Skill

Starts implementation of one decomposed task: isolates a workspace (a feature branch by default; a git worktree only when isolation is critical), loads the relevant PRD, ADR, and frozen contract, then proposes a compact in-session plan for approval before any code is written. Use at the start of Stage 4 (Implement) once scope is approved, or when the user says "start working on issue #N", "begin this task", or "let's implement {feature}".

hraness Bundle

Reviews and fixes a just-implemented phase of a multi-phase plan during a phase-orchestrator run. Use after a phase's implementation and initial validation: checks the phase against the plan, PRD/spec, repo conventions, security, tenancy/data ownership, migrations, and test coverage, and patches bounded low-risk issues directly. Never commits unless commit authority is explicitly delegated. Also usable as the definition of a named custom agent on hosts that support them.

hraness Bundle

Writes or restructures an implementation plan in the format the phase-orchestrator skill consumes: dependency-ordered phases with explicit scope, acceptance criteria, validation commands, and status/log conventions. Use when the user asks to write a plan for phase orchestration, prepare a plan or PRD for delegated multi-agent implementation, or convert a spec, checklist, or design doc into implementable phases.

hraness Bundle

Orchestrates phase-based implementation plans using the host's todo tracker and subagents for implementation, review, validation, default phase commits, plan finalization, and a final end-to-end review. Delegates work through the companion phase-implementer, phase-reviewer, and phase-final-reviewer skills and consumes plans in the write-phase-plan format. Use when the user provides a plan, checklist, PRD, or phase document and asks for delegated multi-agent execution across phases.

hraness Bundle

End-to-end reviewer for a completed multi-phase feature at the end of a phase-orchestrator run. Use after all requested phases are finalized: inspects the whole feature against the plan and PRD/spec, hunting integration bugs across phase boundaries, missing acceptance criteria, stale plan state, and validation gaps. Patches only safe concrete issues; never commits unless commit authority is explicitly delegated. Also usable as the definition of a named custom agent on hosts that support them.

huajiexiewenfeng Bundle

Use this whenever the user wants to initialize, adopt, map, onboard, or set rules for an Obsidian vault as an LLM Wiki. Trigger on requests like "initialize Obsidian LLM Wiki", "adopt this vault", "create a knowledge center", "generate a knowledge map", "scan my vault", "guide me step by step", or "set Obsidian wiki rules". This skill creates structure, inventories existing content, generates an onboarding roadmap, and guides the user toward the first ingest batch. It must not move or delete existing user files.

ishands Bundle

Enrol in a curated learning path. Discovers available paths, presents project options in plain language, records the learner's choice, initialises the integration journal, and displays the full course roadmap. Run once at the start of the path — not at the start of each course. Distinguishes enrolment (path level, one-time) from starting a course (delegates to start-course).

ivy-interactive Skill

Find "Tendrillable" GitHub issues - open, recent, code-requiring issues that an agent can plan and one-shot WITHOUT asking clarifying questions, with high probability of success. Classifies a repo's open issues against the Tendrillable rubric and prints a ranked list of issue URLs. Use when asked to find tendrillable issues, source candidates for Tendril, or triage a repo's backlog for one-shottable work. Usage: tendrillable <githubUrl> <amount>.

javimosch Skill

Optimization history (434s → 19.8s), patterns that worked, and the roadmap for further gains. Read this before planning optimizations.

minhuw Bundle

Survey a codebase as a senior advisor and write prioritized, semantically bounded Herder plan graphs from verified repository findings without changing source code. Use when asked to audit code, find bugs or improvement opportunities, suggest evidence-backed product direction, or produce a herder-plans/ backlog for Herder Fire. Route user-defined new features that require intent clarification to Grill.

xiaomi Bundle

可作为 `hiui-page-workflow` 等更大页面工作流的标准 S0 前置 skill，专注 B 端中后台与 HiUI 页面生成前的需求细化。将模糊或抽象的后台/管理台/运营台/配置台/审批流需求细化为可执行的产品方案、MVP 范围、用户流程、业务规则、可追踪页面清单、产品 PRD、全局生成上下文、页面级提示词和 HiUI 交接包。适用于澄清后台产品想法、把粗略需求转成 PRD 或产品方案、拆解列表/详情/编辑/配置等工作面、定义角色权限/数据权限/状态机/审计规则，并在需要时补齐权限矩阵、状态流转表、字段字典、异常与审计矩阵、批量/导入导出规范、存量系统改造与发布策略；同时承担 B 端产品专家判断，包括业务价值拆解、优先级建议、方案取舍、多租户/版本/开通模型、主数据与系统边界、反模式识别与风险提示，持续把模糊的 B 端需求变成可落地输入；当需求发生在已有项目/仓库中时，也用于结合当前仓库的页面、模块、接口、类型和文档做带上下文的需求细化。

yisean Bundle

把原始需求澄清并定稿为规范化 PRD（带 R/F 功能需求编号与 AE/AC 可验收标准），写入 docs/product/prd/。Use when 用户给出原始需求/想法、要写或更新一份 PRD、把一个特性意图固化成正式需求。新需求取新序号；已有特性的增量改动请改用 /spec-change。

yisean Bundle

以已定稿 PRD + 原型 + 设计为输入，生成可执行的实现计划：把设计拆成可独立认领的实现单元（U：Files/依赖/Patterns/原型页面/设计依据/Execution note/覆盖需求/Test scenarios）、DB migration（与设计 ER 逐字段一致）、三向覆盖矩阵，写入 docs/engineering/plans/。Use when 技术设计（/spec-design）已完成、要据设计拆任务与迁移脚本。计划复用与 PRD/设计相同的 NNN 序号；架构与数据模型在 /spec-design，不在此重做。

yisean Skill

对某个特性（同一 NNN）的 PRD → 原型 → 设计 → plan 做一致性体检：校验覆盖矩阵（每条 R/F 都有 AE/AC 验收且落到实现单元、AE/AC 不悬空）、编号续编无重排无重复、跨文档 NNN 与 status 一致、设计 ER 与 migration 是否一致、NFR 是否缺位，输出带定位与修法的报告。只读不改文档。Use when 想确认某特性的需求/原型/设计/计划是否对得上、提交或评审前自检、spec-change 回流后核对、怀疑有漏验收或悬空需求。修复请回到 /spec-prd、/spec-change、/spec-design 或 /spec-plan。

yisean Skill

统管需求变更的回流：把对已有特性的任何改动按「先文档后代码」的铁律同步回 PRD → 原型 → 设计 → plan，复用原 NNN、续编 R/F 与 AE/AC、不重排。Use when 客户/内部对已上线或在研特性提出改动、原型评审后要变更需求、开发中发现需求漏洞要回流。全新特性请改用 /spec-prd。

yisean Bundle

以已定稿 PRD + 原型为输入，做技术设计：概要设计（架构/模块/技术选型/关键决策/接口清单/NFR 承接/风险）、数据 ER 模型（Mermaid）、详细设计（按模块/接口/关键流程组织，写接口签名与核心逻辑），写入 docs/engineering/design/。Use when PRD 与原型已确认、要先把架构与数据模型定下来，产出供 /spec-plan 拆任务。设计复用与 PRD 相同的 NNN 序号；任务拆分与 migration 在 /spec-plan。

yisean Bundle

依据已定稿 PRD，按 prototype/_spec.md 生成或更新纯静态可点击原型（仿 Element-UI、无外部依赖、双击即开），用于内部对齐或向客户演示。Use when PRD 已完成、需要把界面/交互画成原型、或要把原型发客户确认。客户确认后的需求变更请走 /spec-change（先回流 PRD 再改原型）。

ysm-dev Bundle

Install, configure, and use the wachi CLI to monitor any URL for new content and get notifications via 90+ services (Slack, Discord, Telegram, email, etc.). Use when the user wants to: (1) subscribe to web pages, blogs, YouTube channels, or RSS feeds for change notifications, (2) set up URL monitoring with wachi sub/check/ls commands, (3) configure notification channels via apprise URLs, (4) schedule periodic checks with cron, (5) troubleshoot wachi errors or configuration, or (6) understand how wachi detects changes (RSS auto-discovery, LLM-based CSS selectors).

ytubecoder Skill

Specify ideas into backlog-ready tickets — write descriptions, acceptance criteria, and optionally suggest TDD test cases. Walks through Ideas tickets to get them past the specification gate.

zhuyansen Bundle

One-click daily alpha scanner that runs a full 8-step on-chain research pipeline using OKX OnchainOS + social sentiment + historical backtesting + trend monitoring & alerts: (1) Hot Token Discovery with narrative categorization, (2) Smart Money / KOL / Whale buy-signal tracking, (3) Social Sentiment Scan via crypto news (opennews), Reddit, and Twitter KOL tracking (xreach), (4) Meme Coin launchpad scanning with dev reputation and bundle/sniper detection, (5) Batch security audit (honeypot, mintable, fake LP, wash trading), (6) Historical Signal Validation via DexPaprika OHLCV — backtest what happened after past smart money entries, (7) Trend Monitoring & Alerts via TrendRadar (Chinese platforms: Zhihu/Weibo/Bilibili) + Google Trends (global search interest) — detect tokens trending BEFORE they pump, plus multi-channel alert push (Telegram/Feishu/Slack/DingTalk/WeChat), (8) Consolidated briefing with 8-dimension composite scoring (0-100) and BUY / WATCH / AVOID verdicts. Supports Solana, Base, Ethereum, BSC, A

zhuyansen Bundle

On-chain alpha discovery and research pipeline. Chains together Token Discovery, Holdings Analysis, Smart Money Tracking, and Research Report generation using on-chain data, Twitter intelligence, deep research methodology, and Excalidraw visualizations. Use when the user wants to: research a token, find alpha, track smart money, analyze on-chain holdings, generate a crypto research report, discover trending tokens, or investigate whale/KOL activity. Trigger keywords: "alpha", "research token", "smart money", "whale tracking", "on-chain research", "链上研究", "Token分析", "持仓分析", "研报", "Smart Money", "聪明钱", "巨鲸追踪", "meme coin analysis", "token discovery"

jetbrains Skill

Experimental jbcontext org-wide dependency search across multiple repositories. Use when need to find APIs in other repositories, or dependency configuration are used across repos for upgrades, removals, CVEs, migrations, or ownership discovery.

karrioapi Skill

Skill: Create PRD

dorgonman Skill

Local-first, multi-product backlog management with agent collaboration discipline.

fy-agent Skill

Guides collaborative requirements discovery before implementation. Creates task directory, seeds PRD, asks high-value questions one at a time, researches technical choices, and converges on MVP scope. Use when requirements are unclear, there are multiple valid approaches, or the user describes a new feature or complex task.

millionco Bundle

Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.

vijpatel7 Skill

Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.

canonical Skill

Pulls design context from Figma via the Figma desktop MCP server during documentation workflows. Use when a user provides a Figma URL, selects a node in the Figma desktop app, or references existing designs during discovery, drafting, or review.

unifapi-agent Bundle

When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce — grounded in real public demand, not guesswork. For a single ranked opportunity list, see content-opportunity-brief. For the audience language behind it, see customer-research.