agentleFS
m-binimranm-binimran/marketing-pack/skills/seo-brief/SKILL.md

seo-brief

Skill1 starsChanged 5 months agoMITView on GitHub

Build an SEO content brief - target keyword, search intent, SERP analysis, outline, and on-page elements - for a writer. Use when planning content to rank, before drafting.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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 for the searcher first, the engine second - no keyword stuffing or thin AI content.

    line 24
  2. Very specific:

    Verify keyword/volume claims with a real tool.

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

seo-brief

A brief that lets a writer produce a page that actually ranks and converts.

Process

  1. Target keyword + intent: the primary term and what the searcher actually wants (informational / commercial / transactional). Verify real search terms - don't assume volume.
  2. SERP analysis: what's ranking, the angle/format that wins, and the gap you can fill (do better/different).
  3. Outline: H1 + H2/H3 structure covering the intent and related subtopics/questions (People Also Ask).
  4. On-page: title tag, meta description, URL slug, primary + secondary keywords (used naturally), internal links, and a schema type if relevant.
  5. Conversion: the CTA/next step for readers who are ready.

Output

  • A brief: keyword + intent, SERP insight, outline (H1-H3), on-page elements, internal links, word-count guidance, and the CTA.

Guardrails

  • Write for the searcher first, the engine second - no keyword stuffing or thin AI content.
  • Verify keyword/volume claims with a real tool; mark assumptions [verify] (truth-telling).

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.