CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

end-user-ui

End-user UX for node_web_interface (React) and web_interface (Flask/templates): entry-level trading terms OK, no pro-trader jargon, minimal UI, situational focus, no AI slop, no em dash in UI strings. Apply on any UI copy, layout, error, or help change.

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

An exemplary lean style-guide skill: terse, concrete, and well-structured, with explicit pre-handoff validation steps and cleanly signaled external references. The only meaningful improvement would be a worked bad-to-good copy example and an explicit step ordering for the reinstall/test sequence.

DimensionReasoningScore

Conciseness

The body is a lean rule set with zero padding and no explanation of concepts Claude already knows ("Short sentences; active voice", "Empty states: one line what this is plus one action"). Every section is a tight, token-efficient list that assumes Claude's competence.

5 / 5

Actionability

Guidance is largely executable: exact paths, concrete commands ("bash .cursor/reinstall-tentacles.sh", "npm test" with full path, pytest for web_interface/tests), a stack-to-copy-location table, and specific banned phrases with replacements. Minor gap: no before/after example rewrites of UI copy, which would make a copy-style skill fully copy-paste ready.

4 / 5

Workflow Clarity

The flow is discernible (edit only under the two tentacle paths, then the Before handoff checklist with explicit validation: re-read strings aloud, npm test, pytest, no new e2e), and validation checkpoints are concrete. Not a 5 because the ordering of the reinstall script relative to editing/testing is implicit rather than an explicit sequenced workflow.

4 / 5

Progressive Disclosure

With no bundle files, the ~53-line body is a well-organized overview with clear sections and one-level-deep, clearly signaled pointers (colocated AGENTS.md guides, sibling skills, README, /app/debug). Nothing inlined belongs in a separate file, so navigation is easy.

5 / 5

Total

18

/

20

Passed

Description

78%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 highly specific, well-scoped description that explicitly states both capabilities and trigger conditions with minimal fluff. Its only weakness is that the trigger clause could echo the stack/package scope and include more natural synonym phrasing.

Suggestions

Fold the stack scope into the trigger clause, e.g. "Apply on any UI copy, layout, error, or help change in node_web_interface or web_interface" so the when-conditions are as concrete as the what.

Add one or two natural synonyms users would say, such as "wording", "labels", or "error messages", to broaden trigger-term coverage.

State at least one positive action (e.g. "Write and review end-user copy") alongside the constraint list to round out capability coverage.

DimensionReasoningScore

Specificity

Lists several concrete constraints scoped to two named interfaces ("entry-level trading terms OK, no pro-trader jargon, minimal UI, situational focus, no AI slop, no em dash in UI strings"), which goes beyond naming the domain. It falls short of anchor 5 because these are policies/constraints rather than a comprehensive inventory of concrete actions the skill performs.

4 / 5

Completeness

Both what (the end-user UX constraints for the two UI tentacles) and when ("Apply on any UI copy, layout, error, or help change") are explicitly stated. Not anchor 5 because the when-clause omits the stack scoping, so the trigger phrases are less concrete than the what.

4 / 5

Trigger Term Quality

The trigger clause "Apply on any UI copy, layout, error, or help change" uses natural terms users would say. Not anchor 5 because common synonyms and variations (wording, labels, text, screens, frontend, React components) are missing.

4 / 5

Distinctiveness Conflict Risk

Scoped to two specific OctoBot tentacle packages (node_web_interface React UI and web_interface Flask templates) with distinct UI-copy triggers, giving it a clear niche with minimal conflict risk against generic design or documentation skills.

5 / 5

Total

17

/

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

Drakkar-Software/OctoBot

Path

.cursor/skills/end-user-ui/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.