Product & Planning

jfrog Bundle

Use this skill when the user asks to set up, configure, bind, or connect a package manager (npm, pip, uv, pipenv, maven, gradle, go, docker, helm, ...) to JFrog Artifactory via `jf setup` and `.jfrog/local/package-resolution.json`; when a workspace manifest exists with no matching binding entry; or when a session hook reports package-manager config missing. Skip when the binding already has the same repo key. Never pick a repo by discovery; use resolver output only (unless the user names or asks to browse repos). On unresolved or failed setup, ask with the failure verbatim — never switch servers. NOT for installing packages, general Artifactory repo operations (use the base jfrog skill), or MCP server setup (use jfrog-mcp-management).

jiayaoqijia Skill

Generate a comprehensive security report with executive summary, detailed findings, remediation roadmap, and compliance mapping. Supports markdown and HTML output.

joelborellis Skill

Verifies that Claude Code can detect and load Skills. Use this to test skill discovery.

metronome-industries Bundle

Guides migration from Stripe Usage-Based Billing (Billing Meters and Subscriptions) to Metronome. Covers scoping and discovery (metering, pricing models, credit grants, dashboards), design (concept mapping, billable metrics, group keys, rate cards, integration pattern selection), implementation (product catalog setup, event ingestion, customer creation, contracts, credit grant migration, alerting), testing (parallel run parity checks, sandbox validation), and production cutover (legacy customer migration, rollback planning). Use when planning, executing, or troubleshooting a migration from Stripe UBBv1 to Metronome — including scoping the effort, mapping Stripe objects to Metronome equivalents, designing billable metrics and group keys, running parallel validation, migrating credit grants, or cutting over production customers.

mhmzdev Skill

Turn an idea or brainstorm into an actionable execution plan for The Holy Qur'an app with phases, file changes, and machine-checkable success criteria. Use when the user says "plan this", "write a plan", "how should we build X". Writes the plan into docs/exec-plans/backlog/ and registers it in docs/exec-plans/index.md.

mskayyali Skill

Build a Stateful condition inventory for a confirmed system sentence across four related lenses: lifecycle states, failures, interruptions, and surfaces. Use after system-sentence on greenfield or feature-level work when the user needs systematic discovery with evidence, explicit coverage checks, typed relationships, and an optional v0.1 JSON mirror. For existing products, prefer state-audit. Do not treat the four lenses as equivalent state-machine node types or claim exhaustive completeness.

mskayyali Skill

Render an existing Stateful v0.1 condition map as Mermaid, grouping lifecycle states, failures, interruptions, and surfaces while drawing only recorded typed relationships and styling confirmed scope. Use for visual overviews in STATEFUL.md, READMEs, reviews, or stakeholder discussions. Do not invent conditions or relationships, call the result an executable statechart, or render an unreadable 50-node graph without a cut.

ohmyskyhigh Bundle

Create, review, and monitor five-to-ten Twitter/X reply tasks with target discovery through ThreadWave, retry one conclusively undispatched reviewed reply through a fresh exact-action flow, or send one exact final reply to one exact target through a strict dry-run and approval flow. Use for create replies, retry failed replies, reply to several posts, batch reply tasks, engage with posts about a topic, manual Twitter replies, or reply to this exact tweet with this exact text. Do not use for original posts or the daily strategy/plan loop. 中文：用于创建、审核并监控 5 到 10 条带目标发现的推特回复任务、通过新的精确操作流程重试一条已确认未发送的已审核回复、批量回复任务，或在严格 dry-run 和批准后向一个准确目标发送一条准确回复；不用于原创推文或日常策略计划。

peterzat Skill

Test strategy review and design from the perspective of a Principal SDE/T. `/tester` audits the current test strategy and appends a dated finding to TESTING.md. `/tester design` writes (or revises) a durable test-architecture contract in TESTING.md and seeds rollout items in BACKLOG.md. Manual invocation only. Do not invoke automatically.

jrajasekera Bundle

