CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

web-apps

Build an app that runs in the Open SWE web UI, preview it beside the thread with preview_app, and release it with publish_app. Read this before building an Open SWE app or plugin.

Quality

92%

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

93%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 skill body: copy-paste-ready setup commands, exact file paths, platform-specific gotchas, and a clear build-preview-iterate-publish loop. The only gap is the absence of an explicit build-failure/validation recovery step in the iterate loop; structure and token efficiency are excellent given no bundle files are needed.

DimensionReasoningScore

Conciseness

Every line teaches something Claude cannot know about this platform ("The frame's policy blocks every request, so a CDN script, a fetch or a font URL fails", "a sandboxed frame with no network", "keep the app beside plugins/sdk, where its package.json finds the local SDK") with zero padding or explanation of known concepts — matching the 5 anchor 'every token earns its place'.

5 / 5

Actionability

Fully executable, copy-paste-ready guidance: a complete sparse-checkout command block ("git clone --depth 1 --filter=blob:none --sparse ... && npm install && npm run build"), exact files to edit ("Edit manifest.json and src/App.tsx"), the build output path (bundle/index.html), and concrete API usage ("host.threads.list({ source })") — matching the 5 anchor; specific examples cover the common cases.

5 / 5

Workflow Clarity

Clear sequenced process (starter → edit → build → preview_app → iterate → publish_app) with a human-in-the-loop checkpoint ("The person sees it beside the thread and can chat with you from it", "When the person wants to keep it, call publish_app"), matching the 4 anchor. Not 5 because there is no explicit error-recovery step (e.g. what to do when the build or preview fails); not 3 since the iterate loop and publish gate are genuine checkpoints.

4 / 5

Progressive Disclosure

No bundle files exist, and this short (~56 line) skill needs none: well-organized sections (The manifest, Start from the starter, Iterating) with external references kept one level deep and clearly signaled ("The SDK's README.md and src/client.ts document the host API"), matching the 5 anchor for a compact skill with well-organized sections.

5 / 5

Total

19

/

20

Passed

Description

87%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 strong description: it states concrete, tool-named capabilities covering the build-preview-release lifecycle and gives an explicit 'Read this before...' trigger clause. Keyword coverage is good but could add a few natural synonyms; the manifest/permissions aspect of the work is not surfaced.

DimensionReasoningScore

Specificity

Lists three concrete actions with named tools — "Build an app that runs in the Open SWE web UI", "preview it beside the thread with preview_app", "release it with publish_app" — matching the anchor for several specific actions with minor gaps; it omits manifest/permissions setup, so not the comprehensive coverage of the 5 anchor.

4 / 5

Completeness

Explicitly answers both: what ("Build an app... preview it... release it with publish_app") and when ("Read this before building an Open SWE app or plugin"), an explicit trigger clause with concrete trigger phrases matching the 5 anchor. Not a 4, because the 'when' is as explicit and specific as the anchor-5 example's 'Use when...' clause.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "Open SWE web UI", "app", "plugin", "preview_app", "publish_app" — terms a user in this environment would say. A few natural variations (e.g. "web app", "sidebar app", "publish") are missing, so it falls just short of the comprehensive synonym coverage of the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

Clear niche scoped to the "Open SWE web UI" with platform-specific tool names (preview_app, publish_app); no overlap risk with generic app-building or plugin skills, matching the 5 anchor's 'clear niche with distinct triggers'.

5 / 5

Total

18

/

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

langchain-ai/open-swe

Path

openswe/bundled_skills/web-apps/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.