CtrlK
BlogDocsLog inGet started
Tessl Logo

clang-format

Configure clang-format code formatting. Use when: user mentions clang-format or .clang-format, analyzing code style/patterns, creating/modifying formatting config, troubleshooting formatting, brace styles/indentation/spacing/alignment/pointer alignment, or codifying conventions.

64

Quality

76%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./plugins/clang-format/skills/clang-format/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%

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

The skill demonstrates strong actionability with executable commands and excellent workflow clarity with validation checkpoints and feedback loops, particularly in the code style analysis workflow. However, it is significantly too verbose—the trigger routing section, bundled resources catalog, and duplicated workflow descriptions inflate the token cost substantially. Content that describes bundle structure could be dramatically condensed since Claude can read the files directly.

Suggestions

Condense the 'Workflow Routing by Trigger Type' section to a brief routing table (trigger → workflow/reference) rather than inline detailed procedures that duplicate the Common Workflows section below.

Reduce the 'Bundled Resources' section to a compact file listing with one-line descriptions—Claude can read the actual files when needed rather than having their contents described.

Remove the duplicate 'Analyzing Existing Code Style' content that appears both in trigger routing and in Common Workflows; keep only the detailed version in Common Workflows and reference it from the routing table.

DimensionReasoningScore

Conciseness

The skill is extremely verbose at ~200+ lines. It over-explains routing logic, repeats information across sections (e.g., the 'Analyzing Existing Code Style' workflow appears twice with overlapping content), and includes extensive descriptions of bundled resources that Claude could discover by reading file listings. The trigger routing section alone is excessively detailed with information that could be condensed significantly.

1 / 3

Actionability

The skill provides concrete, executable bash commands throughout (clang-format --dry-run, diff commands, find/xargs patterns, pre-commit YAML config). The code style analysis workflow includes specific verification steps with actual command syntax, and the testing section provides copy-paste ready commands for common operations.

3 / 3

Workflow Clarity

Multi-step workflows are clearly sequenced with numbered steps and explicit validation checkpoints. The code style analysis workflow includes a thorough feedback loop (generate hypothesis → verify impact → measure with weighted scoring → iterate → report → await approval). Troubleshooting has clear diagnostic steps. The 'Creating New Configuration' workflow includes test-before-apply verification.

3 / 3

Progressive Disclosure

The skill references a well-organized bundle structure with clear navigation paths (templates, category guides 01-09, quick reference, complete reference). However, without bundle files provided to verify, and given that the SKILL.md itself is monolithic with substantial inline content that could be offloaded (e.g., the detailed trigger routing, the full 'Bundled Resources' catalog), the disclosure structure is only partially effective. The Navigation Strategy section at the end is helpful but the body itself contains too much detail inline.

2 / 3

Total

9

/

12

Passed

Description

89%

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

This is a strong skill description with excellent trigger term coverage and clear 'Use when' guidance that makes it highly selectable. The specificity of capabilities could be slightly improved by listing more concrete actions (e.g., 'generate config files', 'map style options'), but the domain is well-defined and the description is distinctive enough to avoid conflicts with other skills.

Suggestions

Add more concrete action verbs to the initial capability statement, e.g., 'Generate .clang-format files, map coding conventions to config options, diagnose formatting inconsistencies' to improve specificity.

DimensionReasoningScore

Specificity

Names the domain (clang-format configuration) and some actions like 'analyzing code style/patterns', 'creating/modifying formatting config', 'troubleshooting formatting', but doesn't list multiple concrete discrete actions (e.g., 'generate .clang-format files', 'convert style guides to config options').

2 / 3

Completeness

Clearly answers both 'what' (configure clang-format code formatting) and 'when' with an explicit 'Use when:' clause listing multiple trigger scenarios including file mentions, style analysis, config creation/modification, and troubleshooting.

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms: 'clang-format', '.clang-format', 'code style', 'formatting config', 'brace styles', 'indentation', 'spacing', 'alignment', 'pointer alignment', 'codifying conventions'. These are terms users would naturally use when needing this skill.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive — clang-format is a specific tool with a clear niche. The trigger terms like '.clang-format', 'brace styles', 'pointer alignment' are very unlikely to conflict with other skills. It's clearly distinguishable from general code formatting or other linter/formatter skills.

3 / 3

Total

11

/

12

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
Jamie-BitFlight/claude_skills
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.