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

47%

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 ./skills/content-research-writer/SKILL.md

Quality

Content

35%

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

The skill delivers genuinely useful, actionable writing templates and a clear workflow, but it is far too long for what it conveys — heavy on redundant template scaffolding and inline blocks that belong in separate reference files. Verification is limited to a single checklist rather than explicit feedback loops.

Suggestions

Cut the redundant sections (Writing Workflows, Pro Tips, Best Practices, Related Use Cases) which restate material already covered in Instructions and Examples, and remove the marketing fluff closing line.

Move the large template blocks (outline, research output, section feedback, citation formats) into reference files under references/ and link to them one level deep, keeping SKILL.md a lean overview.

Add explicit validation checkpoints to the workflow — e.g., after research and after each section, require a confirm-proceed step mirroring the validate-then-fix loop the rubric rewards.

Dimension	Reasoning	Score
Conciseness	At roughly 530 lines the body is padded with redundant template boilerplate and restated sections (Writing Workflows, Pro Tips, File Organization, Best Practices, Related Use Cases) that rehash earlier material, well beyond the 'mostly efficient' bar.	1 / 3
Actionability	It supplies concrete templates (outline, research output, feedback, citation styles) and a worked hook-improvement example with three real rewrites, but much guidance remains in placeholder form ([Specific issue] -> [Suggested fix]) rather than fully executable artifacts.	2 / 3
Workflow Clarity	The multi-step process is clearly sequenced with per-workflow checklists, but verification checkpoints are largely implicit — only a Pre-Publish Checklist exists with no validate-then-proceed loops for the writing workflow.	2 / 3
Progressive Disclosure	The skill is a single monolithic file with no bundle files; template blocks (research/feedback/citation formats) that could be split into reference files are inlined, fitting the 'content that should be separate is inline' anchor.	2 / 3
	Total	7 / 12 Passed

Description

60%

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 strong on specificity with a clear list of concrete actions, but it omits any explicit 'when to use' trigger guidance and lacks natural user-facing keywords. The marketing-fluff closing line adds nothing functional.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger terms (e.g., blog posts, articles, newsletters, citations, outlines, hook improvement) so Claude knows when to invoke this skill.

Remove the marketing sentence 'Transforms your writing process from solo effort to collaborative partnership' — it is vague fluff that does not aid triggering.

Tighten the opening from 'Assists in writing high-quality content' to a sharper, more distinctive verb phrase that signals the writing-research niche.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section' — matching the highest anchor.	3 / 3
Completeness	It clearly answers 'what' but never answers 'when Claude should use it'; per the judging guidelines a missing explicit trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	It contains some relevant keywords (citations, outlines, hooks, feedback) but lacks the natural trigger phrasing a user would actually say and provides no 'Use when...' keywords; common variations are missing.	2 / 3
Distinctiveness Conflict Risk	The writing-content niche is somewhat specific, but the generic 'Assists in writing high-quality content' framing and absence of distinct trigger terms leave it able to overlap with general assistance skills.	2 / 3
	Total	9 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (540 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: MoizIbnYousaf/Ai-Agent-Skills
Path: skills/content-research-writer/SKILL.md
Commit: 039ad59

Reviewed: about 5 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.