CtrlK
BlogDocsLog inGet started
Tessl Logo

product-tutorial-pipeline

Reproduce or refresh a product tutorial with polished screenshots end-to-end — cloud dashboard flows, desktop app flows, Screen.Studio-style framing, tutorial doc, PR. Use when asked to "redo the tutorial", "refresh tutorial screenshots", "make a tutorial/walkthrough with screenshots", or to document a cloud + desktop flow like the OpenWork Cloud team quickstart.

80

Quality

100%

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

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An efficient, actionable pipeline doc: numbered steps, executable commands, explicit verification checkpoints, and clean delegation of detail to companion skills. No bundle files exist, but the body is appropriately split into short sections and routes outward for depth.

DimensionReasoningScore

Conciseness

Lean and dense — assumes Claude knows git worktrees, Electron, CDP, etc., and spends tokens only on non-obvious gotchas like the macOS 'app.whenReady() never fires' warning; every line earns its place.

3 / 3

Actionability

Fully executable commands with placeholders throughout (git worktree add, bash dev scripts, window.resizeTo, node beautify.mjs, the image-verify loop, gh pr create), copy-paste ready.

3 / 3

Workflow Clarity

Clearly sequenced pipeline (sections 0–5 + Cleanup) with explicit validation checkpoints (Verify orgMode, spot-check outputs, verify every referenced image exists, wait for 'Ready for new tasks') and a feedback loop that prints MISSING images.

3 / 3

Progressive Disclosure

Well-organized overview that offloads depth to clearly signaled one-level-deep companion skills (agent-first-screenshots, daytona-electron-den, cloud-dashboard-walkthrough) and the beautify.mjs script; no monolithic wall or nested references.

3 / 3

Total

12

/

12

Passed

Description

100%

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: concrete actions, explicit third-person 'what', a well-formed 'Use when' clause with natural quoted triggers, and a distinct niche. No first/second-person voice or vague fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete pipeline actions — 'cloud dashboard flows, desktop app flows, Screen.Studio-style framing, tutorial doc, PR' — matching the anchor for several specific concrete actions rather than a single domain.

3 / 3

Completeness

Explicitly answers both what (reproduce/refresh tutorial end-to-end with screenshots, doc, PR) and when ('Use when asked to ...') with explicit triggers, satisfying the top anchor.

3 / 3

Trigger Term Quality

Quotes natural user phrases ('redo the tutorial', 'refresh tutorial screenshots', 'make a tutorial/walkthrough with screenshots') giving good coverage of terms a user would actually say, not jargon.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (polished tutorial screenshots for cloud + desktop flows, e.g. OpenWork Cloud quickstart) with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
different-ai/openwork
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.