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.
84
80%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/clang-format/skills/clang-format/SKILL.mdQuality
Discovery
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 well-crafted skill description with strong trigger terms and explicit 'Use when' guidance that clearly delineates its niche around clang-format configuration. The main weakness is that the 'what' portion could be slightly more specific about the concrete actions performed (e.g., generating .clang-format files, analyzing existing code to derive style rules). Overall it's a strong description that would perform well in skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (clang-format configuration) and some actions like 'analyzing code style/patterns', 'creating/modifying formatting config', 'troubleshooting formatting', but the primary action 'Configure clang-format code formatting' is somewhat general and doesn't list multiple distinct concrete operations like generating configs, validating options, or migrating between styles. | 2 / 3 |
Completeness | Clearly answers both 'what' (configure clang-format code formatting) and 'when' with an explicit 'Use when:' clause listing multiple specific trigger scenarios including file mentions, style analysis, config creation/modification, and troubleshooting. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: '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 seeking help with clang-format configuration. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche around clang-format specifically. The mention of '.clang-format', 'brace styles', 'pointer alignment', and other clang-format-specific terms make it very unlikely to conflict with general code formatting or other formatting tool skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill excels at actionability, workflow clarity, and progressive disclosure—providing concrete commands, well-sequenced workflows with validation steps, and clear navigation to categorized reference documentation. However, it is significantly over-verbose: the trigger routing section duplicates workflow content, bundled resource descriptions are unnecessarily detailed, and explanatory text throughout could be cut substantially without losing clarity. The content would benefit from being roughly half its current length.
Suggestions
Consolidate the 'Workflow Routing by Trigger Type' section and 'Common Workflows' section to eliminate duplication—the code style analysis workflow is essentially described twice with overlapping content.
Trim the 'Bundled Resources' section to a compact table or bullet list of filenames with one-line descriptions, removing 'When to use' paragraphs and other guidance Claude can infer.
Remove or drastically shorten the 'Key Concepts' section—Claude already knows what base styles, multi-language configs, and penalty systems are; a single line pointing to the relevant reference file suffices.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~250+ lines. It over-explains routing logic, repeats information across sections (e.g., the 'Analyzing Existing Code Style' workflow appears twice with overlapping content), lists every bundled file with descriptions Claude doesn't need, and includes extensive 'when to use' guidance that Claude can infer. The weighted scoring system in Trigger 2 is detailed but could be much more concise. | 1 / 3 |
Actionability | The skill provides concrete, executable bash commands throughout (clang-format --dry-run, diff commands, find/xargs pipelines, pre-commit YAML config). The code style analysis workflow includes specific verification commands and a clear scoring methodology. Commands are copy-paste ready. | 3 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with numbered steps and explicit validation checkpoints. The code analysis workflow includes a verify-iterate-report-await approval loop. Troubleshooting has a clear diagnostic sequence. The trigger routing system provides clear decision paths with feedback loops for error recovery. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear navigation to one-level-deep references organized by category (01-09.md). The Navigation Strategy section provides a clear progression path. References are clearly signaled with file paths and descriptions. The overview/detail split between SKILL.md and reference files is appropriate. | 3 / 3 |
Total | 10 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- Jamie-BitFlight/claude_skills
- Commit
11ec483
- 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.