How do I install the Easy Cheese Setup skill?

Run npx skillmds add paulnsorensen/easy-cheese-setup in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Easy Cheese Setup safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Easy Cheese Setup?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Easy Cheese Setup free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Easy Cheese Setup?

paulnsorensen (@paulnsorensen) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Easy Cheese Setup by paulnsorensen — Agent Skill

Name: Easy Cheese Setup
Rating: 4.666666666666667 (3 reviews)
Author: paulnsorensen

Easy Cheese Setup

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. Use scripts/install.sh to install the MCP server.

paulnsorensen 3d72033 3 files · 1.5 MB Updated Sep 9, 2026

File contents

/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 scripts/easy-cheese-setup.pyz. It has three commands. Each command changes data only with --apply. Without this option, each command only reports.

python3 <skill>/scripts/easy-cheese-setup.pyz global [--apply]   # durable-corpus registration/repair
python3 <skill>/scripts/easy-cheese-setup.pyz local  [--apply]   # per-repository tenant registration
python3 <skill>/scripts/easy-cheese-setup.pyz doctor [--apply]   # both legs

At installation, install.sh calls global --apply when --mcp includes hallouminate. This skill controls the interactive process.

Flow

Run doctor without --apply first. It reports the planned actions for both 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 <skill>/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.

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.

---name: easy-cheese-setupdescription: 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. Use scripts/install.sh to install the MCP server.license: MIT--- # /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 `scripts/easy-cheese-setup.pyz`. It has three commands. Each command changes data only with `--apply`. Without this option, each command only reports. ``` python3 <skill>/scripts/easy-cheese-setup.pyz global [--apply] # durable-corpus registration/repair python3 <skill>/scripts/easy-cheese-setup.pyz local [--apply] # per-repository tenant registration python3 <skill>/scripts/easy-cheese-setup.pyz doctor [--apply] # both legs ``` At installation, `install.sh` calls `global --apply` when `--mcp` includes `hallouminate`. This skill controls the interactive process. ## Flow Run `doctor` without `--apply` first. It reports the planned actions for both 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: ```bash python3 <skill>/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. ## 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`](references/commands.md).

Frequently asked questions