CtrlK
BlogDocsLog inGet started
Tessl Logo

simplified-english

Write user-facing comments, plans, and documents in ASD-STE100 Simplified Technical English — short, unambiguous sentences with approved words and one meaning each — so readers understand them the first time.

59

Quality

69%

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 ./packages/skills-catalog/catalog/optional/content/simplified-english/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 tight, well-organized, single-purpose rule set with concrete, actionable guidance and no bundle-file overhead, scoring at the top on workflow clarity and progressive disclosure.

DimensionReasoningScore

Conciseness

The body is lean — short bullet rules and a concrete word-substitution list with no padding — with only a minor explanatory stretch in the approved-words paragraph ("the Dictionary in the current ASD-STE100 specification..."), so it sits just below the fully-lean anchor.

4 / 5

Actionability

Guidance is concrete and executable for an instruction-only skill: specific length limits ("procedures ≤ 20 words, descriptions ≤ 25 words") and exact substitution pairs ("start/stop" not "initiate/commence/terminate/kill"), missing only a worked before/after example to reach fully copy-paste-ready.

4 / 5

Workflow Clarity

This is a simple single-purpose skill (apply STE rules when writing) under 50 lines with no destructive or batch operation, so per the simple-skill exception the single unambiguous action scores the top of the scale.

5 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references (none exist in references/scripts/assets), and is organized into clear "Core rules" and "Approved words" sections, satisfying the well-organized-sections exception for top marks.

5 / 5

Total

18

/

20

Passed

Description

53%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 clearly states what the skill does and carves out a distinct niche, but it lacks an explicit "Use when..." trigger clause and natural-language synonyms, so it lands at mid-level on trigger term quality and completeness.

Suggestions

Add an explicit "Use when..." clause with concrete triggers, e.g. "Use when the user asks for plain, simple, or clear English, or wants to simplify comments, plans, or documents."

Include natural synonyms users actually say ("plain English", "simple language", "clear writing") alongside the technical term "ASD-STE100".

Broaden capability coverage by naming a few concrete actions beyond "write", such as "simplify", "rewrite", or "check" existing text against the rules.

DimensionReasoningScore

Specificity

It names the domain ("user-facing comments, plans, and documents") and one concrete action ("Write ... in ASD-STE100 Simplified Technical English"), but offers only that single action rather than several distinct capabilities, matching the domain-plus-1-2-actions anchor.

3 / 5

Completeness

The "what" is clear (write in Simplified Technical English), but there is no explicit "Use when..." trigger clause; the artifact scope ("for user-facing comments, plans, and documents") only weakly implies the "when", so completeness is capped at 3 per the missing-trigger guidance.

3 / 5

Trigger Term Quality

Relevant terms appear ("comments, plans, and documents", "short, unambiguous sentences", "approved words"), but it leans on the technical name "ASD-STE100" and omits natural synonyms a user would say like "plain English", "simple language", or "clear writing".

3 / 5

Distinctiveness Conflict Risk

The ASD-STE100 / Simplified Technical English niche is fairly distinct with specific triggers for user-facing text, leaving only minor overlap risk with general writing or clarity skills.

4 / 5

Total

13

/

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
paperclipai/paperclip
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.