How do I install the Enable skill?

Run npx skillmds@latest add marcel-bich/enable 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 Enable 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 Enable?

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

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Enable?

Marcel-Bich (@marcel-bich) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Enable by marcel-bich — Agent Skill

Name: Enable
Author: Marcel-Bich

Enable

Enable credo for the current directory. Use when the user wants credo active here - for example "enable credo here", "use credo here", "turn credo on here", "credo hier an", "credo hier aktivieren", "credo hier einschalten" - or runs the /credo:enable command. It persists a per-directory accepted decision (keyed by the git top-level else the working directory), which overrides any earlier declined: credo becomes active for this directory again, so its knowledge is re-fed at the next SessionStart and the onboarding ASK no longer fires here.

Marcel-Bich c344e89 2.0 KB Updated Sep 17, 2026

File contents

Enable credo here

Opt the current directory back in to credo. This flips the persistent per-directory decision to accepted, overriding any earlier /credo:disable (declined). From here on credo treats this directory as opted-in: the SessionStart hook re-feeds credo's command and skill knowledge, and the one-time onboarding ASK no longer fires here.

When to use

The user runs /credo:enable.
The user says, in any wording, that they want credo on for this directory / repo - for example "enable credo here", "use credo here", "turn credo on here", "credo hier an", "credo hier aktivieren".

What it does

Record this directory as opted-in (persistent, per-directory - keyed by the git top-level else the current working directory; overrides an earlier declined):

"${CLAUDE_PLUGIN_ROOT}/scripts/credo-dir-decision.sh" set accepted

Confirm

Confirm in one or two short sentences, and point out the session-mode option, for example:

credo enabled for this directory - its knowledge is re-fed at the next SessionStart and the onboarding question no longer fires here. For a specific working style you can additionally set a session mode now: /credo:session-active (intensive live collaboration) or /credo:session-passive (the agent carries most of the work, you answer clarifications).

Do not do anything else - this skill only enables credo for the directory. Setting a session mode is the user's call via the commands above.

---name: enabledescription: Enable credo for the current directory. Use when the user wants credo active here - for example "enable credo here", "use credo here", "turn credo on here", "credo hier an", "credo hier aktivieren", "credo hier einschalten" - or runs the /credo:enable command. It persists a per-directory accepted decision (keyed by the git top-level else the working directory), which overrides any earlier declined: credo becomes active for this directory again, so its knowledge is re-fed at the next SessionStart and the onboarding ASK no longer fires here.---# Enable credo hereOpt the current directory back in to credo. This flips the persistent per-directory decision toaccepted, overriding any earlier `/credo:disable` (declined). From here on credo treats thisdirectory as opted-in: the SessionStart hook re-feeds credo's command and skill knowledge, andthe one-time onboarding ASK no longer fires here.## When to use- The user runs `/credo:enable`.- The user says, in any wording, that they want credo on for this directory / repo - for example "enable credo here", "use credo here", "turn credo on here", "credo hier an", "credo hier aktivieren".## What it doesRecord this directory as opted-in (persistent, per-directory - keyed by the git top-level elsethe current working directory; overrides an earlier declined):```bash"${CLAUDE_PLUGIN_ROOT}/scripts/credo-dir-decision.sh" set accepted```## ConfirmConfirm in one or two short sentences, and point out the session-mode option, for example:> credo enabled for this directory - its knowledge is re-fed at the next SessionStart and the> onboarding question no longer fires here. For a specific working style you can additionally set> a session mode now: `/credo:session-active` (intensive live collaboration) or> `/credo:session-passive` (the agent carries most of the work, you answer clarifications).Do not do anything else - this skill only enables credo for the directory. Setting a sessionmode is the user's call via the commands above.

Frequently asked questions