CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

settings

Old name of /project-settings. Prints one line, then runs /project-settings.

Quality

80%

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/settings/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%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 body is an exemplary minimal redirect skill: it gives the exact line to print, an unambiguous delegation instruction with argument passthrough and an empty-args edge case, and a clear scope guard, all in 14 lines with zero padding. Organization is appropriate for a simple skill needing no external files.

DimensionReasoningScore

Conciseness

The 14-line body is lean: one project-specific rationale sentence ("Several AI tools keep /settings for a command of their own..."), the exact line to print, the delegation instruction, and a scope guard — every token earns its place and nothing explains concepts Claude already knows.

5 / 5

Actionability

Fully executable for an instruction-only skill: the exact output text is given copy-paste ready ("/settings is now /project-settings. Running /project-settings."), the tool to call is named, argument passthrough is specified via $ARGUMENTS, and the empty-arguments edge case is covered ("none, if this is empty").

5 / 5

Workflow Clarity

This is a simple single-purpose skill and the action is unambiguous: a numbered two-step sequence (print the notice line, then invoke project-settings with unchanged arguments) plus "Do nothing else here" as an explicit scope boundary; no destructive or batch operations, so no validation cap applies.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references (no references/, scripts/, or assets/ directories exist), and the body is well-organized with a heading, brief context, and numbered steps, which merits a 5 under the simple-skill guideline.

5 / 5

Total

20

/

20

Passed

Description

53%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 honest and concrete about what the skill does (a rename shim that prints a line and delegates), but it lacks an explicit "Use when..." trigger clause and standalone natural keywords, leaving the "when" only implied and trigger coverage thin. It is well-distinguished as a legacy alias, with minor overlap risk from the generic word "settings".

Suggestions

Add an explicit trigger clause, e.g. "Use when the user invokes /settings, the old name of /project-settings.", to raise completeness above the cap of 3.

Include the standalone natural keyword "settings" and common phrasings such as "project settings" so trigger-term coverage matches what users actually type.

Briefly state what the delegated skill handles (e.g. "accepts key, key=value, and --local key=value arguments, passed through unchanged") to strengthen specificity beyond two bare actions.

DimensionReasoningScore

Specificity

"Prints one line, then runs /project-settings" names two concrete actions, matching the anchor for 1-2 concrete actions; it does not list several actions, so it is not a 4.

3 / 5

Completeness

The "what" is clear ("Prints one line, then runs /project-settings"), but the "when" is only weakly implied by "Old name of /project-settings" with no explicit "Use when..." clause, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

The terms present are "project-settings" and "Old name"; the plain natural keyword "settings" appears only embedded inside "project-settings" and no variations or synonyms are given, so keyword coverage is relevant but thin rather than good.

3 / 5

Distinctiveness Conflict Risk

"Old name of /project-settings" positions it as a legacy alias of one specific skill, making it mostly distinct, though the generic word "settings" carries minor overlap risk with other settings/config skills — not a 5 because the standalone trigger word is generic.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

Donchitos/Claude-Code-Game-Studios

Path

.claude/skills/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.