CtrlK
BlogDocsLog inGet started
Tessl Logo

research-writing-assistant

Use when writing academic papers, theses, or research articles - supports brainstorming, chapter writing, literature review, and LaTeX output

64

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%Weight 40%Scale 1-3

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 reasonably organized modular-skill index with useful process rules and red-flag tables, but it suffers from duplicated sections, a numbering error in the standard flow, and references to non-existent skill/module paths while ignoring the bundled scripts. Tightening the structure and fixing the references would raise most dimensions.

Suggestions

Remove the duplicate "## 模块兼容(向后兼容)" header (lines 139 and 157) and consolidate the two two-stage Review descriptions (lines 135-137 and 141-155) into one canonical section to save tokens and remove ambiguity.

Fix the step numbering in "标准流程" so the two "4." entries (章节写作 and 两阶段 Review) become distinct sequential steps, yielding a clean 1-5 (or 1-6) sequence.

Reference the actual bundled scripts (e.g. scripts/style_check.sh, scripts/scholar_search.py, scripts/research_quality_gate.ps1) from the relevant workflow steps so progressive disclosure points to real, actionable files instead of non-existent skills/ and modules/ paths.

DimensionReasoningScore

Conciseness

Mostly efficient tables and rules, but redundancy hurts: "## 模块兼容(向后兼容)" appears twice (lines 139 and 157) and the two-stage Review is described twice (lines 135-137 then 141-155), so it could be tightened. Not a 3 because duplicate content wastes tokens; not a 1 because it avoids explaining concepts Claude already knows.

2 / 3

Actionability

Provides routing to sub-skills and concrete do/don't red-flag tables, but no executable code or commands in the body, and the real bundle scripts (e.g. style_check.sh, scholar_search.py) are never referenced. Score caps at 2 because guidance delegates to sub-skills not present in the bundle rather than giving copy-paste-ready instruction.

2 / 3

Workflow Clarity

The "标准流程" sequence (steps 1-5) and two-stage Review checkpoints are present, but step numbering is broken (two "4." entries at lines 125 and 135) and the duplicated sections obscure the sequence. Not a 1 because steps and checkpoints exist; not a 3 because the numbering error and duplication break the clean sequence.

2 / 3

Progressive Disclosure

The body is organized as an overview with tables pointing to skills/ and modules/ paths, but those referenced paths do not exist in the bundle while the actual scripts/ files are orphaned and unreferenced. Some structure exists, but references are not clearly signaled toward real files, capping the score at 2.

2 / 3

Total

8

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 concise, third-person, and follows the recommended 'Use when...' pattern with concrete capabilities and explicit triggers. It cleanly answers both what the skill does and when to invoke it.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "brainstorming, chapter writing, literature review, and LaTeX output" — matching the anchor that enumerates several specific capabilities.

3 / 3

Completeness

Explicitly states what it does ("supports brainstorming, chapter writing, literature review, and LaTeX output") and when to use it ("Use when writing academic papers, theses, or research articles"), answering both what and when.

3 / 3

Trigger Term Quality

Uses natural terms a user would say ("academic papers, theses, or research articles") with good coverage and no jargon.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear academic/research-writing niche with distinct triggers, unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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
Norman-bury/research-writing-skill
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.