et-code

ET framework C# code authoring and review workflow. Use when creating or modifying Entity, Component, System, Helper, message handlers, package dependencies, assemblies, module analyzer boundaries, C# file placement, .meta handling, ECS layering, or component contract logic in WOW/ET packages.

Quality

86%

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

Quality

Content

80%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.

A concise, well-structured instruction skill with strong progressive disclosure and concrete guardrails. Its main weakness is workflow clarity: validation/verification is delegated to another skill rather than embedded as an explicit inline checkpoint.

Suggestions

Add an explicit validation checkpoint inside '默认动作' (e.g., a numbered step: 'run analyzer/build validation and only proceed on pass; on failure fix and re-validate') rather than only deferring to et-build.

In '输出要求', require stating the validation outcome (pass/fail) so the verify-then-proceed loop is concrete rather than implied.

Tighten actionability by naming the concrete analyzer/build command or script path the user should run, instead of an abstract handoff to et-build.

Dimension	Reasoning	Score
Conciseness	The body is a lean set of bulleted and numbered directives with no padding and no explanation of concepts Claude already knows; every line earns its place (e.g., '严禁 AI 手工生成 `.meta` 或手工修改 `.csproj`').	5 / 5
Actionability	It provides concrete, specific directives (reuse existing structure, one class per file, move .meta with the .cs file, layer et-async) and clear file/pointer references, but defers build/analyzer execution to et-build rather than giving inline executable commands, leaving minor gaps.	4 / 5
Workflow Clarity	The '默认动作' section gives a clear 8-step ordered workflow, but validation/verification is only implicit—compile/analyzer checking is handed off to et-build instead of an explicit validate-then-proceed feedback loop, which caps it at the anchor for steps-listed-but-checkpoints-missing.	3 / 5
Progressive Disclosure	SKILL.md is a concise overview that defers detail to a verified one-level-deep reference (references/et-code-rules.md) clearly signaled in '快速分流', and also signals cross-skill jumps (et-async, et-build), matching the clear-overview anchor.	5 / 5
	Total	17 / 20 Passed

Description

92%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.

A strong, specific description that clearly states both capability and trigger conditions for a well-scoped niche. It would benefit only marginally from adding a few synonyms or file-extension variants to round out trigger term coverage.

Dimension	Reasoning	Score
Specificity	The description enumerates many concrete actions across the ET domain (Entity, Component, System, Helper, message handlers, package dependencies, assemblies, module analyzer boundaries, C# file placement, .meta handling, ECS layering, component contract logic), matching the comprehensive-coverage anchor.	5 / 5
Completeness	It explicitly answers both 'what' ('ET framework C# code authoring and review workflow') and 'when' ('Use when creating or modifying ...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	It covers strong natural domain terms an ET developer would say (Entity, Component, System, .meta, ECS layering, message handlers), but lacks common synonyms or file-extension variants the way the score-5 example lists 'PDFs, .pdf', so it falls just short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	The niche is tightly scoped to ET framework C# code in WOW/ET packages with distinct triggers (.meta, ECS layering, module analyzer), giving it minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: egametang/ET
Path: Packages/cn.etetet.harness/skills/et-code/SKILL.md
Commit: ff68102

Reviewed: 10 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.