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.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

78%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 well-structured, highly actionable skill with verified one-level-deep progressive disclosure and validated workflows. The main weakness is token efficiency: redundant sections (Purpose, Key Concepts, Testing Configurations) restate the description, known concepts, or earlier commands.

Suggestions

Cut the 'Purpose' section, which restates the frontmatter description verbatim in bullet form.

Trim 'Key Concepts' to the two items that add non-obvious information (penalty system pointer, multi-language example) and drop the base-style enumeration Claude already knows.

Remove the 'Testing Configurations' section or merge its unique commands into the existing workflows to eliminate repeated dry-run/diff/-i command blocks.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient concrete guidance, but the 'Purpose' section restates the description, 'Key Concepts' enumerates base styles (LLVM, Google, Chromium, ...) Claude already knows, and 'Testing Configurations' repeats commands shown in earlier workflows.	3 / 5
Actionability	Copy-paste ready bash blocks (cp, chmod, clang-format --dry-run, diff pipelines), a pinned pre-commit YAML config, and a concrete weighted impact-scoring formula with an exact verification command for each hypothesis.	5 / 5
Workflow Clarity	Numbered workflows with explicit validation steps (dry-run, diff, --dump-config) and an iterate-with-user-approval loop in the analysis workflow; held below 5 because the critical Trigger 2 workflow is compressed into a single dense run-on paragraph and the CI/CD workflow lacks a verification step.	4 / 5
Progressive Disclosure	The body acts as a navigation hub with well-signaled, one-level-deep references: all cited paths (references/01-09.md, quick-reference.md, cli-usage.md, complete/, assets/configs/, assets/integrations/) resolve to real files, no reference chains nest deeper than one level, and a Navigation Strategy section orders the progression.	5 / 5
	Total	17 / 20 Passed

Description

91%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 strong description: concise, third-person, with an explicit 'Use when' clause and rich trigger coverage including the file extension. Only minor overlap risk from the broader code-style triggers.

Dimension	Reasoning	Score
Specificity	The capability statement 'Configure clang-format code formatting' is concrete, and the trigger clause enumerates further specific actions (analyzing code style, creating/modifying config, troubleshooting), but the primary 'what' is a single action rather than the comprehensive multi-action list of a 5.	4 / 5
Completeness	Explicitly answers both what ('Configure clang-format code formatting') and when ('Use when: user mentions clang-format or .clang-format, analyzing code style/patterns, ...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural-language coverage including the tool name, the '.clang-format' file extension, and phrases users would actually say: 'analyzing code style/patterns', 'troubleshooting formatting', 'brace styles/indentation/spacing/alignment/pointer alignment', and 'codifying conventions'.	5 / 5
Distinctiveness Conflict Risk	The named tool and file extension give it a clear niche with minimal conflict risk, but broad triggers like 'analyzing code style/patterns' and 'codifying conventions' could overlap with generic lint/format skills, keeping it below a 5.	4 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 5 missing, 7 deeper-than-1-level	Warning

	Total	15 / 16 Passed

Repository: Jamie-BitFlight/claude_skills
Path: plugins/clang-format/skills/clang-format/SKILL.md
Commit: 3e0b2af

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.