CtrlK
BlogDocsLog inGet started
Tessl Logo

content-research-writer

内容创作者、技术写作员在撰写博客、深度文章或技术文档时,使用此技能可开启全流程写作协作。它能帮你研究资料、构建大纲、逐段打磨并自动添加引用,快速优化Hook,让你高效产出高质量内容,告别孤军奋战!

62

Quality

73%

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

Quality

Content

63%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 delivers actionable, well-sequenced templates for a collaborative writing workflow. It is held back by verbosity from duplicated and peripheral sections and by a monolithic single-file structure with no progressive disclosure.

Suggestions

Remove the 'What This Skill Does' list (it duplicates the frontmatter description) and trim Pro Tips/Best Practices/Related Use Cases to essentials to reduce token load.

Move the full feedback, citation, and final-review templates into a referenced file (e.g. references/templates.md) and keep only a concise quick-start in SKILL.md to improve progressive disclosure.

Consolidate the four overlapping Writing Workflows into a single compact decision table or shorten Examples to two representative cases.

DimensionReasoningScore

Conciseness

The ~400-line body is mostly actionable templates rather than concept re-explanation, but 'What This Skill Does' duplicates the description and the Examples/Pro Tips/Best Practices/Related Use Cases sections add notable padding that could be tightened.

3 / 5

Actionability

Provides concrete, copy-paste-ready templates for outlining, research output, hook analysis, section feedback, three citation styles, and a final review with checklist, with only minor abstraction in placeholders.

4 / 5

Workflow Clarity

A clear 1–8 sequence (understand → outline → research → hook → feedback → voice → citations → final review) with feedback loops and a pre-publish checklist; no destructive or batch operations requiring validation caps.

4 / 5

Progressive Disclosure

Sections are clearly headed, but everything is inlined in a single long file with no file references or bundle structure, and at ~400 lines it does not qualify for the simple-skill exception.

3 / 5

Total

14

/

20

Passed

Description

83%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 conveys both capability and trigger context with concrete actions and natural keywords. Its main weakness is the second-person voice, which the rubric penalizes, and a few missing synonym triggers.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (研究资料, 构建大纲, 逐段打磨, 自动添加引用, 优化Hook) giving comprehensive coverage, but the second-person voice (它能帮你, 让你) triggers a 1-point specificity penalty per the rubric.

4 / 5

Completeness

Explicitly answers both 'what' (research, outline, polish, cite, optimize hook) and 'when' (在撰写博客、深度文章或技术文档时) with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural terms a user would say are well covered (博客, 深度文章, 技术文档, 引用, Hook, 大纲), though a few common synonyms (newsletter, tutorial, essay) are missing.

4 / 5

Distinctiveness Conflict Risk

The research-plus-citation-plus-collaborative-writing niche is mostly distinct with concrete triggers, with only minor overlap risk against general writing skills.

4 / 5

Total

17

/

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

skill_md_line_count

SKILL.md is long (539 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
anbeime/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.