Product & Planning

rabbit-ivan Bundle

Audit and design entity data models into a field-by-field markdown report: a target-vs-current audit table per entity, a classification of every field (table column / config blob / runtime-computed / remove), a grouped migration change list, and design-decision justifications. Use this whenever the user reasons about what fields an entity should have or where they should live, even if they never say "audit": designing a data model, checking PRD fields against a DB schema, deciding store-vs-compute or column-vs-jsonb, spotting a bloated or over-modeled entity, or planning a schema migration. Trigger even when they just paste a PRD, schema, or Prisma/SQLAlchemy model and ask "are the fields right", "what's missing", "should this be a column or jsonb", "is this field even needed". Also on 实体建模, 数据模型审核, 字段审查, 字段太多了, 这个表设计得对吗, PRD 对齐, 模型设计, 该存还是该算, 列还是配置, 帮我看下这个模型.

rabbit-ivan Bundle

Audits a document or doc set from the inside and produces a prioritized findings report (P0-P3) of internal conflicts, stale content, terminology drift, duplication, and misplaced or unsupported claims, plus update/move/merge/remove/split decisions and a suggested repair order. Use this whenever the user wants docs sanity-checked or cleaned up for self-consistency without comparing against code, even when they never say "audit": contradictory or duplicate sections, stale assumptions, unclear structure, or a PRD/spec that should hang together. Trigger on casual and Chinese phrasings too: 文档自相矛盾, 文档前后不一致, 文档内部冲突, 审一下这份文档, 帮我审审这个 PRD, 文档体检, "these two sections disagree", "is this spec consistent", "the docs repeat themselves". If the truth source is the code, use hai-audit-docs-against-code instead.

vodailocz Skill

Use when integrating or optimizing Model Context Protocol (MCP) servers and clients. Keywords: MCP, Model Context Protocol, tool discovery, lazy loading, sampling, resource subscription, MCP server.

vodailocz Skill

Use when starting a new feature, product, or system design. Eliminates the spec-implementation gap by making specifications the primary artifact that drives code generation. Keywords: SDD, spec-driven, PRD, feature spec, user stories, implementation plan, specification, acceptance criteria, Given-When-Then.

hk-hub Skill

Domain expertise for Ai2 Asta MCP tools (Semantic Scholar corpus). Intent-to-tool routing, safe defaults, workflow patterns, and pitfall warnings for academic paper search, citation traversal, and author discovery.

hk-hub Bundle

Prioritize drug targets from a ranked gene list (e.g., scRNA-seq DE output) by orchestrating parallel API queries against UniProt, OpenTargets (with integrated DepMap CRISPR essentiality + gnomAD constraint), PubMed, the Human Protein Atlas (HPA), and ChEMBL tool compounds, then re-ranking by a composite score combining protein localization, druggability, disease genetics, tissue specificity (safety), focus-cell-type expression, CRISPR essentiality, LoF safety constraint, and research maturity. Use whenever the user wants to filter, triage, prioritize, or "do due diligence" on a list of candidate genes for drug discovery, especially after a DE / DEG analysis when they say things like "which of these should I follow up on", "filter for druggable targets", "make a target dossier", "rank these for tractability", "annotate these genes for druggability", or "build a target report". Trigger even when the user says just "filter these candidate genes" or hands over a CSV from a DE pipeline.

jsuvic Skill

Use when a stakeholder request is rough, ambiguous, or underspecified and needs clarification before planning, writing a spec, or creating issues.

ccdawn Bundle

Use when Chinese-first active intent discovery, local context probing, user calibration before downstream skill selection, owner/workflow routing, continuation, permission inference, or multi-thread/conflict coordination is needed.

docat0209 Skill

Prioritizes features and manages product roadmap. Triggers ONLY when: user asks to prioritize features, plan a roadmap, evaluate feature requests, or decide what to build next. Do NOT trigger during development or when implementing already-decided features.

docat0209 Skill

Decomposes a milestone into atomic GitHub issues with commit plans and test requirements. Triggers ONLY when: roadmap-steer has selected a feature/milestone to build next, biz-think acid test has passed and work is greenlit, or user explicitly asks to plan/decompose/break down work. Do NOT trigger when: implementation is already in progress, the task is a single-file quick fix requiring no planning, or issues already exist for the milestone.

doris-labs Skill

Turn an upcoming sales call into a one-page brief — who's in the room, why they're meeting, what to ask, what to land, and the single next step you're driving toward. Use before a discovery, demo, or any customer meeting. Triggers on: prep for my meeting, meeting prep, prep this call, call brief, prepare for the meeting.

doris-labs Skill

Lead a discovery call that uncovers real pain, quantifies it, and locks the next step before you hang up. Use before or during a discovery call to prep questions and structure. Triggers on: run discovery, discovery framework, lead the call, qualify on the call, discovery technique.

