Menu
Orchestrate V2 transaction documentation by tracking all endpoints and delegating analysis to /analyze-transaction
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Decide how to document complementary tools and support repos (CLI, SDK, templates, bots, dev/agent repos) so they drive adoption and contributions without competing with the products. Use when adding or reviewing docs for anything that is not itself a sold product, or when deciding where a tool belongs in the IA.
Track guide writing progress, manage blockers, and coordinate the publish pipeline for Andamio documentation guides.
Orchestrate V2 transaction MDX documentation coverage and quality tracking
Parse decoded V2 transaction CBORs from Atlas API and create/update documentation YAML files
Review individual V2 transaction MDX documentation for coverage and accuracy
| name | transaction-audit |
| description | Orchestrate V2 transaction documentation by tracking all endpoints and delegating analysis to /analyze-transaction |
Source of Truth: https://atlas-api-preprod-507341199760.us-central1.run.app/swagger.json
Worker Skill: Use /analyze-transaction to process individual transactions.
Tracking File: .claude/skills/transaction-audit/v2-transaction-tracker.json
Scope note: This skill is the V2-transactions-specific instance of the broader release-cycle drift practice. For the cross-cutting pattern (release-cycle hook + drift detector + scheduled audit across the developer-facing surface), see docs/solutions/workflow-issues/docs-release-sync-drift-2026-05-20.md.
Sync with Swagger (if requested or stale)
Display Status Dashboard
Identify Work Needed
not-analyzed statusPrompt for Action
/analyze-transaction for specific transactions| Command | Description |
|---|---|
/transaction-audit | Show dashboard and status |
/transaction-audit sync | Sync tracker with swagger.json |
/transaction-audit status | Show summary counts only |
/transaction-audit next | Suggest next transaction to analyze |
/transaction-audit analyze <id> | Run /analyze-transaction for specific tx |
| Status | Meaning |
|---|---|
not-analyzed | Known from swagger, no YAML/TS files created yet |
analyzed | YAML + TS files created via /analyze-transaction |
verified | Tested against live API, confirmed working |
not-analyzed → analyzed → verified
↑ ↓
└──────────────┘ (if API changes)
{
"version": "1.0.0",
"lastUpdated": "YYYY-MM-DD",
"swaggerSource": "https://atlas-api-preprod-507341199760.us-central1.run.app/swagger.json",
"totalTransactions": 17,
"summary": {
"analyzed": N,
"not-analyzed": N,
"verified": N
},
"transactions": [
{
"id": "system.role.action",
"endpoint": "/v2/tx/...",
"method": "POST",
"system": "global|instance|course|project",
"role": "general|owner|teacher|student|manager|contributor",
"description": "...",
"status": "not-analyzed|analyzed|verified",
"lastAnalyzed": "YYYY-MM-DD" | null,
"files": {
"yaml": "path/to/file.yaml" | null,
"ts": "path/to/file.ts" | null,
"mdx": "path/to/file.mdx" | null
},
"legacyFiles": { // Only if path mismatch exists
"yaml": "old/path.yaml",
"note": "Migration needed"
},
"notes": "..."
}
]
}
File paths MUST match the API endpoint structure:
| API Endpoint | YAML Path | TS Path |
|---|---|---|
/v2/tx/{system}/{role}/{action} | {system}/{role}/{action}.yaml | {system}/{role}/{action}.ts |
/v2/tx/global/general/access-token/mint → global/general/access-token/mint.yaml/v2/tx/course/student/assignment/commit → course/student/assignment/commit.yaml/v2/tx/project/contributor/task/commit → project/contributor/task/commit.yamlpublic/yaml/transactions/v2/packages/andamio-transactions/src/definitions/v2/content/docs/protocol/v2/transactions/
Some transactions must be analyzed in order:
global.general.access-token.mint - Required for all other transactionsinstance.owner.course.createinstance.owner.project.createcourse.owner.teachers.manage, course.teacher.modules.manageproject.owner.managers.manage, project.owner.contributor-blacklist.manage, project.manager.tasks.managecourse.student.enroll, course.student.assignment.action, course.teacher.assignments.assess, course.student.credential.claimproject.contributor.enroll, project.contributor.task.commit, project.contributor.task.action, project.manager.tasks.assess, project.contributor.credential.claim
═══════════════════════════════════════════════════════════════
V2 TRANSACTION AUDIT DASHBOARD
═══════════════════════════════════════════════════════════════
Last Updated: YYYY-MM-DD
Swagger Source: https://atlas-api-preprod-507341199760.us-central1.run.app/swagger.json
SUMMARY
───────────────────────────────────────────────────────────────
Total: 17 | Analyzed: 1 | Not Analyzed: 16 | Verified: 0
BY SYSTEM
───────────────────────────────────────────────────────────────
Global (1): ████████████████████ 100% [1/1]
Instance (2): ░░░░░░░░░░░░░░░░░░░░ 0% [0/2]
Course (6): ░░░░░░░░░░░░░░░░░░░░ 0% [0/6]
Project (8): ░░░░░░░░░░░░░░░░░░░░ 0% [0/8]
TRANSACTIONS
───────────────────────────────────────────────────────────────
[✓] global.general.access-token.mint
[ ] instance.owner.course.create ⚠️ Legacy path mismatch
[ ] instance.owner.project.create
[ ] course.owner.teachers.manage ⚠️ Legacy path mismatch
...
NEXT RECOMMENDED
───────────────────────────────────────────────────────────────
→ instance.owner.course.create (Tier 2, has legacy file to migrate)
To analyze: /analyze-transaction <paste decoded CBOR>
═══════════════════════════════════════════════════════════════
/analyze-transaction - Worker skill that processes individual transaction CBORs/glossary-game - Terminology validation (different domain)