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.
Install with Tessl CLI
npx tessl i github:davepoon/buildwithclaude --skill content-research-writer68
Quality
26%
Does it follow best practices?
Impact
98%
1.44xAverage score across 6 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/content-research-writer/SKILL.mdDiscovery
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') and reads as marketing copy rather than functional guidance. The description is too generic and would likely conflict with other writing or content-related skills.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'write article', 'draft blog post', 'need citations', 'improve my writing', 'content creation'
Remove the marketing fluff sentence ('Transforms your writing process...') and replace with specific use cases or file types this skill handles
Define a clearer niche to distinguish from general writing help - e.g., specify if this is for academic writing, blog content, technical documentation, or long-form articles
| 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 actions. | 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 which violates guidelines. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords like 'writing', 'content', 'research', 'citations', 'outlines', 'hooks', but missing common variations users might say like 'draft', 'article', 'blog post', 'essay', 'edit', or 'proofread'. | 2 / 3 |
Distinctiveness Conflict Risk | Very generic writing assistance description 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 |
Implementation
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 (writing basics, file organization, what hooks are) while providing templates that are more illustrative than actionable. The content would benefit from aggressive trimming to ~100 lines focusing on the unique value-add (specific feedback formats, citation handling) with detailed examples moved to separate reference files.
Suggestions
Cut 70%+ of content by removing explanations of basic concepts (what hooks are, how to organize folders, generic writing advice) and keeping only project-specific templates and formats
Split detailed examples, workflow variations, and best practices into separate reference files (e.g., EXAMPLES.md, WORKFLOWS.md) with clear links from a concise main skill
Add validation checkpoints to workflows - e.g., 'After outline: verify all research gaps are identified before proceeding to drafting'
Replace generic advice ('create curiosity', 'promise value') with specific, executable techniques or concrete before/after transformations
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400+ lines. Explains obvious concepts Claude knows (what hooks are, how to organize files, basic writing workflows). The 'What This Skill Does' section redundantly lists capabilities that are then repeated in detail. Much content could be cut by 70%+ without losing actionable value. | 1 / 3 |
Actionability | Provides concrete examples and templates (outline structure, feedback format, citation styles), but much is template/placeholder rather than executable. The examples show output formats but lack specificity on HOW to actually perform research or improve hooks beyond generic advice like 'create curiosity' and 'promise value'. | 2 / 3 |
Workflow Clarity | Multiple workflows are listed (Blog Post, Newsletter, Technical Tutorial) with numbered steps, but they lack validation checkpoints. No feedback loops for error recovery - just linear 'do this then that' sequences. The 8-step instruction process is clear but doesn't specify when to verify quality or iterate. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. Everything is inline despite being 400+ lines. Content like 'File Organization', 'Pro Tips', 'Best Practices', and detailed examples could easily be split into separate reference files. No navigation structure beyond headers. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- 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.