core-dynamic-skills

Internal command support for dynamic Rust crate skill management. Use only when explicitly invoked by /sync-crate-skills, /clean-crate-skills, or /update-crate-skill.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/core-dynamic-skills/SKILL.md

Quality

Content

57%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 skill is actionable and reasonably organized with concrete commands, but it is held back by redundant/verbose sections, missing validation for destructive batch operations, and the absence of any progressive disclosure to supporting files.

Suggestions

Add explicit validation/confirmation checkpoints before destructive or batch operations, e.g., confirm the crate list before 'rm -rf ~/.claude/skills/*' and verify a generated skill loads after sync.

Move the Inline Mode detail steps and workspace support into a reference file (e.g., references/inline-mode.md) and link to it from a leaner SKILL.md overview.

Drop the duplicated Related Commands section and the version/last-updated line, or relocate version info to a changelog, to reduce token overhead.

Dimension	Reasoning	Score
Conciseness	The body is mostly operational, but the Concept section, the duplicate Related Commands list (repeating Manual Commands), and the time-sensitive 'Version: 2.1.0 \| Last Updated: 2025-01-27' line add padding that could be trimmed.	3 / 5
Actionability	It provides concrete, mostly executable bash, agent-browser, and WebFetch commands for parsing Cargo.toml, creating skill dirs, and fetching docs, with minor gaps where commands are templated ({crate}) or pseudo-bash ('for member in members; do').	4 / 5
Workflow Clarity	Steps are sequenced (Inline Mode Step 1-4, Sync Command), but destructive/batch operations like 'rm -rf ~/.claude/skills/*' and syncing over all dependencies have no validation or confirmation checkpoints, capping this dimension at 3 per the rubric.	3 / 5
Progressive Disclosure	The body is well-sectioned with clear headers, but no bundle files exist and all content (Inline Mode details, workspace support, error handling) is inlined in SKILL.md with no split-out reference files or navigation pointers.	3 / 5
	Total	13 / 20 Passed

Description

66%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 cleanly answers both what and when and is highly distinct, but it relies on command names as triggers rather than natural user language and frames its actions somewhat generically.

Suggestions

Add natural-language trigger phrases (e.g., 'Use when managing auto-generated Rust crate skills') alongside the command names so users who don't know the commands can still match it.

Briefly state what each command does (e.g., 'sync, clean, and update crate skills') instead of only listing the command identifiers.

Dimension	Reasoning	Score
Specificity	Names the domain ('dynamic Rust crate skill management') and concrete actions via the sync/clean/update commands, but the framing verb 'command support' is generic and the actions are only referenced indirectly through command names rather than described.	3 / 5
Completeness	It states both what ('Internal command support for dynamic Rust crate skill management') and when ('Use only when explicitly invoked by ...'), with concrete command triggers; the 'what' could be more specific about what each command does.	4 / 5
Trigger Term Quality	The triggers are explicit command invocations ('/sync-crate-skills, /clean-crate-skills, or /update-crate-skill') rather than natural-language phrases a user would spontaneously say, and no synonyms or variations are offered.	3 / 5
Distinctiveness Conflict Risk	It occupies a clear niche (dynamic Rust crate skill management) gated by three named command invocations, making accidental triggering by other skills very unlikely.	5 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: actionbook/rust-skills
Path: skills/core-dynamic-skills/SKILL.md
Commit: 5c40d3a

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

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.