CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

patch-creation

Create and register new patches for tweakcc. Use when adding new customizations to Claude Code.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A high-quality, highly actionable skill: complete executable code, a well-sequenced workflow with validation checkpoints, and clean navigation. The only notable weakness is redundancy between the checklist, the pattern tips, and the inline code comments, plus examples that could live in a reference file.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence (no explanations of regex or JS basics), but the Registration Checklist restates the numbered steps and Pattern Writing Tips 1, 2, 5, and 6 duplicate the inline IMPORTANT comments in the code template, so some trimming is possible.

4 / 5

Actionability

The skill provides a complete, copy-paste-ready TypeScript template with real imports and failure handling, exact registry entries with file paths, and concrete test commands (npm run build, npx tweakcc --apply), plus two additional executable patterns (feature-flag bypass, value replacement) covering common cases.

5 / 5

Workflow Clarity

The five-step creation sequence is explicit and numbered, reinforced by a checklist, with validation built in (showDiff for inspection, return null on failure, and a Testing section that checks console output and verifies behavior in Claude Code).

5 / 5

Progressive Disclosure

No bundle files exist, and the self-contained body is well organized with clear section headers and a Key Files table; however, at roughly 210 lines, the worked examples and pattern tips are inline where a references file could hold them, keeping it just short of the clear-overview-with-split-content ideal.

4 / 5

Total

18

/

20

Passed

Description

70%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A solid description with a clear what and an explicit Use-when clause tied to a distinct niche. Its main gaps are limited enumeration of capabilities and a somewhat generic trigger clause that misses natural variations.

Suggestions

Enumerate the full scope of actions in the description (e.g., 'Create patch files, add config types and defaults, register patches in the index, and add UI toggles') to lift specificity.

Make the when-clause more concrete with trigger phrases users would actually say, e.g., 'Use when the user wants to add a feature, toggle, or customization to Claude Code via tweakcc, or asks to write or register a new patch.'

Include a couple of natural synonyms (e.g., 'tweak cc', 'patch the Claude Code CLI') to broaden trigger coverage without losing the niche focus.

DimensionReasoningScore

Specificity

"Create and register new patches" names the domain (tweakcc patches) and two concrete actions, but stops short of the fuller workflow (config types, defaults, UI registration) covered in the body, matching the '1-2 concrete actions, not comprehensive' anchor.

3 / 5

Completeness

It answers both questions — what ("Create and register new patches for tweakcc") and when ("Use when adding new customizations to Claude Code") — but the when-clause is general rather than packed with concrete trigger phrases, so it falls just below the explicit anchor-5 example.

4 / 5

Trigger Term Quality

"patches", "tweakcc", "customizations", and "Claude Code" are terms a user would naturally say when needing this skill, though common variations (e.g., "tweak cc", "add a feature to Claude Code", "patch the CLI") are missing.

4 / 5

Distinctiveness Conflict Risk

The tweakcc patching niche is well-scoped and distinct, but the trigger "adding new customizations to Claude Code" could fire for non-tweakcc customization requests, creating minor overlap risk with broader Claude Code configuration skills.

4 / 5

Total

15

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Piebald-AI/tweakcc

Path

.claude/skills/patch-creation/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.