Menu
Analyse an Arkadian orchestrator session - read transcripts, logs, and artifacts to understand what happened and suggest improvements. Use when: user wants to debug or review a past session.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | analyse-arkadian-session |
| description | Analyse an Arkadian orchestrator session - read transcripts, logs, and artifacts to understand what happened and suggest improvements. Use when: user wants to debug or review a past session. |
| allowed-tools | ["Read","Glob","Grep","Bash"] |
When to use:
User input: A session identifier and an optional question.
Examples:
latestabc123-def4562026-02-11-add-grpc-endpoint-arkd Why did the implement phase fail?latest What agents were used?Parse arguments: everything before the first question word ("why", "what", "how", "which", "did", "was", "is", "show", "list") that doesn't look like a session ID becomes the question.
Resolution order:
latest — Read ${ARKADIAN_DIR}/sessions/.index/manifest.json, pick the first entry (newest).${ARKADIAN_DATA_DIR}/<id>_log.txt (active or ended)${ARKADIAN_DATA_DIR}/<id>_state.json (active only)${ARKADIAN_DIR}/sessions/.index/manifest.json entry where session_id contains <id>2026-02-11-add-grpc-endpoint-arkd) — Search manifest.json for matching entry or scan sessions/.If not found, list available sessions.
Set: SESSION_ID, LOG_FILE, STATE_FILE, SESSION_DIR, TRANSCRIPT_PATH, QUESTION.
Read ${LOG_FILE} (<id>_log.txt in DATA_DIR). Build a timeline:
Read from ${SESSION_DIR}:
Always read (if exists):
session.md — Session summaryworkflow.yaml — Workflow definitionRead based on existence:
specs/*.yaml — Execution specificationsartifacts/explore/assessment.yaml — Exploration assessmentartifacts/implement/detailed_report.md — Implementation reportartifacts/implement/test-evidence.md — Test resultsartifacts/*/_result.json — Agent result manifestsOnly for deep analysis questions. The transcript can be very large.
Locate: Check state file transcript_path, grep log line 1, or derive from ~/.claude/projects/<slug>/<id>.jsonl.
Strategy: Read in chunks with limit parameter. Focus on assistant messages and tool calls.
If question provided: Answer specifically using gathered data.
If no question: Produce comprehensive analysis:
| Source | Path Pattern | Active | Ended |
|---|---|---|---|
| State file | ${ARKADIAN_DATA_DIR}/<id>_state.json | YES | DELETED |
| Hook log | ${ARKADIAN_DATA_DIR}/<id>_log.txt | YES | PRESERVED |
| Session folder | sessions/<id>/ or renamed | YES | PRESERVED |
| Manifest | sessions/.index/manifest.json | N/A | PRESERVED |
| Transcript | ~/.claude/projects/<slug>/<id>.jsonl | YES | PRESERVED |
Analyze a project repository and add it to the Arkadian documentation registry with standardized structure. Use when: user provides a path to a new project to onboard.
Generate validated operational SOPs for Ark ecosystem projects by testing commands before documenting them. Use when: user wants to create or audit SOPs for a project.
Remove a project from the Arkadian documentation registry and delete all associated documentation files. Use when: user wants to deregister a project.
Update project documentation based on new commits and changes in the repository. Use when: user wants to sync docs after project changes.
Self-improvement loop for arkadian. Launches arkadian -d with a GitHub issue, polls until done, evaluates per-agent criteria, reads transcripts on failure, improves prompts, deletes worktree, and relaunches. Loops until passing or max iterations.
Debug and investigate fulmine production issues. Downloads logs and SQLite datadir from remote Docker containers, and queries the Boltz PostgreSQL database remotely. Analyzes errors and queries databases for root cause analysis. Use when: (1) investigating fulmine production errors or failures, (2) checking swap/vHTLC/delegate task status in prod, (3) analyzing fulmine logs for recent issues, (4) debugging VTXO or transaction problems on mainnet, (5) inspecting Boltz swap state in PostgreSQL. Triggers on: "fulmine prod", "production logs", "prod errors", "check prod fulmine", "debug fulmine", "fulmine mainnet issue", "boltz db", "boltz prod".