loomcycle-diff-agentdefs

Stars1

Forks0

UpdatedJune 1, 2026 at 09:22

Diff two loomcycle AgentDef versions by def_id and show what changed in system_prompt, allowed_tools, max_tokens, and other fields. Use when the user wants to compare two versions of a self-evolving agent definition.

Installation

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.

Source

denn-gubsky

denn-gubsky/claude-code-plugin-loomcycle

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Computer Occupations, All OtherComputer and Mathematical Occupations·SOC 15-1299

SKILL.md

readonly

name	loomcycle-diff-agentdefs
description	Diff two loomcycle AgentDef versions by def_id and show what changed in system_prompt, tools, max_tokens, and other fields. Use when the user wants to compare two versions of a self-evolving agent definition.

Diff two loomcycle AgentDef versions

Use when the operator wants to see what changed between two versions of a self-evolving agent definition (the loomcycle AgentDef substrate tracks versioned definitions with lineage).

Steps:

Get the two def_ids. The operator supplies two def_ids (often a parent and its descendant). If they only have one and want "the previous version," fetch the one they have first and read its parent_def_id.
Fetch both with the agentdef tool, get op, once per id:
```
{ "op": "get", "def_id": "<def_id>" }
```
Each returns a row whose definition field is the agent config — system_prompt, tools, max_tokens, provider/model/tier, etc.
Diff the definitions field by field. Highlight, in this order:
- system_prompt — show a readable diff (added / removed lines), not the two full prompts side by side unless they're short.
- tools — which tools were added / removed.
- max_tokens, model, provider, tier, effort — any scalar changes.
- Any other changed keys.
provider: code-js (v0.16, RFC J). If either version sets provider: code-js, that version is a synthetic code agent — it runs operator-authored JavaScript (agent_code/<name>/index.js) instead of calling an LLM, at zero token cost. For such a version model / effort / max_tokens are inert (no model is called), so don't read into them; the behavioural ground truth is the JS file, not the def fields. Call out a provider flip into or out of code-js prominently — it turns the agent from model-driven to code-driven (or back), a far bigger change than any prompt edit.
Summarise the intent. In one line, characterise the change ("widened tool access + tightened the system prompt's output format"). Note the lineage (parent_def_id) and which is newer (version / created_at).
Stay descriptive. This skill reports a diff; it does not promote, retire, or pin a version. Selection between AgentDef versions is operator policy — if the operator wants to act on the diff, point them at the relevant agentdef ops, but don't mutate on their behalf without an explicit ask.

More from this repository

same repository

loomcycle-configure

denn-gubsky/claude-code-plugin-loomcycle

Configure a loomcycle runtime — providers, model tiers, user tiers, fallbacks, per-agent sampling and context-compaction, environment variables, deployment profiles (brew/in-system, containerized, true sandbox, server, multi-tenant, cloud), filesystem Volumes, the Bashbox in-process sandbox, the Path VFS, chunked-graph Documents, inbound webhooks, and third-party MCP servers. Use when the user wants to set up or tune loomcycle.yaml or its env, pick a deployment posture, wire provider routing/cost-cascades, gate plans, tune decoding (temperature/top_p) or compaction, lock down tool/sandbox/auth, enable or choose between Bash and the Bashbox sandbox (incl. its host-command fallback), name resources with Path, author chunked-graph Documents (and the SQL Memory they require), receive webhooks, or connect external MCP tools.

2026-06-221

loomcycle-import-claude-code

denn-gubsky/claude-code-plugin-loomcycle

Guide the user through importing a .claude/ directory into loomcycle yaml using the `loomcycle import claude-code` CLI — dry-run first, review the report, then write. Use when the user wants to move Claude Code agents/skills/MCP servers into a loomcycle config.

2026-05-291

loomcycle-replay-failed-run

denn-gubsky/claude-code-plugin-loomcycle

Walk through replaying a failed loomcycle run — inspect the failure, adjust the prompt or agent, and re-spawn. Use when a loomcycle run errored or produced a bad result and the user wants to retry with a fix.

2026-05-291

loomcycle-spawn-evaluator

denn-gubsky/claude-code-plugin-loomcycle

Spawn a loomcycle evaluator agent to score the current Claude Code transcript (or a named run) and report the result. Use when the user wants an independent quality/score judgement of work just done via loomcycle.

2026-05-291

name	loomcycle-diff-agentdefs
description	Diff two loomcycle AgentDef versions by def_id and show what changed in system_prompt, tools, max_tokens, and other fields. Use when the user wants to compare two versions of a self-evolving agent definition.

Diff two loomcycle AgentDef versions

Use when the operator wants to see what changed between two versions of a self-evolving agent definition (the loomcycle AgentDef substrate tracks versioned definitions with lineage).

Steps:

Get the two def_ids. The operator supplies two def_ids (often a parent and its descendant). If they only have one and want "the previous version," fetch the one they have first and read its parent_def_id.
Fetch both with the agentdef tool, get op, once per id:
```
{ "op": "get", "def_id": "<def_id>" }
```
Each returns a row whose definition field is the agent config — system_prompt, tools, max_tokens, provider/model/tier, etc.
Diff the definitions field by field. Highlight, in this order:
- system_prompt — show a readable diff (added / removed lines), not the two full prompts side by side unless they're short.
- tools — which tools were added / removed.
- max_tokens, model, provider, tier, effort — any scalar changes.
- Any other changed keys.
provider: code-js (v0.16, RFC J). If either version sets provider: code-js, that version is a synthetic code agent — it runs operator-authored JavaScript (agent_code/<name>/index.js) instead of calling an LLM, at zero token cost. For such a version model / effort / max_tokens are inert (no model is called), so don't read into them; the behavioural ground truth is the JS file, not the def fields. Call out a provider flip into or out of code-js prominently — it turns the agent from model-driven to code-driven (or back), a far bigger change than any prompt edit.
Summarise the intent. In one line, characterise the change ("widened tool access + tightened the system prompt's output format"). Note the lineage (parent_def_id) and which is newer (version / created_at).
Stay descriptive. This skill reports a diff; it does not promote, retire, or pin a version. Selection between AgentDef versions is operator policy — if the operator wants to act on the diff, point them at the relevant agentdef ops, but don't mutate on their behalf without an explicit ask.