CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

research-report

将deep调研结果汇总为markdown报告,覆盖所有字段,跳过不确定值。

Quality

65%

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-zh/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 a well-structured, actionable specification for generating a report script, respecting Claude's intelligence and staying concise. Its main weakness is the absence of validation/verification around the batch script execution step.

Suggestions

Add a validation checkpoint after Step 4: confirm report.md was created, is non-empty, and spot-check that no '[不确定]' values leaked through and every item appears in the table of contents.

Add an error-recovery loop for script execution (e.g., if generate_report.py raises, read the traceback, fix the script, and re-run) since it is a generated script run on batch input.

Consider moving the CATEGORY_MAPPING table and complex-value formatting rules into a referenced file to keep the overview lean, signaling it as one-level-deep detail.

DimensionReasoningScore

Conciseness

Dense and instructional, assuming Python competence without explaining basic concepts; the large CATEGORY_MAPPING block is justified detail rather than padding, with only minor tightening possible.

4 / 5

Actionability

Provides a concrete, executable spec for generate_report.py with explicit field lookup order, skip conditions, and formatting rules; not copy-paste code but a detailed actionable blueprint with minor gaps.

4 / 5

Workflow Clarity

Steps 1–4 are clearly sequenced, but Step 4 simply runs the script with no validation checkpoint for a batch operation over all JSON results, capping workflow clarity at 3 per the batch-operation guidance.

3 / 5

Progressive Disclosure

Single self-contained SKILL.md with well-organized Step sections and no nested references; slightly over 50 lines, with the CATEGORY_MAPPING detail that could arguably live in a separate file.

4 / 5

Total

15

/

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 and domain but omits any trigger guidance, so it does not tell Claude when to invoke the skill. It is reasonably specific and distinctive but incomplete as a discovery signal.

Suggestions

Add an explicit 'Use when...' clause naming the natural trigger phrases a user would say (e.g., 'Use when summarizing deep research results into a report, or when the user asks to aggregate research JSON into markdown').

Include synonyms or related terms users might say (报告, 汇总, 总结, research report) to improve trigger-term coverage.

Mention the expected input artifacts (e.g., */outline.yaml with output_dir of JSON results) so Claude can recognize the matching context.

DimensionReasoningScore

Specificity

Names the domain ('deep调研结果') and a concrete action ('汇总为markdown报告') plus two behavioral filters, but the filters are constraints rather than additional actions so coverage is not comprehensive.

3 / 5

Completeness

The 'what' is clear (aggregate research results into a markdown report) but the 'when' is entirely missing, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Contains domain terms like 'deep调研' and 'markdown报告' but lacks natural user trigger phrases, a 'Use when…' clause, synonyms, or file extensions.

2 / 5

Distinctiveness Conflict Risk

Niche focus on aggregating deep-research results into a report makes it mostly distinct with only minor overlap risk against related reporting skills.

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-zh/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.