Skills

The nine skills exist because the mechanical parts — scaffolding, frontmatter, index regeneration, validation — are tedious, and doing them for you leaves the time for the part only you can do: deciding what the thing is.

The skills are optional. The framework is not.

You can write every file by hand; nothing in the standard depends on tooling. But keep _eidos/ on disk either way. The framework is what holds you to the standard — without it, the shape you’re writing to lives in your head, drifts a little with each blueprint, and stops being a standard the moment someone else writes one.

A skill is a folder with a SKILL.md in it, so any agent that reads that format can run them. The standard they operate on is agent-neutral by design.

The authoring path

Three skills overlap, and picking the wrong one is the usual source of a bad session:

You have	Use	It produces
An idea, half-formed	iterate	An understanding. No file.
Something you’ve decided	eidos	The blueprint
A draft already written	format	The same words, in shape

All nine

iterateQuestion one rough idea until it holds still. Writes nothing.

eidosAuthor and validate blueprints. The main skill.

formatReshape a rough draft, preserving your words.

installStand up a root where there isn't one.

configureAdd a collection, flavor, or property; backfill it.

indexRebuild each collection's generated listing.

canvasDraw the blueprints as an Obsidian canvas.

whoamiSet who's in the seat: role and calibration.

migrateMove to another version of the standard.

Installing

Claude Desktop / Web

Customize → Plugins → + → Add marketplace from repository, and give it the repository:

https://github.com/BuildableWorks/Eidos

Then install eidos from that marketplace. Any paid plan.

Desktop runs each skill scoped to its own folder, and every skill is self-contained, so this behaves exactly as it does in Claude Code.

If you’d rather upload a file than add a repository — or you’re sharing a private framework — build the zip from a clone and pick upload a custom plugin file instead:

./scripts/package-plugin.sh   # → dist/eidos-plugin.zip

Claude Code

The repository is a public plugin marketplace:

/plugin marketplace add BuildableWorks/Eidos
/plugin install eidos@eidos

For development against a local clone:

claude --plugin-dir /path/to/eidos     # ephemeral, one session

Or drop a folder straight in, no plugin involved: <repo>/.claude/skills/<name>/ for one project, ~/.claude/skills/<name>/ for everywhere. A project copy wins over a global one.

Codex

Codex scans for skills in .agents/skills/, nearest first — the repo root, then ~/.agents/skills/ for every repo. Copy the folders in:

git clone https://github.com/BuildableWorks/Eidos.git
mkdir -p .agents/skills && cp -r Eidos/skills/* .agents/skills/

Nothing to configure. Codex picks up any folder whose SKILL.md carries name and description, which every Eidos skill does. To turn one off without deleting it, add it to ~/.codex/config.toml:

[[skills.config]]
path = "/path/to/skill/SKILL.md"
enabled = false

Any other agent

There’s no packaging for it, but there’s nothing to package: each skill is a self-contained folder with a SKILL.md, and the format is an open standard.

Vendor the folders wherever your agent reads instructions from, and point at them however it expects. The three that need part of the standard carry a committed copy of it, so nothing breaks when they’re moved.

Why three skills carry a copy of the standard

You’ll notice EIDOS.md, seeds/, and versions/ appear twice in the repository — once at the root, once inside a few skill folders. That’s deliberate.

The top-level copies are the source of truth and the public review surface. But a skill often can’t reach them once installed:

• Claude Desktop sandboxes each skill to its own folder — no sibling files.
• A git-marketplace install ships only what’s committed — anything gitignored never arrives.

So the three that need part of the standard carry it, committed: eidos (the ruleset), install (the seeds), and migrate (the version history). The other six read your root’s framework at runtime and need nothing.

scripts/sync-skills.sh regenerates those copies from the top-level sources, and --check fails if one has drifted.

Note

The trade was chosen on purpose. Gitignoring the copies breaks Desktop installs; dropping the top-level copies would cost the single reviewable home for the standard. So both exist, and a script holds them together.

Adding your own

Create skills/<your-skill>/SKILL.md and it ships with the plugin automatically.

To share a framework with a colleague, hand them the self-contained zip the package script builds, or push to a private git repo and share the URL.