Product & Planning

anilcancakir Bundle

Use when investigating a running Laravel application through the agent-mcp read-only MCP tools: inspect the live database schema, run read-only queries to find or count records, read application logs to diagnose a 500, exception, or failed job, check queue backlog, failed jobs, or Horizon, inspect cache or optimization state, or audit routes, schedule, events, config, env keys, and storage. Use whenever the answer depends on live runtime state rather than source code, even when the user does not name the tools. Do NOT use for write operations (insert, update, delete, migrate, schema change) or for projects without the /agent-mcp endpoint; for shell-based one-off calls, use the agent-mcp-cli skill instead.

ansys Skill

Reinstalls the local ansys-api-discovery proto package synced to the current ApiServer branch. Use when: updating proto definitions from ApiServer, refreshing local gRPC stubs after proto changes, syncing ansys-api-discovery with an ApiServer feature branch, or re-running pip install after proto edits.

backlogmd Skill

Use when planning work (to create items and tasks), when starting implementation (to start and work tasks), when completing work (to mark tasks done), or to check backlog status. Manages .backlogmd/ (work/ and z-archive/); no shared manifest or backlog file. Item index.md has metadata, description, and CONTEXT for agents.

a-h-911 Bundle

Transform a project description into a complete, validated, traceable, execution-ready planning and handoff package for Claude Code to implement — requirements, constraints, invariants, assumptions, open decisions, risks, architecture + ADRs, technology comparisons, R&D/experiment plans, a phased roadmap with slices, acceptance criteria, full traceability, and handoff prompts — stored as a relational package (SQLite runtime, canonical JSONL) written only through the Tamheed MCP tools. Use whenever the user wants to plan, scope, spec, or "inception" a project; run an R&D, architecture, or design mission; produce a charter or execution plan; de-risk a build before coding; update a package as execution progresses; or prepare kickoff prompts for Claude Code. Trigger on "plan this project", "turn this idea into a plan", "scope this out", "design before we build", "prepare a handoff", "project charter", or a long pasted project brief — even if the word "Tamheed" is never said.

airtonlira Bundle

Use quando uma necessidade de negócio ou técnica precisar de discovery estruturado em pt-BR e de um prompt de implementação autocontido.

aravindkurapati Skill

Researches computational pathology and health AI literature using HuggingFace Papers MCP and Exa web search. Use when user says "find papers on", "research", "what's the latest on", "literature review", "survey", or asks about methods like MIL, SSL, WSI analysis, attention-based pooling, patch embedding, weakly supervised learning in pathology, or asks about specific tasks like tumor classification, survival prediction, biomarker detection, or lymphoma subtyping. Also activate for: "what has been done on X in comp path", "how do people approach Y in WSI analysis", "find related work for Z". Do NOT use for: general coding help, non-research queries, clinical deployment questions without a research component, or drug discovery / genomics topics outside pathology.

blacklinecloud Bundle

Facilitate EventStorming for domain discovery and DDD-first software design. Use when the user wants to run, structure, or summarize Big Picture EventStorming, Process Modelling EventStorming, Software Design EventStorming, or document-first EventStorming pre-work, or to produce a canonical EventStorming handoff from stakeholder input or business documents.

gaokab Bundle

Customer research skill for planning, listening, and synthesizing — the conversations that move the needle. Use this skill whenever the user mentions customer research, user research, user interviews, depth interviews, listening sessions, discussion guides, interview guides, research plans, qualitative research, screeners, participant recruitment, research synthesis, interview transcripts, codebooks, personas, or research reports. Also trigger when the user wants to talk to customers, conduct discovery research, design a study, run user interviews, or analyze interview data. Covers planning a study, running the conversation, and synthesizing what you heard into evidence-backed reports.

justkurayy Skill

Run an R&D planning meeting on this codebase. Dispatches three Haiku "seats" (Senior Engineer, Security Engineer, Product/UX) to analyze the code in parallel, has them cross-critique each other once, then synthesizes a ranked roadmap of what to build, fix, or improve next. Use when the user invokes /rd-council, or asks "what should we work on / build / improve next", wants a code health + roadmap review, or wants a multi-perspective audit of next steps.

kodenaime Skill

Turns a rough project idea into a developer-ready spec, full blueprint (PRD, TRD, user flow, UI/UX brief, DB schema/ERD, implementation plan), a timeline, and a sequenced set of code-gen prompts for building it. Use this whenever the user is starting a new project, app, or feature from scratch and wants help thinking it through before coding, even if they just describe the idea casually ("I want to build an app that...", "here's an idea I've been noodling on...") without naming the skill. Also trigger on explicit invocation ("use my project spec method", "/spec", "let's spec this out", "run the blueprint process"). Do NOT use this for small, well-defined coding tasks, bug fixes, or requests to modify existing code, this is specifically for the planning phase of a brand-new project or substantial new feature.

