agentleFS
RylaispiritRylaispirit/rylai-codex-hermes-skills/skills/content-research-writer/SKILL.md

content-research-writer

Skill56 starsChanged 3 months agoMITView on GitHub

Research, outline, draft, cite, and revise articles, reports, tutorials, newsletters, and case studies with traceable sources and preserved voice.

72 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use skill-share, raffle-winner-picker and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ArogyaReddySkill

    skill-share

    A skill that creates new Claude skills and automatically shares them on Slack using Rube for seamless team collaboration and skill discovery.

    Also in 22 projects that use this

  • ArogyaReddySkill

    raffle-winner-picker

    Picks random winners from lists, spreadsheets, or Google Sheets for giveaways, raffles, and contests. Ensures fair, unbiased selection with transparency.

    Also in 26 projects that use this

  • pepebot-spaceSkill

    llm-application-dev

    Building applications with Large Language Models - prompt engineering, RAG patterns, and LLM integration. Use for AI-powered features, chatbots, or LLM-based automation.

    Also in 4 projects that use this

  • trendinuxSkill

    twitter-algorithm-optimizer

    Analyze and optimize tweets for maximum reach using Twitter's open-source algorithm insights. Rewrite and edit user tweets to improve engagement and visibility based on how the recommendation system ranks content.

    Also in 13 projects that use this

  • guaderramaSkill

    lead-research-assistant

    Identifies and qualifies potential leads by analyzing products/services, understanding ideal customer profiles, conducting intelligent web research using Bright Data MCP tools, and providing actionable outreach strategies. Use when researching leads, prospecting, qualifying contacts, analyzing companies, enriching lead data, or creating outreach campaigns.

    Also in 27 projects that use this

  • +6 more from ArogyaReddy

The file

Show its rules and text

We split this skill into the rules it gives an agent

19 rules. 0 are common, 19 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 68 edited versions we read keep these.

  • 19

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the research and file tools available in the active runtime.

    line 23
  2. Distinctive:

    Add questions for context, counterarguments, examples, and practical impact.

    line 46
  3. Distinctive:

    Prefer primary material for factual and technical claims.

    line 49
  4. Distinctive:

    Use reputable synthesis for context and competing interpretations.

    line 50
  5. Distinctive:

    Check publication date, authorship, methodology, and conflicts of interest.

    line 51
  6. Distinctive:

    Do not put a source in the final reference list unless it was opened and used.

    line 61
  7. Distinctive:

    Write from the outline and source ledger.

    line 83
  8. Distinctive:

    Use examples to explain, not to substitute for evidence.

    line 85
  9. Distinctive:

    Keep the user's voice, terminology, and preferred level of formality.

    line 86
  10. Distinctive:

    Check argument order, transitions, redundancy, and paragraph purpose.

    line 89
  11. Distinctive:

    Remove unsupported authority cues and decorative statistics.

    line 91
  12. Distinctive:

    Check that the cited source supports the exact nearby claim.

    line 96
  13. Distinctive:

    Do not rewrite the whole section when a focused edit would preserve more of the writer's voice.

    line 120
  14. Distinctive:

    Follow the user's requested citation format.

    line 134
  15. Distinctive:

    Never invent a source, author, title, date, URL, quotation, or page number.

    line 135
  16. Distinctive:

    Prefer direct links or identifiers to vague publication names.

    line 136
  17. Distinctive:

    Keep source notes long enough to audit but do not reproduce large passages.

    line 138
  18. Distinctive:

    Avoid flattening personal prose into generic professional language.

    line 146
  19. Distinctive:

    Ask for confirmation only when a voice choice changes meaning or audience fit.

    line 147

“Common” is measured: kept by at least 6 in 10 of the 68 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Content Research Writer

Build useful prose from a traceable research base. Keep verified facts, source interpretation, and the writer's own argument clearly separated.

Runtime Compatibility

  • Use the research and file tools available in the active runtime.
  • Resolve workspace files from the user's stated project path.
  • Confirm network and source access before promising current citations.
  • Preserve existing drafts and user edits unless replacement is explicitly requested.

Establish The Brief

Infer available details, then fill only material gaps:

  • topic and central question;
  • intended audience;
  • purpose and publication format;
  • target length and deadline;
  • voice or writing samples;
  • citation style;
  • required, preferred, or excluded sources.

Record uncertain assumptions before research begins.

Research Workflow

  1. Create research questions
    • Convert the topic into a short list of claims the piece must establish.
    • Add questions for context, counterarguments, examples, and practical impact.
  2. Choose sources
    • Prefer primary material for factual and technical claims.
    • Use reputable synthesis for context and competing interpretations.
    • Check publication date, authorship, methodology, and conflicts of interest.
  3. Build a source ledger
| ID | Source | Claim Supported | Evidence | Limits | Status |
|---|---|---|---|---|---|
| S1 | [title and locator] | [claim] | [fact or short note] | [caveat] | verified |

Do not put a source in the final reference list unless it was opened and used.

  1. Resolve conflicts
    • Compare definitions, dates, sample populations, and measurement methods.
    • Report meaningful disagreement instead of selecting a convenient number.
  2. Stop when evidence is sufficient
    • Each major factual claim has support.
    • Important counterevidence is represented.
    • Additional searching is unlikely to change the structure or conclusion.

Writing Workflow

  1. Thesis
    • State the article's central answer in one or two sentences.
  2. Outline
    • Give every section a job.
    • Link claims to source IDs.
    • Mark evidence gaps before drafting.
  3. Draft
    • Write from the outline and source ledger.
    • Cite factual claims near the relevant sentence.
    • Use examples to explain, not to substitute for evidence.
    • Keep the user's voice, terminology, and preferred level of formality.
  4. Edit
    • Check argument order, transitions, redundancy, and paragraph purpose.
    • Replace vague claims with evidence or narrower wording.
    • Remove unsupported authority cues and decorative statistics.
  5. Verify
    • Open every citation again when accuracy matters.
    • Confirm names, titles, dates, quotations, quantities, and links.
    • Check that the cited source supports the exact nearby claim.

Collaboration Modes

Outline First

Return:

  • thesis options;
  • proposed section order;
  • claim-to-source map;
  • research gaps;
  • questions that require the user's judgment.

Section Review

Lead with the highest-impact feedback:

  • argument or evidence issue;
  • structure and flow;
  • audience or voice mismatch;
  • concrete revision;
  • citations still needed.

Do not rewrite the whole section when a focused edit would preserve more of the writer's voice.

Full Draft

Deliver the requested article and a short verification note containing:

  • citation style used;
  • claims still awaiting evidence;
  • assumptions or source limitations;
  • optional editorial alternatives.

Citation Rules

  • Follow the user's requested citation format.
  • Never invent a source, author, title, date, URL, quotation, or page number.
  • Prefer direct links or identifiers to vague publication names.
  • Quote only when exact wording is necessary; otherwise paraphrase accurately.
  • Keep source notes long enough to audit but do not reproduce large passages.
  • For current or changing facts, research them at the time of writing.

Voice Preservation

  • Study supplied writing samples before making broad stylistic changes.
  • Preserve intentional vocabulary, rhythm, and point of view.
  • Distinguish correctness edits from optional stylistic suggestions.
  • Avoid flattening personal prose into generic professional language.
  • Ask for confirmation only when a voice choice changes meaning or audience fit.

Final Check

  • The thesis answers the stated question.
  • Each section advances the piece.
  • Important factual claims have traceable support.
  • Sources are represented fairly, including limitations and disagreement.
  • Citations and reference entries agree.
  • The final voice belongs to the user, not to a generic template.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.