agentleFS
foversefoverse/seoverse/.agents/skills/openseo-review-web-content/SKILL.md

openseo-review-web-content

Skill4 starsChanged 13 days agoMITView on GitHub

Write and review content for the OpenSEO website (web/), including blog posts, guides, feature pages, FAQs. Makes sure each page delivers real value to its target reader. Use whenever adding or editing user-facing prose in web/content or web/src.

4 other projects use a version of this.

Adopted by

Steady: 0 new projects 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: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 3

    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 lists instead of dense paragraphs: bullet points for things the reader needs to do or check, and numbered lists for steps in order.

    line 17
  2. Distinctive:

    Use the deslop skill for AI tells.

    line 33
  3. Distinctive:

    Run prettier on the files you touch.

    line 35

“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

OpenSEO Web Content

Every page is for a specific reader. A blog post should leave them better at SEO. A product page should help them decide whether OpenSEO solves their problem. Judge every edit by one question: is this better for that reader? We are not writing to pass a review.

Write for the reader

  • Say up front what the reader will get, in their terms.
  • Organize around their job, not the source material. Interviews become a plan, not a roundup of quotes.
  • Carry one real example through, with real numbers.
  • Use lists instead of dense paragraphs: bullet points for things the reader needs to do or check, and numbered lists for steps in order.
  • Give practical advice, even when it's messier than the official rules.
  • Answer straight. "No" and "it costs money" are complete answers.

Cut what isn't for them

  • Notes for whoever checks the draft: method footers, "verbatim" assurances, tool or API names, "re-checked on" dates.
  • Hedges that protect the writer, and links or asides that interrupt.
  • Anything that reads like an ad. A company used as an example is there to teach.

Don't make things up

That's the whole accuracy bar. Product capabilities, prices, quotes, and data must be real, so check product claims against the code. Framing, figures of speech, and opinions are the writer's call. Don't ask for disclosures or a source for every number. Never call OpenSEO simply "free."

Voice

Use the deslop skill for AI tells. When editing someone else's post, keep their voice and examples. In the playbook library, an approach is a "strategy," never a "play."

Run prettier on the files you touch.

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.