Loading...
Loading...
Found 217 Skills
Performance optimization coordination playbook. Contains specialist routing table, TileIR two-step pipeline, kernel generation specialist selection, prioritization criteria, and safe modification workflow. Use when the user asks to apply optimizations, write kernels, or improve performance. Covers both user-specified optimization and autopilot-driven iterative optimization.
Revenue.io platform help — Salesforce-native revenue orchestration with RingDNA dialer, Guided Selling cadences, Moments real-time coaching, conversation intelligence, and Revenue Intelligence dashboards. Use when calls not logging to Salesforce from Revenue.io, setting up Guided Selling cadences and task prioritization, configuring Moments real-time coaching notifications, choosing between Activate vs Engage vs Orchestrate tiers, dialer call dispositions not syncing to Salesforce, or Revenue.io vs Gong for conversation intelligence. Do NOT use for general conversation intelligence strategy (use /sales-note-taker) or building a coaching program (use /sales-coaching).
Triage CI failures and PR review comments using scripts/pr-status.js. Use when investigating failing CI jobs, flaky tests, or PR review feedback. Covers blocker-first prioritization (build > lint > types > tests), CI env var matching for local reproduction, and the Known Flaky Tests distinction.
Structurally deconstruct competitors from four dimensions: strategy, functionality, experience, and growth, and output referenceable points, non-replicable points, and differentiation suggestions. Use this Skill when users say "competitor analysis", "competitor deconstruction", "help me analyze competitors", "take a look at these competitors", "compare with competitors", "benchmarking analysis", "how to do differentiation", or when users provide a list of competitors and require systematic analysis. Also applicable for: users upload competitor screenshots/links/experience reports and require structured deconstruction; users require comparison of gaps between their own products and competitors; users want to find differentiation entry points. Not applicable for: pure requirement document writing (use prd-writer), pure priority sorting (use prioritization-engine), pure user research design (use survey-designer).
Run a structured business analysis workflow: requirements elicitation with stakeholder interviews and MoSCoW prioritization, as-is/to-be process mapping with BPMN notation, data-driven analysis (CBA, SWOT, root cause), and production-ready documentation (BRD, FRD, user stories with INVEST acceptance criteria). Triggers on "gather requirements", "write user stories", "map business process", "BRD", "FRD", "gap analysis", "cost-benefit analysis", "facilitate workshop", "business requirements", "process mapping", "as-is to-be", "stakeholder interview", or "business analyst". For management consulting (issue trees, steerCo business cases, operating model), use business-consultant—not business-analyst. For business model canvas, market sizing, and unit economics research, use business-model-researcher. Human data / labeling platform PRDs: product-management-human-data-platform. Monetization PRDs and packaging: product-management-monetization.
Produce a multi-quarter QA strategy document. Covers scope, risk-based prioritization, test levels (unit/integration/E2E), pyramid analysis, entry/exit criteria, quality KPIs, tool selection rationale, CI scaling levers, and timeline planning. Output is an actionable strategy document, not a shelf document. Use when: "test strategy," "QA strategy doc," "testing approach," "QA roadmap," "multi-quarter QA direction." Not for: a single-sprint or single-release plan — use test-planning. Not for: identifying which areas carry the most risk — use risk-based-testing first. Related: risk-based-testing, qa-metrics, release-readiness, test-planning, test-reliability.
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.
Apply Stakeholder Theory (Freeman, 1984) and the Mitchell et al. (1997) salience model to identify, classify, and prioritize stakeholders based on power, legitimacy, and urgency. Use this skill when the user needs to map stakeholders for a project or strategy, determine which stakeholders demand immediate attention, balance competing stakeholder interests, or when they ask 'who are our key stakeholders', 'how do we prioritize conflicting demands', or 'which stakeholders can block this initiative'.
Vendor-neutral skill to analyze onboarding funnel dropoff and propose prioritized interventions.
Identify and prioritize causal variants at GWAS loci using statistical fine-mapping and locus-to-gene predictions. Computes posterior probabilities for causal variants, links variants to genes via L2G predictions, annotates functional consequences, and suggests validation strategies. Use when asked to fine-map GWAS loci, prioritize causal variants, identify credible sets, or link GWAS signals to causal genes.
Use this skill when users need to validate their marketing channel strategy, assess channel focus, or determine lead gen priorities. Activates for "validate my channels," "am I on the right platforms," "should I focus on X or Y channel," or when assessing marketing spread.