agentleFS
Sign inStart free
prestariusprestarius/jet-skills-stack/skills/article-writing/SKILL.md

article-writing

Skill1 starsChanged 2 months agoMITView on GitHub

Draft a long-form article, blog post, essay, or technical write-up in the author's own voice — outline first, then a full draft that reads like a person wrote it. Use whenever the user asks to "write an article", "draft a blog post", "write a long-form piece", "turn this into an essay", or wants a publishable write-up rather than notes or a spec.

55 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use bun-runtime, agent-sort and 10 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.
  • tpavanipradeepSkill

    bun-runtime

    Bun as runtime, package manager, bundler, and test runner. When to choose Bun vs Node, migration notes, and Vercel support.

    Also in 22 projects that use this

  • niloykumarbarmanSkill

    agent-sort

    Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.

    Also in 10 projects that use this

  • royaluniondesign-sysSkill

    configure-ecc

    Interactive installer for Everything Claude Code — guides users through selecting and installing skills and rules to user-level or project-level directories, verifies paths, and optionally optimizes installed files.

    Also in 9 projects that use this

  • royaluniondesign-sysSkill

    content-hash-cache-pattern

    Cache expensive file processing results using SHA-256 content hashes — path-independent, auto-invalidating, with service layer separation.

    Also in 12 projects that use this

  • mryeastcodeSkill

    everything-claude-code-conventions

    Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.

    Also in 8 projects that use this

  • junimnjwSkill

    ralphinho-rfc-pipeline

    RFC-driven multi-agent DAG execution pattern with quality gates, merge queues, and work unit orchestration.

    Also in 8 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 45 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write something worth reading: a clear argument in the author's voice, not generic AI filler.

    line 6
  2. Very specific:

    Get the facts straight: If the piece makes claims that could be wrong or dated, research them first (use the market-research skill) and …

    line 11
  3. Distinctive:

    Draft in voice: Write the full piece. Make an argument.

    line 16
  4. Distinctive:

    Don't pad to hit a word count, and don't bury the point.

    line 24

“Common” is measured: kept by at least 6 in 10 of the 45 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

Write something worth reading: a clear argument in the author's voice, not generic AI filler.

  1. Set the brief. Pin down topic, audience, the one thing the reader should take away, rough length, and voice. If the user gave a writing sample or ./CONTEXT.md defines a tone, match it; otherwise ask once. Respond in the language the user is writing in (PL or EN).
  2. Get the facts straight. If the piece makes claims that could be wrong or dated, research them first (use the market-research skill) and verify on the web. Don't invent sources, quotes, or statistics.
  3. Outline, then confirm. Propose a structure — a strong lede (a hook or a sharp claim, not a warm-up paragraph), the body beats, and a real takeaway. Get a nod before drafting a long piece.
  4. Draft in voice. Write the full piece. Make an argument; be concrete and specific; have a point of view where the genre allows it. Vary sentence rhythm. Avoid the AI tells — apply the humanizer patterns to your own prose as you write (no "in today's fast-paced world", no rule-of-three padding, no hollow conclusion).
  5. Finish clean. Markdown by default. If it's destined for the vault, emit it via the obsidian-note schema instead. If the source was a Markdown document, stay exhaustive — restructure for readability but don't quietly drop content.

Don't pad to hit a word count, and don't bury the point. One strong draft the author can edit beats a hedged, voiceless one.

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.

Check your setup, free