CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

moyu

Anti-over-engineering guardrail that activates when an AI coding agent expands scope, adds abstractions, or changes files the user did not request.

Quality

81%

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 highly actionable, well-structured behavioral guardrail with concrete examples, an escalation ladder, and a pre-delivery validation checklist. Its main weakness is token efficiency: motivational persona sections and two overlapping example table sets could be merged or trimmed to cut roughly a third of the body.

Suggestions

Merge the 'Grinding vs Moyu' tables and the 'Anti-Grinding Table' into a single deduplicated example set — several rules (no unprompted tests, docs, dependencies, refactors) currently appear three times across sections.

Trim the motivational persona material ('Your Identity', 'Moyu Recognition', and the closing blockquotes) to one or two lines, or move it into a reference file, to reduce token cost without losing guidance.

Consider moving the 15-row Anti-Grinding Table to a references/ file and keeping only a pointer plus the most common urges inline, keeping SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

The body is mostly instructive with no explanation of concepts Claude already knows, but it could be tightened considerably: persona padding ("You are a Staff engineer who deeply understands that less is more", "You do not grind. You moyu.", "Restraint is not inability.") and substantial duplication between the "Grinding vs Moyu" tables and the "Anti-Grinding Table" (e.g., no-tests-unless-asked and no-docs-unless-asked each appear three times). This fits anchor 3's 'could be tightened'; it is not 2 because the padding is motivational rather than conceptual explanation, and not 4 because roughly a third of the lines are cuttable without losing guidance.

3 / 5

Actionability

As an instruction-only skill, the guidance is fully actionable with concrete examples covering common cases: "Fix bug A only, don't touch anything else", "`json.load(f)`" instead of a config class, "Propose a minimal solution with no more than 10 lines of diff", and specific anti-patterns paired with exact correct responses. This matches anchor 5's 'specific examples cover the common cases'.

5 / 5

Workflow Clarity

The skill provides a clear escalation sequence (L1 self-reminder through L4 emergency brake, each with explicit triggers and actions) plus an explicit validation feedback loop: "Run through this before every delivery. If any answer is 'no,' revise your code" and L2's stop-re-read-reimplement-recheck cycle. It is not a destructive/batch operation skill, so the validation cap does not apply; this matches anchor 5's 'clear sequence with explicit validation steps and feedback loops'.

5 / 5

Progressive Disclosure

No bundle files exist and the body is well-organized into clearly headed sections (Iron Rules, comparison tables, Checklist, Detection Levels, exceptions), matching anchor 4's 'good structure, most content appropriately placed'. It is not 5 because at ~250 lines with heavily overlapping tables, a portion of the example content (the 15-row Anti-Grinding Table or the 28 comparison rows) could be split into a reference file, and the under-50-line simple-skill exception does not apply at this length.

4 / 5

Total

17

/

20

Passed

Description

75%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 description that explicitly states activation conditions in the user's own vocabulary and occupies a distinct niche. Its main weakness is that "guardrail" leaves the skill's actual mechanism unspecified, and a few natural synonyms (e.g., scope creep, minimal diff) are absent.

DimensionReasoningScore

Specificity

The description names the domain ("Anti-over-engineering guardrail") and several concrete trigger behaviors ("expands scope, adds abstractions, or changes files the user did not request"), matching anchor 4's 'several specific actions with minor gaps'. It is not a 5 because it never states what the guardrail actually does (constrain edits, revert, ask), and not a 3 because behavior coverage is broad rather than just 1-2 actions.

4 / 5

Completeness

Both halves are explicit: 'when' is concrete ("activates when an AI coding agent expands scope, adds abstractions, or changes files the user did not request") while 'what' is present but abstract ("guardrail" does not specify the mechanism). This fits anchor 4; it is not 5 because the 'what' lacks concreteness, and not 3 because neither half is missing or merely implied.

4 / 5

Trigger Term Quality

Natural terms like "over-engineering", "expands scope", "abstractions", and "changes files the user did not request" give good keyword coverage of the failure modes. Missing common variations such as "scope creep", "stay in scope", or "minimal diff" keep it below anchor 5, while core domain vocabulary is well covered beyond anchor 3's 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

The anti-over-engineering niche is clearly distinct with behavior-specific triggers, giving minimal conflict risk with unrelated skills. Minor overlap remains with code-review/simplify-style skills that also police scope, matching anchor 4 rather than 5.

4 / 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.

Validation — 15 / 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

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/moyu/SKILL.md

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.