CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-arguments-dsl

Audits a command class's arguments DSL definition to verify it accurately maps Ruby call arguments to git CLI arguments in the correct order with correct DSL methods and modifiers.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/review-arguments-dsl/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 a well-organized, information-dense audit guide with concrete paths, URLs, DSL semantics, and a clear stepwise workflow. Its principal defect is that its core detail (the DSL method mapping table and per-option-type checklist) lives in a CHECKLIST.md that is absent from the bundle, so the skill cannot actually be executed as delivered, and several inline sections could be trimmed for token efficiency.

Suggestions

Include CHECKLIST.md in the skill bundle (or inline its DSL method mapping table in SKILL.md), since workflow steps 1–5 and multiple reference sections link to it and the audit cannot be performed without it.

Trim the Contents TOC, the 'Attach this file to your Copilot Chat context' invocation examples, and the HTML meta-comment to reduce token overhead without losing guidance value.

Add an explicit mismatch-handling step to the workflow — what to do and record when the man-page behavior and the DSL definition disagree — to close the validation loop for the audit findings.

DimensionReasoningScore

Conciseness

The body is dense with project-specific semantics Claude could not already know ('key_value_option ... emits --flag key=value per pair', 'Case is preserved: :A → -A', 'false is absent, not --no-*'), with essentially no filler about general concepts. It falls short of 5 because the 25-line Contents TOC, the 'Attach this file to your Copilot Chat context' invocation examples, and the HTML meta-comment are tokens that do not earn their place.

4 / 5

Actionability

Highly concrete: exact source/test paths (lib/git/commands/{command}.rb, spec/unit/git/commands/{command}/**/*_spec.rb), exact doc URLs for latest and minimum versions, a 6-step audit procedure, a per-entry verification chain, and a fully specified output table format. Not 5 because the 'full DSL method mapping table' and the bulk of the audit rules are deferred to CHECKLIST.md, which is not present in the bundle, leaving gaps the reader cannot fill from this file alone.

4 / 5

Workflow Clarity

Steps 1–6 are clearly sequenced, each naming exactly what to verify, and the per-entry verification chain 'Ruby call → bound argument → expected git CLI' acts as an explicit checkpoint compared against man-page documentation. It is not 5 because there is no error-recovery loop (e.g. what to do when docs and DSL disagree, or how to re-verify ambiguous version-split claims) and the checkpoints are described rather than framed as pass/fail gates.

4 / 5

Progressive Disclosure

References are clearly signaled and nominally one level deep, but the actual bundle contains only SKILL.md — CHECKLIST.md, on which every workflow step depends, is missing, as are the cross-linked sibling files (../command-implementation/SKILL.md, ../project-context/SKILL.md, etc.). Structure is good, so it is above 2, but the primary referenced file failing to resolve keeps it below 4.

3 / 5

Total

15

/

20

Passed

Description

58%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 specific and correctly third-person, clearly stating what the skill audits and along which dimensions (mapping accuracy, order, DSL methods, modifiers). Its main weakness is the complete absence of any 'when to use' trigger guidance, and its keyword coverage lacks the natural phrasings or synonyms that would help it fire reliably.

Suggestions

Append an explicit trigger clause, e.g. 'Use when reviewing or auditing the arguments do ... end block of a command class, when adding new options to a DSL definition, or when the user mentions argument mapping, flag emission, or CLI ordering issues.'

Add natural trigger synonyms users would actually say — 'review the arguments block', 'audit the DSL', 'check flag/option mapping' — so the description matches how requests are phrased, not just the internal domain vocabulary.

DimensionReasoningScore

Specificity

Concrete terms throughout — 'Audits a command class's arguments DSL definition', 'maps Ruby call arguments to git CLI arguments', 'in the correct order with correct DSL methods and modifiers' — name the domain and several specific verification dimensions. It stays at 4 because it describes a single audit action with attributes rather than the multiple distinct actions of the 5-anchor pattern.

4 / 5

Completeness

The 'what' is clear and specific (audit the DSL definition for accurate mapping, ordering, methods, and modifiers), but the 'when' is entirely absent — no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 2 because the 'what' is explicit rather than vague.

3 / 5

Trigger Term Quality

Relevant domain keywords ('arguments DSL', 'Ruby call arguments', 'git CLI arguments') are present, but there are no natural variations or synonyms a user might say ('review the arguments block', 'check the CLI mapping') and no trigger phrasing at all. Missing common variations keeps it at the anchor for 'some relevant keywords'.

3 / 5

Distinctiveness Conflict Risk

The niche is narrow (a Ruby command class's arguments DSL mapping to git CLI arguments) and unlikely to trigger the wrong skill, but it belongs to a family of sibling command-class skills (implementation, test conventions, YARD docs) that share the same 'command class' vocabulary, creating minor overlap risk. Not 5 because those adjacent skills could plausibly compete for the same request.

4 / 5

Total

14

/

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

relative_links

Relative link issues: 11 missing, 8 suspicious

Warning

Total

15

/

16

Passed

Repository

ruby-git/ruby-git

Path

.github/skills/review-arguments-dsl/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.