experiment-receipts
Skill from aliraza2025/receipts
Install
npx skills add aliraza2025/receipts --skill experiment-receipts
Runs the open skills CLI and installs the skill for your agent (Claude Code, Codex, Cursor …). Alternatively copy the skill folder into .claude/skills/ or upload it in Claude.ai under Settings → Skills.
What does the experiment-receipts skill do?
Description from the SKILL.md in the source repository.
Questions about experiment-receipts
What does the experiment-receipts skill do?
Plans and reads out product experiments (A/B tests, variant tests, usability pilots) with the decision stated first, a precise primary metric, sample size as a planning assumption, guardrails, a privacy-scoped event contract, and a clear split between what was verified and what was simulated. Use when the user designs an A/B test, picks an experiment metric, estimates sample size, instruments analytics events, or writes an experiment readout.
How do I install experiment-receipts?
In a terminal: npx skills add aliraza2025/receipts --skill experiment-receipts. The skills CLI asks which agents to install it for. In Claude.ai you can upload the skill folder as a ZIP under Settings → Skills.
Which agents can use experiment-receipts?
Skills use the open SKILL.md format, which Claude Code, Claude.ai, the Claude API, OpenAI Codex, Cursor, Gemini CLI and other agents support.
Is experiment-receipts safe to use?
Our automatic check found no risky patterns (piped shell scripts, hidden characters, secret access, prompt overrides). It is not a full audit – read the SKILL.md and any scripts before installing.
More skills from aliraza2025/receipts
Writes an evaluation plan and readiness gates for an LLM or AI feature before launch, including abstention rules, the model's boundary in the workflow, and a limitations section.
Audits product writing (READMEs, launch pages, decks, case studies, resumes, PRDs, investor updates) for claims that are not backed by evidence, labels each claim, and rewrites unsupported ones.
Pairs every product metric with the decision it informs and states what the number does not prove. Use when defining success metrics, writing dashboards or metric sections in PRDs, reporting results, preparing …
Rewrites product, portfolio, and launch copy into plain, specific language by removing AI-sounding filler, em dashes, inflated verbs, and vague outcomes, without adding any new claims.
Turns interview notes, call transcripts, support tickets, or stakeholder requests into a PRD that keeps observations, inferences, and assumptions separate, with quotes as receipts, explicit non-goals, and success metrics.
Related skills in Testing & QA
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any …
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code
Automate browser interactions, test web pages and work with Playwright tests.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.