Product & Planning

clawic Skill

Prepare approval-gated Need Route Lab opportunities for docs, report, backlog, or issue promotion without publishing directly.

aresbit Bundle

HarmonyOS/OpenHarmony System Ability Manager (SAMgr) daemon domain expertise. Covers SA architecture, lifecycle management, IPC/RPC communication patterns, service registration/discovery, source code structure, and API reference. Use when: (1) Working with OpenHarmony SAMgr / systemabilitymgr_samgr code, (2) Questions about SA lifecycle, daemon startup, or boot sequence, (3) Implementing or debugging IPC/RPC Proxy/Stub patterns for system services, (4) Understanding SA registration (AddSystemAbility, GetSystemAbility, LoadSystemAbility), (5) Analyzing SAMgr crash recovery, on-demand loading, or distributed SA routing, (6) Navigating the systemabilitymgr subsystem source tree.

aresbit Bundle

Electron application reverse engineering — ASAR unpacking, webpack bundle analysis, auth/payment logic discovery, IPC channel mapping, and client-side authorization bypass analysis. Use when the user needs to: reverse engineer an Electron app (.deb/.dmg/.exe), analyze auth/subscription/license logic in Electron apps, map IPC channels between main and renderer processes, identify client-side enforcement vulnerabilities (CWE-602), or perform security audit of Electron-based desktop applications for CTF or research.

3a2dev Skill

Create a new Ansible playbook. Triggered by /new-playbook. Runs discovery to find existing roles and collections, then collects path, filename, target hosts/groups, and roles to include. Generates a complete playbook with header, vars block, pre/post tasks, roles section, error handling, and tags. Shows summary before writing. Never overwrites existing files without confirmation.

3a2dev Bundle

AI-assisted Ansible authoring toolkit for Claude Code. Scaffolds, reviews, and updates playbooks, roles, collections, and ansible.cfg files following production best practices. Sub-commands: new-playbook, review-playbook, update-playbook, new-role, review-role, update-role, new-collection, review-collection, update-collection, new-conf, review-conf, update-conf. Runs discovery (CLAUDE.md to ansible.cfg to README to filesystem) at the start of every command.

avyayalaya Bundle

Use when decomposing a vague problem into a structured problem statement, identifying who has the problem and why it matters, sizing the opportunity, mapping constraints, prioritizing across multiple problems, or producing a Problem Definition Document that feeds into Discovery, Competitive Analysis, or Spec Writing. Encodes Problem Definition Canvas, 5 Whys Root Cause, JTBD Problem Framing, Opportunity Sizing, Problem-Solution Fit Assessment, Constraint Mapping, Stakeholder Impact Matrix, and ICE/RICE Prioritization.

avyayalaya Bundle

Use when building product strategy, roadmaps, or strategic plans — vision articulation, strategic bet definition, roadmap sequencing, resource allocation, portfolio planning, or quarterly/annual planning. Encodes bet-sizing, option-value sequencing, strategic tension surfacing, and explicit deprioritization. Produces a strategy document, not a feature backlog.

avyayalaya Bundle

Use when synthesizing user research, analyzing interview data, conducting discovery sprints, evaluating evidence quality across sources, or building research-backed feature hypotheses

avyayalaya Bundle

Use when building product positioning, crafting strategy narratives, preparing stakeholder pitches, writing launch narratives, or constructing the 'why now' story for a product or initiative. Encodes Narrative Arc Construction, April Dunford-inspired Positioning, Why Now analysis, Audience Adaptation, Evidence-Narrative Integration, Objection Anticipation, Competitive Narrative Analysis, and Narrative Testing. Produces a Strategic Narrative Document.

avyayalaya Bundle

Use when navigating organizational alignment — stakeholder mapping, influence analysis, coalition building, decision archaeology, cross-functional alignment, executive buy-in, or any situation where the path to a decision runs through multiple people with different interests. Produces a stakeholder alignment strategy, not a RACI matrix.

netresearch Bundle

Use when writing, configuring or running Behat integration tests for Oro Commerce 6.1 bundles against a LOCAL app — suites, contexts, elements, page objects, Alice fixtures, `bin/behat`. Covers auto-discovery vs `symfony_bundle` registration, `shared_contexts`, `behat.yml.dist` vs `behat.yml`, `--strict`/`--consumers`/`-s`, `@fixture-Bundle:file.yml`, `oro_behat_extension`, `OroMainContext`, feature-tag mocking, `config_behat_test.yml`, Mink, ChromeDriver, isolators. Triggers on "suite shows 0 features", "element not found", "step undefined", "fixture not loading".

netresearch Bundle

