8Dionysus/atm10-source-of-truth-check
.agents/skills/atm10-source-of-truth-check/SKILL.md
Apply the aoa-source-of-truth-check workflow inside an atm10-* repository using repo-relative document maps, canonical-file patterns, and local review posture. Use when contributors need a thin project overlay to identify authoritative docs inside an atm10-* repo. Do not use when the task is broader policy design, purely code-local, or better handled by the base skill without local adaptation.
$ install --global
skillsauthnpx skillsauth add 8Dionysus/aoa-skills atm10-source-of-truth-checkInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 9:58 PM27.3s2 files scanned
SKILL.md
- name:
- atm10-source-of-truth-check
- description:
- Apply the aoa-source-of-truth-check workflow inside an atm10-* repository using repo-relative document maps, canonical-file patterns, and local review posture. Use when contributors need a thin project overlay to identify authoritative docs inside an atm10-* repo. Do not use when the task is broader policy design, purely code-local, or better handled by the base skill without local adaptation.
- license:
- Apache-2.0
- compatibility:
- Designed for Codex or similar coding agents with repository file access and an interactive shell. Network access is optional and only needed when repository validation or referenced workflows require it.
- aoa_scope:
- project
- aoa_status:
- evaluated
- aoa_invocation_mode:
- explicit-preferred
- aoa_source_skill_path:
- skills/atm10-source-of-truth-check/SKILL.md
- aoa_source_repo:
- 8Dionysus/aoa-skills
- aoa_technique_dependencies:
- AOA-T-0013,AOA-T-0002
- aoa_portable_profile:
- codex-facing-wave-3
atm10-source-of-truth-check
Intent
Use this skill to adapt aoa-source-of-truth-check to an atm10-* repository when the base workflow is right but the local doc map needs repo-relative detail.
Trigger boundary
Use this skill when:
- the base
aoa-source-of-truth-checkworkflow is already correct, but anatm10-*repo needs local canonical-file patterns, repo-relative docs, or doc review rules - contributors need a thin overlay that maps repo-relative docs such as
README.md,docs/ARCHITECTURE.md, ordocs/[canonical-guide].md - confusion exists between overview docs and authoritative files inside one local repo
- the family review doc and bundle-local checklist still need to stay aligned
Do not use this skill when:
- the main need is broader policy design rather than local document authority mapping
- the task is purely code-local and has no meaningful docs or guidance ambiguity
- the work would introduce new upstream technique meaning instead of thin local adaptation
- the main need is recording rationale for a decision rather than clarifying authority; use
aoa-adr-write
Inputs
- repo-relative docs or guidance surfaces
- local canonical-file candidates
- local review rules for doc changes
- contributor confusion points
- base skill reference
Outputs
- local source-of-truth map
- bounded clarification note
- repo-relative canonical-file pattern
- pointer to the family review surface
- verification summary for the local docs surface
Procedure
- start from
aoa-source-of-truth-checkinstead of inventing a family-specific docs doctrine - name the repo-relative docs and guidance files involved in the ambiguity
- map which file should stay authoritative for each local concern
- keep the adaptation bounded to the local repo surface under review
- make explicit what still depends on downstream human review or unpublished local policy
Contracts
- preserve the base skill meaning
- keep local file maps repo-relative and explicit
- surface local authority and review posture without hiding it
- keep the overlay public-safe and reviewable
Risks and anti-patterns
- inventing a broader docs governance framework inside a thin overlay
- using family labels without reducing local ambiguity
- hiding local review rules in prose that looks canonical
- silently replacing the base skill with project doctrine
Verification
- confirm the base skill is still the right workflow
- confirm authoritative repo-relative files are named explicitly
- confirm local review posture is visible rather than implied
- confirm the adaptation reduces ambiguity without widening scope
- confirm the family review doc and bundle-local checklist stay aligned
Technique traceability
Manifest-backed techniques:
- AOA-T-0013 from
8Dionysus/aoa-techniquesat5c6f0496edc3c2e74590baa35627c85fe58ef765using pathtechniques/docs/single-source-rule-distribution/TECHNIQUE.mdand sections: Intent, When to use, Inputs, Outputs, Core procedure, Contracts, Risks, Validation - AOA-T-0002 from
8Dionysus/aoa-techniquesat5c6f0496edc3c2e74590baa35627c85fe58ef765using pathtechniques/docs/source-of-truth-layout/TECHNIQUE.mdand sections: Intent, When to use, Inputs, Outputs, Core procedure, Contracts, Risks, Validation
Adaptation points
- local doc hierarchies
- repo-relative canonical-file patterns
- local review rules for doc changes
- repository-specific authority examples
- family review doc and bundle-local review checklist
Related Skills
8Dionysus/aoa-knowledge-stewardship
development
VerifiedTrustedCommunity
Sanitize private technical material into a public-safe owner-bounded derivative, or resolve authority among authored, generated, runtime, and installed sources. Use for governed incidents, logs, configs, diagnostics, or conflicting source roles. Do not use for ordinary editing, memo/session work, direct publication, or durable-memory authority.
4SKILL.mdUpdated Jul 16, 2026
8Dionysus/aoa-session-recovery
tools
VerifiedTrustedCommunity
Diagnose a reviewed recurring session/workflow failure, or carry one bounded owner repair through checkpoint, rollback, and real health verification. Use for reviewed contamination, drift, repeated route/tool failure, or an established diagnosis ready for repair. Do not use on live evidence, for vague self-improvement, or to call a proposed or merely executed change verified.
4SKILL.mdUpdated Jul 16, 2026
8Dionysus/aoa-session-harvest
tools
VerifiedTrustedCommunity
Use only when a literal ref to a closed/reviewed session packet is supplied, to extract, classify, propose promotion or branching, or identify an automation opportunity. Missing, live, or unreviewed evidence must fail closed without inventing a ref. Natural closeout preservation belongs to aoa-memo-writeback. Do not use for generic summaries, progression, direct owner writes, scheduling, mutation, or telemetry authority.
4SKILL.mdUpdated Jul 16, 2026
8Dionysus/aoa-verification
testing
VerifiedTrustedCommunity
Turn one stable technical truth into bounded evidence through contract, coverage-audit, or property mode. Use to define a named consumer seam, audit what existing checks really constrain, or express a broad invariant after manual cases establish meaning. Compose with aoa-eval when an evaluation surface must first be found or applied. Do not use for undefined behavior, generic test plans, or green checks as whole-system proof.
4SKILL.mdUpdated Jul 16, 2026