doris-labs Skill

Build a sharp, one-page account brief before a call — firmographics, recent triggers, the likely buying committee, mapped pains, and hypotheses to test. Use before a discovery call, an outbound push, or any first touch with a new account. Triggers on: research this account, company research, account brief, who are they, account profile.

doris-labs Skill

Build a discovery call plan — a hypothesis-driven question tree, a pain-to-impact-to-priority ladder, and multi-threading targets — so you walk in knowing exactly what to ask and why. Use before a discovery call or any meeting where you need to uncover problem, impact, and decision process. Triggers on: plan discovery, discovery questions, what to ask, discovery prep, question plan.

doris-labs Skill

Turn a sales call into a follow-up email, clear next steps, and a clean CRM update. Use after a discovery, demo, or any customer call. Triggers on: follow up email, post call, recap email, log this call, update the deal.

doris-labs Skill

Map the buying committee on a deal — who holds power, who's on your side, and which roles you haven't reached yet — then build a plan to close the gaps. Use when a deal feels single-threaded, before a big meeting, or when forecasting risk. Triggers on: map stakeholders, buying committee, who else, power map, stakeholder map.

dropfan Bundle

飞书 OKR：管理目标与关键结果。查看和编辑 OKR 周期、目标、关键结果、对齐关系、量化指标和进展记录。当用户需要查看或创建 OKR、管理目标和关键结果、查看对齐关系时使用。不负责：待办任务管理（lark-task）、日程/会议安排（lark-calendar）、绩效评估

lu1sdv Bundle

Web search, content extraction, site crawling, URL discovery, and AI-powered research using Tavily API via curl. Use when user needs web search results, current events, news, finance data, content from URLs, site-wide extraction, or multi-topic research with citations. Trigger phrases: 'search the web', 'find online', 'extract from URL', 'crawl site', 'research topic', 'latest news about', 'web search', 'tavily'.

lu1sdv Bundle

Use when performing vulnerability research, security auditing, code analysis, bug bounty hunting, CTF challenges, penetration testing, or exploit development. Covers source audit across 30+ attack domains, sink analysis for 12 languages, SAST/DAST integration, vulnerability chaining, and proof-of-concept development. Triggers: vuln assessment, pentest, bug bounty, security audit, find vulns, exploit, ctf, code audit, hunt bugs, 0-day, SAST, DAST, taint analysis, CI/CD pipeline security, GitHub Actions, Terraform, Traefik, n8n workflow, OpenTelemetry, supply chain attack, agent sweep, find me zero days, sweep everything, automated vuln discovery, binary analysis, reverse engineering, firmware audit, kernel driver, memory corruption, ROP, fuzzing harness, patch diffing.

zgiai Bundle

Support structured business decision analysis for product, technical, project, presales, customer solution, and management choices. Use when the user asks for 决策, 帮我选, 怎么选, 要不要做, 方案对比, 技术选型, 功能优先级, 项目优先级, 风险收益, 取舍, 权衡, 决策复盘, 客户方案, 售前方案, 管理决策, decision, choose, tradeoff, prioritization, roadmap, technical choice, option comparison, risk-benefit, ROI, should we, or decision review.

zgiai Bundle

Compare two or more existing parsed documents, pasted document texts, or document contents from chat context to identify similarities, differences, additions, deletions, modifications, conflicts, risks, version changes, and dimension-based comparisons. Use when the user asks for 多文档对比, 文档对比, 版本对比, 合同对比, 方案对比, PRD对比, 招投标文件对比, 制度新旧版本对比, 供应商方案比较, 差异点, 共同点, 冲突点, 新增删除修改, 横向比较, compare documents, document comparison, version comparison, diff, conflict clauses, or vendor comparison.

composiohq Skill

One CLI for all of Google Workspace — Drive, Gmail, Calendar, Sheets, Docs, Chat, Admin, and more. Dynamically built from Google's Discovery Service. Use when an agent needs broad Google Workspace access with 100+ built-in agent skills.

benknightdark Bundle

Use this skill when the user needs to establish, review, or improve an ISO/IEC 27001 ISMS, perform information security risk discovery, define scope, create an evidence matrix, conduct a gap analysis, draft a Statement of Applicability, prepare for an internal audit, or create an improvement plan. Use neo-iso-27701 when the main concern is PII, privacy management, or PIMS. Do not use this skill for legal advice or certification guarantees.

mauricioquezadahaintech Bundle

Initialize a new Karvey spec. Creates the directory structure, spec.json, and registers the Epic in ClickUp (or PLAN.md if not using ClickUp). Use after karvey-grill or when starting a new feature. Triggers include "karvey init", "iniciar spec", "init spec", "nueva feature", "new feature", "nuevo cambio", "new change", "spec-driven", "SDD", "kiro", "cc-sdd", "gstack", "Garry Tan", "PRD", "iniciar proyecto spec-driven", "start spec-driven project", "nuevo método", "new method", "scaffolding".