Build, migrate, and debug integrations with the Venice.ai API. Covers OpenAI-compatible chat and Responses, live model discovery and routing, multimodal and file inputs, reasoning, tools, web/X search, image generation and editing, audio, video, embeddings, augment APIs, characters, API-key administration, billing, x402/SIWX wallet authentication, and crypto RPC. Use whenever code calls api.venice.ai, a user asks which Venice model or endpoint to use, or an existing Venice integration may be stale.

jrajasekera Bundle

Build, migrate, debug, and operate integrations with the OpenRouter API. Covers live model and provider discovery, Chat Completions, the stateless Responses API, the Anthropic-compatible Messages API, official SDKs, routing and fallbacks, reasoning, structured outputs, client and server tools, streaming, multimodal inputs, image/audio/video generation, embeddings, reranking, caching, OAuth, administration, observability, privacy, and production error handling. Use whenever code calls openrouter.ai, a user asks which OpenRouter endpoint/model/provider to use, or an existing OpenRouter integration may be stale.

juncoding Skill

Add an MCP (Model Context Protocol) entry point to an existing project scaffolded with nextjs-fullstack-starter. Use when the user wants AI clients (Claude Desktop, Cursor) to query the project's data over OAuth, mentions MCP, wants to expose tools to AI, or invokes /nfs-add-mcp. Wires up /api/mcp/route.ts inside an (mcp) route group, the MCP plugin in Better Auth (the project's OAuth provider), the .well-known OAuth discovery endpoints, a tool registry at src/server/mcp/registry.ts, one example tool, and the migration for the three OAuth tables. Requires Better Auth to be wired — if not, prompts to run /nfs-add-auth first.

juncoding Skill

Add an MCP (Model Context Protocol) entry point to an existing project scaffolded with nextjs-trpc-prisma-starter. Use this when the user wants AI clients (Claude Desktop, Cursor) to query the project's data over OAuth, mentions MCP, wants to expose tools to AI, or invokes /nts-add-mcp. Wires up /api/mcp/route.ts, the MCP plugin in Better Auth (the project's OAuth provider), the .well-known OAuth discovery endpoints, a tool registry at src/server/mcp/registry.ts, one example tool, and the migration for the three OAuth tables. Requires Better Auth to be wired — if not, prompts to run /nts-add-auth first.

sanada123 Bundle

Multi-source skill discovery for OpenClaw, Claude Code, Codex, Cursor, Windsurf, and more. Search ClawHub, GitHub, and npm — then install to every AI platform you use in one command.

signjing Skill

苏格拉底追问型（Socratic）PRD评审技能——只提问、不给结论。以10年B端测试经验的QA工程师视角，逐条阅读PRD功能点，找出"被默认但未明确"的假设，以苏格拉底式追问输出问题并附测试重要性说明。当用户提到苏格拉底评审、追问型PRD评审、Socratic PRD Review、苏格拉底式追问需求、以追问方式审PRD、用提问方式找需求漏洞、QA视角追问PRD、测试视角拷问需求文档时使用。

signjing Skill

5角色PRD评审；同时从产品、测试、后端、前端、运营5个专业视角对需求文档进行独立审查

signjing Bundle

多Agent并行需求评审技能；同时启动3个子Agent分别执行完整性、一致性、可测试性审查，各子Agent内部以5角色视角串行评审；主Agent汇总结果；适用于需求文档评审、PRD审查、方案评审等场景

signjing Skill

结构化多轮需求评审能力；将评审拆解为"完整性→一致性→可测试性"三个独立轮次，每轮聚焦单一维度，适用于需求评审、PRD 检查、需求对齐等场景

signjing Skill

交互细节挖掘型PRD评审技能。以专注交互逻辑测试的QA工程师视角，从7个维度（弹窗行为、下拉联动、操作反馈、异步状态感知、限制条件执行方式、只读与可编辑边界、字段业务语义边界）逐维度扫描PRD，识别"PRD未明确描述"的交互细节遗漏并给出建议补充方向。当用户提到交互细节评审、交互完备性检查、PRD交互遗漏挖掘、交互逻辑审查、B端后台交互细节、Interaction Detail Review、交互细节挖掘型评审、UI交互PRD审查时使用。