Use when a Behat scenario in Oro Commerce 6.1 fails, hangs or flakes — element not found, intermittent runs, AJAX races, waitForAjax with fetch/XHR, step discovery (`-dl`/`-di`), snippets, verbosity, ScreenshotTrait, `And I wait for action` blocking CI, var/log forensics for hidden 500s, Xdebug across split CLI + PHP-FPM. Also without the word "behat": step definitions, feature files, Mink, Gherkin.

owasp Skill

Server-Side Request Forgery (SSRF) testing skill with focus on Azure metadata services and internal network pivots. Covers discovery, bypass techniques, and Azure-specific exploitation (IMDS, Managed Identities).

pariyar07 Bundle

Register existing Markdown knowledge vaults for machine-level discovery so cold agents can find long-term knowledge from any workspace. Use when checking, adding, updating, repairing, or removing global vault discovery.

pariyar07 Bundle

Create, audit, or improve Obsidian Kanban work boards and Dataview dashboards for durable project, roadmap, evaluation, implementation, QA, or recurring workstream tracking inside an agent-maintained vault.

pariyar07 Bundle

Create or update workspace-level instruction files for code repositories or ordinary project folders, including AGENTS.md, CLAUDE.md, GEMINI.md, local override files, and Ariadne vault-link blocks. Use when a user wants to initialize, repair, or refresh workspace instructions, connect a workspace to a registered Ariadne vault or scope, or make instructions portable across Codex, Claude Code, Gemini CLI, and other agent runtimes without duplicating global discovery.

probabl-ai Skill

Source the next ML experiment proposal by **reading the audit digest** at `scratch/audit/<stem>/audit.md` (produced by `audit-ml-pipeline` at § 4 record-outcome). For every row in the digest's `## Checks summary` whose `severity` is `issue` or `tip`, follow the row's `documentation_url` to draft a Backlog row whose `Item` is the mitigation the docs recommend. The `## Metrics summary` provides context for the human summary paragraph but does not drive Backlog rows on its own. Returns the enriched Backlog rows + a one-paragraph summary back to `iterate-ml-experiment`, which writes the rows into `JOURNAL.md` and re-presents the sourcing menu so the user can promote a `B<N>` row. Stops at "Backlog enriched, summary returned"; never writes a per-experiment design note, never picks the "winning" finding — the user picks via `B<N>`. TRIGGER when: `iterate-ml-experiment` is picking a sourcing strategy and the user picks `skore` from the menu; the user says "mine the report", "what does skore see?", "fill the backlog

onshoreoutsourcing Bundle

Analyze coverage of business requirements across feature plans, wave plans, and implementations to ensure completeness. Creates traceability matrices mapping requirements to features/waves/user stories, identifies uncovered or partially covered requirements, detects orphaned features, and validates acceptance criteria. Use after feature planning, before wave design, during epic reviews, for stakeholder reporting, or when validating requirement coverage.

onshoreoutsourcing Bundle

Track and analyze implementation velocity metrics (actual vs estimated hours, defects per wave, test coverage trends, completion rates) to provide data-driven estimates for remaining work. Records wave completion metrics, calculates team velocity, identifies quality trends, predicts completion dates, and generates velocity dashboards. Use after wave completion, before epic planning, for sprint reviews, stakeholder reporting, or process improvement analysis.

rp7o Skill

Interactive product discovery — what are we building, who is it for, and what does v1 look like. Use when starting product exploration, adding a new feature, revisiting scope or requirements, or when the user says "discover".

sjunepark Bundle

Review completed code changes, roadmap or specification implementation, architecture, technical choices, or overengineering.

sjunepark Bundle

Design or audit AGENTS.md and tool-specific instruction hierarchies for nested scope, conflicts, legacy or cross-tool migration, bloat, discovery, or precedence failures.

tmchow Skill

Investigate open questions through parallel research — prior art, constraints, competitive analysis. Triggers: "research this", "investigate questions", "resolve open questions", "look into this", or when a PRD has unresolved questions.

tmchow Bundle

Review PRDs, brainstorm docs, tech plans, design docs, specs, or any planning document for issues. This skill should be used whenever the user wants feedback, critique, or a quality check on an existing planning or requirements document — even if they don't use the word "review." Common triggers include: "review the plan", "check the PRD", "critique my tech plan", "what's wrong with this plan", "poke holes in the requirements", "is this plan solid", "take a look at this spec", "give feedback on the brainstorm", or pointing to a doc file and asking if anything is off. Also triggers after writing a PRD or tech plan (to review what was just created), or when invoked by brainstorming or tech-planning skills. Do NOT trigger for code review (PRs, diffs, source files), writing/creating new plans, debugging, or reviewing non-planning documents (READMEs, CLAUDE.md, test coverage).

