CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

project-settings

Shows or changes a project setting and where its value comes from. Use to check or set one.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/project-settings/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a strong operational skill: every phase gives copy-paste-ready commands, exact edit strategies, and explicit validation gates with feedback loops, making it hard to execute incorrectly. The main weakness is rhetorical padding — several passages argue for design decisions rather than instruct, which inflates token cost without adding executable value.

DimensionReasoningScore

Conciseness

The body is dense with executable detail, but carries several multi-sentence rationale passages that justify design choices rather than instruct — e.g. "view-one and view-all are twins in exactly the way the two write paths are", "Identical to Phase 4 step 2, and deliberately so... warning on one only would leave --local as the silent route", and the extended blockquote on why reserved keys go unnamed. Mostly efficient but could be tightened past anchor 4's "minor instances" threshold.

3 / 5

Actionability

Fully executable throughout: exact helper invocations (resolve_setting <path>, validate_enum_value <key> <value>), a copy-paste bash template for the helper, concrete old_string/new_string edit examples for each YAML-write case, and exact output blocks and approval-prompt wording. The guidance covers all common cases copy-paste ready.

5 / 5

Workflow Clarity

Phases 0-6 are clearly sequenced with explicit validation before every write: enum validation, a known-key dry-run check, reserved and shadow warnings, an approval gate, a Case A-D edit strategy with a STOP-and-ask fallback for unusual files, and verbatim error display with exit-without-write. Feedback loops are present at each checkpoint.

5 / 5

Progressive Disclosure

No bundle files exist, and the single SKILL.md is organized into clear phase sections with one-level-deep, clearly signaled references to project docs (effects-map.md, settings-guidance.md, automation-modes.md) at the point of use. Minor gap: the ~490-line body inlines detail (e.g. the Phase 1b meta-commentary and full output templates) that could live in a reference file.

4 / 5

Total

17

/

20

Passed

Description

62%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 concise and answers both what and when with a distinctive provenance angle, but it undersells the skill's breadth (view-all, view-one, local overrides, validation) and omits common trigger synonyms like "config" or "project.yaml". It is solid mid-range quality: clear and honest, yet not compelling as a trigger surface.

Suggestions

Name the concrete artifacts and operations to raise specificity, e.g. "Views, checks, or changes settings in project.yaml / project.local.yaml, showing which file or default each effective value comes from."

Add natural trigger synonyms users would actually say — "project settings", "config", "check a setting", "change project config" — so the skill surfaces when those phrases appear.

Mention the local-override capability (--local, per-developer gitignored values) in the description; it is a distinct, commonly-needed function currently invisible to trigger matching.

DimensionReasoningScore

Specificity

"Shows or changes a project setting and where its value comes from" names the domain and 2-3 concrete actions (show, change, trace provenance), but coverage is not comprehensive — no mention of viewing all settings, local overrides, or validation. It stops at anchor 3 rather than 4 because it does not list several specific actions with only minor gaps.

3 / 5

Completeness

The description answers both questions: "what" is stated concretely ("Shows or changes a project setting and where its value comes from") and "when" is explicit ("Use to check or set one"). It is not a 5 because the when-clause is terse and lacks concrete trigger phrases or synonyms.

4 / 5

Trigger Term Quality

"project setting", "check", and "set" are natural terms users would say, but common variations are missing — "config", "configuration", "settings", or the concrete file name (project.yaml). This matches anchor 3 (some relevant keywords, missing variations); it falls short of anchor 4's good keyword coverage.

3 / 5

Distinctiveness Conflict Risk

The provenance angle ("where its value comes from") and the project-setting domain give it a mostly distinct niche with only minor overlap risk against generic config/settings skills. Not 5, because no file name or project-specific marker further narrows the trigger space.

4 / 5

Total

14

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

Donchitos/Claude-Code-Game-Studios

Path

.claude/skills/project-settings/SKILL.md

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.