spaceyuan Bundle

Use when converting an existing request需求文档 into a structured PRD through AI drafting, user revision, iterative completion, boundary tracking, and convergence checking. Requires a request需求文档 as the input source; do not use for writing a PRD from a blank slate.

wrathza Bundle

Create a new SKILL.md via discovery recap, pattern selection, WebFetch spec fetch, knowledge delta discipline, skill-forge-judge + skill-forge-hitl quality gate. Triggers: create a skill, write a skill, new skill, SKILL.md, build a skill.

accoil Bundle

Write a business case for adding product telemetry and analytics to a product. Produces a concise, stakeholder-ready document explaining what telemetry enables, what you're currently blind to, what's involved in implementation, and the business value. Sits outside the main telemetry lifecycle — use before committing to the technical work. Use when the user asks to 'write a business case,' 'justify analytics,' 'make the case for tracking,' 'telemetry brief,' 'why add analytics,' 'convince leadership about tracking,' or 'analytics ROI.'

adol1111 Bundle

Prepares one selected concrete task for implementation through task-local spec, optional plan, review pauses, and execution handoff. Use when roadmap state is confirmed and the next work is task-local preparation.

adol1111 Bundle

Resolves roadmap-blocking planning ambiguity before roadmap decomposition. Use when goals, constraints, success criteria, or now-vs-later boundaries are unresolved by docs or prompt evidence.

adol1111 Bundle

Routes docs-driven repository work to the correct workflow stage and preserves handoff context. Use when the next step is unclear between bootstrap, clarification, roadmap planning, task preparation, or execution.

agency-shift Bundle

Turn a raw sales, discovery, or kickoff call transcript into a structured project brief with scope, deliverables, deadlines, decision-makers, and open questions. Use whenever the user pastes a call transcript (Otter, Fireflies, Fathom, Zoom auto-transcript, voice memo transcription) and asks for "the brief", "the scope doc", "the SOW input", or "turn this call into a brief". Do NOT use this skill for internal team meeting notes or for one-off conversation summaries — it is specifically scoped to client-facing project briefs that will be sent back to the client for sign-off.

naderelewa Skill

Set up this plugin on this machine, the one-time, gated setup for the only thing here that writes anything outside your project (an optional local event log), plus the one optional integration this plugin can be connected to (read-only issue-tracker reads). Use when the user says "set up the plugin", "run the setup", "turn on the usage log", "is telemetry on?", "what does this record about me?", "stop logging", "delete the log", "remove the config", "connect my issue tracker", "connect Jira", "hook this up to our backlog", or has just installed the plugin. Also handles --verify (re-prove everything, ask nothing) and --uninstall (remove the log and the config, dry-run first). It asks in plain words, walks 5 numbered telemetry gates plus 1 numbered integration offer, verifies each one by running a real command and quoting its real output, defaults every answer to NO, and ends with a proof report that says what is on, what is off, and what it could not verify.

naderelewa Skill

THE front door for product, strategy and go-to-market work, use this when someone wants product work done and has not named a specific verb: "new feature", "write a PRD", "prioritize this backlog", "build the roadmap", "growth plan", "verify the release", "user stories for <company>", "interview case exercise", or any plain-language product ask. It interviews in plain words (company/context → area → output wanted → standalone or handed to engineering), echoes the locked choices back so nothing drifts, then routes to the one verb that does the work with the right context pack attached. Nobody has to know which verbs exist.

naderelewa Skill

