CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

research-report

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

Quality

69%

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

Quality

Content

68%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 well-structured, specific, and actionable, providing concrete technical requirements for generating the report script. Its main weakness is the absence of a validation/verification checkpoint in the batch generate-and-execute workflow, which caps workflow clarity.

Suggestions

Add an explicit validation checkpoint after Step 4 (e.g., verify {topic}/report.md exists, is non-empty, and contains every expected item) with a fix-and-rerun feedback loop, which would lift workflow clarity above 3.

Provide a copy-paste-ready skeleton of generate_report.py (or move the full CATEGORY_MAPPING and formatting rules into a reference file) to push actionability toward 5.

Move the large CATEGORY_MAPPING dict and detailed value-formatting rules into a reference file referenced from SKILL.md to improve progressive disclosure and conciseness.

DimensionReasoningScore

Conciseness

The body is dense and task-specific (CATEGORY_MAPPING, formatting rules, skip conditions) without explaining concepts Claude already knows. Not a 5 because a few enumerated lists and the large mapping dict could be trimmed or externalized.

4 / 5

Actionability

Concrete field lists, an exact CATEGORY_MAPPING dict, explicit TOC format with a worked example, and precise skip conditions give mostly executable guidance. Not a 5 because the actual generate_report.py is not provided as copy-paste code; Claude must synthesize it from requirements.

4 / 5

Workflow Clarity

Steps 1-4 are clearly sequenced, but this batch operation (reading all JSON, generating, then executing a script) has no validation or verification checkpoint and no error-recovery loop. Per the judging guidelines, missing validation for a batch operation caps workflow clarity at 3.

3 / 5

Progressive Disclosure

No bundle files exist; content is organized into clear Trigger/Workflow/Output sections. Not a 5 because all content is inline (~80 lines) and the large CATEGORY_MAPPING dict plus detailed technical requirements could reasonably live in a separate reference file.

4 / 5

Total

15

/

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 clearly states what the skill does but omits any explicit trigger ('Use when...') guidance, which caps completeness. Trigger-term coverage is adequate but lacks synonyms and natural user phrasings.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill (e.g., 'Use when summarizing deep research results or generating a markdown report from JSON result files').

Include natural trigger synonyms and file/extension hints users might say (e.g., 'research report', 'outline.yaml', 'result JSON') to improve trigger term quality.

Tighten the capability list to concrete, distinct actions (e.g., 'Scan JSON result files, generate a Python conversion script, produce a markdown report with TOC') to lift specificity toward a 4.

DimensionReasoningScore

Specificity

Quotes 'Summarize deep research results into markdown report, cover all fields, skip uncertain values' name the domain plus a couple of concrete actions/constraints, but coverage is not comprehensive. Not a 4 because the actions are few and partly behavioral constraints rather than a broad capability list.

3 / 5

Completeness

A clear 'what' is present but there is no 'Use when...' trigger clause, which per the judging guidelines caps completeness at 3. Not a 4 because the 'when' is entirely missing rather than weakly implied.

3 / 5

Trigger Term Quality

Terms 'deep research results' and 'markdown report' are relevant but common synonyms and file extensions are missing. Not a 4 because natural user phrasings and variations are largely absent.

3 / 5

Distinctiveness Conflict Risk

The niche of summarizing research results into a markdown report while skipping uncertain values is mostly distinct with only minor overlap against generic report skills. Not a 5 because it could still overlap with general report-generation skills.

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

Weizhena/Deep-Research-skills

Path

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