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

89%

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

85%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 body with explicit validation and approval checkpoints for the risky batch-formatting workflow and clean progressive disclosure to verified bundle files. The main weakness is conciseness: the Trigger 2 routing paragraph is a dense wall of text and some content overlaps between routing and common-workflow sections.

Suggestions

Break the dense Trigger 2 paragraph into a short numbered procedure or bullet list so the weighted-metric impact scoring is scannable instead of an inline wall of text.

Consolidate the 'Workflow Routing by Trigger Type' and 'Common Workflows' sections to remove duplicated routing of the same workflows (e.g., code-style analysis appears in both).

Trim the 'Key Concepts' explanations of Base Styles and the Penalty System, which cover clang-format behavior Claude largely already knows.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of generic concept explanation, but the dense Trigger 2 paragraph embeds a multi-bullet weighted-metric procedure as a wall of text and the 'Common Workflows' section partially duplicates the routing section, so it could be tightened.	3 / 5
Actionability	Provides copy-paste-ready, executable commands throughout ('clang-format --dry-run --Werror', 'clang-format file.cpp \| diff - file.cpp', 'find src include ... \| xargs clang-format -i') plus a concrete pinned pre-commit YAML example covering the common cases.	5 / 5
Workflow Clarity	Multi-step workflows are explicitly sequenced with validation checkpoints and a feedback loop: Trigger 2 has VERIFY IMPACT, MEASURE IMPACT, ITERATE, and AWAIT USER APPROVAL before finalizing the batch formatting change.	5 / 5
Progressive Disclosure	SKILL.md is a clear overview pointing to well-signaled one-level-deep references (assets/configs, assets/integrations, references/01-09, references/complete), all of which exist on disk, with a Navigation Strategy section guiding discovery.	5 / 5
	Total	18 / 20 Passed

Description

95%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, third-person description that explicitly covers what the skill does and when to invoke it, with rich natural trigger terms and low conflict risk. Minor tightening could turn grouped categories into discrete actions.

Dimension	Reasoning	Score
Specificity	Lists several concrete capability areas ('analyzing code style/patterns, creating/modifying formatting config, troubleshooting formatting, brace styles/indentation/spacing/alignment/pointer alignment, or codifying conventions'), though some are grouped categories rather than discrete actions, leaving minor gaps versus fully comprehensive.	4 / 5
Completeness	Explicitly answers both 'what' ('Configure clang-format code formatting') and 'when' via a concrete 'Use when:' clause enumerating specific trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural-term coverage including the tool name, the '.clang-format' file extension, and concrete feature keywords (brace styles, indentation, spacing, alignment, pointer alignment) users would naturally say.	5 / 5
Distinctiveness Conflict Risk	Targets a distinct niche tool with file-extension-specific triggers ('clang-format', '.clang-format'), giving it a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	19 / 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: 4e1e73b

Reviewed: ~14 hours 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.