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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 content is a strong, highly actionable instruction skill: concrete rule tables with exact thresholds, a mechanical scan checklist, a runnable linter with fully specified flags, and clear output-format contracts including a before/after rule table. Weaknesses are moderate verbosity in the explanatory sections and one broken bundle reference (the missing examples/before-after.md).

Suggestions

Create examples/before-after.md (or remove the reference) — the Additional Resources section promises worked examples that do not exist in the bundle.

Add an explicit validation loop to the Process section, e.g. "After rewriting, re-run scripts/ste-lint.py on the output; fix and re-run until hard violations are at or below baseline."

Tighten Source and Scope and Boundaries: cut the editorial asides (e.g. "personality transplant", "clean, short, well-punctuated hollow paragraph") and the repeated licensing justification to roughly half their current length without losing the licensing constraint itself.

DimensionReasoningScore

Conciseness

Much of the body earns its tokens — the structural/lexical rule split, the licensing rationale for omitting the ASD dictionary, and the hedge-preservation warnings are non-obvious and load-bearing. But sections like Source and Scope and Boundaries run long with editorial flourishes ("reads as a personality transplant rather than a clarification", "a clean, short, well-punctuated hollow paragraph") and repeated justifications that could be tightened. This is anchor 3 (mostly efficient, some unnecessary explanation) rather than 4.

3 / 5

Actionability

The guidance is fully concrete: Do/Don't tables with exact thresholds (sentence length ≤20/≤25 words, noun clusters ≤3 words), a mechanical six-habit Scan Checklist with named fixes, and a copy-paste-ready linter invocation with flags ("scripts/ste-lint.py", "--json", "--baseline N", "--disable rule1,rule2") whose behavior and exit codes are fully specified. This matches anchor 5 for an instruction-only skill: the guidance is executable and covers the common cases.

5 / 5

Workflow Clarity

The Process section is a clear six-step sequence with an explicit validation tool ("run scripts/ste-lint.py" for a mechanical first pass) and pre-commit checks ("Check modality before you commit to a rewrite", "Never add a fact the source did not state"), plus a checklist (Scan Checklist). It misses anchor 5 because there is no explicit feedback loop — nothing says to re-run the linter after rewriting until violations are at or below baseline.

4 / 5

Progressive Disclosure

Good structure: core rules stay inline where they belong, the full rule summary is offloaded to a clearly signaled reference (references/writing-rules.md, which exists and is 59 lines), and a deterministic script handles mechanical checks (scripts/ste-lint.py, which exists). The gap keeping it from 5: the body promises "examples/before-after.md — worked examples" but no examples/ directory exists in the bundle, so one of the three referenced paths is dead.

4 / 5

Total

16

/

20

Passed

Description

70%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 excels at trigger guidance — an explicit Use-when clause, a dedicated Triggers list, and a clear negative scope — and carves out a distinctive niche. Its main weakness is that the skill's actual capability (rewriting ambiguous English into short, single-meaning, active-voice sentences) is never stated directly, only implied through trigger terms.

Suggestions

Open with a direct third-person capability statement, e.g. "Rewrites dense or ambiguous English into short, single-meaning, active-voice sentences that an agent or pipeline can parse without a human", before the Use-when clause.

Add the natural trigger variations users would most likely say — "simplify this text", "clarify this", "plain English" — to the Triggers list.

Narrow the broad "plain-language rewrite" trigger (e.g. "plain-language rewrite for machine consumption") to reduce overlap with general writing/editing skills.

DimensionReasoningScore

Specificity

The description names the domain precisely ("tool descriptions, error messages, inter-agent instructions, system prompts, status reports") and implies the core action through triggers ("STE100 rewrite", "plain-language rewrite", "controlled-language rewrite"), but never states a direct capability such as "rewrites dense English into short, single-meaning sentences". This matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive) rather than 4, which expects several explicitly listed actions.

3 / 5

Completeness

"When" is explicit and detailed ("Use when English text must be parsed without a human to resolve ambiguity... and misreading has a real cost", plus a Triggers list and an exclusion), while "what" is only conveyed indirectly through the trigger phrases rather than a stated capability. Between anchors 3 and 4: the strong, explicit Use-when clause and the implicit-but-present what put it at 4, though a direct what-statement would reach 5.

4 / 5

Trigger Term Quality

The explicit trigger list ("disambiguate", "STE100 rewrite", "apply Simplified Technical English", "controlled-language rewrite", "rewrite so an agent cannot misread this") gives good natural-phrase coverage. It falls short of anchor 5 because common variations users would actually say — "simplify this text", "clarify this", "make this clearer", "plain English" — are missing.

4 / 5

Distinctiveness Conflict Risk

A clear niche (Simplified Technical English / controlled-language rewriting for machine parseability) with near-unique triggers ("STE100 rewrite", "apply Simplified Technical English") and an explicit exclusion ("Not for creative or marketing copy"), giving minimal conflict risk with unrelated skills. It stays at 4 rather than 5 because the broad trigger "plain-language rewrite" overlaps with general writing/editing skills that would produce a non-STE rewrite.

4 / 5

Total

15

/

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

danyuchn/asd-ste100-skill

Path

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.