agentleFS
Sign inStart free
VercelKnown publishervercel-labs/eve-content-agent-template/agent/skills/blog-style/SKILL.md

blog-style

Skill28 starsChanged 22 days agoApache-2.0View on GitHub

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

3 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 1

    1. vercel-labs/marketing-team-eve-template★ 45981% same

    Wrote their own version · 2

    1. AgriciDaniel/claude-blog★ 2.7ksame name
    2. alpit-patel/seo-aeo-geo-kit★ 2same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

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 16

“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: title/meta length, heading hierarchy, word-count ranges, readability targets, slug, alt text, internal links.
  • references/banned-words.json — the list of words to avoid. Read it once up front for awareness, then run the lint_against_style tool on your draft to check it against this file before proposing the draft to the writer.

Shared references

Shared global references for all skills in the content agent. These apply regardless of the content type.

  • references/ai-phrases-to-avoid.md — AI-tell words, phrases, and punctuation to avoid.
  • references/plain-english-alternatives.md — plain-English swaps for bloated or vague wording.

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