Name: bevy-ecs-expert
Rating: 52 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

bevy-ecs-expert

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

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/bevy-ecs-expert/SKILL.md

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

Quality

Content

63%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 solid introductory Bevy ECS skill with good executable code examples and logical structure. Main weaknesses are moderate verbosity (explanatory text Claude doesn't need) and lack of progressive disclosure to deeper reference material. The actionability is strong with copy-paste ready code covering the core ECS patterns.

Suggestions

Remove the 'When to Use This Skill' section entirely—Claude can infer when Bevy ECS guidance is relevant from context.

Trim explanatory sentences before code blocks (e.g., 'Systems are regular Rust functions that query components') since the code is self-explanatory.

Add references to separate files for advanced topics like parallel scheduling strategies, performance profiling, and complex query patterns to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The skill includes some unnecessary framing ('When to Use This Skill' section explains obvious use cases Claude would know) and minor verbosity like 'Systems are regular Rust functions that query components' which is redundant given the code. However, the code examples themselves are lean and well-chosen.	3 / 5
Actionability	Provides concrete, executable Rust code examples covering components, systems, resources, scheduling, and spawning. Minor gaps include no error handling examples and the troubleshooting section gives a solution (.chain()) without a full code example of the fix.	4 / 5
Workflow Clarity	The step-by-step guide follows a logical progression from components to systems to resources to scheduling, which mirrors the actual development workflow. However, there are no explicit validation checkpoints (e.g., how to verify systems are running correctly, how to debug query conflicts before they panic). Since this isn't a destructive/batch operation, the missing validation doesn't cap the score.	4 / 5
Progressive Disclosure	The content is reasonably structured with clear sections, but everything is inlined in a single file with no references to external files for advanced topics (parallel scheduling details, performance optimization, advanced query patterns). For a skill of this length (~100 lines), some content like the full examples section could be split out.	3 / 5
	Total	14 / 20 Passed

Description

52%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 identifies a clear technical niche (Bevy ECS in Rust) with relevant domain keywords, but it reads more like a course title than a skill description. It lacks concrete action verbs describing what the skill actually does and entirely omits 'when to use' guidance, which significantly weakens its utility for skill selection.

Suggestions

Add a 'Use when...' clause with trigger phrases like 'Use when the user asks about Bevy game engine, ECS architecture in Rust, or needs help with Bevy systems, queries, or resources.'

Replace the vague 'Master...covering' framing with concrete action verbs describing what the skill does, e.g., 'Implements Bevy ECS patterns, writes systems and queries, manages resources, and configures parallel scheduling in Rust.'

Include additional trigger terms like 'game development', 'components', 'entities', 'plugins', and 'bevy_ecs' to improve keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Bevy ECS in Rust) and lists several concepts (Systems, Queries, Resources, parallel scheduling), but these are topic areas rather than concrete actions. It says 'Master' and 'covering' which are vague verbs rather than specific capabilities like 'implement', 'debug', or 'optimize'.	3 / 5
Completeness	Has a somewhat clear 'what' (covers Bevy ECS topics) but completely lacks a 'when' clause. There is no 'Use when...' or equivalent trigger guidance, which per the rubric should cap completeness at 3, and since the 'what' is also more topical than actionable, a score of 2 is appropriate.	2 / 5
Trigger Term Quality	Includes strong trigger terms like 'Bevy', 'ECS', 'Entity Component System', 'Rust', 'Systems', 'Queries', 'Resources', and 'parallel scheduling' that users would naturally mention. Missing some common variations like 'components', 'entities', 'plugins', 'bevy_ecs', or 'game development'.	4 / 5
Distinctiveness Conflict Risk	Bevy ECS is a fairly specific niche (a particular Rust game engine's architecture pattern), making it unlikely to conflict with most other skills. However, it could overlap with a general Rust skill or a broader game development skill, creating minor conflict risk.	4 / 5
	Total	13 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/bevy-ecs-expert/SKILL.md
Commit: fbdfd63

Reviewed: about 18 hours 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.