CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

asd-ste100

Use when English text must be parsed without a human to resolve ambiguity — tool descriptions, error messages, inter-agent instructions, system prompts, status reports — and misreading has a real cost, or when text reads as dense, hedged, or easy to misparse. Triggers: disambiguate, STE100 rewrite, apply Simplified Technical English, plain-language rewrite, controlled-language rewrite, rewrite so an agent cannot misread this. Not for creative or marketing copy.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.cursor/skills/asd-ste100/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 well structured and highly actionable, with concrete rule tables, a mechanical scan checklist, a disciplined process with genuine checkpoints, and a real linter script. Its weaknesses are redundancy (the linter and the modes/split are each explained multiple times, and the licensing paragraph runs long) and one broken reference to a nonexistent examples file.

Suggestions

Document ste-lint.py once — fold the flag-by-flag detail from Process step 3 into the Additional Resources entry (or vice versa) so the linter's behavior is stated in one place.

Trim the Source and Scope licensing paragraph to one sentence ('the standard's license forbids redistribution, so the dictionary is not included; request it from the official downloads page'), dropping the quoted clause and the eight exempt categories.

Create examples/before-after.md (the worked examples the body promises) or remove the reference to it — as written, two sections point to a file that is not in the bundle.

DimensionReasoningScore

Conciseness

The body is tight sentence-by-sentence but over budget overall: the linter's flags and options are documented twice with overlapping detail (Process step 3 and Additional Resources both cover --baseline, --disable, synonym rotation, and never-flagging hedges), the Source and Scope section spends a full paragraph on ASD licensing details (quoting page 2 and enumerating eight exempt categories), and the modes/structural-lexical split is explained three separate times. This matches anchor 3 ('mostly efficient but includes some unnecessary explanation or could be tightened') better than 4.

3 / 5

Actionability

Concrete Do/Don't rule tables, a Scan Checklist with example phrases and fixes, a precise Output Format with an example table, and a real executable script with flags give mostly executable guidance. Minor gaps: no literal sample invocation of ste-lint.py (its usage is described, not shown), and the worked-examples file the body relies on (examples/before-after.md) does not exist — keeping this at anchor 4 rather than 5.

4 / 5

Workflow Clarity

The Process gives a clear six-step sequence with real checkpoints: read for meaning before rewriting, the modality check before committing to a rewrite, flag-instead-of-silently-simplify error handling, and 'if the input already complies, say so'. This is an instruction-only rewriting skill, so the destructive/batch cap does not apply. The gap is the absence of an explicit post-rewrite verification pass (e.g., re-running the linter or checklist on the output), which holds it at anchor 4 rather than 5.

4 / 5

Progressive Disclosure

The body is a well-organized overview with one-level-deep, clearly signaled references (inline cross-references plus a consolidated Additional Resources section), and the two existing bundle files (references/writing-rules.md, scripts/ste-lint.py) are substantive and correctly placed. However, one of the three referenced paths — examples/before-after.md, cited twice in the body — does not exist in the bundle, a concrete navigation defect that fits anchor 4 ('minor organization gaps') rather than 5.

4 / 5

Total

15

/

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 with an explicit, richly textured 'when' clause, a clear niche, and a good trigger list anchored by the standard's name. Its main weakness is that the core capability is implied through trigger phrasings rather than stated directly, and its action coverage is narrow (rewriting variants only).

DimensionReasoningScore

Specificity

Names several concrete actions ('STE100 rewrite', 'plain-language rewrite', 'controlled-language rewrite', 'disambiguate') and concrete text types ('tool descriptions, error messages, inter-agent instructions, system prompts, status reports'), but all actions are variants of one rewriting operation and the rule-analysis/lint capabilities are absent. Anchor 4 ('several specific actions; minor gaps in coverage') fits better than 3 (more than 1-2 actions named) or 5 (coverage is narrow, not comprehensive).

4 / 5

Completeness

The 'when' is explicit and detailed ('Use when English text must be parsed without a human to resolve ambiguity... or when text reads as dense, hedged, or easy to misparse'), but the 'what' is only implied through the trigger verbs — no direct capability statement like 'Rewrites dense English into short, unambiguous sentences'. Both are present with one weaker side, matching anchor 4 rather than 5, where both are explicit.

4 / 5

Trigger Term Quality

The trigger list covers natural phrasings including the standard's own names ('STE100 rewrite', 'apply Simplified Technical English', 'plain-language rewrite', 'rewrite so an agent cannot misread this'), but common variations like 'simplify', 'clarify', or 'plain English' are missing. This matches anchor 4 ('good keyword coverage; a few natural terms missing'), not 5.

4 / 5

Distinctiveness Conflict Risk

The niche (controlled-language rewriting for machine/agent consumption) is distinct, with named triggers tied to the STE standard and an explicit negative scope ('Not for creative or marketing copy'). Minor overlap risk remains with general editing skills via generic phrases like 'plain-language rewrite', matching anchor 4 rather than 5.

4 / 5

Total

16

/

20

Passed

Validation

100%

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

mflux-community/mflux

Path

.cursor/skills/asd-ste100/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.