CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sage-openui

Present answers as streaming native interactive UI or presentations in Sage Desktop v2. Use when structured visual presentation or user interaction helps accomplish the task.

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 ./app/skills/sage-openui/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 lean, well-structured instruction-only skill with a genuine validation feedback loop and appropriate externalization of the component contract to a reference file. Its main gap is the total absence of a worked example of the openui output format, which forces Claude to assemble the format from scattered rules.

Suggestions

Add one minimal annotated `openui` fenced code block (e.g., a root component with two children and a computed binding) so the abstract rules have a concrete template to follow.

Make the generation workflow order explicit (choose format, define root, add bindings, run self-check, replace if defective) instead of leaving it implied by section order.

Trim duplicated computation-related constraints in the 'Protocol and interaction' section into a single rule set.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence without explaining known concepts, but sentences like "Do not approximate an unsupported computation with a result that appears live but does not update correctly" restate constraints already covered and could be trimmed.

4 / 5

Actionability

Concrete micro-rules exist ("fenced code block whose language is exactly `openui`", "Children are arrays even when there is only one child", "Use a Deck root for presentations"), but the body contains no example of an actual openui block or component tree, leaving key execution details missing.

3 / 5

Workflow Clarity

The "Output self-check" section provides an explicit validate-then-fix feedback loop ("correct their underlying cause and emit one complete replacement") and construction order is stated ("Define the root first and referenced content afterwards"), but the overall sequence is implicit across sections rather than explicitly ordered.

4 / 5

Progressive Disclosure

The skill is under 50 lines with well-organized sections and a single clearly signaled, one-level-deep reference ([components.md](references/components.md)) that exists on disk as the generated component-contract reference, matching the simple-skill pattern for a top score.

5 / 5

Total

16

/

20

Passed

Description

62%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 answers both what and when in third-person style and is anchored to a specific host product, giving reasonable distinctiveness. It is held back by thin action coverage (essentially two actions) and abstract trigger language that misses natural user phrasings.

Suggestions

Enumerate more concrete capabilities in the description (e.g., builds interactive forms with live-computed results, renders dashboards, generates navigable slide decks with PPTX export).

Add natural trigger terms users would actually say, such as "dashboard", "interactive form", or "slide deck".

Sharpen the when-clause from "helps accomplish the task" to specific conditions, e.g., "Use when the user asks for an interactive UI, dashboard, or presentation in Sage Desktop".

DimensionReasoningScore

Specificity

"Present answers as streaming native interactive UI or presentations in Sage Desktop v2" names the domain and two concrete actions, matching anchor 3 rather than 4, which requires several specific actions.

3 / 5

Completeness

Both what ("Present answers as streaming native interactive UI or presentations") and when ("Use when structured visual presentation or user interaction helps accomplish the task") are present, but the when-clause is generic and lacks concrete trigger phrases, matching anchor 4.

4 / 5

Trigger Term Quality

Terms like "interactive UI", "presentations", and "user interaction" are relevant, but common user phrasings such as dashboard, charts, slides, or demo are missing, matching anchor 3 ("Some relevant keywords but missing common variations or synonyms").

3 / 5

Distinctiveness Conflict Risk

Tying the skill to "Sage Desktop v2" native UI gives it a clear niche, but "presentations" and "visual presentation" carry minor overlap risk with pptx- and dataviz-oriented skills, matching anchor 4.

4 / 5

Total

14

/

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

ZHangZHengEric/Sage

Path

app/skills/sage-openui/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.