CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

naming-and-resources

Pick and record the names of a new concept in every layer (database table and column, ORM model, DTO, route, JSON field, UI label), and give every stored item kind the same resource shape and the same actions. Holds the glossary format with an Avoid list, the per-layer name table, the resource template, standard and custom actions, field, enum, state and owner rules, the Agenta convention table, the folder naming rule, and the spec naming checklist. Use when writing or changing a spec, design or plan that adds or renames a table, column, index, route, DTO field, enum value, config field or UI label, when asked "what should this be called", "is this name consistent", "fill the naming section", or when another skill asks for the per-layer names. It applies even when the word "naming" never appears. Do not use it for field grouping by role (use design-interfaces), for migration errors, or for a rated review (use review-naming).

Quality

99%

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

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.

A model instruction-only skill body: a lean overview that assumes Claude's competence, an eight-step procedure where every step yields a concrete artifact with explicit validation checkpoints, and a two-tier reference structure with load conditions that keeps the main file free of inlined detail. The bundle structure matches the body's claims exactly, with all referenced files present and no nested references.

DimensionReasoningScore

Conciseness

The ~80-line body is lean throughout: a four-line role statement ("You help a spec author choose one name per concept... You do not change code"), an eight-step procedure with one-to-three-line steps, a two-tier reference list, and four terse rules. It explains nothing Claude already knows and contains no padded or filler sentences, matching the anchor "every token earns its place" rather than the level below, which requires minor instances of over-explanation to trim — none are present.

5 / 5

Actionability

For an instruction-only skill the guidance is fully executable: each step names its exact artifact ("Read `references/project-conventions.md`", "search the repo (not memory) for the closest existing one", "Write three caller examples. The common call, a realistic composition, and a likely mistake with its recovery") with concrete decision rules ("A cell that differs from the term needs a reason", "A shipped name changes only with a migration plan or a recorded exception"). Per the scoring notes, absence of code in an instruction-only skill is not penalized when the guidance is this actionable; every step produces a named output, so the level below ("minor gaps") does not apply.

5 / 5

Workflow Clarity

The eight steps are clearly sequenced (conventions → analog → glossary → layer table → resource template → name check → caller examples → checklist) with explicit validation checkpoints: step 4 requires a reason for every deviation, step 7 is a predictability test ("a reader can predict arguments, result, effects and errors from the names alone"), step 8 gates completion ("A spec that adds a concept without this section is not ready for design review"), and step 3 is an error-recovery loop (conflict → "say so at once and ask which meaning is right"). This matches the top anchor with explicit validation, feedback, and a checklist; the skill involves spec writing, not destructive or batch operations, so the validation cap does not apply.

5 / 5

Progressive Disclosure

The body is a pure overview with all detail delegated one level deep: six always-needed references plus four conditional ones under "Only when needed" with explicit load conditions (e.g. edge-values.md "when a field can be absent, null, empty or zero"). All ten referenced paths exist in the bundle, and a grep of the reference files confirms none points to another file, so references are exactly one level deep. This matches the top anchor (clear overview, well-signaled one-level-deep references, easy navigation) rather than the level below, which requires organization gaps that are not present.

5 / 5

Total

20

/

20

Passed

Description

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

An exemplary description: concrete capabilities enumerated across every layer, explicit 'Use when' triggers with quoted natural user phrasings, third-person voice, and explicit negative boundaries that route overlapping requests to sibling skills. No vague language, buzzwords, or padding is present despite the length, since every clause carries discovery-relevant information.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with comprehensive coverage: "Pick and record the names of a new concept in every layer (database table and column, ORM model, DTO, route, JSON field, UI label)" and "give every stored item kind the same resource shape and the same actions", then enumerates the skill's full holdings (glossary format with Avoid list, per-layer name table, resource template, action/enum/state/owner rules, convention table, folder rule, spec checklist). This matches the anchor for multiple specific concrete actions with comprehensive coverage, not the level below, which requires minor gaps in coverage — every clause names a concrete artifact or action.

5 / 5

Completeness

It explicitly answers both what ("Pick and record the names of a new concept in every layer... give every stored item kind the same resource shape and the same actions") and when ("Use when writing or changing a spec, design or plan that adds or renames a table, column, index, route, DTO field, enum value, config field or UI label... or when another skill asks for the per-layer names") with concrete trigger phrases. This is a direct match for the top anchor; the 'when' clause is fully explicit rather than vague or implied as at lower anchors.

5 / 5

Trigger Term Quality

It includes direct quotes of natural user phrasings — "what should this be called", "is this name consistent", "fill the naming section" — plus a full enumeration of the objects users would name (table, column, index, route, DTO field, enum value, config field, UI label) and the note that it applies "even when the word 'naming' never appears". Coverage of natural terms including synonyms is comprehensive, exceeding the level below ("good keyword coverage; a few natural terms missing").

5 / 5

Distinctiveness Conflict Risk

It carves out an unambiguous niche (per-layer naming in specs) and explicitly redirects near-miss cases to sibling skills: "Do not use it for field grouping by role (use design-interfaces), for migration errors, or for a rated review (use review-naming)". Clear niche with distinct triggers and minimal conflict risk, matching the top anchor rather than the level below, which allows minor overlap with closely related skills.

5 / 5

Total

20

/

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

referenced_paths_exist

Referenced path issues: 4 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

Agenta-AI/agenta

Path

.agents/skills/naming-and-resources/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.