kodenaime Skill

Turns a rough project idea into a complete, frontend-ready design package, covering brand direction, user flows, HTML/CSS screen mockups, design tokens, and a component spec. Use this whenever the user wants to figure out branding, visual identity, UI, or user flow for a new project or feature, even if they describe it casually ("I need to figure out the look and feel", "what should this app's UI be like", "help me design the branding"). Also trigger on explicit invocation ("use my design blueprint process", "/design-blueprint", "run the design system process"). Works standalone, or after spec-blueprint if a spec or blueprint doc already exists. Do NOT use this for writing the PRD/TRD, database schema, or implementation plan/timeline, that is spec-blueprint's job, and do NOT use it for small one-off tweaks to an existing design (a color change, a single component fix) where the user is not asking to establish a system.

zeropointrepo Skill

PRD Builder Skill

adobe Skill

Use when authoring or validating an FFCPE (Firefly Creative Production for Enterprise) custom-action catalog-entry.json for the run-workflow service (App Builder actions). Covers installing the Adobe I/O CLI and this plugin, schema shape, org/auth, agent discovery, customActionConfig, validation, workflow usage, and troubleshooting. Use **`aio ffcpe catalog`** to validate/register—never raw curl. Older searches may say **Workflow Builder**; same plugin and topic **`ffcpe`**.

aks-builds Bundle

Spec-driven, BDD-shaped project management for AI agents. Converts natural language proposals into BDD feature files and tracked work items in GitHub Issues, Azure DevOps, Jira, Linear, or GitLab. Use when writing specs, defining acceptance criteria, creating user stories from requirements, or managing a product backlog from natural-language descriptions.

alialavia Bundle

Hypothesis-specific patterns for property-based testing in Python — strategies, RuleBasedStateMachine, settings, and Hypothesis ecosystem gotchas. Use this skill whenever the task involves Hypothesis tests, the `hypothesis` package, `@given`, `st.` strategies, `RuleBasedStateMachine`, `@example`, or any Python property-based testing work. This skill pairs with the core `property-based-testing` skill, which handles property discovery and design — load both together for any Hypothesis task. This skill does not re-derive the workflow; it assumes the core skill is loaded and only covers Hypothesis syntax, idioms, and library-specific patterns.

alialavia Bundle

Find genuine property-based tests for existing code, design new code so properties hold by construction, and diagnose property-test failures — always contract-first, reading the implementation only after properties have been designed. Use this skill whenever the user asks for property-based tests, PBT, QuickCheck-style tests, invariant tests, generative tests, or fuzz tests, in any language (Python/Hypothesis, TypeScript/fast-check, Rust/proptest, Haskell/QuickCheck, Scala/ScalaCheck, etc.). Also use it whenever the task mentions properties, invariants, oracles, generators, arbitraries, shrinking, stateful/model-based testing, or a property test that is failing — even if the user doesn't say "property-based" explicitly. Pair this skill with the library-specific skill (pbt-hypothesis, pbt-fast-check, etc.) when one is available — this skill handles property discovery, design, and failure interpretation; the library skill handles syntax, strategies/arbitraries, and ecosystem-specific patterns. Without this skil

alikmlsipahi Bundle

Turn already-extracted YouTube artifacts (the JSON produced by the youtube-artifact-collector skill) into a structured Module→Feature→Requirement document, with each requirement traced back to a transcript segment. Use when the user wants requirement extraction, feature/product discovery, business-rule extraction, or a spec/requirements document FROM existing artifacts — e.g. "extract requirements from this artifact", "what features does this video demonstrate", "build a requirements doc from this collection". Runs offline by default (Claude-native, no API key); an optional OpenAI engine is available via `--engine openai`. This consumes Skill 1 JSON, not URLs — it does not download videos or transcripts.

bitoex Bundle

Crypto market intelligence, macro indicators, listing-catalog discovery, and BitoPro-relevant news aggregation — strictly scoped to BitoPro-listed spot coins. No API key. Use when: checking Fear & Greed index, global total crypto market cap, BTC/ETH dominance, BitoPro coin market-cap rankings, BitoPro coins on CoinGecko trending list, public-company BTC/ETH holdings, multi-timeframe price-change snapshots for a BitoPro coin (1h / 24h / 7d / 30d comparison), the BitoPro listing catalog with per-pair specs (which coins are currently listed, min/max order size, precision, 掛單上限, maintenance status), or curated cryptocurrency news filtered to BitoPro-listed coins (繁中 + English auto-translated to 繁中). Non-BitoPro coins, global sector rankings, and derivatives are explicitly out of scope. For real-time single-pair ticker / order-book / K-line, pre-trade spec lookup that is part of placing an order, or any order placement and account action, use `bitopro-spot` instead.

