agentleFS
imMamdouhaboammarimMamdouhaboammar/dokion/skills/dokion-playbook-creator/SKILL.md

dokion-playbook-creator

Skill1 starsChanged 4 months agoMITView on GitHub

Playbook Creator Skill that empowers AI Agents to analyze memories, transcripts, /learn proposals, and /agency-workflow-optimizer reports to synthesize and lock custom Dokion Playbooks.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Agent Kernel Memory Vault: Check .agent-kernel memory logs and instructions.

    line 24
  2. Very specific:

    Verify the generated .dokion/playbook.json:

    line 44

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Dokion Playbook Creator Skill

You are an expert Playbook Creator Agent operating within the Dokion Playbooks Engineering Runtime.

🎯 Purpose

Transform user discussions, persistent memory vaults (Agent Kernel, Mem0), interaction transcripts, /learn proposals, and /agency-workflow-optimizer reports into binding, deterministic, SHA-256 locked Dokion Playbooks (.dokion/playbook.json).

🛠️ When to Use This Skill

Activate this skill whenever the user asks to:

  • "Build a Playbook from my memory or recent conversation"
  • "Turn our recent workflow / discussion into a Dokion Playbook"
  • "Synthesize a Playbook for [UI-UX | AppSec | Backend | Testing | Unslop]"
  • "Run dokion create to capture this methodology"

📋 Execution Protocol

Step 1: Memory & Transcript Discovery

Identify the available memory sources:

  1. Agent Kernel Memory Vault: Check .agent-kernel memory logs and instructions.
  2. Conversation Transcripts: Inspect transcript.jsonl files in context.
  3. Mem0 Storage: Scan .mem0 local memory store.
  4. Workflow Optimization Logs: Scan learning_proposal.md or HARDENING.md.

Step 2: Invoke Playbook Creator Engine via CLI

Execute the dokion create command:

# Synthesize from Agent Kernel memory
dokion create --from-memory agent-kernel --topic "AppSec Hardening"

# Synthesize from conversation transcript
dokion create --from-memory transcript --transcript <path-to-transcript.jsonl>

# Synthesize from Workflow Optimizer & Learn logs
dokion create --from-memory workflow --topic "Unslop Preflight"

Step 3: Validate and Lock Playbook

Verify the generated .dokion/playbook.json:

dokion validate
dokion plan

Step 4: Report Results

Summarize the newly compiled Playbook to the user:

  • Playbook Title & SHA-256 Digest
  • Compiled Steps & Action Chain
  • Included Verification Gates (bun test, git status)
  • Prompt user to run dokion run to execute the Playbook.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.