agentleFS
Ormus-SolutionsOrmus-Solutions/LibreGEO-Claude-Code/skills/geo-content/SKILL.md

geo-content

Skill1 starsChanged 43 days agoMITView on GitHub

E-E-A-T and content quality assessment for AI citability: scores experience, expertise, authoritativeness, and trustworthiness, plus word count, readability, structure, freshness, topical authority, and low-quality AI content signals, and writes GEO-CONTENT-ANALYSIS.md. Use when the user wants a content quality review of a page or blog, or asks whether their content is credible enough to be cited.

10 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

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

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 0

    Distinctive

    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:

    Check for low-quality AI content signals (see signals.md)

    line 24

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

GEO content quality and E-E-A-T assessment

Purpose

AI search platforms do not just find content — they evaluate whether content deserves to be cited. The primary framework for this evaluation is E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness), which per Google's December 2025 Quality Rater Guidelines update now applies to ALL competitive queries, not just YMYL topics. Content that scores high on E-E-A-T is dramatically more likely to be cited by AI platforms.

Two lenses:

  1. E-E-A-T signals — does the content demonstrate real expertise and trust?
  2. AI citability — is the content structured so AI platforms can extract and cite specific claims?

Operational protocol

  1. Fetch the target page(s) — homepage, key blog posts, service/product pages
  2. Evaluate E-E-A-T across the 4 dimensions (25 points each) using rubrics in signals.md
  3. Assess content quality metrics (word count, readability, paragraph/heading structure, internal linking) using scoring.md
  4. Check for low-quality AI content signals (see signals.md)
  5. Evaluate content freshness and topical authority modifier (scoring.md)
  6. Score and generate GEO-CONTENT-ANALYSIS.md using the template in templates.md

References

  • signals.md — per-signal scoring rubrics for all 4 E-E-A-T dimensions, plus AI content quality signals (low/high)
  • scoring.md — word count benchmarks, readability, paragraph/heading/linking rules, freshness scoring, topical authority modifier
  • templates.md — GEO-CONTENT-ANALYSIS.md output template

Final scoring (0-100)

ComponentWeightMax points
Experience25%25
Expertise25%25
Authoritativeness25%25
Trustworthiness25%25
Subtotal100
Topical Authority Modifier+10 to -5
Final ScoreCapped at 100

Interpretation

  • 85-100: Exceptional — strong AI citation candidate across platforms
  • 70-84: Good — solid foundation, specific improvements will increase citability
  • 55-69: Average — multiple E-E-A-T gaps reducing AI visibility
  • 40-54: Below Average — significant content quality and trust issues
  • 0-39: Poor — fundamental content strategy overhaul needed

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.