CtrlK
BlogDocsLog inGet started
Tessl Logo

sn-research-report

用于撰写或组织研究报告结构。按读者认知任务(全景/对比/调查/时序)和领域惯例(学术/医疗/法律/政策)选择报告模板。

52

Quality

57%

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

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, highly actionable instruction skill whose template tables and format rules give Claude concrete structural guidance, weakened only by dot-graph/prose redundancy, the absence of an explicit validation checkpoint, and a monolithic single-file layout with no progressive disclosure.

Suggestions

Remove the redundancy between the dot decision-graph and the "领域专属触发条件" / "复合意图处理" bullets — keep one representation.

Add an explicit final validation step (e.g. "Before finishing, verify every 必须 section is present and every conclusion is tagged with a certainty level") to turn 执行纪律 into a true checkpoint.

Consider moving the four domain-specific templates (学术/医疗/法律/政策) into reference files linked from the body to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is dense and table-driven with no re-explanation of concepts Claude already knows, but the dot decision-graph largely duplicates the adjacent "领域专属触发条件" / "复合意图处理" prose, so it could be tightened.

2 / 3

Actionability

Provides concrete, directly usable guidance: per-template chapter tables with 必须/可选 markers, hard format requirements ("对比矩阵…必须有", evidence grading A/B/C, IRAC), and explicit 必须/禁止 rules — fully actionable for an instruction-only skill.

3 / 3

Workflow Clarity

The selection flow is clearly sequenced via the decision tree and reinforced by a 必须/禁止 checklist, but there is no explicit validation checkpoint or fix→retry feedback loop embedded in the workflow.

2 / 3

Progressive Disclosure

Well-sectioned internally (clear ## headers and tables, not a wall of text), but it is a single ~250-line file with no external references, and the four domain-specific templates are content that could plausibly be split into reference files.

2 / 3

Total

9

/

12

Passed

Description

50%

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 competent, reasonably specific description that states the skill's purpose and selection logic, but it omits an explicit "Use when…" trigger and does not enumerate multiple concrete actions or natural-term variations, capping most dimensions at the middle level.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to write or structure a research report, industry analysis, due-diligence, competitive comparison, or event timeline."

List a few more concrete output actions (e.g. "draft chapter skeletons, build comparison matrices, format evidence-graded findings") to raise specificity.

Include common natural variations users would say ("调研报告", "竞品分析", "行业研究", "尽调") alongside the existing terms.

DimensionReasoningScore

Specificity

Names concrete actions ("撰写或组织研究报告结构", "选择报告模板") and the selection mechanism (cognitive tasks + domain conventions), but offers only ~2 verbs rather than the multiple distinct concrete actions the top anchor calls for.

2 / 3

Completeness

Clearly states what the skill does, but the "when" is only implied via selection criteria — there is no explicit "Use when…" trigger clause, which caps completeness at 2 per the rubric guideline.

2 / 3

Trigger Term Quality

Includes natural terms a user might say ("研究报告", "报告模板"), but leans on the skill's own taxonomy jargon (全景/对比/调查/时序) and lacks common variation coverage; no explicit "Use when…" phrasing.

2 / 3

Distinctiveness Conflict Risk

The report-structure-templating framing with its task/domain taxonomy is a recognizable niche, but "研究报告" is broad enough to overlap with general writing or document skills.

2 / 3

Total

8

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
OpenSenseNova/SenseNova-Skills
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.