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.
67
80%
Does it follow best practices?
Impact
—
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 strong skill description that clearly identifies its niche (clang-format configuration) and provides explicit trigger guidance with a comprehensive 'Use when:' clause. The trigger terms are excellent, covering both the tool name and specific formatting concepts users would mention. The only minor weakness is that the 'what' portion could be slightly more specific about the concrete actions performed beyond 'configure'.
| 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 mentioning clang-format, analyzing code style, creating/modifying config, troubleshooting, and specific formatting concerns. | 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 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 — it provides concrete commands, well-sequenced workflows with validation steps, and clear navigation to supporting references. However, it is significantly over-engineered and verbose: the trigger routing section duplicates content found in the common workflows, the bundled resources descriptions are unnecessarily detailed, and the overall document could be cut by 40-50% without losing any actionable information. The weighted impact scoring formula in Trigger 2 is a good idea but is presented with excessive ceremony.
Suggestions
Consolidate the 'Workflow Routing by Trigger Type' section and 'Common Workflows' section — currently the code style analysis workflow is described twice with slightly different detail levels, which wastes tokens and creates maintenance burden.
Trim the 'Bundled Resources' section to a compact table or bullet list of file paths with one-line descriptions — Claude doesn't need paragraphs explaining when to use templates or what a pre-commit hook is.
Remove explanatory prose like 'This skill provides procedural workflows for clang-format configuration tasks' and 'This workflow minimizes whitespace-only changes when introducing clang-format to existing projects' — these describe rather than instruct.
| Dimension | Reasoning | Score |
|---|---|---|
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 in both the trigger routing and the common workflows section), and includes extensive descriptions of bundled resources that Claude could discover by reading file listings. The trigger routing section alone is excessively detailed with weighted scoring formulas that could be much more concise. | 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 commands and a clear scoring methodology. The template workflow includes copy-paste ready examples. | 3 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with numbered steps and explicit validation checkpoints. The code style analysis workflow includes a verify-iterate-report feedback loop with explicit user approval gates. The troubleshooting workflow has clear diagnostic steps. The 'Creating New Configuration' workflow includes test-before-apply verification. | 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 consistently signaled with specific file paths. The bundled resources section clearly maps assets to their purposes. | 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
4e61312
- 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.