CtrlK
BlogDocsLog inGet started
Tessl Logo

content-research-writer

Research, outline, draft, cite, and revise evidence-based articles, briefs, and reports.

84

1.21x
Quality

78%

Does it follow best practices?

Impact

91%

1.21x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./resources/bundled-skills/content-research-writer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 lean, well-structured instruction skill with concrete workflow steps and an explicit validation checklist; it is strong across all dimensions with only minor actionability and inline-validation gaps.

DimensionReasoningScore

Conciseness

The body is lean and well-sectioned with no over-explanation of concepts Claude already knows; every line (tool routing, workflow, gates, boundaries) earns its place, matching the lean/efficient anchor.

5 / 5

Actionability

Concrete guidance is given via the tool-routing table and specific workflow directives ("record URLs, dates, and relevant claims", "Draft with claim-to-source traceability"), but some terms ("source standard", "freshness requirement") are left for Claude to interpret, so minor gaps remain.

4 / 5

Workflow Clarity

A clear five-step sequence is paired with an explicit Completion-gates checklist acting as validation, but the validation lives in a separate section rather than as tight inline gate-and-retry loops, so it falls just short of the explicit-checkpoint anchor.

4 / 5

Progressive Disclosure

At under 50 lines with no need for external references, the well-organized sections (Purpose, Tool routing, Workflow, Completion gates, Boundaries, Delivery) qualify for the simple-skill exception scoring 5.

5 / 5

Total

18

/

20

Passed

Description

71%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 is specific and action-rich with a clear niche, but omits an explicit "Use when..." trigger clause, which caps completeness at 3 and slightly limits distinctiveness.

Suggestions

Add an explicit "Use when..." clause naming concrete triggers, e.g. "Use when the user asks to research, outline, draft, or revise an evidence-based article, brief, or report."

Broaden trigger terms with common synonyms (papers, memos, white papers, essays) so the skill surfaces for the phrasings users naturally say.

Add a freshness/source-standard cue to the description (e.g. cite primary sources with URLs and dates) to sharpen the niche versus generic writing skills.

DimensionReasoningScore

Specificity

"Research, outline, draft, cite, and revise" lists five concrete verbs covering the full evidence-based writing lifecycle, matching the comprehensive-coverage anchor; not below because coverage is broad rather than 1-2 actions.

5 / 5

Completeness

The description clearly states "what" (research, outline, draft, cite, revise evidence-based articles, briefs, reports) but has no "Use when..." clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural verbs (research, outline, draft, cite, revise) plus document types (articles, briefs, reports) give good keyword coverage, but a few common synonyms (e.g. paper, memo, essay) are missing, so it stops short of the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

The evidence-based + citation framing carves a clear niche with distinct triggers, with only minor overlap risk against general drafting skills; not 5 because the absent explicit trigger clause leaves slight ambiguity.

4 / 5

Total

16

/

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
KunAgent/Kun
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.