agentleFS
VercelKnown publishervercel/eve/apps/templates/marketing-team-eve-template/agent/subagents/content-marketer/skills/blog-style/SKILL.md

blog-style

Skill5.9k starsChanged 4 days agoApache-2.0View on GitHub

Use when drafting or editing a blog post or long-form article in the house voice.

4 other projects use a version of this, 1 of them edited; 1 new project in the last 4 weeks, against 0 the 4 before.

How people change it

All 1 edited versions we compared keep every one of its 2 rules.

Of the 1 edited version we compared: 1 keep every rule.

We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.

Adopted by

Surging: 1 new project took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 1 new project
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 1 in all, so this is a hint, not a trend.

Most recently taken up by

Who's talking about vercel/eve

The biggest 5 of 57 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 57

Talked about on GitHub and Bluesky (57 times).

On GitHub · 50

45 more on GitHub

On Bluesky · 7

2 more on Bluesky

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

    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:

    When writing or editing a blog post:

    line 7
  2. Distinctive:

    No exclamation points; no "in today's fast-paced world" openers.

    line 14

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

Blog voice & style

When writing or editing a blog post:

  • Lead with the reader's problem, not the product. Most people scan and read maybe a quarter of the words, so front-load the point: first in the post, first in each section and paragraph.
  • Short paragraphs, 2–4 sentences, one idea each. White space is a feature, not filler.
  • Descriptive subheads that read as a map: skim only the H2s and you should get the gist. Break up any section that runs past ~300 words. Use lists for steps or anything parallel.
  • Most sentences under ~20 words. Active voice. Cut hedges: "just", "simply", "very", "really".
  • Concrete over abstract; show an example before stating a principle.
  • No exclamation points; no "in today's fast-paced world" openers.
  • Match length to what the question needs; there's no magic word count. A quick answer can be a few hundred words; a real guide earns its length. Don't pad to hit a number.
  • Mind the SEO surface: one descriptive title (~50–60 chars, keyword near the front), a short hyphenated slug, 3–5 internal links with real anchor text, and alt text on meaningful images. See references/format-specs.md for the numbers.

Structure

  1. Hook: the problem or tension, in the reader's words; promise the payoff and preview it.
  2. Stakes: why it matters now.
  3. Payoff: the idea/solution, with one concrete example.
  4. Close: the single takeaway, then one focused next step. No "in conclusion".

References

  • references/best-practices.md: sourced checklist of current blog tactics (scanning, hook, structure, readability, length, SEO basics, close).
  • references/format-specs.md: concrete specs for title and meta length, heading hierarchy, word-count ranges, readability targets, slug, alt text, and internal links.
  • references/banned-words.json: the words to avoid. The lint_against_style tool checks a draft against this list, so run the tool rather than reading the file.

Layers on top of

The writing-quality skill carries the surface-independent rules: AI tells, plain-English swaps, front-loading, concrete over abstract, voice. Load it too; this skill only adds what's specific to blog posts.

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.