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.
90
87%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 well-chosen and cover 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 style versions. | 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
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with excellent workflow clarity and progressive disclosure. The trigger-based routing system is a strong organizational pattern, and the code style analysis workflow with weighted impact scoring is particularly well-designed with proper validation loops. The main weakness is moderate verbosity—some explanatory content could be trimmed since Claude already understands concepts like base styles and penalty systems.
Suggestions
Trim the 'Key Concepts' section—Claude already understands base styles, multi-language configs, and penalty systems; reduce to just the non-obvious details like specific BasedOnStyle syntax.
Remove the 'Purpose' section as it largely restates the skill description and the workflow routing section already serves as an effective overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately verbose. The 'Workflow Routing by Trigger Type' section is detailed and useful but could be tightened. Some sections like 'Key Concepts' explain things Claude already knows (e.g., what base styles are, what a penalty system is). The 'Purpose' section restates what the description already covers. However, most content is functional rather than padded. | 2 / 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 weighted scoring methodology and iteration steps. The template selection, editor integration, and CI/CD workflows all have copy-paste ready commands and configurations. | 3 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with numbered steps and explicit validation checkpoints. The code style analysis workflow includes a full feedback loop: generate hypothesis → verify impact → measure with weighted scoring → iterate → report → await approval. Troubleshooting has clear diagnostic steps (dump-config → identify category → test isolated). The trigger routing system provides clear decision logic. | 3 / 3 |
Progressive Disclosure | Content is well-structured with a clear overview pointing to one-level-deep references organized by category (01-09.md). The 'Bundled Resources' section clearly catalogs all available assets with descriptions and when-to-use guidance. The 'Navigation Strategy' section provides explicit progression from templates → quick reference → category guides → complete reference. References are clearly signaled with file paths. | 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
b9f32ec
Table of Contents
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.