CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

screenpipe-process-guide

Convert a recorded or starred procedure into a reusable guide with verified steps and explicit gaps.

Quality

71%

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 ./crates/screenpipe-core/assets/skills/screenpipe-process-guide/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is an efficient, non-padded instruction set with a sensible implicit workflow and built-in verification/sanitization rules. Its weakness is actionability: the screenpipe-api mechanics — the one tool-specific thing Claude could not guess — are described only abstractly, and the short body has no section headers to aid navigation.

Suggestions

Add one or two concrete screenpipe-api examples (e.g., the actual starred-only search call with a bounded time-range parameter) so the recovery step is executable rather than descriptive.

Add brief section headers (e.g. "## Recover evidence", "## Write the guide", "## Handle starred work") so the four implicit phases are signaled for navigation.

Clarify what "the activity summary's starred intervals" refers to and what a "bounded time range" looks like in practice, since these are tool-specific details Claude cannot infer.

DimensionReasoningScore

Conciseness

Four lean paragraphs with no padding, no explanation of concepts Claude already knows, and no filler — every sentence adds guidance the model would not infer on its own. This matches the 'lean and efficient; assumes Claude's competence' anchor.

5 / 5

Actionability

The deliverable structure is concrete ("prerequisites, the trigger, steps with observable results, meaningful branches, and a final verification") and constraints are specific ("exact UI labels only when visible", "remove account-specific identifiers, secrets"), but the core tool operation is left vague — no screenpipe-api invocation, no example search, and no concrete meaning for "bounded time range" or "the activity summary's starred intervals". Key execution details are missing, matching the 'some concrete guidance but incomplete' anchor rather than the 'mostly executable' level of 4.

3 / 5

Workflow Clarity

A clear paragraph-ordered sequence emerges (identify audience → recover demonstration → inspect frames → write the guide → sanitize → deliver), with validation checkpoints present ("a final verification", "distinguish instructions captured from a demonstration from a procedure independently tested"). It is not a numbered step list with explicit fix-and-retry feedback loops, so it does not reach 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files and no external references needed, so monolithic-content penalties do not apply. However, the body has no section headers at all — only the H1 and four unmarked paragraphs — so it lacks the "well-organized sections" that would justify a 5 under the simple-skill exception; paragraph grouping is logical but not signaled.

4 / 5

Total

16

/

20

Passed

Description

53%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 is concise and names a genuinely specific niche, with a clear "what". Its main weakness is the complete absence of "when to use" trigger guidance, which caps completeness at 3, and a keyword set that misses the natural phrases users would say when needing this skill.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to turn a screen recording, starred activity, or captured demonstration into a how-to guide, SOP, or step-by-step documentation."

Include natural user synonyms such as "screen recording", "how-to", "documentation", or "SOP" so the description matches the phrases users actually say, not just the tool's vocabulary.

Consider naming the evidence source (screenpipe activity capture) in the description to further reduce overlap with generic documentation-writing skills.

DimensionReasoningScore

Specificity

"Convert a recorded or starred procedure into a reusable guide with verified steps and explicit gaps" names the domain (recorded/starred procedures) and adds output qualifiers ("verified steps", "explicit gaps"), but describes essentially one action rather than several distinct capabilities. It sits at the 'names domain and 1-2 concrete actions' level, not the 'several specific actions' level of 4.

3 / 5

Completeness

The "what" is clear (convert a recorded/starred procedure into a reusable guide with verified steps and explicit gaps), but there is no "Use when..." clause or equivalent trigger guidance at all. Per the rubric guideline, a missing explicit trigger caps completeness at 3 — it is not weakly implied, it is entirely absent, so it cannot score 4.

3 / 5

Trigger Term Quality

Keywords like "recorded", "starred", "procedure", "guide", and "steps" are relevant, but common user variations are missing — "screen recording", "how-to", "documentation", "SOP", "turn this into a guide". "Starred" is also tool-specific jargon rather than a natural user term, matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The "recorded or starred procedure" niche is fairly distinct and unlikely to trigger for unrelated skills, but without naming the capture tool or medium, it could overlap with generic documentation/how-to writing skills. This fits 'mostly distinct; minor overlap risk' rather than the clear-niche minimal-conflict level of 5.

4 / 5

Total

13

/

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

screenpipe/screenpipe

Path

crates/screenpipe-core/assets/skills/screenpipe-process-guide/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.