Product & Planning

jawhnycooke Bundle

Guides creation and organization of Claude Code plugin directory structure, including the plugin manifest (plugin.json), component directories (commands, agents, skills, hooks), MCP server configuration, auto-discovery mechanism, portable path references with ${CLAUDE_PLUGIN_ROOT}, and file naming conventions. Activates when the user asks to create a plugin, scaffold a plugin, organize plugin components, set up plugin.json, or needs guidance on plugin architecture.

dasein108 Skill

Use to produce and publish a chosen Slope Studio backlog bet, then bind the run to the marketing journal so it can be measured later.

dasein108 Skill

Use when deciding what short video to make next for a Slope Studio channel: generate falsifiable viral bets and persist them to the marketing backlog.

dasein108 Bundle

Umbrella orchestrator for a Slope Studio channel's viral-growth loop. Use when the user wants to RUN THE WHOLE ideate→deploy→measure→learn cycle, or doesn't know which step they need, or wants to READ channel state / PICK the next bet / WRITE a growth brief (journal · backlog · report all live here). It composes the per-step lego-block skills (marketing-ideate, marketing-deploy, marketing-measure-learn) and the hands-off driver (marketing-autopilot). For one creative step, invoke that step's skill directly.

dasein108 Skill

Use to produce + publish a chosen backlog bet and bind it to the journal so it can be measured later. Calls the film-maker skill to render+upload, sized to the per-video budget, then links the run. One lego-block of the growth loop. Fed by the backlog pick (marketing-guru); precedes marketing-measure-learn (after a maturation wait).

dasein108 Skill

