CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

research-report

Summarize deep research results into markdown report, cover all fields, skip uncertain values.

Quality

61%

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 ./skills/research-en/research-report/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 skill body is a concrete, well-structured recipe that is mostly actionable, but it lacks validation/feedback checkpoints for a batch-generation operation and carries some redundancy and a large inline mapping that could be tightened or externalized.

Suggestions

Add an explicit validation checkpoint after generating generate_report.py and before executing it (e.g. lint or dry-run, verify report.md exists and TOC links resolve) to lift workflow clarity above the batch-operation cap.

Trim redundant requirement restatements (e.g. "Cover all field values from each JSON" vs "Skip fields with values containing [uncertain]") and move the long CATEGORY_MAPPING dict to a referenced file to improve conciseness.

Show a minimal complete runnable snippet or the script skeleton inline so the guidance is copy-paste ready rather than a specification.

DimensionReasoningScore

Conciseness

The body is mostly efficient and task-focused, but it includes some padding (restated requirements, redundant bullets under "Cover all field values" / "Skip fields") and a hard-coded CATEGORY_MAPPING dict that could be trimmed, fitting the mostly-efficient-but-tightenable anchor.

3 / 5

Actionability

It provides a concrete, near-executable recipe: locate outline.yaml, scan JSON fields, generate a Python script with a real CATEGORY_MAPPING example and explicit formatting rules, then run it; minor gaps remain since no full runnable script is shown inline.

4 / 5

Workflow Clarity

Steps are clearly sequenced (locate results -> scan fields -> generate script -> execute), but the workflow involves batch file generation over many JSON inputs with no validation/checkpoint between script generation and execution, so the feedback-loop cap applies.

3 / 5

Progressive Disclosure

Content is well-organized into Trigger/Workflow/Output sections with numbered steps and clearly delimited technical requirements; no bundle files exist so this is essentially a single self-contained file, with only minor bulk (the category mapping) that could be externalized.

4 / 5

Total

14

/

20

Passed

Description

46%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 states a clear purpose but lacks any explicit trigger guidance, which caps its completeness and trigger-term quality. Adding a "Use when..." clause with natural user keywords would meaningfully improve it.

Suggestions

Add an explicit trigger clause, e.g. "Use when summarizing completed research into a single markdown report."

Include natural user-facing keywords such as "research report", "summary report", or "research results" so it matches what a user would actually say.

Spell out the concrete actions (generate a Python conversion script, build a TOC with anchor links, produce report.md) to raise specificity beyond high-level phrasing.

DimensionReasoningScore

Specificity

The description names the domain (deep research results -> markdown report) and a few concrete actions ("cover all fields", "skip uncertain values"), but the actions are high-level and not comprehensively enumerated, matching the score-3 anchor.

3 / 5

Completeness

It gives a clear "what" (summarize research into a markdown report) but no explicit "when" or trigger guidance; per the rubric, a missing "Use when..." clause caps completeness at 3.

3 / 5

Trigger Term Quality

It relies on technical phrasing ("deep research results", "markdown report") with no natural user keywords or "Use when..." trigger phrases, so only a couple of generic terms are present, fitting just below the score-3 anchor.

2 / 5

Distinctiveness Conflict Risk

"Summarize deep research results into markdown report" carves a fairly distinct niche with low overlap risk versus general skills, sitting between the score-3 and score-5 anchors and noticeably above the midpoint.

4 / 5

Total

12

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

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

Warning

Total

15

/

16

Passed

Repository

Weizhena/Deep-Research-skills

Path

skills/research-en/research-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.