simple-english

Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop. Use for documentation, READMEs, runbooks, procedures, error messages, release notes, incident reports, and API guides. Also use when the user says "STE", "Simplified Technical English", "ASD-STE100", "de-slop", "make this readable", "write for non-native readers", or asks for docs that translate well. Enforces the standard's 53 rules: 20/25-word sentence limits, one word one meaning, simple tenses, active voice, condition before command.

Quality

94%

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

88%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 well-organized, highly actionable rule catalog with concrete before/after examples and a mandatory self-check validation gate. It loses a little on conciseness and progressive disclosure because the full rule set lives inline rather than being offloaded to a reference file.

Suggestions

Move the bulk rule catalog (Sections 1-9) into a references/rules.md file and keep only a quick-start example plus mode/classification guidance in SKILL.md, citing the catalog the way use-cases.md and checklist.md are cited.

Trim explanatory asides like the 'AI slop' enumeration in the intro to a single clause so the opening stays lean.

Consider splitting the slop-to-simple substitution table into references/checklist.md alongside the existing verification pass, since it is reference material rather than core procedure.

Dimension	Reasoning	Score
Conciseness	The body is dense and table-driven with almost no padding of concepts Claude already knows, but a few elaborations (e.g. 'They remove the usual signs of AI-generated text as a side effect: long sentences, synonym rotation, hedges, filler, and decorative clauses') could be trimmed, keeping it just below the lean top anchor.	4 / 5
Actionability	Concrete, specific guidance throughout — before/after rewrites for each rule section, a modal-ladder table, a slop-to-simple substitution table, and a self-check with exact search strings ('ll, 're, 's, has been, should, -ing) — covers the common cases copy-paste ready.	5 / 5
Workflow Clarity	A clear 6-step numbered sequence ('Your Task') with an explicit, mandatory validation gate ('Run the self-check before you deliver. This step is not optional') and a fix-then-deliver feedback loop, matching the top anchor for sequenced validation.	5 / 5
Progressive Disclosure	Good structure with clearly signaled, real one-level-deep references (references/checklist.md and references/use-cases.md, both present in the bundle), but the 53-rule catalog is inlined in full in SKILL.md rather than split out, leaving a minor organization gap.	4 / 5
	Total	18 / 20 Passed

Description

100%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 a strong, third-person statement that covers what the skill does, when to use it, and the natural trigger phrases a user would say, with concrete rule specifics. It hits the top anchor on every dimension without padding or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Write or rewrite technical text', 'Enforces the standard's 53 rules: 20/25-word sentence limits, one word one meaning, simple tenses, active voice, condition before command' — with comprehensive coverage of what the skill does.	5 / 5
Completeness	Explicitly answers both what ('Write or rewrite technical text with the rules of ASD-STE100...') and when ('Use for...', 'Also use when the user says...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Comprehensive natural terms including synonyms and the formal name — 'STE', 'Simplified Technical English', 'ASD-STE100', 'de-slop', 'make this readable', 'write for non-native readers' — plus concrete doc types users name (READMEs, runbooks, release notes, incident reports).	5 / 5
Distinctiveness Conflict Risk	Clear niche (Simplified Technical English / ASD-STE100 de-slop) with distinct triggers; minimal overlap risk with other writing skills because the STE/ASD-STE100 vocabulary is unmistakable.	5 / 5
	Total	20 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: TanStack/ai
Path: .agents/skills/simple-english/SKILL.md
Commit: 7fb4a5f

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