测试与 QA
测试、调试、验证和质量工作流
Skills 列表
ziniao-shared
紫鸟 CLI 共享基础：应用配置初始化、统一 apiKey 认证、错误处理、输出格式、安全规则。当用户需要第一次配置(`ziniao-cli config init`)、遇到认证/权限问题、或首次使用 ziniao-cli 时触发。
ziniao-open
limrun-detox-testing
Configure, run, or debug Detox on Limrun iOS simulators. Use when attaching the Limrun Detox runtime to an app, wiring Detox mediator connectivity, or validating app/tester connections over reverse tunnels.
limrun-inclimrun-expo-development
Prepare and run Expo / React Native apps on Limrun with Expo dev-client iteration. Use when the user wants an Expo dev build, Metro tunnel, hot reload, JS/TS iteration without repeated native rebuilds, or to run/test an Expo app on a remote iOS simulator.
limrun-inc
groundcover-cli
Invoke the `groundcover` Go CLI to manage Groundcover resources (dashboards, monitors, silences, connected apps, notification routes, API keys, policies, integrations, pipelines, workflows) AND to answer production observability questions by querying logs, traces, metrics, k8s inventory, and k8s events. Use whenever a task needs an authenticated call against the Groundcover API or whenever the user is debugging a prod issue and asks things like "why is X erroring in prod", "show me logs for service Y", "what's the p99 latency on Z", "what pods are crashlooping", "search traces for slow requests", "any k8s events for namespace N", "is service S receiving traffic", "list groundcover monitors", "create a silence", "update notification route", "hit a groundcover endpoint". Covers required env vars, the SDK-backed vs raw command split, and concrete request-body templates for logs/traces/metrics/k8s so the CLI can be driven from anywhere.
paymog
affiliate-performance-dashboard
Define the metric set and layout for an affiliate performance dashboard, delivered as a dashboard specification document - metric definitions with explicit formulas, views per audience, refresh and review cadence, and alert thresholds for top affiliates, conversion by source, and program ROI. Covers B2B SaaS recurring revenue-share and B2C ecommerce order-level CPA programs. Use whenever the user mentions affiliate program reporting, affiliate KPIs, affiliate ROI, revenue concentration, or what to put on an affiliate dashboard, even if they never say dashboard. Specifies metrics, never builds them in a BI tool. Do NOT use for one creator campaign's measurement plan - use mbfinotti/partnerships-skills@influencer-measurement-framework instead.
mbfinottiaffiliate-payout-audit
Audit an affiliate or partner commission payout run for accuracy before money is disbursed - per-line rate and tier recomputation, double-counted conversions, clawback and validation windows, period cutoff, currency, rounding, and tax-form status, delivered as an audit report with severities and recommended holds. Covers B2B SaaS recurring revenue-share and B2C ecommerce order-level CPA programs. Use whenever the user mentions an affiliate payout audit, commission accuracy, payout reconciliation, overpaid or underpaid affiliates, or a pre-disbursement review, even if they never say audit. Do NOT use for spotting fraudulent affiliates - use mbfinotti/partnerships-skills@affiliate-fraud-detection instead.
mbfinottiaffiliate-fraud-detection
Build the detection rule set an affiliate program manager uses to flag fraudulent affiliate activity, plus the investigation and escalation path behind it - cookie stuffing, fake lead and form-fill fraud, self-referral rings, traffic-quality baselines, commission holds and clawbacks, and separating real fraud from legitimate low-incrementality coupon or cashback partners. Covers B2B SaaS lead-gen and B2C ecommerce programs. Use whenever the user mentions affiliate fraud, suspicious affiliate traffic, invalid clicks or leads, bot traffic, or an affiliate whose numbers look too good, even if they never say fraud. Do NOT use for consumer refer-a-friend gaming - use mbfinotti/partnerships-skills@referral-abuse-guardrails instead.
mbfinottipartnerships-career
Plans a partnerships career from the candidate side across the field's four sub-disciplines - channel/alliance, affiliate, influencer/creator, referral. Covers the internal-transfer entry tactic, the company-type hiring bar, channel-manager interview-loop prep including the negotiation role-play and the "same deal in December as January" judgment test, job-posting red-flag reads, and offer evaluation gated on live verification since published comp benchmarks disagree by 2-3x. States plainly that no cross-company career ladder is published for this field. Use whenever the user asks how to break into partnerships, prep a partner-manager interview, read a posting, or evaluate an offer. Do NOT use for the hiring/employer side (mbfinotti/partnerships-skills@partnerships-hiring).
mbfinotti
jupyter-notebook-writing
Write Milvus application-level Jupyter notebook examples using a Markdown-first workflow with jupyter-switch for format conversion.
zc277584121
alan-test-feature
Scope coverage, build a testing strategy, test the feature with agent-browser, capture screenshots/video (always mandatory), upload to S3, and create a structured test report (never skip)
supatest-ai
api-review
Review the current Kelos branch, or an explicitly specified PR, issue, or diff, for Kubernetes API and CRD design quality. Use when asked for a Kelos API review, CRD/API compatibility review, Kubernetes API convention review, or review of changes under api/, generated CRDs, examples/, or self-development/ manifests. Default to the current branch when no target is specified. This skill is review-only.
gjkim42
skill-best-practices
Guide for creating, structuring, and improving Claude skills (SKILL.md). Use when building a new skill, reviewing an existing skill, writing SKILL.md frontmatter, defining trigger conditions, troubleshooting skill problems (not triggering, over-triggering, instructions not followed), or planning skill distribution. When working on any skill in this repository: also load the cc-best-practices skill, and always update both CLAUDE.md and README.md skill tables after any skill change. Do NOT use for general Claude Code configuration or hook setup.
dboeckli
safe-action-testing
Use when writing tests for next-safe-action actions or hooks -- Vitest patterns for testing server actions directly, middleware behavior, hooks with React Testing Library, validation errors, and server errors
next-safe-action
cournot
Query Cournot probabilities and manage prepaid calls, balances, and API keys. Use only for /cournot or an explicit request to use Cournot, not for casual odds questions.
cournot-aisales-account-tiering
Designs the tier layer downstream of an existing account fit score - where the cutoffs sit, tier names, rep-to-account capacity caps, the coverage model per tier (touch cadence, channel mix, QBR frequency, executive involvement), coverage-ratio health metrics, and the recalibration cadence. Covers B2B account tiering and B2C key-account tiering through retail/distribution channels. Use whenever the user mentions tiers, strategic/key/growth/long-tail accounts, accounts-per-rep ratios, 1:1 or 1:few or 1:many ABM coverage, or "everything drifted into Tier 1", even without the word tiering. Takes the fit score as input. Do NOT use for building that score (mbfinotti/sales-skills@sales-account-segmentation).
mbfinottisales-call-review
Scores one sales call transcript against an anchored rubric - opener, discovery, objection handling, close - quoting the transcript for every judgement and naming one focus behaviour. Handles messy ASR transcripts, missing speaker labels, and partial calls, covering B2B deal calls and B2C/inside-sales QA, rep self-review and manager tape review. Use whenever the user mentions a call recording, transcript, Gong or Chorus review, tape review, call scoring, or "how did this call go", even without the word review. Do NOT use for writing the follow-up email (mbfinotti/sales-skills@sales-meeting-recap) or scoring the deal itself (mbfinotti/sales-skills@meddpicc-scorecard).
mbfinottisales-hiring
Employer-side hiring workflow for SDR/BDR and AE roles, producing an outcome-based scorecard, a structured interview loop with question bank, a scored mock-call work sample, and a 30-60-90 ramp plan with certification gates. Recommends SDR vs AE vs full-cycle from ACV, cycle length and inbound volume, and rests on selection-validity evidence - structured interviews, independent scoring, no brainteasers. Use whenever the user mentions hiring a rep, sales interview questions, a hiring scorecard, a mock call interview, rep onboarding, or a ramp plan, even without the word hiring. Do NOT use for candidate-side prep (mbfinotti/sales-skills@sales-career) or comp plan design (mbfinotti/sales-skills@sales-comp-design).
mbfinottisales-motion
Chooses and designs the company-level sales motion at VP Sales / CRO altitude - product-led growth (PLG), sales-led, hybrid product-led sales, developer-led/open-source, or channel/partner-led - plus the transitions between them (exiting founder-led sales, layering sales onto self-serve, moving upmarket, adding channel), mapped to ACV, time-to-value, buyer-vs-user separation, TAM shape and procurement friction. Covers B2B SaaS and consumer self-serve motions. Use whenever the user mentions PLG vs sales-led, hiring the first salesperson, going upmarket, self-serve vs demo, or adding partners, even without the word motion. Do NOT use for org topology (mbfinotti/sales-skills@sales-org-structure) or quotas (mbfinotti/sales-skills@sales-quota-setting).
mbfinottisales-pipeline-hygiene
Run a periodic, checklist-based hygiene audit over an active pipeline snapshot - stale deals (no stage, close date, or amount change, not logged touches) flagged against segment-specific stage medians, close-date push-count anomalies, and missing forecast-critical fields - producing an exception list with a disposition per flagged deal, a remediation plan, and a pass threshold. Use whenever the user mentions pipeline hygiene, a stale deal audit, pipeline cleanup before a QBR, deals that keep pushing, a close date that keeps slipping, missing fields on deals, or "our pipeline is full of junk" - even if they never say "hygiene". Covers B2B and B2C/high-velocity/PLG. Do NOT use for rewriting stage definitions - use mbfinotti/revops-skills@pipeline-stage-definition-audit instead.
mbfinottirevops-hiring
Build the complete hiring packet for a RevOps or Sales Ops role - archetype and level decision, outcome scorecard, interview stage map with a competency question bank and anchored rating scales, a work-sample exercise with rubric and debrief, and a 30-60-90 ramp plan branched on seniority and archetype. For the hiring manager or founder recruiting the hire. Use whenever the user mentions hiring a RevOps manager, sales ops interview questions, a RevOps take-home exercise, a scorecard for a first ops hire, or a 30-60-90 for a new ops hire - even if they never say "hiring packet". Does not source candidates or post jobs. Do NOT use for a candidate's own interview prep - use mbfinotti/revops-skills@revops-career instead.
mbfinottirevenue-kpi-framework
Design the org-wide revenue KPI framework at the macro level - which metrics matter at each org level from board to IC, how they roll up through a reconciling metric tree with explicit math, who owns each branch, which guardrail counter-metrics ride alongside each owned number, and how the set is gated by company stage and business model. Use whenever the user mentions a revenue KPI framework, a metric hierarchy, a KPI tree, a North Star metric, driver metrics, guardrail counter-metrics, NRR, or which revenue metrics each org level should track - even if they never say "framework". Covers B2B and B2C. Do NOT use for writing the board report itself - use mbfinotti/revops-skills@revenue-reporting instead.
mbfinottirevops-career
Build and advance a RevOps or Sales Ops career from the candidate's side - place the candidate on the ladder by scope rather than title, close competency gaps, build defensible evidence of structurally invisible work, and prepare the four exercises RevOps interview loops actually run. Produces a career plan with a gap roadmap, an evidence ledger, interview readiness, and a compensation ask. Use whenever the user mentions a RevOps career, a sales ops career path, RevOps interview prep, RevOps certifications, "how do I break into RevOps", "am I ready for a RevOps manager role", or proving impact when nobody notices ops working - even if they never say "career". Candidate side only - for the hiring manager's side, use mbfinotti/revops-skills@revops-hiring instead.
mbfinottirevenue-leakage
Trace where deals and revenue silently exit one specific funnel and size the loss in recoverable (never gross) dollars - untracked steps, unworked leads, manual handoffs, mid-funnel stalls, paper-process drops, billing and renewal misses - separating real leaks from healthy disqualification and data-capture gaps. Use whenever the user mentions revenue leakage, funnel drop-off, a leaky funnel, deals disappearing, unworked leads, handoff gaps, "where are we losing deals", or "why did pipeline vanish" - even if they never say "leakage". Covers B2B sales-led and B2C/self-serve/PLG, one funnel instance at a time. Takes stage definitions as given - to audit those, use mbfinotti/revops-skills@pipeline-stage-definition-audit instead.
mbfinottirevenue-data-governance-strategy
Set org-wide revenue data governance policy - which system is source of truth per object class (account, contact, opportunity, subscription, usage event, revenue metrics), how cross-team data contracts bind producers to consumers, where revenue metric definitions live, and who arbitrates disputes. Produces a per-object SOR/SOT designation table, an identity-resolution spine, a data-contract register, and a federated ownership model. Use whenever the user mentions source of truth, "two ARR numbers", GTM data contracts, revenue data governance, metric definition ownership, or "finance and sales report different numbers" - even if they never say "governance". Covers B2B, PLG/B2C, hybrid. Do NOT use for CRM field-level rules - use mbfinotti/revops-skills@crm-data-governance instead.
mbfinotti