content-research-writer

Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.

Quality

26%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./content-research-writer/SKILL.md

Quality

Content

27%

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

This skill is excessively verbose, explaining concepts Claude already understands (feedback structure, writing workflows, file organization) while providing limited actionable, executable guidance. The content would benefit from aggressive trimming to ~100 lines focusing on project-specific conventions and splitting detailed templates into referenced files.

Suggestions

Cut 75% of content by removing explanations of concepts Claude knows (what hooks are, how to structure feedback, basic writing advice) and keep only project-specific conventions or unique approaches

Split detailed templates (feedback format, citation styles, workflow checklists) into separate reference files like FEEDBACK_TEMPLATE.md and CITATION_FORMATS.md

Add validation checkpoints to workflows, e.g., 'Confirm outline addresses user's stated goals before proceeding to research phase'

Replace abstract guidance like 'Find credible sources' with concrete instructions such as specific search strategies or source evaluation criteria unique to this workflow

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~400+ lines. Explains obvious concepts Claude already knows (what hooks are, how to give feedback, basic file organization). The 'What This Skill Does' section lists capabilities Claude inherently has. Multiple sections could be condensed to 1/4 their length.	1 / 3
Actionability	Provides structured templates and example outputs, but most content is abstract guidance rather than executable instructions. The 'research' examples show output format but not how to actually conduct research. Shell commands for setup are concrete but trivial.	2 / 3
Workflow Clarity	Multiple workflows are listed (Blog Post, Newsletter, etc.) with clear sequences, but they lack validation checkpoints. No feedback loops for error recovery. The numbered steps are present but don't include verification points like 'confirm outline meets user goals before proceeding.'	2 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files. Everything is inline despite being 400+ lines. Content like citation formats, workflow templates, and example feedback could be split into separate reference files. No navigation structure beyond headers.	1 / 3
	Total	6 / 12 Passed

Description

25%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description provides a moderate list of writing-related capabilities but fails to include explicit trigger guidance ('Use when...'), making it difficult for Claude to know when to select this skill. The final sentence uses second person voice ('your writing') which violates the rubric guidelines, and reads as marketing copy rather than functional description. The scope is too broad and would likely conflict with other writing or research skills.

Suggestions

Add an explicit 'Use when...' clause with trigger terms like 'write article', 'draft blog post', 'add citations', 'improve my writing', 'outline essay'

Remove the marketing fluff sentence and replace with specific use cases or file types this skill handles

Narrow the scope to a specific type of content (e.g., 'academic papers', 'blog posts', 'technical documentation') to reduce conflict risk with other writing skills

Dimension	Reasoning	Score
Specificity	Names domain (writing/content) and lists several actions (conducting research, adding citations, improving hooks, iterating on outlines, providing feedback), but these are somewhat generic writing activities rather than highly specific concrete operations.	2 / 3
Completeness	Describes what it does but completely lacks a 'Use when...' clause or any explicit trigger guidance. The final sentence 'Transforms your writing process...' is marketing fluff rather than usage guidance, and uses second person voice.	1 / 3
Trigger Term Quality	Contains some relevant keywords like 'writing', 'citations', 'outlines', 'research', but missing common variations users might say like 'draft', 'article', 'blog post', 'essay', 'edit', 'proofread', or file types.	2 / 3
Distinctiveness Conflict Risk	Very generic writing assistance that would conflict with any other writing, editing, research, or content creation skills. No clear niche or distinct triggers to differentiate it.	1 / 3
	Total	6 / 12 Passed

Validation

68%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 11 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (539 lines); consider splitting into references/ and linking	Warning
description_voice	'description' should use third person voice; found second person: 'your '	Warning
description_trigger_hint	Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')	Warning
metadata_version	'metadata' field is not a dictionary	Warning
license_field	'license' field is missing	Warning

	Total	11 / 16 Passed

Repository: ComposioHQ/awesome-claude-skills
Path: content-research-writer/SKILL.md
Commit: 362d354

Reviewed: about 10 hours ago

Table of Contents

Discovery Implementation Validation

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.