@thomasasen/autodarts-local-tournament
AATA Quality and Compliance Skill
Install
agr install @thomasasen/autodarts-local-tournament --target claudeWrites 5 files into .claude/skills/, pinned to git-32cddbe5.
- .claude/skills/autodarts-local-tournament/.gitignore
- .claude/skills/autodarts-local-tournament/AGENTS.md
- .claude/skills/autodarts-local-tournament/LICENSE
- .claude/skills/autodarts-local-tournament/README.md
- .claude/skills/autodarts-local-tournament/SKILL.md
Document
SKILL.md
Name
ATA Quality and Compliance Skill
Use when
- Implementing or reviewing tournament logic.
- Changing DRA/PDC-related behavior.
- Touching import/sync/autodetect flows.
- Preparing releases with high confidence.
Primary objectives
- Preserve deterministic tournament behavior.
- Keep DRA/PDC mapping explicit and auditable.
- Prevent regressions via domain + runtime tests.
Operating procedure
- Map the change to affected layer(s).
- Identify impacted rule(s) and docs:
docs/DRA-RULE_BOOK.pdfdocs/dra-regeln-gui.mddocs/dra-compliance-matrix.md
- Implement in
src/*only. - Add tests:
- Pure unit tests for functions.
- Scenario tests that run complete tournament paths.
- Rebuild and run checks:
powershell -ExecutionPolicy Bypass -File scripts/build.ps1powershell -ExecutionPolicy Bypass -File scripts/test-domain.ps1powershell -ExecutionPolicy Bypass -File scripts/test-runtime-contract.ps1powershell -ExecutionPolicy Bypass -File scripts/qa.ps1
- Update docs/changelog if behavior changed.
Quality checklist
- No hidden side effects in domain logic.
- Explicit failure modes (
reasonCode, message). - No ambiguous auto-writes when mapping is unclear.
- Migration/backward compatibility considered.
- Docs match real behavior and wording is consistent.
Scenario-test expectations
ko: seeded/byes, open_draw determinism, advancement, champion/result index.league: standings, tie-break ordering, playoff-required deadlocks.groups_ko: group resolution, cross-semis, final assignment, deadlock blocking.
Done criteria
- All QA scripts green.
- New behavior covered by automated tests.
- Compliance text and changelog updated where relevant.
Trustgrade A
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- passLicense
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-32cddbe587ed2026-07-31