paulnsorensenpaulnsorensen/easy-cheese/skills/easy-cheese-setup/SKILL.md

easy-cheese-setup

Skill19 starsChanged 28 days agoMITView on GitHub

Register the durable `cheese-durable` Hallouminate corpus. Repair the durable corpus when its configuration changes. Register the repository tenant. Repair the repository tenant when its configuration changes. Use this skill when the user requests durable corpus setup or repair. Use it when the user requests repository tenant registration. Also use it when the user invokes /easy-cheese-setup. Use the wiki skills for general Hallouminate wiki work.

In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- python-authoringSkill
- skill-authoringSkill
- affinageSkill
- ageSkill
- briesearchSkill
- cheeseSkill
- cookSkill
- cultureSkill
- cureSkill
- hard-cheeseSkill
- meltSkill
- moldSkill
- pasteurizeSkill
- plateSkill
- pressSkill
- ultracookSkill
- wheypointSkill

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
11
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Run doctor without --apply first.
line 34
Very specific:
Create the directory from paths.corpus_home() if it does not exist.
line 38
Very specific:
Read config_path() for that file.
line 40
Very specific:
Use # >>> easy-cheese:cheese-durable as the start marker.
line 42
Very specific:
Use # <<< easy-cheese:cheese-durable as the end marker.
line 43
Very specific:
Use --apply to correct a marked block that points elsewhere.
line 46
Very specific:
Leave a cheese-global block unchanged if it points anywhere except ~/.cheese.
line 53
Very specific:
Run hallouminate init-repo <name> --path <main-root> when both required conditions are true.
line 57
Very specific:
Run artifacts after new repositories accumulate .cheese artifacts worth searching.
line 62
Very specific:
After an --apply that changes the file, run hallouminate daemon restart, then hallouminate index --corpus cheese-artifacts.
line 66
Very specific:
Use the imported paths.corpus_home() as the only source for the durable root.
line 71
Distinctive:
Do not delete data by default.
line 72
Distinctive:
Remove a legacy block only after user confirmation.
line 74

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

/easy-cheese-setup

Register the durable cheese-durable Hallouminate corpus. The corpus makes each project's XDG artifacts searchable across sessions.

Register the current repository as a Hallouminate tenant when the user requests it. This process is idempotent. It does not delete data.

The engine is a self-contained bundle at skills/easy-cheese-setup/scripts/easy-cheese-setup.pyz. It has four commands. Each command changes data only with --apply. Without this option, each command only reports.

python3 skills/easy-cheese-setup/scripts/easy-cheese-setup.pyz global    [--apply]                     # durable-corpus registration/repair
python3 skills/easy-cheese-setup/scripts/easy-cheese-setup.pyz local     [--apply]                     # per-repository tenant registration
python3 skills/easy-cheese-setup/scripts/easy-cheese-setup.pyz artifacts [--apply] [--root PATH ...]    # register every .cheese dir as one corpus
python3 skills/easy-cheese-setup/scripts/easy-cheese-setup.pyz doctor    [--apply]                     # all three legs

Install the Hallouminate MCP server first. See README.md § Installing MCP servers. This skill controls the interactive registration process.

Flow

Run doctor without --apply first. It reports the planned actions for all three legs without changes. Show the report as evidence. Ask the user for confirmation. Apply only the approved legs.

Global leg — durable corpus

Create the directory from paths.corpus_home() if it does not exist. This action prevents Hallouminate issue #101.
Insert or replace the marked [[corpus]] block in the Hallouminate configuration file.
Read config_path() for that file. Its default is ~/.config/hallouminate/config.toml.
HALLOUMINATE_CONFIG and XDG_CONFIG_HOME override that default. Do not assume the default path.
Use # >>> easy-cheese:cheese-durable as the start marker.
Use # <<< easy-cheese:cheese-durable as the end marker. Write the identifier in both markers.
An end marker without the identifier does not close the block. The rewrite then replaces the rest of the file.
Point the block at corpus_home(). A second global --apply leaves the file unchanged.
Use --apply to correct a marked block that points elsewhere.
Legacy migration requires user interaction. An unmarked cheese-global → ~/.cheese block is stale. Show the report. Ask the user for confirmation. Then use the explicit migration option. The installer never uses this option:
```
python3 skills/easy-cheese-setup/scripts/easy-cheese-setup.pyz global --migrate-legacy --apply
```
Leave a cheese-global block unchanged if it points anywhere except ~/.cheese.

Local leg — repository tenant

Run hallouminate init-repo <name> --path <main-root> when both required conditions are true. The repository must have .cheese/ artifacts. It must not have a Hallouminate tenant.
Register the main repository root. Do not register a worktree. This rule prevents a temporary path from replacing the tenant identity.

Artifacts leg — machine-wide `.cheese` corpus

Run artifacts after new repositories accumulate .cheese artifacts worth searching. Hallouminate indexes a gitignored .cheese dir only when a paths entry names that dir directly, so the block lists each .cheese directory, not a shared parent root. A paths entry that no longer exists on disk makes the daemon skip the whole corpus with a warning. A complete scan removes missing entries; an incomplete scan reports an error and leaves the block unchanged. After an --apply that changes the file, run hallouminate daemon restart, then hallouminate index --corpus cheese-artifacts.

Rules

Detect the current state. Report proposed changes. Ask the user for confirmation. Require --apply for each operation that changes data.
Use the imported paths.corpus_home() as the only source for the durable root. Do not hardcode ~/.cheese or an XDG path.
Do not delete data by default.
global --apply rewrites the marked block. It also creates the corpus directory.
Remove a legacy block only after user confirmation.

See the generated bundle command inventory in references/commands.md.

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.

Check your setup, free