agentleFS
Sign inStart free
afaraha8403afaraha8403/mental/skills/mental-setup/SKILL.md

mental-setup

Skill5 starsChanged yesterdayMITView on GitHub

Install or upgrade the Mental CLI when the Mental plugin is present, mental is missing from PATH, the user asks to set up or upgrade continuity, or doctor / JSON says the CLI is behind npm. Use when installing Mental CLI from a marketplace or plugin UI. For daily continuity once the CLI is current, follow the Mental skill copied by mental install.

  • Installs packages

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 0 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Never execute a .mjs file as a command (Windows shows "how do you want to open this file?").

    line 32
  2. Very specific:

    Run this migration once. The distinct repair bin remains reachable when an old mental shadows npm.

    line 48
  3. Very specific:

    If PowerShell blocks npm-generated .ps1 launchers, use npm.cmd and mental.cmd explicitly.

    line 58
  4. Very specific:

    Use only this client's plugin flow if they still need the host plugin.

    line 78
  5. Very specific:

    Do not run other hosts' /plugin, copilot plugin, or Command Palette steps from this session.

    line 79
  6. Very specific:

    After doctor, re-run mental doctor --json.

    line 81
  7. Very specific:

    Do not start a plugin MCP server.

    line 89

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

Mental setup — install the CLI

The Mental plugin is discovery only. It does not run Mental CLI. The product is the CLI on PATH.

Never execute a .mjs file as a command (Windows shows "how do you want to open this file?"). Do not install from a git clone or plugin cache. npm owns the executable; mental install only copies the procedure/rule/config.

Fresh install — every supported shell

npm i -g @balacode/mental
mental install
mental doctor

Daily invoke: mental … --json.

Existing Windows install from Mental 0.8.1 or older

Run this migration once. The distinct repair bin remains reachable when an old mental shadows npm.

npm i -g @balacode/mental
mental-repair.cmd
mental install
mental doctor

If PowerShell blocks npm-generated .ps1 launchers, use npm.cmd and mental.cmd explicitly. Never change execution policy on the user's behalf.

If mental is already current

Daily work: follow the Mental skill (copied by install into ~/.cursor/skills/mental, ~/.claude/skills/mental, ~/.agents/skills/mental). Use the daily invoke for this OS. Stop.

Upgrade (the user asked, JSON includes update, or doctor says the CLI / copied skill / host plugin is behind): run the fresh-install block again. Existing Windows 0.8.1-or-older installs run the migration block once. Journals stay. Do not re-run this client's plugin marketplace unless doctor says the host plugin is behind. Then follow the Mental skill.

If the CLI is missing

  1. Continue the user's coding task; Mental fails open.
  2. Tell the user to run the fresh-install block. If this is an existing Windows install, use the one-time migration block. Never run a .mjs file as a command.
  3. Use only this client's plugin flow if they still need the host plugin. Do not run other hosts' /plugin, copilot plugin, or Command Palette steps from this session.
  4. After doctor, re-run mental doctor --json. If error-level checks remain that --fix can repair, run mental doctor --fix --json once (home skills/rules + git excludes; never --project or optionals). Then ask whether they want optional hooks or time tracking (sit-down clock, default off), and whether MCP is needed (mental install --mcp). Skip MCP if this client can run the CLI. Never run mental option … on until they say yes this turn.

Do not start a plugin MCP server. Do not silent-global-install from a hook. Missing Mental must not block the user's coding task (fail open).

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.

Reviews can't be read right now.

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