schliff

Solid

Deterministic skill linter and scoring engine for Claude Code — the Ruff for SKILL.md files. 7-dimension structural scoring (structure, triggers, quality, edges, efficiency, composability, clarity) with anti-gaming detection, ~32% rule-based patches, and cross-session episodic memory. An autoresearch loop that measures first, then fixes — not the other way around. Use for linting, scoring, and autonomously improving any Claude Code skill: trigger accuracy, output quality, edge coverage, token efficiency, composability, or custom metrics. Works with community, custom, project-local, or global skills. Trigger phrases: "make this skill better", "optimize my skill", "iterate on this skill overnight", "improve [metric] from X to Y", "audit skill", "review my skill", "harden skill", "benchmark skill", "lint my skill", "score my skill", or paste SKILL.md for auto-analysis. Also use when user shares skill without explicit instructions. Do NOT use for brand-new skills from scratch — use skill-creator first, then come

Code & Development 11 stars 0 forks Updated today MIT

Install

View on GitHub

Quality Score: 79/100

Stars 20%
36
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Schliff — Skill Measurement & Iteration Framework Constraint + clear metric + disciplined iteration = compounding gains. The composite score measures structural quality (file organization, keyword coverage, eval suite breadth) — not runtime effectiveness. Use `--runtime` to validate actual behavior. ## Quick Start (Only 2 Inputs Required) ```bash /schliff Target: path/to/SKILL.md Goal: Make the skill trigger correctly for deployment scenarios ``` Defaults: Metric=composite_score, Verify=score-skill.py, Iterations=30. ## Core Loop (NEVER Pauses) ``` INPUT: Skill path + GOAL + PRIMARY METRIC + VERIFY method + time budget SETUP: Read ALL files → Analyze → Generate eval suite → Baseline (#0) LOOP (N iterations, continues until goal met or budget exhausted): Exp N: Review skill + results + git history → Pick ONE atomic change (based on gaps + history) → Edit SKILL.md or references → Commit: "schliff exp-N: [description]" → Run VERIFY, compute PRIMARY METRIC → Improved? Keep. Worse? Revert. Error? Fix or skip. → Append to history/ with diffs CONSTRAINT: Fixed iterations prevent infinite loops; autonomous mode = NO prompts between iterations, just continuous improvement. ``` ## When to Use - **Skill not triggering** → Run `/schliff` on trigger-accuracy metric - **Wrong/incomplete outputs** → Set goal, metric = binary eval pass rate - **Harden for edge cases** → Focus on edge-coverage metric - **Skill too verbose** → Optimize token-efficiency metric - **Do...

Details

Author
Zandereins
Repository
Zandereins/schliff
Created
4 months ago
Last Updated
today
Language
Python
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

skill-improver

Autoresearch loop for Claude Code skills — greedy keep/discard hill climbing on a 10-dimension quality rubric, with blind subagent validation for self-scoring bias, plus a `freshen` mode that probes external references (release notes, docs, deprecation signals) and applies verified updates, plus a `trigger` mode that measures and tunes the skill's frontmatter description until it reliably fires when it should and stays silent when it shouldn't (60/40 train/test split, 7 runs/query, blinded test scores).

3 Updated 2 days ago
air-gapped
AI & Automation Listed

skill-creator

Author, audit and iterate on Claude skills - write a new SKILL.md from scratch, restructure or trim an existing one, and measure whether it actually works. Use when the user wants to create a skill, turn a workflow they just did into a skill, edit or improve an existing skill, fix a skill's frontmatter or description, run evals against a skill, benchmark a skill against a no-skill baseline, or optimize a description so it fires at the right time and not the wrong one. Also use when a skill needs validating before it ships - frontmatter key allowlist, the 1024-character description cap, ASCII, referenced-path existence. Not for acquiring or installing a skill from a repo or URL, or porting an already-authored skill between platforms - that is install-skill.

1 Updated today
M4NUSH7
AI & Automation Solid

claude-codeskill

Creating and optimizing Claude Code Skills including activation patterns, content structure, and development workflows. Use when creating new skills, converting memory files to skills, debugging skill activation, or understanding skill architecture and best practices.

15 Updated today
bendrucker