rules-distill

Extract cross-cutting principles from skills and distill them into rule files.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/freedom909/real-estate-saas --skill rules-distill-freedom909
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rules-distill
Source: https://github.com/freedom909/real-estate-saas/tree/main/.trae/skills/rules-distill
Command: npx skills add https://github.com/freedom909/real-estate-saas --skill rules-distill-freedom909

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Over time, installed skills accumulate overlapping principles that belong in shared rule files, but manually cross-reading dozens of skills to find them is impractical. This Skill automates the discovery of recurring principles across skills and proposes concrete additions or revisions to your rules, with user approval required before any change. ## Core Features & Use Cases - Deterministic Inventory: Shell scripts exhaustively scan skill frontmatter and rule file headings, outputting structured JSON for analysis. - LLM Cross-Reading with Verdicts: Batched subagent analysis matches candidate principles against full rules text and assigns verdicts — Append, Revise, New Section, New File, Already Covered, or Too Specific. - User-Gated Execution: Every candidate is presented in a summary table; rules are never modified automatically, and results are saved to results.json. - Use Case: After installing several new skills, run a monthly rules maintenance pass to surface principles like "treat LLM output as untrusted" that appear in multiple skills but are missing from your security rules. ## Quick Start Ask the AI to run rules-distill to scan all installed skills and propose updates to your rule files.

Frequently Asked Questions about rules-distill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract shared principles from multiple AI skills?▼

Run the rules-distill workflow: it scans all SKILL.md files and rule headings with shell scripts, then uses LLM subagents to cross-read batches and identify principles appearing in two or more skills. Candidates are presented for your approval before any rule file changes.

How to keep AI agent rules up to date after installing new skills?▼

Run rules-distill periodically, such as monthly or after a skill-stocktake. It compares skill content against your full rules text and proposes appends, revisions, new sections, or new rule files, each with evidence and a draft.

Does rules-distill modify rule files automatically?▼

No, rules-distill never modifies rules automatically. Every candidate is shown in a summary table with its verdict, target, and draft, and you must explicitly approve, modify, or skip each one by number.

What criteria must a principle meet to become a rule?▼

A candidate must appear in at least two skills, describe an actionable behavior change, carry a clear violation risk if ignored, and not already be covered in existing rules. Single-skill or overly specific principles stay at the skill level.

What dependencies does the rules-distill scanning require?▼

The scan scripts require bash, jq, awk, find, grep, and stat, which are standard on macOS and Linux. They read skills from ~/.claude/skills and the project .claude/skills directory, with environment overrides available for testing.