bomx Bundle

Run the Distribb 90-Day SEO Sprint - a founder-built 13-week playbook for shipping pre-launch SEO, core pages, a content engine, and a backlink starter stack on the way to compounding organic traffic. Use when the user asks for an "SEO sprint", "90-day SEO plan", "SEO tracker", "SEO roadmap", "where do I even start with SEO", "how do I get my first 1,000 organic visitors", or anything similar. This sub-skill opens the Distribb tracker spreadsheet in the user's browser, walks them through each phase, and hands off keyword research / backlink targets / publishing / Microworkers tasks to the parent Distribb skill.

brandonburrus Bundle

This skill should be used when authoring a new graphspec-conformant OKF knowledge-graph spec bundle, or adding concepts to an existing one, from a product or engineering intent: a feature idea, a system or component design, a requirement, a decision, or a user journey to capture. It applies when the user says "write a spec", "create a graphspec", "document this system as a graphspec", "spec out this feature", "add a requirement/component/decision to the spec", "wire this concept into the graph", or is working inside a directory that already looks like a graphspec bundle (an `index.md` plus `<name>.<type-token>.md` files). It should not be used to implement or build software FROM an already-written graphspec bundle (use follow-graph-spec instead), to author specs in any other format such as a PRD, ADR, or OpenAPI document (graphspec has zero awareness of other spec formats), or to invent node types or relation names outside the closed 13-type/16-relation graphspec vocabulary.

catoncat Bundle

为 browser-brain-loop 项目自动认领 backlog issue / slice。用于用户要求“认领 issue”“自动 claim backlog”“挑一个可并行的 slice 开工”“找下一个可做 issue”时触发。会读取 docs/backlog 和 next-development-slices 文档，优先认领依赖已满足且与当前 in-progress write_scope 不冲突的 open issue。

crafter-station Bundle

Optimizes LATAM hackathon discovery scrapers for the hack0.dev project. Reads every scraper in lib/scraper/sources/, launches one optimizer subagent per scraper in parallel (each iterates 2-3 times with self-scored F1 improvements and edits the file directly), then runs an evaluator that scores all scrapers on Quantity/Quality/Cost/Uniqueness and estimates a confusion matrix, writing the result to SCRAPER_EVALUATION.md. Use this skill whenever the user wants to improve scraper coverage, reduce false positives, add geographic or thematic queries, tune the discovery pipeline, rank scrapers, update SCRAPER_EVALUATION.md, or says anything like "optimize scrapers", "scraper quality", "scraper evaluation", "mejorar scrapers", or "falsos positivos en los scrapers". Trigger even if they only mention one scraper by name.

curiousdima Skill

Start a spec-driven development project constitution by collaboratively drafting specs/mission.md, specs/tech-stack.md, and specs/roadmap.md from stakeholder input and, for existing projects, current codebase reality. Use when a user asks to create, initialize, adopt, or bootstrap an initial project constitution, mission, tech stack, or roadmap for spec-driven development, including greenfield projects and existing projects without a constitution.

curiousdima Skill

Create a feature specification for the next roadmap phase in a spec-driven development project. Use when a user asks to write, create, draft, start, or initialize a feature spec from specs/roadmap.md, including creating a branch and producing specs/YYYY-MM-DD-feature-name/plan.md, requirements.md, and validation.md guided by specs/mission.md and specs/tech-stack.md.

daniel-ddtech Skill

Research what real people say about a topic, product, company, or problem by finding Reddit discussions and extracting structured comments or reviews from supported community platforms. Use for customer-voice research, pain-point mining, sentiment and theme analysis, competitive intelligence, objection discovery, Reddit research, discussion extraction, review analysis, or when a user provides a supported discussion URL and wants its comments. Do not use for general web crawling, arbitrary page extraction, or documentation search.

datagallery-ai Skill

Answer data questions from quick metric lookups to full investigations and stakeholder-ready reports.

dekan-aleksandr Skill

A routed repertoire of ~90 scientific thinking operators for biological research agents - visual reasoning, detectability and information budgets, search reframing, causal identification, competing explanations, observation and selection processes, pipeline artifact diagnosis, effort allocation, and confirmation hygiene. Use when a screen returns null or weak results, a result looks too good, search has stagnated, a causal claim is being made, an anomaly needs explaining, a pipeline is suspected, or a lead is about to be escalated. Load the smallest relevant section, activate 1-3 operators, then return to the research loop.

