configuring-the-build

modifying build configuration to enable/disable variants, switch compilers or flags, or otherwise prepare for a build

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/configuring-the-build/SKILL.md

Quality

Content

75%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.

The content is an efficient, actionable instruction-only skill with a clear build pipeline sequence, explicit guardrails, and validation/error-recovery hints. Minor placeholders and inlined reference material keep it just short of top marks.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and assumes Claude's competence (it does not re-explain autoconf/automake basics), with only minor trimmable phrases like 'Normally you should not have to change these' and 'Try not to do anything too strange', fitting 'efficient; minor instances of over-explanation' rather than the fully lean 5.	4 / 5
Actionability	Concrete, runnable commands are given throughout (./autogen.sh, ./configure, CXX=g++ CC=gcc ./configure ..., --enable-asan, etc.), but the '...' placeholders in the CC/CXX and CXXFLAGS examples leave minor gaps, matching 'mostly executable guidance; concrete commands with minor gaps' rather than the copy-paste-ready 5.	4 / 5
Workflow Clarity	The autogen → configure sequence is clearly ordered with explicit ALWAYS/NEVER rules and validation hints ('configure also writes config.log, if there are errors they will be there') plus an error-recovery note ('re-run ./autogen.sh and ./configure'), fitting 'clear sequence with most checkpoints present; minor validation gaps' rather than the fully-checkpointed 5.	4 / 5
Progressive Disclosure	The single-file body is well-organized into Overview, Configuration variables, and Configuration flags sections and signals one-level-deep deeper reading ('reading configure.ac directly'), but some flag reference material is inlined and there are no bundle files to split into, fitting 'good structure; most content appropriately placed; minor organization gaps' rather than the cleanly-split 5.	4 / 5
	Total	16 / 20 Passed

Description

66%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.

The description is third-person, specific, and reasonably distinctive, but it omits an explicit 'Use when...' trigger clause, which caps its completeness. Adding concrete trigger phrasing would raise the score.

Suggestions

Append an explicit trigger clause such as 'Use when changing build settings, enabling/disabling variants, switching compilers, or preparing for a build'.

Add natural synonyms users say (e.g. 'configure the build', 'change build flags', 'build settings') to broaden trigger coverage.

Consider naming specific flags or variants as concrete triggers to push specificity toward 5.

Dimension	Reasoning	Score
Specificity	Names the domain (build configuration) and several concrete actions — 'enable/disable variants, switch compilers or flags, or otherwise prepare for a build' — with only the trailing 'otherwise prepare' being generic, fitting the 'several specific actions; minor gaps' anchor rather than the comprehensive 5.	4 / 5
Completeness	The 'what' is clearly stated (modifying build configuration for variants/compilers/flags), but there is no explicit 'Use when...' trigger clause; per the guidelines a missing trigger clause caps completeness at 3, and the 'when' is only weakly implied by 'prepare for a build'.	3 / 5
Trigger Term Quality	Natural terms like 'build configuration', 'compilers', 'flags', and 'variants' are terms users would actually say, but common synonyms (e.g. 'configure the build', 'change build settings') are missing, matching 'good keyword coverage; a few natural terms missing' rather than the comprehensive 5.	4 / 5
Distinctiveness Conflict Risk	The build-configuration niche with compiler/flag/variant triggers is mostly distinct from other skills with only minor overlap risk against a general build/run skill, fitting 'mostly distinct; minor overlap risk' rather than the fully-niched 5.	4 / 5
	Total	15 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: stellar/stellar-core
Path: .claude/skills/configuring-the-build/SKILL.md
Commit: 457f20b

Reviewed: 2 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.