Use when deciding WHAT short video to make next for a channel — generate falsifiable viral bets (idea + hook + assumption + goal + theme). The AGENT does the ideation (web-search current trends + recall the channel's past winners), then persists each bet to the backlog. One lego-block of the ideate→deploy→measure→learn growth loop. Pairs with marketing-guru, which picks the next bet from the backlog and reads/writes channel state.

dasein108 Skill

Use SPECIFICALLY for hands-off SCHEDULING of the growth loop — the unattended driver that keeps a channel turning on a cron/interval with no operator in the seat. Each tick it asks the engine what's due (measure matured videos / reflect / refill the backlog / produce the next bet) and does that ONE action, handling the deferred-measurement timing automatically — then defers the actual step-level work to the per-step skills. Set it on a recurring schedule (the /loop or /schedule skill, or cron). For a single manual step, invoke that step's skill directly instead.

lythos-labs Bundle

Declarative skill deck governance. `deck link` reconciles the working set to match skill-deck.toml — deny-by-default removes undeclared skills. DEFAULT patterns: PHASE SWITCH via separate deck files (deck link --deck phase<N>.toml), SEED bootstrap (minimal deck → agent self-expands via deck add + curator discovery). Always restores parent deck. Zero state pollution between phases. INNATE FIRST: after compaction, session reload, or skill refresh — read every innate skill's full SKILL.md before any tool skill. Innate = eagerly loaded, always full context. Tool = lazy, read only on trigger. CRITICAL when writing a deck for others: verify every locator path against the REAL repo structure before publishing.

lythos-labs Bundle

Register tasks BEFORE fixing bugs. Close epics when work is done. Always move state through the CLI — never mv files by hand: CLI moves write Status History, manual moves create probe mismatches. Never leave state drift for the next agent to discover via git log. GTD (Getting Things Done)-style governance across ADR (architecture decision record) / Epic / Task / Wiki. Zero-knowledge (ZK) review = a fresh-agent pass over a task card (WHAT/WHY/HOW) before assignment, so an executor with no conversation context can still run it. `cortex probe` = drift detector: stale backlog, drifted epics, history mismatches vs git reality. **Task-git discipline**: one task = 2-5 commits (core, tests, docs, trailer); every commit carries its full TASK-id (see ID Format — truncated IDs are not addressable).

hartmut-ux Skill

Litigation war room AI. Organise evidence, build chronologies, draft briefs, create visual timelines. Structure case narratives. Prepare strategy memos. Generate litigation-ready documents that persuade judges. Organise discovery, deposition summaries."

hartmut-ux Skill

Litigation war room AI. Organise evidence, build chronologies, draft briefs, create visual timelines. Structure case narratives. Prepare strategy memos. Generate litigation-ready documents that persuade judges. Organise discovery, deposition summaries."

aspenkit Bundle

Deterministic repo analysis — language/framework detection, structure mapping, domain discovery, health checks, and import graph integration

onekeyhq Skill

Test Designer - 从 PRD 到可执行测试。分析用例 → 引导录制 → 生成测试脚本。 Triggers on: /onekey-test-designer, "设计用例", "写用例", "新增测试".

romiluz13 Skill

Builds a complete meeting brief before any sales call. Never walk in blind. Trigger with "prep me for [company]", "meeting prep for [company]", "call prep [company]", "prepare for my call with [company]", "going into a call with [company]", or "what should I know before [company]".

aws-samples Bundle

EKS cluster reconnaissance and environment discovery — reports the raw FACTS of a cluster and its environment. Detects compute (Karpenter, MNG, Auto Mode, Fargate, nodes/AMI), networking (VPC/CNI, subnets, load balancers, DNS), security facts (auth mode, IRSA/Pod Identity, RBAC, encryption), add-ons/Helm, observability, workloads (Deployments, StatefulSets, PDBs, HPAs), storage (CSI, StorageClasses, PVs, backup tooling), IaC (Terraform, CDK, eksctl), CI/CD (Actions, ArgoCD, Flux), and cluster insights. Triggers on "what am I running", "tell me about my setup", "what version am I on", cluster inventory, or documenting current state before an upgrade/migration/design. Reports facts only; it does not score, rate, plan, or recommend, and overlapping facts with other skills is fine. Route elsewhere for a judgment or artifact — readiness scoring/deprecated-API checks (eks-upgrade-check), GREEN/AMBER/RED audits (eks-operation-review), design docs/diagrams (eks-design).

aws-samples Bundle

EKS security and compliance assessment — 7-layer hardening stack, CIS/HIPAA/PCI/FedRAMP/SOC2/GDPR audit prep, and 30/60/90 roadmap. Covers OS/AMI selection (Bottlerocket, AL2023, RHEL, Ubuntu), identity (EKS Pod Identity vs IRSA, Access Entries vs aws-auth), workload security (Pod Security Admission, Kyverno/OPA, NetworkPolicy, Security Groups for Pods), image supply chain (ECR scanning, Cosign/Notation signing), runtime detection (GuardDuty, Falco), audit logging, etcd / secrets encryption, and compliance accelerators (Config conformance packs, Security Hub, Audit Manager maintenance-mode status). Triggers on CIS Benchmark, HIPAA, PCI-DSS, FedRAMP, SOC 2, GDPR compliance, cluster hardening, audit-prep, or any regulated-workload assessment. Does not cover non-EKS platforms (ECS/ROSA), account-level security with no EKS angle, or GenAI-workload security.

bartolli Skill

This skill should be used to write wiki stories — Gherkin scenarios plus a first slice list — from either input: the current conversation, synthesized into a thin `plan/plan-{name}.md` with one `plan/{name}/story-N-{slug}.md` per story; or a promoted intent, elaborated into one story under the active plan with the intent linked and `promoted_to` reported back. Default `triage_state: needs-triage`. Does NOT interview — if intent is unclear it suggests `$intent` and stops. Use when the user says "turn this into a plan", "draft a PRD", "$to-stories", "write up what we discussed", "synthesize this into stories", "write the story for intent X", or "elaborate intent X". Reads `glossary.md` and existing ADRs to use the project's vocabulary correctly.

questnova502 Bundle

Universal AI-powered web scraper for any platform. Scrape data from Instagram, Facebook, TikTok, YouTube, LinkedIn, X/Twitter, Google Maps, Google Search, Google Trends, Reddit, Airbnb, Yelp, and 15+ more platforms. Use for lead generation, brand monitoring, competitor analysis, influencer discovery, trend research, content analytics, audience analysis, review analysis, SEO intelligence, recruitment, or any data extraction task.

rcarmo Bundle

Add or validate SCRIPT_JDOC metadata on skill-shipped and workspace scripts so list_scripts and future script discovery can find them reliably.

viewway Skill

当需要编写PRD、跟进开发进度、进行产品验收时使用

viewway Skill

当需要制定产品规划、审批PRD、决策需求优先级时使用

studio-moser Skill

Use when Harness has been installed but this developer still needs a personal agents-repo relationship, portable links, runtime capability discovery, a model rubric, or optional Shelby enrichment configured.

arboraistudio Skill

Plan customer discovery, user interviews, first-user acquisition, founder sales, cold outreach, rejection handling, customer conversion, and learning from prospects.

helius-tech-labs Bundle

Build Solana applications combining OKX DEX aggregation, token intelligence, and market data with Helius infrastructure. Covers DEX swaps (500+ liquidity sources), token discovery, smart money signals, meme token analysis, transaction submission via Sender, fee optimization, shred-level streaming via LaserStream, and wallet intelligence.

pedronauck Bundle

Creates a Product Requirements Document plus its companion user-story catalog (_user_stories.md) through interactive brainstorming with parallel codebase and web research. Use when starting a new feature or product, building a PRD, brainstorming requirements, or cataloging user stories and edge cases. Do not use for technical specifications, task breakdowns, or code implementation.

pedronauck Bundle

Creates a Technical Specification plus its companion test contract (_tests.md) by translating PRD business requirements into implementation designs through interactive technical clarification. Use when a PRD exists and needs a technical plan, when technical architecture decisions need documentation, or when a feature needs its exhaustive test-case catalog. Do not use for PRD creation, task breakdown, or direct code implementation.

risukisu Bundle

Strategic SEO planning for new or existing websites. Industry-specific templates, competitive analysis, content strategy, and implementation roadmap. Use when user says "SEO plan", "SEO strategy", "SEO planning", "content strategy", "keyword strategy", "content calendar", "site architecture", or "SEO roadmap".

lqf0624 Bundle

Problem-discovery skill for systems, networking, and AI research. Use when the user has a broad area and is willing to choose among paper-sized problems. Do not use it to force a topic change when the user has fixed the topic and needs a new method; use method-synthesis instead.

atrislabs Skill

Atris workspace navigation for atris repos, TODO files, tasks, MAP.md, backlog, and where-is-X questions. Use when navigating an Atris workspace, finding files via MAP.md, or checking task state.

tuliosousapro Skill

Creates an llms.txt file from scratch based on repository structure. Use when configuring LLM discovery files. For updating existing configurations, see update-llms.

us Skill

Scrape, crawl, map, and search the web using fastCRW's native /v1 API. Use when the user needs web page content, site-wide extraction, URL discovery, or web search results. Single binary, 14 MB RAM; /v2 exists separately for Firecrawl migration.

qualcomm Skill

Canonical PowerShell block that detects the Windows ARM64 build toolchain (host arch, Visual Studio path, ARM64-target cl.exe, MSBuild, dumpbin, vcvars script) and caches the result to .copilot/state/wos-toolchain.json for reuse across agents/phases. Load when any wos-* agent needs to build/validate ARM64 artifacts. Cached results survive across tool calls within a session; re-run only if the cache is missing or stale.

alexpialetski Skill

Close a story end-to-end — flip its status to a terminal value and reconcile every downstream artifact in one pass: the backlog Status cell, the {{DOCS_DIR}}/queue.md row, the parent epic table (when the project uses epics), then a queue-audit reconcile. Use whenever the user says "close", "mark done", "ship", "finish", "complete", or "resolve" a story / ticket / backlog item, or moves work to a terminal state (done, done-no-promote, abandoned, absorbed). Reach for this instead of hand-editing the story file alone — a half-applied close (status flipped but queue/backlog/epic left stale) is exactly the drift this skill exists to prevent. Works for single-root and monorepo projects.

alexpialetski Skill

Author or update product stories (a.k.a. planning docs, backlog items, tickets, specs) as Markdown under {{DOCS_DIR}}/stories/ with a YAML frontmatter contract (id, status, impact, urgency, depends_on, tags, openspec). Use this whenever the user is creating a story, reprioritising work, writing acceptance criteria, linking a story to OpenSpec or an ADR, or editing anything under {{DOCS_DIR}}/stories/ — even if they call it a spec, ticket, backlog row, or planning doc.

alexpialetski Skill

Reconcile the dependency graph, pick-next queue, and backlog status across {{DOCS_DIR}}/stories/, {{DOCS_DIR}}/queue.md, and {{DOCS_DIR}}/backlog.md. Use after adding or editing a story (especially one with depends_on), after reshuffling priorities, or when the user asks "what can I work on next", "what's unblocked", "sanity-check the queue", "check my story dependencies", "fix the queue order", or "what parallel work is ready". In Agent mode (the tool can write files), apply objective mechanical fixes in the same turn and report what changed; in Ask / read-only mode, emit a proposal instead. Stop and report — never guess — on directed cycles, unknown depends_on ids, duplicate ids, or ambiguous editorial reorders.

alexpialetski Skill

After a design, research, business, or prioritisation thread, evaluate whether the conversation produced durable insight worth capturing in {{DOCS_DIR}}/, then propose only the artifacts that are clearly justified (ADR, research note, reference doc, business update, story, backlog/queue edit). Use when the user says "wrap this session", "propose docs artifacts", "what should we capture", "summarize this into docs", "end-of-session", or similar close-out phrasing. If nothing warrants capture, say so in one sentence and stop. Never write files unless the user explicitly asks to create or update them in the same turn — propose drafts only.