agentleFS
oegeyilmaz9oegeyilmaz9/seo-aeo-geo-ultimate/skills/seo-authority/SKILL.md

seo-authority

Skill6 starsChanged 3 months agoApache-2.0View on GitHub

Use when auditing backlinks, referring domains, source citations, brand mentions, unlinked mentions, linkable assets, digital PR evidence, or off-site source landscapes from authorized first-party, Bing, vendor, or public evidence; preserve vendor metric definitions, detect manipulative risk, and never treat a proprietary authority score as universal truth or recommend link schemes.

1 other project uses 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. Very specific:

    Read markdown-delivery-contract.md for every task.

    line 10
  2. Distinctive:

    Read authority-evidence-protocol.md before a formal audit.

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Authority and Source Landscape

Markdown delivery contract

Read markdown-delivery-contract.md for every task. Write a substantive .md document for every material work step and register its direct destination in the work index.md. For public-site work, apply the owner-required Markdown discovery profile across the full eligible inventory; preserve native standards and immutable evidence formats.

Lane outputs: authority-review.md; source-landscape.md (combine small related steps with stable section links). Record source ownership, expertise, referring evidence and claims directly in Markdown handoffs; distinguish owned citations from independent endorsement. Keep paid/organic/affiliate relationships explicit and no fabricated authority metrics.

Audit off-site evidence that helps users and systems verify an entity: genuine links, mentions, citations, source coverage, and risk. This skill does not manufacture authority.

Read authority-evidence-protocol.md before a formal audit.

Procedure

  1. Define entity, domains, markets/locales, comparison scope, authorized data sources, time window, and the decision to make.
  2. Preserve each link/mention row with source URL/domain, target URL/entity, anchor or mention text, first/last seen date when supplied, link attributes, source type, collection method, and limitations.
  3. Normalize URLs without discarding raw values. Separate backlinks, citations, unlinked mentions, syndication, scraper copies, social/profile links, and self-controlled properties.
  4. Evaluate source relevance, editorial independence, claim support, topical/locale fit, target-page usefulness, and visible context. Keep proprietary authority/risk/traffic metrics labeled with vendor and date.
  5. Identify broken earned links, incorrect entity facts, missing first-party evidence, unsupported claims, spam patterns, paid/sponsored disclosure, and link-scheme risk.
  6. Recommend source-worthy first-party assets, corrections, reclamation, documentation, partnerships, or editorial outreach only when truthful and policy-safe. Do not prescribe volume quotas or paid/manipulative links.
  7. Route entity/citation suitability to seo-geo, competitor-page copy to seo-competitor-pages, content assets to seo-content, and internal links to seo-architecture.
  8. Package findings as SEO Findings 1.1.0 with backlink_profile, content_set, web_page, or site targets and authority, entity, content, or policy categories.

Formal evidence handoff

Package only supported observations as SEO Findings 1.1.0. Let <suite-root> mean ${CLAUDE_PLUGIN_ROOT} in Claude Code. In Codex, read .seo-suite-runtime.json beside this SKILL.md when present and use its suite_root value; otherwise use the absolute repository checkout, then run python "<suite-root>/scripts/validate_seo_findings.py" validate-findings <bundle>/seo-findings.json --bundle <bundle>. Keep the handoff provisional until this command passes.

Output

Return the source and scope, normalized link/mention inventory, source-quality and claim-support observations, risk patterns, evidence gaps, owners, verification, and limitations. Never collapse the result into a universal domain-authority score.

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.