agentleFS
Sign inStart free
yanstd888yanstd888/agent-product-factory/skills/product-qa/SKILL.md

product-qa

Skill20 starsChanged 23 days agoMITView on GitHub

Validate a local prompt pack, XLSX template, or EPUB/PDF ebook and produce an offline QA report. Use when an agent has created or changed a digital product and must prove it is ready before delivery.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. BenjaminG/ai-skills★ 4same name
    2. cubxxw/agent-kit★ 2same name
    3. AY0-design/product-qa★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run python scripts/run_qa.py doctor before XLSX or ebook checks.

    line 9
  2. Distinctive:

    Keep the report path outside the product path.

    line 11
  3. Distinctive:

    If blockers exist, fix the product and rerun at most three times.

    line 12

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Product QA Gate

  1. Run python scripts/run_qa.py doctor before XLSX or ebook checks.
  2. Run python scripts/run_qa.py check <product-path> --type prompt-pack|xlsx|ebook --json-out <report-path>.
  3. Keep the report path outside the product path; the command will reject overwrites and report paths inside the product.
  4. If blockers exist, fix the product and rerun at most three times.
  5. Deliver the product only with a zero-exit QA report. Otherwise name the remaining blockers plainly.

Result rules

  • Exit 0: no blockers.
  • Exit 1: product or environment blocker.
  • Exit 2: invalid report-output path or report write failure.
  • Warnings do not block delivery, but must be included in the handoff.

Product metadata

Each product directory needs product.json with title, author, version, and license.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free