CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

echo

Simulating users to evaluate existing flows and generate synthetic demand: cognitive walkthroughs, feature requests, unmet needs, JTBD, and opportunity trees. Not real-user research.

Quality

73%

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 ./echo/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 dense, well-sequenced operational skill with genuinely specific numeric contracts and good reference signaling, undermined by a duplicated metadata comment block, repeated rules, date-sensitive details in the body, and a bundle in which none of the referenced files actually ship. Tightening the body and shipping the referenced files would lift both conciseness and progressive disclosure.

Suggestions

Delete the CAPABILITIES_SUMMARY / COLLABORATION_PATTERNS / BIDIRECTIONAL_PARTNERS HTML comment block — it duplicates the Trigger Guidance, Collaboration, and Output Routing sections almost entirely.

State each rule once (emotion-score range, [hypothesis] tagging, council caps) in a single authoritative section instead of repeating it across Core Contract, Always/Never, Workflow, and Output Requirements.

Ship the referenced files (reference/*.md, _common/*.md) in the bundle or trim the body to match what is actually provided; move date-stamped details (WCAG 3.0 WD status, engine policy dates) into the relevant reference file.

DimensionReasoningScore

Conciseness

The body is mostly dense, operational instruction with no pedagogy, but it carries real padding: a ~40-line HTML comment block (CAPABILITIES_SUMMARY, COLLABORATION_PATTERNS, BIDIRECTIONAL_PARTNERS) that duplicates the Trigger Guidance, Collaboration, and Output Routing sections, plus rules repeated across sections (emotion scoring and [hypothesis] tagging each stated 3-4 times) and date-stamped details ("March 2026 Working Draft", "CR expected Q4 2027", "Base Engine Policy (2026-05)"). It fits "mostly efficient but could be tightened" better than the padded anchor 2, since no concept explanations are taught.

3 / 5

Actionability

For an instruction-only skill the guidance is concrete: a 6-phase workflow table with per-phase required actions and reads, an explicit subcommand dispatch allowlist, and hard numeric rules (emotion scores -3 to +3, ≤1-4 tasks per session, `aloud` n≥5, council caps Solo/SMB≤3/Enterprise≤9, SUS mean + 90% CI). Score 4 rather than 5 because key mechanics (the 8 PRE-SCAN risk signals, Persona Contract schema, Pattern H JSON schema, VERIFY gates) are pointers to reference files rather than inline specifics — and none of those referenced files exist in this bundle.

4 / 5

Workflow Clarity

The PRE-SCAN → MASK ON → WALK → SPEAK → ANALYZE → PRESENT sequence is explicit with per-phase actions, key rules, and read-files, and per-recipe VERIFY gates plus degraded-mode fallbacks are named. Not 5 because the actual checkpoint contents are delegated to reference/process-workflows.md (absent from the bundle), so validation steps are referenced rather than specified inline.

4 / 5

Progressive Disclosure

The Reference Map table signals one-level-deep references well ("Read this when" per file), but no bundle files exist — all ~25 referenced `reference/*.md` and `_common/*.md` paths are dead in this bundle — and substantial content that has named reference files is still inlined (Multi-Engine Mode detail despite reference/tri-engine-walkthrough.md; council-mode rules despite reference/council-mode.md). This is more than minor organization drift, fitting anchor 3 better than 4.

3 / 5

Total

14

/

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.

A concise, third-person description that names its niche and several concrete methods, with a strong explicit differentiator ("Not real-user research"). Its main weakness is the absence of an explicit "Use when..." trigger clause, which caps completeness, and some missing natural synonyms (persona, usability).

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks for persona walkthroughs, cognitive walkthroughs, usability or emotion evaluation of a flow, or synthetic feature requests / unmet-needs hypotheses."

Include high-traffic natural synonyms such as "persona", "usability", and "user simulation" to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description lists several concrete capabilities — "Simulating users to evaluate existing flows", "generate synthetic demand", "cognitive walkthroughs, feature requests, unmet needs, JTBD, and opportunity trees" — matching the several-specific-actions anchor with minor gaps. It falls short of 5 because major capabilities (emotion scoring, dark-pattern audits, A/B hypothesis generation) are omitted and "generate synthetic demand" is somewhat abstract.

4 / 5

Completeness

The "what" is clear (simulating users to evaluate flows and generate synthetic demand, with a method list), but there is no "Use when..." clause or equivalent explicit trigger guidance — "when" is only weakly implied by "evaluate existing flows". Per the rubric guideline, a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Natural UX-research keywords are well covered: "cognitive walkthroughs", "feature requests", "unmet needs", "JTBD", "opportunity trees", "simulating users" — terms a user needing this skill would plausibly say. Not 5 because common synonyms like "persona", "usability", "user research", or "emotion" are missing; not 3 because coverage goes beyond a few relevant keywords.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (simulated-persona UX evaluation) and explicitly disambiguates with "Not real-user research", which prevents overlap with real-user-research skills. Distinct method names (JTBD, opportunity trees, cognitive walkthroughs) minimize conflict risk.

5 / 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

simota/agent-skills

Path

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