agentleFS
cezarafcezaraf/avc-template/.agents/skills/avc-live-qa/SKILL.md

avc-live-qa

Skill0 starsChanged 3 months agoMITView on GitHub

Validate an AVC/XP outcome through the real consumer surface such as UI, API, CLI, MCP, preview, or deployed runtime, preserving separate evidence from local tests and CI.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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 the configured live_qa command or the narrowest equivalent already authorized by policy.

    line 10
  2. Distinctive:

    Do not mutate production data or broaden authority.

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Run live QA

Act as Verifier. Identify the consumer surface, environment, authentication, seed/legacy data, observable states, and required artifacts from the active run. Run the configured live_qa command or the narrowest equivalent already authorized by policy.

For UI, check loading, error, empty, success, navigation, console, and network when applicable. For API/CLI/MCP, invoke the real handler or protocol and inspect the actual response. Do not infer runtime success from build output.

Do not mutate production data or broaden authority. Record environment and artifacts separately from focused tests and CI. Return the canonical result.

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.