Compiles an NDJSON error journal into scored, deduplicated project rules and a routing manifest.
npx skills add https://github.com/YoLaub/JohnAI --skill compile-rules-yolaub
Please help me install this Agent Skill. Skill: compile-rules Source: https://github.com/YoLaub/JohnAI/tree/main/.claude/skills/compile-rules Command: npx skills add https://github.com/YoLaub/JohnAI --skill compile-rules-yolaub
bag.ndjson incident log into a curated set of routing-ready rules with explicit triggers, plus a regenerated routing manifest. ## Core Features & Use Cases - Grouping and scoring: Groups journal entries by exact trigger, merges near-duplicates, and scores groups by severity to decide promotion candidates. - Rule lifecycle management: Promotes qualifying incidents into rules, demotes rules with zero routing hits, archives dormant groups, and elevates rules to global scope only when confirmed in at least two projects. - Manifest regeneration and reporting: Rebuilds the routing MANIFEST from rule frontmatter and reports the recurrence rate as the primary quality metric. - Use Case: After accumulating 20+ entries in your project's error journal, ask for a compilation pass to receive a proposed diff of new rules, demotions, and an updated manifest for review before anything is written. ## Quick Start Ask the assistant to run the compile-rules pass on the project's bag.ndjson error journal and propose updated rules and manifest.High-intent search queries and answers about installing and using this skill.
Run a compilation pass over the bag.ndjson journal: entries are grouped by exact trigger, scored by summed severity, and groups scoring 5 or more (or any severity-3 occurrence) become rule candidates. Each promoted rule gets an explicit trigger condition and an action statement of at most six lines.
The journal must be an append-only NDJSON file named bag.ndjson with one JSON object per line containing trigger, symptom, root_cause, fix, severity (1-3), and date fields. The trigger holds the exact technical terms used as the grouping key.
No, the skill only produces a proposed diff. All changes to the rules directory or MANIFEST.md require explicit user validation before being applied, and the pass never triggers automatically without an explicit request.
A rule moves to the global folder only when it has been confirmed independently in at least two different projects. Everything starts local by default, because an incorrect global rule affects every project that routes to it.
The pass requires at least 20 entries in bag.ndjson before grouping, because smaller volumes do not provide enough signal to distinguish real patterns from noise. Below that threshold it stops and reports the insufficient volume.
The primary metric is the recurrence rate: the share of logged errors whose trigger was already covered by an existing rule. A recurrence means the rule exists but its trigger does not match the real context, which is more informative than counting rules.
agencia-conversionCreate an Agentic SEO project structure with brain templates and metadata.
Kord96Classify and route input content into configuration, credential, or memory destinations.
xiaohei-infoCompile raw research notes into an interlinked Obsidian wiki.
cipherstashRun pre-commit checks and create atomic conventional commits.