tmchow Bundle

Scope-first brainstorming with intelligent routing — assesses complexity upfront (Quick/Standard/Full), then adapts depth accordingly. Handles simple bug fixes in ~2 exchanges and complex features with full PRD ceremony. Triggers: "brainstorm", "create a PRD", "write requirements", "explore approaches", "think through options", or starting a new feature with unclear direction.

tsz-org Bundle

Run a deep DRY + code-hygiene audit of the Rust workspace and turn the findings into verified, deduplicated, hierarchical GitHub tech-debt issues. Use this whenever the user asks to find duplication, code smells, derive/boilerplate bloat, oversized files, or "tech debt"; to tighten the Clippy/lint posture; to mass-file or triage hygiene issues; or to assign Priority/Effort issue Fields across the backlog. Reach for it even when the user only says "clean up the codebase", "find DRY violations", "what should we refactor", or "make issues for the cruft" — it is the right tool for evidence-backed, non-spammy hygiene issue creation.

tsz-org Bundle

Start TSZ work safely in a crowded multi-agent checkout. Use when beginning a TSZ task, resuming a goal, switching or creating branches/worktrees, recovering from a merged or stale branch, checking disk/cache state, picking a roadmap goal, or deciding whether local dirty files belong to the requested work.

tuliosousapro Skill

Instructions for discovery and usage of servers through the official MCP registry. Use when discovering new integrations. For building custom servers, see mcp-reference-servers.

us Skill

Scrape, crawl, map, search, parse, and extract web data with fastCRW — the open-source, self-hostable Firecrawl alternative (single Rust binary, ~14 MB RAM, Firecrawl-compatible /v1 + /v2 API). Use whenever the user needs page content, site-wide extraction, URL discovery, web search, PDF parsing, structured JSON from pages, or change tracking. Also use when the user mentions Firecrawl, Tavily, Crawl4AI, or "scrape/crawl/map/fetch/get the page/read this site/search the web" — crw is a drop-in for the Firecrawl SDKs.

voxpelli Bundle

This skill should be used when the user asks to 'triage unsorted bookmarks', 'clean up raindrop inbox', 'sort unsorted', 'organize bookmarks', 'raindrop triage', 'process bookmark backlog', 'promote triaged bookmarks', 'classify triaged', 'raindrop cleanup', 'deduplicate bookmarks', 'find duplicate bookmarks', 'tag unsorted', 'process raindrop inbox'. Fetches unsorted Raindrop bookmarks, deduplicates by normalized URL, detects research bursts, clusters by theme, proposes vocabulary-grounded tags, cross-references burst topics against Basic Memory, then moves approved bookmarks to AI-triaged. A second invocation with --promote classifies AI-triaged items into AI-sorted (default), AI-gems (golden), AI-archive, or AI-attention.

workshop-gbb Bundle

Convert frontend intent and repository evidence into INVEST-shaped user stories, Given/When/Then acceptance criteria, journey and state maps, and story-to-test traceability. Use this skill when feature discovery, acceptance criteria, Definition of Done, or an implementation handoff is needed.

jamiebrynes7 Skill

Use when writing instructions that guide Claude behavior - skills, CLAUDE.md files, agent prompts, system prompts. Covers what earns a place in a directive, token budgets, compliance techniques, discovery, and skill portability.

jal-co Bundle

A realistic co-founder critic for software/product ideas. Use when the user wants an honest assessment of whether an idea is worth building, to find existing competitors, to size a niche, to pressure-test positioning, or to name a product and check domain availability. Triggers include "is this idea worth it", "ship or skip", "vet my idea", "who are the competitors", "is this niche too small", "is the competition too big", "name this product", "critique my startup idea", or sorting a backlog of ideas into pursue / refine / kill.

storyverse2025 Skill

Use for 7-layer Q&A script framework discovery and project dossier generation.

bholmesdev Skill

Write a PRODUCT.md spec for a significant Hubble user-facing feature, focused only on user experience and observable behavior. Use when the user asks for a product spec, UX spec, PRD, desired behavior doc, or wants feature behavior clarified before implementation.

ninthless Bundle

Research unfamiliar, current, regulated, or platform-dependent domains before product scoping or coding. Use when an app, product, or tool idea depends on industry workflows, business rules, policies, standards, compliance, real-world operations, or expert terminology the user or agent may not know. Trigger for domain maps, hidden requirements, workflow discovery, MVP cuts, risk and validation criteria, and build-ready briefs grounded in current sources. Do not use for routine apps in familiar domains, pure UI implementation, generic market summaries, or clear technical tasks that do not require domain discovery.