dekan-aleksandr Skill

Operate as a research director making original discoveries from a given biological question and dataset. Use when the task is open-ended scientific research, exploring omics or experimental data for findings, hypothesis generation and testing, screening a large candidate space of genes, variants, features or compounds, investigating an anomaly, or deciding what experiment or analysis to run next. Triggers on "make discoveries", "explore this data", "find something in", "what's in this dataset", "research this question", "generate hypotheses", "why is this result happening".

devotts Bundle

Harness-aware intent compiler: turns a rough ask into an optimized, context-grounded prompt — routed to the right *-it skill with exactly the slots that target parses, nothing it already owns. Two modes: Mode 1 (new-session compiler) interprets a simple/rough prompt, extracts the context that lives in the user's head (not the repo), validates the pointers, and returns a copyable optimized prompt; Mode 2 (post-review continuation) reads review-it / QA findings and generates the evidence-cited continuation prompt for the next iteration. Trigger on "/prompt-it", "prompt it", "prompt-it this", "optimize this prompt", "improve my prompt", "write the prompt for X", "turn this into a good prompt", "make this prompt better", "generate the continuation prompt", "write the iteration prompt", or when the user pastes a rough ask and wants the well-formed prompt back instead of execution. NOT for post-planning handoffs of a finished PRD/spec — that is /next-session-prompt; prompt-it compiles NEW intent (Mode 1) or post-RE

devotts Bundle

Package a Claude/agent skill (or a whole plugin) into a public, installable, marketing-ready repo — the exact recipe behind the DevOtts *-it family (plan-it, build-it, review-it, prompt-it, conclude-it). Takes a local skill folder (or an idea for one), genericizes it (two-pass sweep proving zero personal/project references), applies progressive disclosure (thin SKILL.md + references/ legs), scaffolds the standard repo (root SKILL.md crawler manifest, Claude Code plugin + marketplace manifests, marketing README with a pain-first headline + hero SVG + per-agent install matrix + 18-row compatibility table, CHANGELOG, QA walkthroughs, MIT LICENSE), validates everything mechanically (JSON/YAML/SVG parse, version consistency, script smoke tests), then ships: gh repo create → main → discovery topics → tagged release with zip — and verifies installability with the skills CLI before claiming anything. Trigger on "/skill-it", "skill it", "package this skill", "ship this skill as a plugin", "create the plugin repo for m

dhzrx Bundle

Generate comprehensive Product Requirements Documents with AI PM best practices for new features and products

goldlegendw80 Bundle

Create a COMPLETE, render-safe brand kit for ANY brand under brand/<id>/ — design.md + the editorial engine (editorial/) + an engine-agnostic voice lock + outlined logos + palette-driven static & dynamic backgrounds + device mockups + stickers + a brand board & sheet + a brand.json manifest. The kit is consumed by /use-brand, which turns it into any deliverable — website, slide deck, PDF, social/OG cards, marketing copy, dev tokens, or a video (handed to /make-video). Two modes - GENERATE from scratch via an interactive discovery flow + a multi-direction inspiration board the user picks in the browser, or IMPORT an existing brand by crawling its portal. Self-contained - every generator reads bundled templates in $SKILL_DIR/assets/, never a reference kit. Trigger - /make-brand.

gutomec Bundle

Autonomous Agile Project Lifecycle — transforms a raw idea into a deployed project following the AIOX Agentic Agile process. Runs 5 phases autonomously: Discovery (web research), Planning (PRD + Architecture + Frontend Spec), Sharding (stories in waves), Development (build + QA loop), Delivery (deploy + release notes). Decides stack, prioritizes features, writes code, reviews quality, and ships — all without human intervention. Supports greenfield and brownfield projects. Use when: starting a new project from scratch, adding features to existing project, or wanting full agile cycle automated.

hackyhunter Skill

SSSNACK discovery

harleycoops Bundle

This skill should be used when the user asks to "create a math animation", "animate a mathematical concept", "generate Manim code", "visualize [topic] with animation", "explain [concept] visually", "create an educational video", "build a Manim scene", or mentions "reverse knowledge tree", "prerequisite discovery", or "verbose prompt generation". Provides a complete six-agent workflow for transforming any concept into professional Manim animations through recursive prerequisite discovery.

harzva Bundle

Use when writing, normalizing, splitting, auditing, or updating roadmp/roadmap Markdown files in the Just-DDL roadmpxx.md style: structured milestones, task files, checkbox governance, evidence-based completion, staged audits, candidate tables, assumptions, blockers, and Chinese production-roadmap prose.