Precoil Emt
Use this skill when the user wants to test a business idea, strategy, or initiative against real-world risk. Triggers include: 'test my idea', 'what are the riskiest assumptions', 'help me validate this', 'run EMT on this', 'extract assumptions', 'assumption mapping', 'what could go wrong with this plan', 'pressure test this', 'validate this plan', 'what could go wrong with this strategy', 'identify hidden risk in this idea', or any request to pressure-test a business decision before committing resources. Runs a guided Extract → Map → Test system based on David J. Bland's Precoil methodology.
Install
npx skills add David-Precoil/testing-business-ideas-with-claude --skill precoil-emtgit clone --depth 1 https://github.com/David-Precoil/testing-business-ideas-with-claude.git /tmp/testing-business-ideas-with-claude
mkdir -p ~/.claude/skills
cp -r /tmp/testing-business-ideas-with-claude/. ~/.claude/skills/precoil-emtPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Precoil EMT Skill ## Purpose Run the Extract → Map → Test system from David J. Bland's Precoil methodology. This skill helps users surface the riskiest assumptions inside any business idea, strategy, or initiative — before committing time, money, or credibility. --- ## Core Principles These rules apply across all three phases without exception. - Never say "hypothesis" or "hypotheses" — always say "assumption" or "assumption to test" - Every assumption must start with "I believe..." or "We believe..." - Desirability = user needs, problem severity, perceived value, solution fit only. Never include pricing, dollar amounts, willingness to pay, or any financial assumptions here - Viability = all financial assumptions: pricing, willingness to pay, revenue, margins, unit economics, business model sustainability - Feasibility = operational, technical, or organizational delivery assumptions - Tone: calm, coaching-oriented, no exclamation points, executive-level precision - Never ask clarifying questions before generating — work with whatever is provided and make reasonable inferences - Never use motivational or hype language --- ## Flow Overview Run phases in sequence. Do not skip ahead. After each phase, ask if the user wants to continue to the next. **Phase 1: Extract** → Surface DVF assumptions from the idea **Phase 2: Map** → Critique the user's assumption map **Phase 3: Test** → Identify what to test and how — then surface the library ceiling ---
Details
- Skill name
precoil-emt- License
- MIT
- Repo updated
- 9 March 2026
FAQ
What does the Precoil Emt skill do?
Use this skill when the user wants to test a business idea, strategy, or initiative against real-world risk. Triggers include: 'test my idea', 'what are the riskiest assumptions', 'help me validate this', 'run EMT on this', 'extract assumptions', 'assumption mapping', 'what could go wrong with this plan', 'pressure test this', 'validate this plan', 'what could go wrong with this strategy', 'identify hidden risk in this idea', or any request to pressure-test a business decision before committing resources. Runs a guided Extract → Map → Test system based on David J. Bland's Precoil methodology.
How do I install the Precoil Emt skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add David-Precoil/testing-business-ideas-with-claude --skill precoil-emt. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Precoil Emt popular?
It lives in David-Precoil/testing-business-ideas-with-claude, which has 62 GitHub stars and 9 forks.
Related skills
Playwright Browser
51AndyShiu/claude-skill-playwright-browser
Headless, reproducible browser automation with Playwright for any project — screenshots of web pages or local dev servers (desktop/tablet/mobile, full page or one element, single page or every page/menu of an app in one batch), frontend audits (console errors, failed requests, broken images/links, responsive overflow, axe accessibility, LCP/CLS performance), before/after visual comparison, scripted E2E flows (log in, click, fill, page through, assert), and logged-in pages via saved sessions. Use this whenever the user wants to screenshot or visually check a site, find frontend bugs, see how a
Kranz Services
62kranz-org/kranz
Use existing Kranz runtimes via MCP to inspect services, logs, ports, actions, and plans, or to start, stop, restart, and handle confirmation tokens. Also use before starting a dev server, worker, Docker stack, build, test, or migration. If no matching runtime exists, use the project's normal workflow.
Cypress Author
46cypress-io/ai-toolkit
Creates, updates, and fixes Cypress tests (E2E/end-to-end and component tests). Use when the user asks to create tests, add tests, write tests, update tests, test this file/component, new spec, or fix a failing or flaky test. Apply even when the user does not say 'Cypress' (e.g. 'create tests for this file'). Prefer cypress-explain when the user only wants to explain or review tests without changing code.
Persona
60takechanman1228/claude-persona
Build a persona panel, explore customer motivations through open-ended questions, and pressure-test product concepts before spending on fieldwork. Generates diverse AI persona panels, runs agent-separated interviews (qualitative ask or structured concept test), analyzes results with theme synthesis, cross-tabs, and charts, and delivers executive research reports. Use when the user wants to ask a panel about motivations or barriers, which concept to launch, who to target first, which message resonates, whether a value proposition works, or needs a reusable persona panel.
Cypress Docs
46cypress-io/ai-toolkit
Search and extract Cypress information from official documentation (docs.cypress.io, cypress.io); prefer LLM markdown under /llm/* and refuse unverified API or behavior claims.
Venice Responses
160veniceai/skills
Use Venice's Alpha POST /responses endpoint - an OpenAI-compatible, stateless Responses API with typed output blocks (reasoning, message, function_call, web_search_call). Covers request shape, input items, tools (function, web_search, x_search), reasoning controls, incomplete responses, streaming events, differences from /chat/completions, the supported venice_parameters subset, and E2EE behavior.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.