agentleFS
45ck45ck/marketing-product-skills/.agents/skills/seo-geo-content-brief/SKILL.md

seo-geo-content-brief

Skill3 starsChanged 8 months agoMITView on GitHub

Create a content brief optimized for search intent, answer-engine visibility, and product-led conversion.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    Use this skill when the user wants a high-quality content brief for blog, landing page, comparison page, feature page, or glossary content …

    line 9
  2. Distinctive:

    If the keyword is not provided, infer a topic cluster from the problem the user wants to solve.

    line 36
  3. Distinctive:

    Use clear entity coverage, definitions, comparisons, and direct answers.

    line 42
  4. Distinctive:

    Avoid fluff and generic introductions.

    line 45
  5. Very specific:

    Use H1/H2/H3 structure.

    line 114

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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 / GEO Content Brief

Use this skill when the user wants a high-quality content brief for blog, landing page, comparison page, feature page, or glossary content that should rank and also convert.

What this skill must produce

Always produce:

  1. Content objective
  2. Audience and intent
  3. Primary query / topic cluster
  4. Outline
  5. Evidence / proof needs
  6. Internal linking plan
  7. Conversion plan
  8. SERP / answer-engine risks
  9. Final brief

Inputs to gather

Use:

  • target keyword or topic
  • product category
  • audience
  • stage of funnel
  • desired CTA
  • competing pages if given
  • brand voice rules if given

If the keyword is not provided, infer a topic cluster from the problem the user wants to solve.

Working rules

  • Optimize for user intent first, not keyword stuffing.
  • Make the brief useful for both traditional search and AI answer engines.
  • Use clear entity coverage, definitions, comparisons, and direct answers.
  • Include proof and examples.
  • Include where the product should appear naturally in the content.
  • Avoid fluff and generic introductions.

Step-by-step method

Step 1: identify search intent

Classify the intent:

  • informational
  • commercial investigation
  • comparison
  • transactional
  • navigational

Step 2: identify the reader

Define:

  • ICP / persona
  • awareness level
  • problem urgency
  • objections

Step 3: define the content angle

State what the page will uniquely do better than commodity content.

Step 4: create the outline

Build a logical structure with:

  • direct answer near the top
  • definitions where needed
  • comparison / framework sections
  • examples
  • FAQs
  • CTA placement

Step 5: identify proof needs

List:

  • stats
  • screenshots
  • examples
  • customer stories
  • product visuals
  • quotes

Step 6: plan linking and conversion

Specify:

  • internal links
  • product links
  • soft CTAs
  • hard CTA
  • downloadable assets if relevant

Output structure

Content objective

  • Page type:
  • Funnel stage:
  • Goal:
  • Primary CTA:

Audience and intent

  • Reader:
  • Primary intent:
  • Secondary intent:
  • Main objections:

Primary query / topic cluster

  • Primary topic:
  • Supporting subtopics:
  • Questions to answer explicitly:
  • Entities to mention naturally:

Outline

Use H1/H2/H3 structure.

Evidence / proof needs

SectionProof neededWhy

Internal linking plan

Link targetWhy

Conversion plan

  • Soft CTA:
  • Hard CTA:
  • Best CTA placement:
  • Product mention strategy:

SERP / answer-engine risks

  • What generic competitors will do:
  • Where this brief may be too broad:
  • Where proof is thin:
  • What should be added for answer-engine usefulness:

Final brief

Summarize the page in 1-2 paragraphs for the writer.

Extra rules

For comparison content:

  • include fair comparison criteria
  • state who each option is best for
  • avoid dishonest dunking

For glossary / educational content:

  • define terms cleanly
  • explain why the concept matters
  • tie naturally to the product or category

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.