Peated QA

What it does

When your agent uses it

• Manually QAing Peated changes across the API
• Selecting smoke checks after code changes
• Using agent-browser for Peated flows
• Verifying local behavior beyond tests and lint

Example prompts

• “/peated-qa”

Requirements

• Docker

Workflow steps

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

1. 1Identify exact route file and operation.
2. 2Hit local API, not peated.com: http://localhost:4300.
3. 3For public reads, use curl against the route or spec-shaped endpoint.
4. 4For protected writes, create/login a throwaway local user and send Authorization: Bearer .
5. 5Check success response, validation failure, auth failure, and not-found/conflict when relevant.
6. 6Verify DB-visible side effects when mutation behavior matters.
7. 7If the route is used by web/CLI, QA that caller too.

What it can do on your machine

Read from SKILL.md and the folder at commit aee6890. 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

  Shell commands in SKILL.md call:

  • pnpm
  • docker

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

• Network

  Hosts in commands or code, which the agent is likely to contact:

  • api.peated.com

  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

Peated QA loads about 1.9k tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 819 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~52

When it runs · the whole SKILL.md, loaded when a task matches

~1.9k

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

• NoteMentions a .env fileSKILL.md:23

  I, worker, package watchers, and shared `.env.local` setup together,

• NoteMentions a .env fileSKILL.md:33

  | loads `.env.local`                                         |

• NoteMentions a .env fileSKILL.md:38

  ttp://localhost:3202 pnpm exec dotenv -e .env.local -- pnpm --filter @peated/server start:api`

• NoteMentions a .env fileSKILL.md:40

  ttp://localhost:3202 pnpm exec dotenv -e .env.local -- pnpm --dir apps/web exec next dev -p 3202`

• NoteMentions a .env fileSKILL.md:92

  5. Live classifier runs use `.env.local`, local DB adapters, and OpenAI config.

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 dcramer/peated at commit aee6890, republished under its Apache-2.0 licence (© dcramer). 819 words, ~1,868 tokens.

name

peated-qa

description

Use when manually QAing Peated changes across the API, CLI, or web UI; selecting smoke checks after code changes; using agent-browser for Peated flows; verifying local behavior beyond tests and lint.

pnpm cli users create qa@example.com password123 --verified --accept-terms --if-exists
pnpm cli users generate-token qa@example.com

{
  "reference": { "name": "Ardbeg Uigeadail" },
  "candidateExpansion": "initial_only"
}

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

Files

SKILL.md and 2 other files in skills/peated-qa of dcramer/peated.

• SKILL.md
• SOURCES.md
• SPEC.md

Open the folder on GitHubat commit aee6890