Go-to-market and growth planning, GTM here means go-to-market, never a tag-manager container. Use when a growth plan needs building or refreshing: "build the go-to-market plan", "growth plan for <period or launch>", "campaign architecture", "channel plan", "media plan", "tracking planning rows", "update the growth plan after <release>". It resolves which plan document is actually current, takes a FRESH gate-state snapshot before planning a single sentence, builds the plan phase by phase, narrates the campaign architecture per channel and per persona, and emits channel and tracking rows CONFIG-ONLY, no credentials, no platform writes, no spend. NOT for executing campaigns or buying media; NOT for implementing tracking (that is engineering work, routed through pm-requirements-v1); NOT for writing a handoff package or scoring a backlog.

naderelewa Skill

Portfolio and roadmap batch intake, turn a pile of asks into a prioritised verdict. Use when someone hands a BATCH and wants a decision: "prioritise this backlog", "score these requests", "batch verdict", "what goes in the next sprint or quarter", "turn this backlog document into a roadmap", "sprint recommendation", or drops a request list. It normalises the asks into a request-form table, scores each one through both lenses (product and strategy) with evidence-labelled RICE, and returns a batch verdict plus a sprint or quarter recommendation. NOT for engineering work; NOT for writing one feature's handoff package (pm-requirements-v1); NOT for verifying a shipped release (pm-verify-release-v1).

naderelewa Bundle

The requirements cycle, turn a strategy statement, a release target and a set of affected surfaces into an evidence-tagged, gated HANDOFF PACKAGE: spec.md, plan.md, data-model.md, contracts/, slices.json, a design gate and a case contract, plus the record that makes all of it auditable. Five phases: P0 context lock (the north-star metric elicited fresh every cycle) → P1 research → P2 strategy → P3 product spec → P4 handoff. Use when someone says "run the requirements cycle", "write the PRD / handoff package for <feature>", "prep the design gate", "requirements for the next release", or hands a strategy statement that needs to become buildable work. NOT for writing code, running CI, deploying or merging, an engineering toolchain owns those; NOT for release verification (pm-verify-release-v1); NOT for scoring a backlog batch (pm-portfolio-v1).

naderelewa Skill

Post-release acceptance verification, grade a shipped release against the spec that promised it. Use when someone says "verify the release", "did the release meet its acceptance scenarios", "post-release verification", "execute the measurement plan", "week-one metrics check", or hands a shipped scope that needs product-side evidence. Every pre-declared acceptance scenario is graded PASS / PARTIAL / GAP / UNVERIFIED against the DEPLOYED build, never the repository, and the pre-declared measurement plan is executed read-only. Returns an acceptance report plus a feedback pack that feeds the next requirements cycle. The owner decides acceptance; this verb prepares the evidence and never marks anything accepted. NOT for tests, CI, deploys, merges or code fixes; NOT for writing a handoff package (pm-requirements-v1); NOT for backlog scoring (pm-portfolio-v1).

nansen-ai Skill

Nansen CLI authentication, setup, and schema introspection. Required foundation for all other Nansen skills. Handles API key management, CLI installation verification, and dynamic command discovery via `nansen schema`. Install this skill first.

nethermindeth Bundle

Use this skill when implementing or debugging direct PXE workflows in TypeScript, including private execution lifecycle, note discovery/synchronization, sender/recipient tagging, private events, scopes, and oracle/debug checks.

nethermindeth Bundle

Use this skill when integrating Aztec wallet connectivity with @aztec/wallet-sdk, including discovery/session flows, secure-channel key exchange, extension handlers, encrypted messaging, and BaseWallet implementations.

nospicyplease Bundle

Find Amazon Ads search terms ready for exact-match harvesting from auto, broad, phrase, or other discovery campaigns. Use when Codex needs standalone or Rocketcart MCP-aware search-term harvesting: classify terms by harvest readiness, resolve live IDs, choose safe destination campaigns/ad groups, preflight duplicates/current negatives/destination feasibility, decide whether source negatives are justified, execute only explicitly approved rows, and read back/monitor Sponsored Products or Sponsored Brands actions without unsafe negatives, duplicate routing, stale approvals, brand-defense cuts, own-ASIN-defense cuts, launch/rank mistakes, or low-sample overfitting.