Monitor CI
nrwl/nx
Monitor Nx Cloud CI pipeline and handle self-healing fixes. An agent skill from nrwl/nx.
Inspect, audit, enable, or disable project live-rules. An agent skill from Eigenwise/eigenwise-toolshed.
Install Manage Rules
$ npx skills add Eigenwise/eigenwise-toolshed --skill manage-rules -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Eigenwise/eigenwise-toolshed manage-rules --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Eigenwise/eigenwise-toolshed.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/live-rules/skills/manage-rules .claude/skills/manage-rules && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "manage-rules" agent skill from https://github.com/Eigenwise/eigenwise-toolshed/tree/main/plugins/live-rules/skills/manage-rules into .claude/skills/manage-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manage-rules", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Eigenwise/eigenwise-toolshed/tree/main/plugins/live-rules/skills/manage-rulesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Eigenwise/eigenwise-toolshed --skill manage-rules -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Eigenwise/eigenwise-toolshed manage-rules --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Eigenwise/eigenwise-toolshed.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/live-rules/skills/manage-rules .agents/skills/manage-rules && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "manage-rules" agent skill from https://github.com/Eigenwise/eigenwise-toolshed/tree/main/plugins/live-rules/skills/manage-rules into .agents/skills/manage-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manage-rules", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Eigenwise/eigenwise-toolshed --skill manage-rules -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Eigenwise/eigenwise-toolshed manage-rules --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Eigenwise/eigenwise-toolshed.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/live-rules/skills/manage-rules .cursor/skills/manage-rules && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "manage-rules" agent skill from https://github.com/Eigenwise/eigenwise-toolshed/tree/main/plugins/live-rules/skills/manage-rules into .cursor/skills/manage-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manage-rules", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Eigenwise/eigenwise-toolshed.git --path plugins/live-rules/skills/manage-rules--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Eigenwise/eigenwise-toolshed --skill manage-rules -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Eigenwise/eigenwise-toolshed manage-rules --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Eigenwise/eigenwise-toolshed.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/live-rules/skills/manage-rules .gemini/skills/manage-rules && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "manage-rules" agent skill from https://github.com/Eigenwise/eigenwise-toolshed/tree/main/plugins/live-rules/skills/manage-rules into .gemini/skills/manage-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manage-rules", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Eigenwise/eigenwise-toolshed manage-rulesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Eigenwise/eigenwise-toolshed --skill manage-rules -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Eigenwise/eigenwise-toolshed.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/live-rules/skills/manage-rules .github/skills/manage-rules && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "manage-rules" agent skill from https://github.com/Eigenwise/eigenwise-toolshed/tree/main/plugins/live-rules/skills/manage-rules into .github/skills/manage-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manage-rules", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Eigenwise/eigenwise-toolshed --skill manage-rules -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Eigenwise/eigenwise-toolshed manage-rules --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Eigenwise/eigenwise-toolshed.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/live-rules/skills/manage-rules .opencode/skills/manage-rules && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "manage-rules" agent skill from https://github.com/Eigenwise/eigenwise-toolshed/tree/main/plugins/live-rules/skills/manage-rules into .opencode/skills/manage-rules/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manage-rules", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
manage-rules- GitHub stars
- 277
- Token cost
- ~2k tokens
- SKILL.md length
- 1,128 words
- Files
- 1
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- MIT
At a glance
Inspect, audit, enable, or disable project live-rules. An agent skill from Eigenwise/eigenwise-toolshed.
- Works in 4 steps: If .claude/live-rules/rules/ exists,… → If the directory exists but… → If the manifest is parseable but hashes… → …
- Check active instructions
- SKILL.md covers Find the rules and manifest, How to read the files, Tasks and Guidelines, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Manage Rules is an agent skill from Eigenwise/eigenwise-toolshed. Inspect, audit, enable, or disable project live-rules. Use to list rules, check active instructions, explain an injected rule, or recover an atomic manifest.
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud. The repository describes itself as: Six Claude Code plugins for the work that keeps coming back: repo maps, conditional rules, ticketed parallel work, extra subscription models, local usage metrics, and guided setup. The licence is MIT.
When your agent uses it
- Check active instructions
- Explain an injected rule
- Recover an atomic manifest
Example prompts
- “/manage-rules”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- If .claude/live-rules/rules/ exists, inspect its .md files and the generated manifest.
- If the directory exists but manifest.json is missing, malformed JSON, or has the wrong schema,
- If the manifest is parseable but hashes or metadata do not match the rule files, report a stale
- If the atomic directory is absent, resolve the legacy file from LIVE_RULES_PATH or the default
What it can do on your machine
Read from SKILL.md and the folder at commit 92c16cd. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Manage Rules loads about 2k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 1,128 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Eigenwise/eigenwise-toolshed at commit 92c16cd, republished under its MIT licence (© Eigenwise). 1,128 words, ~1,978 tokens.
Download SKILL.mdSave it as
.claude/skills/manage-rules/SKILL.md (or your agent's skills folder).- name
- manage-rules
- description
- Inspect, audit, enable, or disable project live-rules. Use to list rules, check active instructions, explain an injected rule, or recover an atomic manifest.
Manage Rules
Read, audit, and toggle live rules without changing what a rule says. For authoring or editing rule
content, use the add-rule skill. The full format is documented in
../add-rule/references/rule-format.md.
New workspaces use one rule per Markdown file under .claude/live-rules/rules/ and a generated
.claude/live-rules/manifest.json. Never edit the manifest directly. After every rule-file change,
run:
node "${CLAUDE_PLUGIN_ROOT}/scripts/sync-atomic-rules.js" --project "${CLAUDE_PROJECT_DIR}"Existing projects may still use a legacy file. The default is .claude/live-rules.md; an explicit
LIVE_RULES_PATH may point to another project-relative, absolute, or ~-relative file. The legacy
format is for migration or an explicit override only. SessionStart automatically migrates the default
legacy file, verifies the atomic result, and removes the old file. An explicit path is preserved, and a
failed verification keeps the legacy file.
Find the rules and manifest
Check the atomic directory first:
- If
.claude/live-rules/rules/exists, inspect its.mdfiles and the generated manifest. - If the directory exists but
manifest.jsonis missing, malformed JSON, or has the wrong schema, report an atomic manifest recovery problem, not "no rules". Run the sync command above to rebuild the manifest from the rule files, then audit again. - If the manifest is parseable but hashes or metadata do not match the rule files, report a stale manifest. The runtime reads the rule files directly and marks the mismatch; run sync to resync it.
- If the atomic directory is absent, resolve the legacy file from
LIVE_RULES_PATHor the default path. If that file exists, report legacy storage and explain that SessionStart can migrate it. If no atomic directory and no legacy file exist, report that no rules are configured and point the user toadd-rule.
A missing or malformed manifest with atomic rule files is never a clean no-rules result. Preserve the rule files while recovering it. If sync names a malformed rule file, repair that file and run sync again.
How to read the files
For atomic storage, inspect every .md rule under .claude/live-rules/rules/. Each file must contain
exactly one rule. Compare its parsed metadata and content hash with the corresponding manifest entry.
For legacy storage, parse the file as a sequence of frontmatter sections. Anything before the first
fence is an intro; a bare file with no complete frontmatter block is one global rule.
Tasks
List the rules
Parse every section or atomic file and present a compact table. Use the description as the rule name,
fallback to the filename or position:
| Rule | Storage | Scope | Fires when | Priority | Enabled |
|---|---|---|---|---|---|
| House style | atomic | global | matching prompt when unseen or changed | 0 | yes |
| React component conventions | atomic | glob | editing **/*.tsx when unseen or changed | 0 | yes |
| API layer rules | atomic | dir | editing under packages/api, or matching cwd | 0 | yes |
| Deploy checklist | atomic | prompt | prompt matches deploy when unseen or changed | 0 | yes |
| Strict lint gate | atomic | glob | matching edit | 0 | no |
Derive scope the same way as the hooks: no globs, dirs, or prompt means global; otherwise list
whichever are present. A rule with only include: is still global. Note the include payload and
whether its target exists.
Audit the rules
Check the storage and manifest before checking individual rules. Report concrete issues and the exact recovery:
- Missing or malformed atomic manifest:
.claude/live-rules/rules/exists butmanifest.jsonis absent, invalid JSON, or has an unsupported shape. Run the owned sync command; do not report no rules. - Stale atomic manifest: a rule hash, path, or metadata field differs from the generated value. The rule files are the authority; run sync to resync the manifest.
- Dropped atomic rule: a manifest entry points to a missing or unsafe path, or a file contains more than one rule. Name the file, repair it, and run sync.
- Broken or empty frontmatter that the parser would skip, such as an unterminated array, missing
closing
---, or no body. - A stray
---inside a body, which the parser reads as the next rule's fence. Suggest***or___instead. - Globs that match nothing in the repo. Compile the glob and test it against tracked files before reporting it.
- Invalid prompt regexes written as
/.../flags. - An
include:target that does not exist. A rule whose includes are all missing is dropped and injects nothing. - Duplicates or conflicts: contradictory instructions or near-identical rules that should be merged.
- Oversized rules: a body long enough to crowd the roughly 10k-character injection budget.
- Over-broad global rules that should be scoped to a file, directory, or prompt.
- Unexpected legacy storage: explain the migration or explicit
LIVE_RULES_PATHexception and check whether SessionStart can migrate it.
Summarize findings as a short list of "rule or manifest: problem, suggested fix". Only change content
if the user asks. add-rule is the right tool for content rewrites; manifest recovery uses the sync
command.
Show full SKILL.md (353 more words)Show less
Enable or disable a rule
Toggle a rule without deleting it: find its atomic file or legacy section, set enabled: true or
enabled: false in its frontmatter, and save. For atomic storage, run sync after saving so the
manifest records the new metadata. Leave other files and sections untouched. Confirm which rule you
toggled and its new state.
Explain what is active
Given a situation such as "for a normal prompt", "when I edit src/app/page.tsx", or "when I say
'tdeploy'", walk the rules and report which ones are eligible and why, mirroring the hook logic:
- At SessionStart: applicable startup rules are injected and the session ledger is reset.
- On a prompt: global rules, matching prompt rules, and directory rules whose directory contains the session cwd are selected; only new or changed unseen hashes are emitted after SessionStart.
- Before an edit: glob rules matching that file and directory rules containing it are selected; only new or changed unseen hashes are emitted.
A rule carrying include: fires only if at least one included file exists. If all are missing it is
dropped. Explain whether a selected rule was already seen unchanged in this session or is newly matching,
so "why did Claude follow this?" and "why didn't it?" have a concrete answer.
Guidelines
- Read and toggle, not rewrite. Send content changes to
add-rule. - Recover manifests from source files. Never hand-edit generated JSON.
- Verify before claiming. Test a glob against the repo file list and inspect include targets.
- Never touch
CLAUDE.mdorCLAUDE.local.md. - After a change, remind the user to review and commit the atomic rule files and generated manifest so the team stays in sync.
Success criteria
- Atomic directory, rule files, manifest, and legacy fallback are distinguished
- Missing or malformed manifests are reported as recovery problems, never as clean no-rules
- Existing resync command is run or clearly directed when the manifest is missing or stale
- Rules are listed with storage, scope, trigger, priority, and enabled state
- Audit reports real, rule-specific issues and tests globs against actual files
- Any enable/disable change applies to the right file or section and is synced when atomic
-
CLAUDE.mdis untouched
© Eigenwise, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/live-rules/skills/manage-rules of Eigenwise/eigenwise-toolshed.
Open the folder on GitHubat commit 92c16cd
Compare with similar skills
Manage Rules next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Manage Rules this skillEigenwise/eigenwise-toolshed | 277 | — | ~2k | Automated safety check: Pass | MIT | |
| Monitor CInrwl/nx | 29k | 6 repos | ~4.7k | Automated safety check: Pass | MIT | |
| Terraform and OpenTofu Guideagentscope-ai/QwenPaw | 35k | 6 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Vercel Optimize Auditvercel-labs/agent-skills | 32k | 9 repos | ~4.3k | Automated safety check: Pass | None | |
| Openclaw Live Updateropenclaw/openclaw | 392k | — | ~3.7k | Automated safety check: Pass | MIT | |
| Analyze GitHub Action Logswithastro/astro | 63k | 1 repos | ~1.3k | Automated safety check: Pass | Custom licence |
Similar skills
Terraform and OpenTofu Guide
agentscope-ai/QwenPaw
Guidance for writing and testing Terraform and OpenTofu code: module structure, naming, test approaches, CI/CD workflows, state handling and security scanning.
- Official
Vercel Optimize Audit
vercel-labs/agent-skills
Runs a metrics-first audit of a deployed Vercel project, gating investigations on real signals to produce ranked, citation-backed cost and performance recommendations.
Openclaw Live Updater
openclaw/openclaw
Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation.
- Official
Analyze GitHub Action Logs
withastro/astro
Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements.
KubeSphere Multi-Tenant Management
kubesphere/kubesphere
Creates and queries KubeSphere users, workspaces and projects and assigns built-in roles, defaulting to least privilege and never deleting anything.
More from Eigenwise/eigenwise-toolshed
All 14 skills in this repoAdd Rule
Eigenwise/eigenwise-toolshed
Create or edit a live-rules instruction in the project's atomic rule set.
Map Codebase
Eigenwise/eigenwise-toolshed
Create a self-maintaining codebase map in .claude/.codebase-info/.
Setup
Eigenwise/eigenwise-toolshed
Set up a Claude Code workspace for a new or existing project, informed by hindsight from the user's whole session history.
Groom
Eigenwise/eigenwise-toolshed
Audit a Sidequest board for completed, stale, duplicate, or superseded tickets, then safely close clear cases.
Toolshed Doctor
Eigenwise/eigenwise-toolshed
Run a read-only health check for Quartermaster and installed Toolshed plugins.
Enable Project Telemetry
Eigenwise/eigenwise-toolshed
Opt the current project into local Claude Code usage telemetry, or verify its setup.
Related
Categories
Questions about Manage Rules
What does Manage Rules do?
Inspect, audit, enable, or disable project live-rules. An agent skill from Eigenwise/eigenwise-toolshed. Manage Rules is an agent skill from Eigenwise/eigenwise-toolshed. Inspect, audit, enable, or disable project live-rules.
When should I use Manage Rules?
Manage Rules fits situations like: check active instructions; explain an injected rule; recover an atomic manifest.
How do I install Manage Rules in Claude Code?
Run `npx skills add Eigenwise/eigenwise-toolshed --skill manage-rules -a claude-code`. Or copy the skill folder (plugins/live-rules/skills/manage-rules in Eigenwise/eigenwise-toolshed) into .claude/skills/manage-rules in your project. Claude Code loads it when a task matches its description.
How do I install Manage Rules in Codex?
Run `npx skills add Eigenwise/eigenwise-toolshed --skill manage-rules -a codex`. Or copy the skill folder (plugins/live-rules/skills/manage-rules in Eigenwise/eigenwise-toolshed) into .agents/skills/manage-rules in your project. Codex loads it when a task matches its description.
Can I use Manage Rules in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Eigenwise/eigenwise-toolshed --skill manage-rules -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/manage-rules, .gemini/skills/manage-rules, .github/skills/manage-rules and .opencode/skills/manage-rules in your project.
What does Manage Rules need to run?
SKILL.md names no scripts, command-line tools or credentials: Manage Rules is instructions for the agent only.
Does Manage Rules access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Manage Rules safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Manage Rules use?
Manage Rules is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Manage Rules use?
About 2k tokens (SKILL.md is roughly 7.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Manage Rules?
Skills that share tags, products or a category with Manage Rules: Monitor CI (nrwl/nx, 29k stars), Terraform and OpenTofu Guide (agentscope-ai/QwenPaw, 35k stars), Vercel Optimize Audit (vercel-labs/agent-skills, 32k stars) and Openclaw Live Updater (openclaw/openclaw, 392k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Manage Rules?
Eigenwise (a GitHub user) maintains it in Eigenwise/eigenwise-toolshed, which has 277 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 7, 2026.
Source: Eigenwise/eigenwise-toolshed on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.