CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

screenpipe-bug-report

Turn a recorded software failure into a reproducible bug report with timestamps and observed behavior.

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-bug-report/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.

An impressively lean, instruction-only body with a sensible implicit workflow, explicit safety gates (sanitize evidence, never repeat destructive actions, draft-only unless authorized), and honest-reporting checkpoints. Its main weakness is actionability: how to actually query screenpipe-api and what shape the final report should take are left unspecified.

Suggestions

Add one concrete example of inspecting recorded activity with screenpipe-api (e.g., a specific query for frames around the failure time) so the investigation step is executable rather than a hint.

Include a minimal bug-report skeleton (title, environment, steps to reproduce, expected/actual, evidence links) so the output format is unambiguous.

Add short section headers for the three phases (Investigate / Write / Sanitize & deliver) to make the implicit sequence and safety gates scannable.

DimensionReasoningScore

Conciseness

Roughly 150 words, three lean paragraphs, zero padding or explanation of concepts Claude already knows — every sentence instructs ('Resolve the affected app...', 'Remove credentials...', 'Do not repeat destructive actions'). Matches 'Lean and efficient; assumes Claude's competence; every token earns its place'; not a 4 because there is no over-explanation to trim.

5 / 5

Actionability

Concrete deliverables are enumerated (reproduction steps, expected behavior, actual behavior, environment/version, evidence links) plus specific sanitization items ('credentials, unrelated screen content, personal identifiers, and private business metrics'), but key execution details are missing: no example of how to inspect activity/frames with screenpipe-api and no report format or template. Fits 'Some concrete guidance but incomplete... missing key details'; not a 4 because 'inspect the relevant activity and frames' is a high-level hint rather than executable guidance.

3 / 5

Workflow Clarity

A clear three-phase sequence (resolve context and recover the sequence via screenpipe-api; write the report; sanitize and return a draft) with several explicit checkpoints: 'environment/version when verified', 'Mark steps that could not be reproduced', 'Return a draft report unless issue creation is explicitly authorized'. Not a 5: the phases are implied by paragraph order rather than enumerated, and there is no review/fix loop on the draft; not a 3: validation checkpoints are explicitly present, and the workflow is read-only rather than destructive or batch, so no cap applies.

4 / 5

Progressive Disclosure

Under 50 lines with no bundle files and no content that belongs in separate references, so the structure is appropriate for a small skill; the three paragraphs are thematically ordered (investigate / write / sanitize). Not a 5: the body has only a single '# bug report' heading with no section headers, so it is not organized into well-signaled sections; not a 3: nothing is inlined that should be split out, and navigation over content this short is unambiguous.

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.

A concise, third-person description with a clear 'what' and a genuinely distinct niche, but it omits any 'Use when...' trigger guidance and lacks natural synonyms like 'crash', 'error', or 'screen recording'. Adding an explicit trigger clause would most directly raise completeness and trigger term quality.

Suggestions

Append a trigger clause such as 'Use when the user recorded a crash or error (e.g., via screenpipe) and wants a bug report or issue draft from it' to answer 'when' explicitly.

Include natural synonyms users would actually say — 'crash', 'error', 'screen recording', 'file an issue' — to broaden trigger term coverage.

Optionally enumerate one or two more concrete actions (e.g., 'sanitize evidence and draft an issue') to strengthen specificity.

DimensionReasoningScore

Specificity

The description names the domain ('recorded software failure', 'bug report') and one concrete transformation with specifics ('reproducible bug report with timestamps and observed behavior'), but does not list several distinct actions — comparable to 'Processes PDF files and extracts content'. Not a 4: no enumeration of multiple specific actions like extraction, redaction, or draft-vs-issue handling; not a 2: the action is concrete, not generic.

3 / 5

Completeness

The 'what' is clear ('Turn a recorded software failure into a reproducible bug report with timestamps and observed behavior'), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3. Not a 2: the 'what' is specific, not vague; not a 4: 'when' is entirely absent, not merely imprecise.

3 / 5

Trigger Term Quality

'bug report', 'software failure', 'reproducible', 'timestamps' are relevant and natural, but common user phrasings are missing: 'crash', 'error', 'screen recording', 'issue'. Matches 'Some relevant keywords but missing common variations or synonyms'; not a 4 because a user saying 'I recorded a crash, file a bug' would not obviously match.

3 / 5

Distinctiveness Conflict Risk

'recorded software failure' plus 'timestamps and observed behavior' carves a fairly clear niche (screen-recording-derived bug reports) with minimal conflict against general debugging or testing skills. Not a 5: it could still overlap with generic 'write a bug report' or QA-reproduction skills since no recording-specific trigger phrase is stated; not a 3: the scope is materially narrower than 'Works with document files'.

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-bug-report/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.