Rules Checkup

Organization

etherfunlab

rules-checkup

Use when the user asks to check up, audit or prune their rule files (CLAUDE.md, AGENTS.md, .claude/rules, memory) — 体检一下, "rules checkup" — or after a reminder that Claude Code changed version. Produces a list of candidate deletions and edits; changes nothing until the user approves.

Overview

Publisher	etherfunlab
Repository	`workflow`
Skill name	`rules-checkup`
Stars	75
Forks	17
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by etherfunlab on GitHub. Read the source before you install it.

Installation

Install the Rules Checkup AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/etherfunlab/workflow/tree/main/modules/checkup/agent/skills/rules-checkup
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/etherfunlab/workflow/tree/main/modules/checkup/agent/skills/rules-checkup

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/etherfunlab/workflow.git /tmp/workflow
mkdir -p .claude/skills
cp -r /tmp/workflow/modules/checkup/agent/skills/rules-checkup .claude/skills/rules-checkup

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Rules Checkup in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Rules Checkup on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Rules Checkup is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Rules checkup

Rule files are written against the harness of the day. A new harness version can change the system prompt, so a rule that once filled a gap may now repeat the system prompt, fight it, or point at files that no longer exist. This skill lists what to cut. The user decides.

Read everything first

User level: ~/.claude/CLAUDE.md and every file it imports with @.
Project: every CLAUDE.md and AGENTS.md from the repo root down to the working directory, and their @ imports.
.claude/rules/*.md.
The memory index: ~/.claude/projects/<project>/memory/MEMORY.md, or .memory/MEMORY.md.
Your own current system prompt and tool descriptions, as you see them in this session.

Six kinds of candidate

Kind	Test
Redundant	The system prompt already says the same thing, in the same direction
Conflicting	The rule pushes against the system prompt or against another rule
Stale fact	A path, command, file, flag or name in the rule no longer exists. Check each one with a command (`ls`, `command -v`, `git ls-files`, `--help`); never judge from memory
Duplicate	The same rule lives in memory and in a rule file, or in two rule files
Hidden brake	A stop-or-ask rule fires only after the agent first classifies the situation ("if this is a side task, ..."). The moment it is needed is the moment the classification gets skipped
Incident residue	Dates, PR or issue numbers, line numbers, measured figures, post-mortems or tombstones inside a rule

Output

One numbered list grouped by kind. Each item: file:line, the rule (quoted, shortened), why it is a candidate, and the proposed change (delete / shorten to "..." / move to ...). End with "Which items should I apply?" and stop.

Rules

Change nothing until the user approves. Approval is per item unless the user says "all".
A checkup only removes, shortens or moves rules. It never adds one.
After applying approved changes, record the date: set last_checkup (YYYY-MM-DD) in ~/.claude/workflow-checkup.json, creating the file if needed, with jq.

Red flags

"These are obviously stale, I'll just delete them." → List first, then wait.
"While I'm here I'll add a rule for X." → Not in a checkup.
"I remember this path exists." → Run the check.
"The user is in a hurry, so I'll apply everything." → Hurry is not approval.

Frequently asked questions

What does the Rules Checkup AI skill do?

Why use Rules Checkup on TypingMind?

Because you install it once and use it with any model. Rules Checkup is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Rules Checkup in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/etherfunlab/workflow/tree/main/modules/checkup/agent/skills/rules-checkup. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Rules Checkup?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Rules Checkup?

As many as you like. As long as a model supports skills, you can use Rules Checkup with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Rules Checkup AI skill free?

Yes. It is published on GitHub by etherfunlab under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Apple Reminders

openclaw

OrganizationPopular

List, add, edit, complete, or delete Apple Reminders and reminder lists via remindctl.

Clawhub

Search ClawHub for skills when a requested capability is not already available; install, verify, update, uninstall, publish, or sync skills.

Diagnosing Superpowers

obra

CommunityPopular

Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so…

Brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Rules checkup

Read everything first

Six kinds of candidate

Output

Rules

Red flags

Frequently asked questions

Related AI Skills

Set up your own AI workspace now