Agent skill

Factory Acceptance Test

by mohitagw15856 in mohitagw15856/pm-claude-skills

Write a factory acceptance test (FAT) plan or report — test coverage matrix against spec, AQL sampling plan, pass/fail criteria, golden-sample handling, deviation log, and sign-off structure.

MITAuto-check passedTesting & QA

Install Factory Acceptance Test

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill factory-acceptance-test -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills factory-acceptance-test --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/factory-acceptance-test .claude/skills/factory-acceptance-test && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
factory-acceptance-test
GitHub stars
1.4k
Token cost
~1.3k tokens
SKILL.md length
680 words
Files
1
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

Write a factory acceptance test (FAT) plan or report — test coverage matrix against spec, AQL sampling plan, pass/fail criteria, golden-sample handling, deviation log, and sign-off structure.

  • Works in 8 steps: Scope & lot definition — product rev,… → Test coverage matrix — table: test #,… → Sampling plan — lot size, code letter,… → …
  • Asked to write a FAT plan
  • SKILL.md covers What This Skill Produces, Required Inputs, Sampling & Classification… and Output Format, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Factory Acceptance Test is an agent skill from mohitagw15856/pm-claude-skills. Write a factory acceptance test (FAT) plan or report — test coverage matrix against spec, AQL sampling plan, pass/fail criteria, golden-sample handling, deviation log, and sign-off structure. Use when asked to write a FAT plan, define outgoing quality inspection, set AQL levels, prepare for a factory acceptance or pre-shipment inspection, or document FAT results. Produces a complete FAT plan or report with sampling tables, defect classification, and a sign-off block.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering End-to-end testing and Test coverage. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.

When your agent uses it

  • Asked to write a FAT plan
  • Define outgoing quality inspection
  • Prepare for a factory acceptance
  • Pre-shipment inspection

Example prompts

  • “/factory-acceptance-test”

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Scope & lot definition — product rev, lot size, factory, date
  2. Test coverage matrix — table: test #, spec clause covered, method/equipment, sample basis (100% / AQL sample), pass criterion
  3. Sampling plan — lot size, code letter, n, and Ac/Re per defect class
  4. Pass/fail & lot disposition rules — accept / reject / rework-and-rescreen conditions
  5. Golden & limit sample register — serials, locations, seal dates, refresh trigger
  6. Deviation log — #, description, class, disposition, approver
  7. Results (report only) — defects found per class vs Ac/Re, failure detail with photos referenced
  8. Sign-off block — lot disposition, name, role, authority, date; rejection escalation path

What it can do on your machine

Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Factory Acceptance Test loads about 1.3k tokens when it runs. Until then it costs about 124 tokens; SKILL.md has 680 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~124
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 680 words, ~1,326 tokens.

