How do I install the Thinkroom Install skill?

Run npx skillmds@latest add phenomenoner/thinkroom-install 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.

What does the Thinkroom Install skill do?

Install and verify Thinkroom skills It is listed under Coding & Dev Tools on SkillMD.

Is Thinkroom Install safe to use?

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

Which AI agents work with Thinkroom Install?

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 Thinkroom Install free to use?

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

Who published Thinkroom Install?

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

Thinkroom Install by phenomenoner — Agent Skill

Name: Thinkroom Install
Author: phenomenoner

File contents

Thinkroom install

Use this skill when installing, checking, or removing Thinkroom's managed Agent Skills bundle.

Install

Use the host profile when available:

# Codex App / CLI / IDE
thinkroom skills install --profile codex
thinkroom skills status --profile codex

# Hermes Agent default profile; pair with `hermes --profile default ...`
unset HERMES_HOME
thinkroom skills install --profile hermes
thinkroom skills status --profile hermes

Codex resolves to $HOME/.agents/skills. Hermes resolves to $HERMES_HOME/skills, defaulting to ~/.hermes/skills. For a named Hermes profile, set the non-empty absolute HERMES_HOME="$HOME/.hermes/profiles/<profile-name>" for every Thinkroom command and use hermes --profile <profile-name> ... for MCP registration and verification. Never rely on sticky profile state. For another Agent Skills-compatible host, use exactly one explicit target:

thinkroom skills install --target <skill-root>
thinkroom skills status --target <skill-root>

The managed projection contains:

thinkroom-trigger
thinkroom-operate
thinkroom-install

Safety contract

Installation is idempotent: managed files that still match are classified EXACT.
New managed files are classified ADD.
Exact files owned by the allowlisted pre-profile v0.2 receipt are classified UPDATE when the current bundle replaces them. The installer migrates only that known receipt and exact payload set.
Existing unmanaged, missing-after-receipt, or modified managed files are DIVERGED.
Never overwrite a DIVERGED target. Inspect and reconcile it outside the installer.
Keep the generated .thinkroom/skills-receipt-v1.json; status and uninstall use it to verify ownership and hashes.

Remove

Check status first, then remove only the exact managed projection:

thinkroom skills status --target <skill-root>
thinkroom skills uninstall --target <skill-root>

The equivalent profile commands are supported for Codex and Hermes. Do not pass --profile and --target together.

After any install or removal, start a fresh agent session or use the agent's supported skill reload command so its skill index reflects the filesystem.

---name: thinkroom-installdescription: Install and verify Thinkroom skillslicense: MIT---# Thinkroom installUse this skill when installing, checking, or removing Thinkroom's managed Agent Skills bundle.## InstallUse the host profile when available:```bash# Codex App / CLI / IDEthinkroom skills install --profile codexthinkroom skills status --profile codex# Hermes Agent default profile; pair with `hermes --profile default ...`unset HERMES_HOMEthinkroom skills install --profile hermesthinkroom skills status --profile hermes```Codex resolves to `$HOME/.agents/skills`. Hermes resolves to `$HERMES_HOME/skills`, defaulting to`~/.hermes/skills`. For a named Hermes profile, set the non-empty absolute`HERMES_HOME="$HOME/.hermes/profiles/<profile-name>"` for every Thinkroom command and use`hermes --profile <profile-name> ...` for MCP registration and verification. Never rely on stickyprofile state. For another Agent Skills-compatible host, use exactly one explicit target:```bashthinkroom skills install --target <skill-root>thinkroom skills status --target <skill-root>```The managed projection contains:- `thinkroom-trigger`- `thinkroom-operate`- `thinkroom-install`## Safety contract- Installation is idempotent: managed files that still match are classified `EXACT`.- New managed files are classified `ADD`.- Exact files owned by the allowlisted pre-profile v0.2 receipt are classified `UPDATE` when the current bundle replaces them. The installer migrates only that known receipt and exact payload set.- Existing unmanaged, missing-after-receipt, or modified managed files are `DIVERGED`.- Never overwrite a `DIVERGED` target. Inspect and reconcile it outside the installer.- Keep the generated `.thinkroom/skills-receipt-v1.json`; status and uninstall use it to verify ownership and hashes.## RemoveCheck status first, then remove only the exact managed projection:```bashthinkroom skills status --target <skill-root>thinkroom skills uninstall --target <skill-root>```The equivalent profile commands are supported for Codex and Hermes. Do not pass `--profile` and`--target` together.After any install or removal, start a fresh agent session or use the agent's supported skill reload command so its skill index reflects the filesystem.

Frequently asked questions

Thinkroom Install