CtrlK
BlogDocsLog inGet started
Tessl Logo

bevy-ecs-expert

Master Bevy's Entity Component System (ECS) in Rust, covering Systems, Queries, Resources, and parallel scheduling.

64

Quality

76%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/bevy-ecs-expert/SKILL.md

The canonical home for this skill is bevy-ecs-expert in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 tight, code-rich reference with strong actionability and clear sequencing. Minor gains are possible by trimming the 'When to Use' bullets and adding an explicit build/run verification step.

DimensionReasoningScore

Conciseness

Lean content with tight code and minimal prose that assumes Claude knows Rust; only the 'When to Use' bullets are slightly verbose, preventing a 5.

4 / 5

Actionability

Every section contains concrete, copy-paste-ready, executable Rust code covering the common cases — component definition, systems, resources, scheduling, spawning, and query filters.

5 / 5

Workflow Clarity

Steps are clearly sequenced (Define → Systems → Resources → Scheduling) and the skill is a reference/tutorial with no destructive or batch operations, so validation checkpoints are not required; lacks explicit error-feedback loops beyond the Troubleshooting note.

4 / 5

Progressive Disclosure

No bundle files exist and none are needed for a skill this size; content is well-organized into clearly labeled sections with no nested references, meeting the simple-skill bar.

4 / 5

Total

17

/

20

Passed

Description

70%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 clearly niched but lacks an explicit 'when to use' trigger clause, which caps its completeness score. Adding a 'Use when...' clause with natural user phrases would lift it substantially.

Suggestions

Add a 'Use when...' clause naming natural user triggers, e.g. 'Use when building games in Bevy, designing data-oriented systems in Rust, or parallelizing game systems.'

Replace capability-naming ('covering Systems, Queries, Resources') with concrete action verbs ('define components, write systems, schedule parallel execution').

Include common natural terms and file/symbol cues a user might say ('Bevy game engine', 'ECS scheduling', 'Query filters').

DimensionReasoningScore

Specificity

Names the domain (Bevy ECS in Rust) and lists several concrete capability areas — Systems, Queries, Resources, and parallel scheduling — but uses capability-naming rather than concrete action verbs, so it does not reach comprehensive 5.

4 / 5

Completeness

Clearly states 'what' the skill covers but provides no 'Use when...' clause or equivalent trigger guidance, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Strong technical keywords (Bevy, ECS, Rust, Systems, Queries, Resources, parallel scheduling) but missing natural user phrasing like 'game logic', 'game development', or 'Rust game engine' that a user might actually say.

4 / 5

Distinctiveness Conflict Risk

The 'Bevy ECS in Rust' niche is highly specific with minimal overlap risk against other skills; unlikely to trigger for the wrong skill.

5 / 5

Total

16

/

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.

Validation15 / 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
administrakt0r/AI-Agents-Safe-Coding-Skills
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.