Download SKILL.mdSave it as .claude/skills/factory-acceptance-test/SKILL.md (or your agent's skills folder).
name
factory-acceptance-test
description
Write a factory acceptance test (FAT) plan or report — test coverage matrix against spec, AQL sampling plan, pass/fail criteria, golden-sample handling, deviation log, and sign-off structure. Use when asked to write a FAT plan, define outgoing quality inspection, set AQL levels, prepare for a factory acceptance or pre-shipment inspection, or document FAT results. Produces a complete FAT plan or report with sampling tables, defect classification, and a sign-off block.

Factory Acceptance Test Skill

A FAT is the last moment a defect is the factory's problem instead of yours. This skill writes the plan (or the report) with the parts that actually get argued over at the line: which spec clause each test covers, how many units get pulled and at what AQL, what exactly fails a lot, and who signs — so acceptance is a decision with a name on it, not a vibe at the end of a factory visit.

What This Skill Produces

  • A test coverage matrix mapping every test to the spec requirement it verifies
  • A sampling plan (ANSI/ASQ Z1.4) with lot size, inspection level, and AQL per defect class
  • Unambiguous pass/fail criteria and lot accept/reject rules
  • Golden-sample handling procedure
  • A deviation log format and a sign-off block with authority levels

Required Inputs

Ask for these if not provided; if the spec is thin, draft the matrix from the product description and mark rows [spec clause to confirm]:

  • Product and spec — the requirements document or at minimum a feature/claims list
  • Lot size — units in the lot(s) under acceptance
  • Product risk profile — safety-relevant? battery? affects AQL choice
  • Prior quality history — first article vs mature product (allows tightened/reduced inspection)
  • Who signs — customer QE, factory QA, third-party inspector?

Sampling & Classification Framework

Defect classes and default AQLs (ANSI/ASQ Z1.4, General Inspection Level II, normal inspection — the consumer-electronics defaults; adjust with reason):

ClassDefinitionDefault AQL
CriticalSafety hazard, regulatory violation, data loss0 — any occurrence rejects the lot
MajorProduct fails to function, or defect the user will certainly notice and return1.0 (tighten to 0.65 for premium/first lots)
MinorCosmetic or workmanship issue within limit samples' tolerance but noted2.5 (relax to 4.0 for bulk/industrial)

From lot size + Level II, derive the sample-size code letter and accept/reject numbers from the Z1.4 tables; state them explicitly in the plan (e.g. "Lot 3,000 → code K → n=125; Major Ac=3/Re=4"). Switch to tightened inspection after 2 of 5 consecutive lots rejected; reduced only with sustained history.

Golden samples. Two signed, serialised golden samples minimum — one held at the factory line, one at the buyer. Sealed, dated, with an expiry/refresh rule (refresh on any ECO that changes fit/finish/function). Cosmetic judgement is against the limit-sample boundary set, never against memory.

Deviations. Any test performed differently than planned, any borderline judgement, and any use-as-is decision goes in the deviation log — numbered, with disposition and approver.

Output Format

Show full SKILL.md (280 more words)Show less
FAT [plan | report]: [product] — lot [ID]
  1. Scope & lot definition — product rev, lot size, factory, date
  2. Test coverage matrix — table: test #, spec clause covered, method/equipment, sample basis (100% / AQL sample), pass criterion
  3. Sampling plan — lot size, code letter, n, and Ac/Re per defect class
  4. Pass/fail & lot disposition rules — accept / reject / rework-and-rescreen conditions
  5. Golden & limit sample register — serials, locations, seal dates, refresh trigger
  6. Deviation log — #, description, class, disposition, approver
  7. Results (report only) — defects found per class vs Ac/Re, failure detail with photos referenced
  8. Sign-off block — lot disposition, name, role, authority, date; rejection escalation path

Quality Checks

  • Every spec requirement appears in the coverage matrix, or its exclusion is stated
  • Sample sizes and Ac/Re numbers are explicit — not "per AQL 1.0"
  • Critical defects have Ac=0 and an immediate-stop instruction
  • Cosmetic criteria reference physical limit samples, not adjectives
  • The report states defects per class against Ac/Re, and the disposition follows arithmetically
  • Sign-off names a role with authority to reject the lot

Anti-Patterns

  • Do not write "inspect to AQL 1.0" without the sample size and accept/reject numbers — that phrase settles nothing
  • Do not let critical defects carry a non-zero acceptance number
  • Do not judge cosmetics against memory or photos alone — physical limit samples or it will be relitigated every lot
  • Do not allow rework-and-reinspect of a rejected lot without 100% rescreen of the reworked defect mode
  • Do not accept a lot with an unsigned deviation in the log
  • Do not let golden samples go stale across an ECO — refresh or they certify the wrong product

Example Trigger Phrases

  • "Write a FAT plan."
  • "Define outgoing quality inspection."
  • "Set AQL levels."
  • "Prepare for a factory acceptance."
  • "Document FAT results."

© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/factory-acceptance-test of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

Factory Acceptance Test next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Factory Acceptance Test compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Factory Acceptance Test this skillmohitagw15856/pm-claude-skills1.4k—~1.3kAutomated safety check: PassMIT
Atdd Mutateswingerman/engineer154—~2.7kAutomated safety check: PassMIT
E2E Test ThinkerUniClipboard/UniClipboard1.9k—~1.7kAutomated safety check: PassAGPL-3.0
Check Test Coverageopenshift/oc-mirror124—~853Automated safety check: PassApache-2.0
E2E Test Creatorletehaha/moneymatter160—~2.4kAutomated safety check: WarnAGPL-3.0
Platform Dsar Policy Manageforcedotcom/sf-skills1.1k—~5.2kAutomated safety check: PassApache-2.0

Similar skills

  • Atdd Mutate

    swingerman/engineer

    A skill your agent uses to add a third validation layer to the ATDD workflow — after acceptance tests verify WHAT and unit tests verify HOW, mutation testing verifies the tests actually catch bugs.

    154 GitHub stars~2.7k tokensUpdated 16 days ago
    Testing & QAAuto-check passed
  • E2E Test Thinker

    UniClipboard/UniClipboard

    Analyze the current branch's diff against main and determine which changes are testable via CLI-based end-to-end tests.

    1.9k GitHub stars~1.7k tokensUpdated today
    Testing & QAAuto-check passed
  • Check Test Coverage

    openshift/oc-mirror

    Analyze oc-mirror CLI feature coverage across integration and e2e tests, identifying untested features and gaps

    124 GitHub stars~853 tokensUpdated yesterday
    Testing & QAAuto-check passed
  • E2E Test Creator

    letehaha/moneymatter

    Creates backend e2e tests for new or existing endpoints. An agent skill from letehaha/moneymatter.

    160 GitHub stars~2.4k tokensUpdated yesterday
    Testing & QAAuto-check: warnings
  • Platform Dsar Policy Manage

    forcedotcom/sf-skills

    Configure, run, and audit DsarPolicy Right-to-Portability exports end to end: author the data map over a subject's related records, resolve a request's subject (email/name/id) to a root-entity…

    1.1k GitHub stars~5.2k tokensUpdated 2 days ago
    Testing & QAAuto-check passed
  • Post Dev Test

    sd0xdev/sd0x-harness

    Post-development test completion. An agent skill from sd0xdev/sd0x-harness.

    192 GitHub stars~1.8k tokensUpdated yesterday
    Testing & QAAuto-check: notes

More from mohitagw15856/pm-claude-skills

All 1,348 skills in this repo
  • Car Tco

    mohitagw15856/pm-claude-skills

    Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Cs Health Scorecard

    mohitagw15856/pm-claude-skills

    Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed
  • Exit Waterfall

    mohitagw15856/pm-claude-skills

    Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated yesterday
    Auto-check passed
  • Fire Number

    mohitagw15856/pm-claude-skills

    Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Freelance Rate

    mohitagw15856/pm-claude-skills

    Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.

    1.4k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Factory Acceptance Test

What does Factory Acceptance Test do?

Write a factory acceptance test (FAT) plan or report — test coverage matrix against spec, AQL sampling plan, pass/fail criteria, golden-sample handling, deviation log, and sign-off structure. Factory Acceptance Test is an agent skill from mohitagw15856/pm-claude-skills. Write a factory acceptance test (FAT) plan or report — test coverage matrix against spec, AQL sampling plan, pass/fail criteria, golden-sample handling, deviation log, and sign-off structure.

When should I use Factory Acceptance Test?

Factory Acceptance Test fits situations like: asked to write a FAT plan; define outgoing quality inspection; prepare for a factory acceptance; pre-shipment inspection.

How do I install Factory Acceptance Test in Claude Code?

Run `npx skills add mohitagw15856/pm-claude-skills --skill factory-acceptance-test -a claude-code`. Or copy the skill folder (skills/factory-acceptance-test in mohitagw15856/pm-claude-skills) into .claude/skills/factory-acceptance-test in your project. Claude Code loads it when a task matches its description.

How do I install Factory Acceptance Test in Codex?

Run `npx skills add mohitagw15856/pm-claude-skills --skill factory-acceptance-test -a codex`. Or copy the skill folder (skills/factory-acceptance-test in mohitagw15856/pm-claude-skills) into .agents/skills/factory-acceptance-test in your project. Codex loads it when a task matches its description.

Can I use Factory Acceptance Test in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill factory-acceptance-test -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/factory-acceptance-test, .gemini/skills/factory-acceptance-test, .github/skills/factory-acceptance-test and .opencode/skills/factory-acceptance-test in your project.

What does Factory Acceptance Test need to run?

SKILL.md names no scripts, command-line tools or credentials: Factory Acceptance Test is instructions for the agent only.

Does Factory Acceptance Test access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Factory Acceptance Test safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Factory Acceptance Test use?

Factory Acceptance Test is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Factory Acceptance Test use?

About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Factory Acceptance Test?

Skills that share tags, products or a category with Factory Acceptance Test: Atdd Mutate (swingerman/engineer, 154 stars), E2E Test Thinker (UniClipboard/UniClipboard, 1.9k stars), Check Test Coverage (openshift/oc-mirror, 124 stars) and E2E Test Creator (letehaha/moneymatter, 160 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Factory Acceptance Test?

mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,433 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 8, 2026.

Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.