design-action-combat

Design, implement, tune, or test readable tactical action combat for web games. Use for attack timing, guard and dodge windows, hit contact, posture, lock-on, weapons, boss phases, combat feedback, and deterministic combat tests.

Quality

89%

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

86%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 tight, well-structured instruction skill that assumes Claude's competence and organizes combat design into clear sequenced sections. The only weakness is that guidance is framed as checklists rather than executable steps with explicit error-recovery loops.

Suggestions

Add a short numbered workflow (specify → implement → tune → test → verify) so the section order reads as an explicit process rather than loosely sequenced topics.

For the test section, include one concrete seeded-scenario example (e.g., a frame-stepped parry-timing test) to make the deterministic-testing guidance directly executable.

Add an explicit validation feedback loop in 'Verify in play' (fail → diagnose → re-tune → re-verify) to lift workflow clarity toward the top anchor.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout: no padding, no explanation of concepts Claude already knows (e.g., what a state machine is), and every section earns its tokens, matching the lean-and-efficient anchor.	5 / 5
Actionability	Concrete, specific checklists (define startup/active/recovery/cancellation/contact shape; test early/late timing, wrong direction, out-of-range, multiple targets, phase changes) give actionable guidance, but as an instruction-only skill it provides frameworks rather than executable code or commands, leaving minor gaps.	4 / 5
Workflow Clarity	Sections form a logical sequence (specify verbs → authoritative outcomes → tune → test deterministically → verify in play) with an explicit verification checkpoint ("Verify in play"), but the steps are prose-headed rather than numbered with explicit error-recovery loops.	4 / 5
Progressive Disclosure	Under 50 lines, single-purpose, with clear section headers and no need for external references; per the simple-skill guidance this is well-organized enough to score 5 without bundle files.	5 / 5
	Total	18 / 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 highly specific, well-triggered description with explicit what/when structure and a clear niche. It is slightly shy of perfect trigger coverage only because a few common combat synonyms (parry, iframe, hitbox) are absent.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("Design, implement, tune, or test") plus comprehensive domain coverage (attack timing, guard/dodge windows, hit contact, posture, lock-on, weapons, boss phases, combat feedback, deterministic tests), matching the comprehensive-coverage anchor.	5 / 5
Completeness	Explicitly answers "what" ("Design, implement, tune, or test readable tactical action combat for web games") and "when" ("Use for attack timing... and deterministic combat tests") with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Strong natural keyword coverage ("attack timing, guard and dodge windows, hit contact, posture, lock-on, weapons, boss phases, combat feedback"), but a few natural terms users say are missing (parry, iframe, hitbox), so it sits just below the comprehensive-synonym anchor.	4 / 5
Distinctiveness Conflict Risk	"Tactical action combat for web games" is a clear niche with distinct triggers (posture, lock-on, boss phases, dodge windows) and minimal overlap 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: MengTo/Skills
Path: agent-skills/game-development/design-action-combat/SKILL.md
Commit: 4c716b5

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