CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sage-desktop-plugin-development

Create, validate, and register custom HTML, CSS, and JavaScript panels in Sage Desktop. Use when asked to build or update a Desktop plugin.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 exceptionally tight, high-signal skill body: every line states host-specific behavior Claude could not infer, workflows carry explicit validation and retry loops, and all referenced bundle files exist. Structure relies on short paragraphs and a bullet list rather than headers, which is adequate at this length.

DimensionReasoningScore

Conciseness

The body is ~24 lines of dense host-specific facts — tool names, CSS variables, sizing constraints, API request/response shapes — with no padding and no explanation of concepts Claude already knows. Every token earns its place, matching the 5 anchor.

5 / 5

Actionability

Guidance is fully concrete: exact tool calls with parameters ("call register_desktop_plugin once with package_path set to the workspace-relative ZIP path"), exact SDK calls ("await sageDesktop.ready", "await sageDesktop.call(method, params)"), per-method parameter shapes ({key}, {name, base64}, {text}), and complete working example bundles to start from. Copy-paste-ready for the common cases.

5 / 5

Workflow Clarity

Build-package-register and list-download-modify-register sequences are clearly laid out with an explicit validation feedback loop ("The tool validates the package before registration. If validation fails, fix the reported issue and retry") plus an uncertain-result reconciliation loop and version-preservation rules. Matches the 5 anchor's validate-fix-retry pattern.

5 / 5

Progressive Disclosure

The body is under 50 lines with one-level-deep references that all resolve to real bundle files (assets/example/manifest.json, assets/project-data/manifest.json, assets/manifest.schema.json), and two complete example plugins are available in the bundle. The simple-skill exception applies: well-organized short content with clear inline-linked references.

5 / 5

Total

20

/

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 concise, concrete description that names specific actions, artifacts, and the target platform, with an explicit trigger clause. Its main limitation is narrow trigger coverage — a single use-when phrase and few synonyms — which leaves it just short of the top anchors.

Suggestions

Expand the 'Use when' clause with additional concrete triggers, e.g., 'Use when asked to build, update, or debug a Sage Desktop plugin, panel, or sidebar extension'.

Add one or two natural synonyms users might say (e.g., 'add-in', 'custom panel') to broaden trigger-term coverage without adding vagueness.

Optionally mention packaging or modifying already-installed plugins in the what-clause to make capability coverage more comprehensive.

DimensionReasoningScore

Specificity

"Create, validate, and register custom HTML, CSS, and JavaScript panels" lists several concrete actions with named artifacts, but coverage is not comprehensive — packaging, modifying installed plugins, and SDK usage described in the body are omitted. Not 3 (more than 1-2 actions) and not 5 (minor gaps in coverage).

4 / 5

Completeness

Both parts are present: a clear what ("Create, validate, and register custom HTML, CSS, and JavaScript panels in Sage Desktop") and an explicit when ("Use when asked to build or update a Desktop plugin"). Falls between anchors 4 and 5 — the when clause is explicit but offers only a single trigger phrase rather than multiple concrete ones — so the even score applies.

4 / 5

Trigger Term Quality

Natural phrases like "build or update a Desktop plugin", "Sage Desktop", and "panels" match what users would say, but there are no synonyms or variations (e.g., "add-in", "extension", "sidebar panel"). Good coverage with a few natural terms missing, matching the 4 anchor.

4 / 5

Distinctiveness Conflict Risk

"Sage Desktop" plugin development is a clear niche with distinct triggers; "build or update a Desktop plugin" is unlikely to fire for unrelated skills. Matches the 5 anchor (clear niche, minimal conflict risk).

5 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 2 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

ZHangZHengEric/Sage

Path

app/skills/sage-desktop-plugin-development/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.