CtrlK
BlogDocsLog inGet started
Tessl Logo

report-writing

How to scope, draft, and revise a Markdown report artifact via generate_report

61

Quality

72%

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 ./surfsense_backend/app/agents/chat/multi_agent_chat/main_agent/skills/builtin/report-writing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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, well-structured, actionable decision guide for a single tool, with only minor gaps — chiefly the absence of a complete example invocation and an explicit verification checkpoint.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what a report is or how the tool works, and every line (param values, fallback rule) earns its place, matching the 'lean and efficient' anchor.

5 / 5

Actionability

Concrete, executable parameter guidance is given throughout (`source_strategy` values, `report_style="detailed"`, `parent_report_id`, example `user_instructions`), but no full `generate_report` invocation example is provided, leaving it just short of copy-paste-ready 5.

4 / 5

Workflow Clarity

A clearly sequenced numbered decision flow plus an explicit KB-no-results fallback hook gives a strong sequence with a checkpoint; it lacks an explicit validate-fix-retry loop, but report generation is not a destructive or batch operation so the 3-cap does not apply.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references and well-organized sections (When to use, Decision flow, Hooks), which the simple-skill exception explicitly scores at 5.

5 / 5

Total

18

/

20

Passed

Description

58%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 specific and tool-bound but omits an explicit 'when to use' trigger clause and lacks synonym coverage, leaving it competent yet mid-range on completeness and trigger quality.

Suggestions

Append a 'Use when…' clause with concrete trigger phrases (e.g., 'Use when the user asks to write a report, draft a memo, produce a brief, or expand an existing report').

Add natural synonyms such as 'memo', 'brief', and 'deliverable' alongside 'report' to improve trigger-term coverage.

Optionally enumerate the supported report styles or source strategies to push specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain ('Markdown report artifact') and three concrete actions ('scope, draft, and revise') plus the bound tool ('via generate_report'), matching the 'several specific actions; minor gaps' anchor; it stops short of the comprehensive multi-action coverage of a 5.

4 / 5

Completeness

It has a clear 'what' (scope/draft/revise a report via the tool) but no 'Use when…' clause or explicit trigger guidance, which the guidelines cap at 3.

3 / 5

Trigger Term Quality

The single natural keyword 'report' is relevant but the description misses common synonyms users say (memo, brief, deliverable), fitting the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

Tightly bound to one tool (generate_report) and one artifact type, making it mostly distinct with only minor overlap risk against general writing skills; it does not quite reach the clear-niche, minimal-conflict bar of 5.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
MODSetter/SurfSense
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.