mauricioquezadahaintech Skill

Pre-spec interrogation. Interviews the engineer relentlessly about their problem before writing any spec. Use at the start of every new feature or initiative — before karvey-init. Triggers include "grill me", "entrevístame", "interview me", "quiero especificar algo", "I want to spec something", "tengo una idea", "I have an idea", "necesito una feature", "I need a feature", "spec-driven", "SDD", "kiro", "gstack", "Garry Tan", "office hours", "producto 10 estrellas", "10-star product", "reframe", "PRD", "método de desarrollo", "development method".

mauricioquezadahaintech Skill

Convert existing specs from Kiro (cc-sdd) or gstack into the Karvey method's `docs/spec/` structure. Maps requirements/design/tasks into Karvey's prd.md, requirements.md, architecture.md, tasks.md + spec.json/project.json. Cross-cutting support skill — does NOT advance any change's phase. Triggers include "karvey import", "import kiro", "kiro to karvey", "migrate kiro", "migrar kiro", "convertir kiro", "import gstack", "gstack to karvey", "migrate gstack", "convertir gstack", "convert specs", "importar specs".

mauricioquezadahaintech Skill

The iteration engine of the Karvey Method. Reads the change's findings inbox, classifies each finding (bug / spec-gap / emergent) and routes it to the right feedback edge — incident tracker + QA micro-loop, spec-revision (re-open requirements), or the discovery backlog. Turns Karvey from a linear pipeline into a spiral so nothing gets dropped. Triggers include "karvey iterate", "iterar", "iterate", "spec cambió", "spec changed", "salió un bug nuevo", "new bug", "qué hago con esto", "triage findings", "route findings", "loop", "reabrir requirements", "reopen spec", "el spec no estaba bien", "feedback loop", "afán".

guillermomurillo Skill

Take a finished feature branch from "I think I'm done" to "PR open with the right body that will close the parent PRD on merge." Verifies the branch is shippable, inventories slice commits and their parent PRD via `## Parent` walks, runs `/code-review` as a gate, drafts a PR body with `Closes

guillermomurillo Skill

Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

guillermomurillo Skill

Implement a piece of work based on a PRD or set of issues.

guillermomurillo Skill

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.

guillermomurillo Skill

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X". Also invoke when running as the review gate inside `/ship`, when confirming a branch is ready to merge, before opening a PR, or when the user says "review this branch", "check the diff", "is this ready to ship", or "gate-check this".

jerseycheese Skill

Periodic and on-demand maintenance pass over a repo's open GitHub issue backlog. Re-labels miscategorized or unlabeled issues (bug/enhancement/question/invalid/duplicate) and bug lifecycle labels (needs-repro/needs-info) following the same decision logic as Anthropic's own dogfooded triage-issue command; re-scores every open issue with prioritize-issues' value/effort/ age rubric and writes the resulting priority:high/medium/low/post-mvp label; fills in missing sizing labels (complexity/model-power or the repo's equivalent) where the repo documents a convention for them; applies mechanical plain-language fixes (AI-tell swaps, filler removal) to issue title/body via the plain-language-audit skill and surfaces jargon/verbosity/tone judgment calls for review. Auto-applies high-confidence changes, flags ambiguous ones in a single tracking issue. Unlike prioritize-issues (read-only ranked report) or analyze-issue (single-issue technical spec), this skill WRITES to issues. Needs no repo clone — GitHub issue metadata

jerseycheese Skill

Analyzes all open GitHub issues to identify the highest-priority candidates for implementation. Scores by value, effort, age, and roadmap alignment. Produces a ranked top-5 with detailed technical specs for the top 3. Use when planning what to work on next, triaging a backlog, or preparing for a sprint. Trigger on phrases like "what should I work on", "prioritize my issues", "what's the highest value issue", "triage my backlog", "help me pick the next issue", "what's worth doing next".

velcrafting Bundle

Scout price discrepancies between Polymarket and Kalshi for discovery and comparison. Read-only; no execution.

dlt-hub Skill

The guided entry point for dltHub workbench use cases — ingestion from APIs, data exploration, transformations, deployment, data quality. Use when the user names a use case or wants to be oriented before starting: 'I want to ingest from Stripe', 'show me how to go from data to dashboard', 'take me through the full workflow', 'explore the workbench', 'what can I do with dlthub', 'give me a quick start', 'show me a demo', 'walk me through ingestion to visualization', 'I want to try everything end-to-end', 'teach me dltHub'. Do NOT use when the user is asking what's available or where to start in general — use the `dlthub-router` skill (in init) for capability-discovery questions ('what can you do', 'what toolkits are there', 'I'm new to dlthub'). Do NOT use when the user already has a specific task underway (debugging, adding an endpoint, deploying).