Menu
Remove a project from the Arkadian documentation registry and delete all associated documentation files. Use when: user wants to deregister a project.
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
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.
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.
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.
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".
| name | remove-project |
| description | Remove a project from the Arkadian documentation registry and delete all associated documentation files. Use when: user wants to deregister a project. |
| allowed-tools | ["Read","Write","Edit","Bash","Glob","Grep"] |
When to use:
User input: A project ID (e.g., boltz-backend).
WARNING: This is a destructive operation. Deleted documentation cannot be recovered unless committed to git.
docs/INDEX.md and verify project existsdocs/projects/<project-id>/ directory existsIf not found: show error with list of available projects.
Collect project information from docs/INDEX.md:
List files to delete in docs/projects/<project-id>/.
Check for dependents — if other projects depend on this one, warn prominently.
Show exactly what will happen:
Require explicit confirmation: User must type "CONFIRM REMOVAL" to proceed.
Only proceed if user explicitly confirms.
Step 4.1: Update Master INDEX.md
Step 4.2: Delete Documentation Directory
Delete entire docs/projects/<project-id>/ directory.
Verify:
Show: files deleted, INDEX.md changes, related projects updated, and next steps (review with git status, restore with git checkout -- docs/ if mistake).