agentleFS
khadinakbarlabskhadinakbarlabs/vibeseo-plugin/skills/content-brief/SKILL.md

content-brief

Skill0 starsChanged 33 days agoMITView on GitHub

Create a SERP-informed SEO content brief, article outline, landing-page brief, title/meta options, or a reviewed first draft. Use before writing a new SEO page, when asked what an article should cover, or to turn a selected keyword into useful content. Grounds suggestions in actual or supplied research and requires an original contribution and factual review.

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use competitor-gap, serp-analysis and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • DarynaRodriguezSkill

    competitor-gap

    Finds the terms rivals rank for and the site does not, confirms who the real organic competitors are, and returns a gap table split into terms to win, terms underperforming, and terms to concede.

    Also in 4 projects that use this

  • opencueSkill

    serp-analysis

    Use when the user asks to "analyze SERPs"; reviews ranking factors, features, intent, AI Overviews, and snippets. SERP分析/搜索结果

    Also in 3 projects that use this

  • indranilbanerjeeSkill

    client-proposal

    Draft a client proposal or RFP response: scope, deliverables, KPIs, pricing tiers. \"respond to this RFP\"

    Also in 3 projects that use this

  • akii-technologies-ltdSkill

    internal-linking

    Analyze and improve internal linking strategy. Use when the user asks about "internal links", "link structure", "site architecture", "link strategy", "orphan pages", "link equity", "page authority distribution", "anchor text", "topical clusters", "siloing", or wants to improve how pages connect.

    Also in 3 projects that use this

  • akii-technologies-ltdSkill

    keyword-clustering

    Cluster and organize keywords into topical groups for SEO. Use when the user asks to "cluster keywords", "group keywords", "organize keywords", "keyword mapping", "topic clusters", "keyword grouping", "build a content plan", "pillar pages", "topical authority", "semantic clustering", or pastes a list of keywords.

    Also in 3 projects that use this

  • silvainfmSkill

    schema-markup

    When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," or "breadcrumb schema." For broader SEO issues, see seo-audit.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 1

    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:

    Read shared rules. Use CLI guidance only for approved live collection.

    line 8

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

Content brief and optional draft

Read shared rules. Use CLI guidance only for approved live collection.

  1. Confirm the chosen keyword, site/audience, conversion goal, language/country and page type from existing context. For an existing page, use content-refresh. Check verified page inventory for overlapping intent before proposing another URL.
  2. Use supplied research or a bounded scrape-google-serp sample. Record capture date, locale, query, organic ranks and features. Review the actual top pages if authorized access exists. A title/snippet-only sample supports a preliminary brief, not claims about a page's full headings or factual depth. Never claim to have read pages you haven't read.
  3. Identify the searcher's job, likely format and necessary questions. Describe common coverage and a specific addition this site can credibly provide: an original dataset, first-hand example, tested procedure, usable checklist, worked comparison or expert explanation. If there is no supportable contribution, prepare a research request rather than another generic article.
  4. Assemble the brief template: intent, proposed URL, primary/secondary topics, 2–3 title options, H1, H2/H3 outline with section purpose, answer blocks where useful, facts/sources needed, original contribution, verified internal links or explicitly proposed candidates, CTA and author/reviewer needs.
  5. Write a concise descriptive title and accurate summary; preview likely truncation. Character lengths are editorial checks, not guaranteed Google limits. Keyword use must read naturally. Don't chase a fixed keyword density, competitor word count or guaranteed E-E-A-T score. Suggest structured data only when it matches content actually present and its current eligibility can be checked.
  6. If the user requests a draft, write it from the approved brief and provided/verifiable facts. Mark unresolved facts for review; don't invent statistics, testimonials, quotes, credentials, results or product capabilities. Give it a human, direct voice with useful examples. Cite sources rather than reproduce competitor passages.
  7. Perform an editorial pass: answers the actual intent, contributes new value, factual claims supported, internal URLs verified, product promises accurate, and no unapproved publication. Finish with a review-ready brief/draft and missing evidence.

Writing a draft does not authorize publishing. Do not invoke a CMS or create new bulk pages automatically. Relevant source guidance: Google people-first content.

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.