Skill v1.0.1

currentAutomated scan100/100

ascorbic/macrodata/macrodata-distill

4 files

──Details

PublishedOctober 25, 2026 at 12:56 PM

Content Hashsha256:7a31a5f9ec09923d...

Git SHAf07def36b56f

Bump Typepatch

Compare with v1.0.0

──Files

Files (1 file, 4.9 KB)

SKILL.md4.9 KBactive

SKILL.md · 168 lines · 4.9 KB

version: "1.0.1" name: macrodata-distill description: Extract distilled actions and facts from today's conversations. Spawns sub-agents per conversation to avoid context blowup.

Distill Conversations

Process today's conversations to extract actionable knowledge. This is the core of memory consolidation.

Important: This runs as a coordinator. Spawn sub-agents for each conversation to avoid loading full transcripts into your context.

Storage Format

OpenCode stores all session data in a SQLite database at ~/.local/share/opencode/opencode.db.

Schema:

session — id, project_id, parent_id, title, time_created, time_updated
message — id, session_id, time_created, data (JSON: role, agent, modelID, etc.)
part — id, message_id, session_id, time_created, data (JSON: type, text, etc.)
project — id, worktree, name

Part types: text, tool, step-start, step-finish, patch, reasoning, compaction, file, subtask

Key JSON paths:

message.data → $.role (user/assistant), $.summary (set on compaction messages)
part.data → $.type (text/tool/etc.), $.text (for text parts)

Process

1. Find Today's Sessions

Query the SQLite database for sessions with activity today. Exclude subtask sessions (parent_id IS NOT NULL).

bash

sqlite3 ~/.local/share/opencode/opencode.db "
  SELECT s.id, s.title, p.worktree, s.time_created
  FROM session s
  LEFT JOIN project p ON p.id = s.project_id
  WHERE s.parent_id IS NULL
    AND s.time_updated > unixepoch('now', '-1 day') * 1000
  ORDER BY s.time_updated DESC
"

2. Process Each Session

For each session, spawn a sub-agent with the Task tool:

Task(subagent_type="general", prompt=`
Read an OpenCode conversation from the SQLite database at ~/.local/share/opencode/opencode.db.
 
Session ID: {sessionId}
Session title: {sessionTitle}
Project: {projectWorktree}
 
Use this query to extract the conversation (user prompts and assistant text responses):
 
sqlite3 ~/.local/share/opencode/opencode.db "
  SELECT
    m.id AS message_id,
    json_extract(m.data, '$.role') AS role,
    m.time_created,
    GROUP_CONCAT(
      CASE WHEN json_extract(p.data, '$.type') = 'text'
        THEN json_extract(p.data, '$.text')
      END,
      char(10)
    ) AS text_content
  FROM message m
  JOIN part p ON p.message_id = m.id
  WHERE m.session_id = '{sessionId}'
    AND json_extract(m.data, '$.role') IN ('user', 'assistant')
    AND json_extract(m.data, '$.summary') IS NULL
  GROUP BY m.id
  HAVING text_content IS NOT NULL AND text_content != ''
  ORDER BY m.time_created ASC
"
 
Filter to actual conversation content:
- Include: user messages, assistant text responses
- Exclude: tool calls, tool results, system content, compaction summaries
 
Extract and return as JSON:
{
  "distilled_actions": [
    {
      "summary": "Fixed auth bug in src/auth.ts where token refresh was racing",
      "files": ["src/auth.ts"],
      "outcome": "Added mutex lock around refresh"
    }
  ],
  "facts": [
    {
      "topic": "project-name",
      "content": "Uses JWT tokens with 15min expiry"
    },
    {
      "topic": "person-name",
      "content": "Prefers explicit error handling over try/catch"
    }
  ],
  "decisions": [
    "Chose Redis over in-memory cache for session storage because of multi-instance deployment"
  ]
}
 
Focus on:
- What was accomplished (not just discussed)
- Decisions made and their rationale
- New information about projects, people, or preferences
- File paths and specific technical details that should survive compression
 
Return ONLY the JSON, no explanation.
`)

3. Collect and Write Results

After all sub-agents complete:

Write distilled actions to journal:

For each action in all results:
  macrodata_log_journal(topic="distilled", content=action.summary + " Files: " + action.files.join(", "))

Write overall summary to journal:

macrodata_log_journal(topic="distill-summary", content="Processed N sessions. Extracted X actions, Y facts.")

Update entity files with facts:

Group facts by topic
For each topic, read existing entity file (if any)
Integrate new facts, removing duplicates
Write updated file

4. Example Sub-Agent Output

json

{
  "distilled_actions": [
    {
      "summary": "Added /distill skill to macrodata plugin",
      "files": ["plugins/macrodata/skills/distill/SKILL.md"],
      "outcome": "Skill extracts facts from conversations via sub-agents"
    }
  ],
  "facts": [
    {
      "topic": "macrodata",
      "content": "Distillation separates narrative context from retained facts for better compression"
    }
  ],
  "decisions": [
    "Coordinator updates state directly to prevent race conditions from parallel sub-agents"
  ]
}

Notes

Sub-agents should be spawned in parallel for efficiency
Empty results are fine - not every conversation has extractable knowledge
Facts should be concise and specific, not narrative summaries

← v1.0.0 All versions