CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gears

cli reference to help with the development of constructor fabric gears framework. It helps with the development of the framework from its initialization, adding/removing gears, modifying configuration files, build and/or run project, lint the project and managing applications through its manifest. Always load this skill whenever you detect Gears.toml or you locate a reference to gears, cargo-gears, gears-toolkit, gears, plugins or packages that include the prefix cf- in its name.

Quality

72%

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 ./crates/cargo-gears-core/shared/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 exceptionally concrete, example-rich CLI reference that tells Claude exactly which commands to run, undermined by systematic duplication (Quick Reference and Important Caveats restate earlier content), command-name inconsistencies that would make some documented invocations fail, and a monolithic single-file structure with no progressive disclosure. Workflow guidance exists and is sequenced, but validation checkpoints are implicit and the end-to-end flows reference a nonexistent command.

Suggestions

Move the per-command reference (Synopsis/Arguments/Behavior details for lint, deploy, config, ls, etc.) into references/ files (e.g. references/commands.md, references/lint.md) and keep SKILL.md as an overview with the command tree, guidelines, and flows — the current 1,500-line monolith loads the entire reference into context on every invocation.

Delete the duplicated content: the Quick Reference section repeats the per-command synopses and the Important Caveats section restates Behavior bullets; keep one canonical location for each fact, and replace the six repeated "[path activation]" bullets with a single shared-pattern note.

Fix the internal inconsistencies before anything else: the end-to-end flows and Quick Reference use "generate module" where the actual command is "generate gear", "ls targets" and the "--dev/--build" flags of "ls deps" appear only in the Quick Reference with no documented section, and the "rest-api" template is used in an example but is not in the built-in template list — these would cause copy-paste failures.

DimensionReasoningScore

Conciseness

A 1,516-line body with systematic padding rather than incidental over-explanation: the "Quick Reference" repeats the per-command synopses already documented above, "Important Caveats" restates Behavior bullets nearly verbatim, the "[path activation]" bullet is repeated across six commands, and the "[exclusive boolean overrides]" explanation is duplicated between build and run — matching the score-2 anchor's several unnecessary padded sections rather than score-3's minor tightening opportunities.

2 / 5

Actionability

Every command has a full synopsis, argument table, behavior bullets, and copy-paste-ready bash examples (e.g. "cargo gears config db add primary -p /tmp/cf-demo -c .../quickstart.yml --engine postgres --host localhost"), which meets the score-5 bar for executability, but command-name inconsistencies ("cargo gears generate module" in the flows and Quick Reference vs. the actual "generate gear" command, an undocumented "ls targets" and "--dev/--build" flags, a "rest-api" template example not in the template list) mean some documented commands would fail as written, dropping it to 4.

4 / 5

Workflow Clarity

The "Practical End-to-End Flows" give a real sequence (generate workspace → generate config → config mod add → run) and the guidelines mandate verification ("Always verify that the application runs successfully after modifying the code"), but the flows contain a broken command name ("generate module"), steps have no explicit validation checkpoints between them (e.g. no "manifest validate" before build/deploy), and risky operations like deploy, clean, and tools have no verify/recovery loops — matching the score-3 anchor of sequence present but checkpoints missing or implicit.

3 / 5

Progressive Disclosure

Internal structure is good (a command tree acts as a table of contents, and each command follows a consistent Synopsis/Arguments/Behavior/Examples pattern), but there are no bundle files at all: all ~1,500 lines — including the exhaustive lint flag semantics, help-topic catalog, and per-command argument tables — are inlined in SKILL.md, exactly the score-3 anchor's pattern of API-reference content that should live in separate files sitting inline; it avoids score 2 only because headers and the tree make it navigable.

3 / 5

Total

12

/

20

Passed

Description

83%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 clearly states both capabilities and explicit load triggers, anchored by concrete identifiers like Gears.toml, cargo-gears, and the cf- package prefix. Its main weaknesses are incomplete capability coverage (deploy, src, help, tools are absent), slightly awkward phrasing, and mildly generic trigger words ("gears", "plugins") that carry minor conflict risk.

DimensionReasoningScore

Specificity

Lists six concrete actions — "initialization, adding/removing gears, modifying configuration files, build and/or run project, lint the project and managing applications through its manifest" — which goes beyond the score-3 anchor's 1-2 actions, but coverage has gaps (deploy, src inspection, help topics, tools are undocumented) and the opening fragment "cli reference to help with the development" is unpolished, so it falls short of the comprehensive score-5 anchor.

4 / 5

Completeness

Explicitly answers both questions: what it does ("initialization, adding/removing gears, modifying configuration files, build and/or run project, lint... managing applications through its manifest") and when to use it ("Always load this skill whenever you detect Gears.toml or you locate a reference to gears, cargo-gears, gears-toolkit... cf-"), matching the score-5 anchor's clear what + concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural triggers: the filename marker "Gears.toml", binary name "cargo-gears", "gears-toolkit", and the "cf-" package prefix — good coverage but missing common variations like the repo name (cyberware-rust), "Gears manifest", or the templates, so it sits between the score-4 and score-5 anchors.

4 / 5

Distinctiveness Conflict Risk

A clear niche (constructor fabric gears framework, Gears.toml, cargo-gears, cf- prefix) with mostly distinct triggers, but "gears" and "plugins" are ordinary English words that create minor false-positive overlap, keeping it below the score-5 anchor's minimal conflict risk.

4 / 5

Total

17

/

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

skill_md_line_count

SKILL.md is long (1527 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

constructorfabric/cargo-gears

Path

crates/cargo-gears-core/shared/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.