Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/inhouseseo-eeat-audit
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: security, agent-building
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/eeat-audit
What's inside
- Skill name
eeat-audit- Description
- Use when auditing a page for E-E-A-T signals. The agent reads the page and scores Experience, Expertise, Authoritativeness, and Trustworthiness — then tells you exactly what to add to each dimension.
- License
- Apache-2.0
- Instructions
- 172 lines in SKILL.md · view on GitHub
Files (12)
- SKILL.md
- author-schema-templates.md · references/
- about-pages.md · references/content-types/
- case-studies.md · references/content-types/
- pricing-pages.md · references/content-types/
- product-reviews.md · references/content-types/
- service-pages.md · references/content-types/
- thought-leadership.md · references/content-types/
- eeat-signal-embedding.md · references/
- experience-detection-playbook.md · references/
- fastest-eeat-wins.md · references/
- ymyl-scoring-rubric.md · references/
SKILL.md (first lines)
# E-E-A-T Audit
Scores a page on Experience, Expertise, Authoritativeness, and Trustworthiness — the four signals Google's quality raters use to evaluate content. Tells you what's missing and how to add it.
Real E-E-A-T is demonstrated, not declared. An author bio is table stakes. What matters is whether the content *feels* like it was written by someone who has actually done the thing.
## Input
**URL of the page to audit**. If the fetch fails, ask the user to paste the content directly.
## Role
You are a senior content quality evaluator with 10+ years reading for Google's quality rater framework. You can tell within 30 seconds of reading whether an author has done the thing they're writing about.
## Step 1: Read the Page
Fetch and read the full rendered page. Note everything that could be an E-E-A-T signal:
- Author name, bio, credentials
- Byline with publication date
- First-person language ("I tried...", "we found...", "when I was at...")
- Specific anecdotes, names, numbers, dates
- Original photos, screenshots, diagrams
- Quoted sources, linked references
- Schema markup (Person, Author, Organization)
- About page linked from the article
- External references to the author or publication
## Step 2: Score Each Dimension (1-10)
### Experience (the most underrated E-E-A-T factor)
**What you're looking for:** evidence the author has DONE the thing, not just researched it.
**Strong signals (8-10):**
- First-person observations with specific details
- "When I tried this, X happened"
- Original photos/screenshots from the author's own work
- Failure stories with specific lessons
- Details only hands-on experience would know (the "smell test")
- A story that reveals workflow, not just outcomes
**Weak signals (4-6):**
- Generic advice that anyone could write after 30 minutes of research
- Third-person narration of other people's case studies
- Examples that feel plucked from Google
- "According to studies..." without identifying which ones
**Absent (1-3):**
- No first-person anywhere
- No specific stories
- No details beyond what's already on the top 10 ranking pages
### Expertise
**What you're looking for:** accurate facts and depth beyond surface level. Verify the claims you can; score the rest on sourcing quality and say which claims you couldn't check — don't assert accuracy you haven't confirmed.
**Strong signals:**
- Every factual claim is accurate and verifiable
- Numbers cited with primary sources (original research, not "studies show")
- Technical details correctly used (terminology, processes, edge cases)
- Willingness to disagree with common advice when the author has a reason
- Depth beyond what a smart generalist could produce in 30 minutes
**Weak signals:**
- Accurate but shallow
- Secondary sources cited (blog posts citing blog posts)
- Common advice repeated without critique
**Absent:**
- Factual errors
- Outdated information presented as current
- Surface-level "what Google says" summary
### Authoritativeness
**What you're looking for:** does this content and author belong in the conversation?
**Strong signals:**
- Page is part of a broader topical cluster on the domain
- Author expertise is verifiable beyond a bio paragraph (LinkedIn, talks, books, citations elsewhere)
- External sites cite this page or author
- Clear track record on this specific topic
**Weak signals:**
- Isolated page on a broad topic site
- Generic author with no verifiable specialty
- No external validation
**Absent:**
- Random blog post with no author attribution
- Site has no topical focus
- No internal linking cluster
### Trustworthiness
**What you're looking for:** transparency and honesty.
**Strong signals:**
- Transparent about limitations ("this didn't work when X")
- Discloses conflicts of interest (affiliate links, paid placements)
- Methodology explained
- Willingness to recommend alternatives, even competitors
- Factually accurate throughout
- Recent publish/update date for time-sensitive topics
**Weak signals:**
- Feels like an advertorial but doesn't disclose
- Hides limitations
- Methodology unclear
**Absent (1-3):**
- Factual errors
- Affiliate-driven content without disclosure
- Misleading claims
- Outdated information on a time-sensitive topic
## Step 3: Output
### E-E-A-T ScorecardFrom inhouseseo/superseo-skills, Apache-2.0.
More from inhouseseo/superseo-skills
- 0.761score
content-brief
inhouseseo
Use when planning a new article.
SkillBFreshness: B★ 366Claude Code +9 - 0.761score
expert-interview
inhouseseo
Use when extracting first-party expertise from a subject-matter expert before writing content.
SkillBFreshness: B★ 366Claude Code +9 - 0.761score
featured-snippet-optimizer
inhouseseo
Use when you want to win a featured snippet for a keyword you already rank for.
SkillBFreshness: B★ 366Claude Code +9 - 0.761score
improve-content
inhouseseo
Use when rewriting or refreshing an existing page that's underperforming.
SkillBFreshness: B★ 366Claude Code +9 - 0.761score
keyword-deep-dive
inhouseseo
Use when planning to rank for a specific keyword.
SkillBFreshness: B★ 366Claude Code +9 - 0.761score
linkbuilding
inhouseseo
Use when planning link acquisition.
SkillBFreshness: B★ 366Claude Code +9 - 0.761score
page-audit
inhouseseo
Use when auditing a specific page's SEO performance, content quality, and competitive position.
SkillBFreshness: B★ 366Claude Code +9 - 0.761score
semantic-gap-analysis
inhouseseo
Use when a page ranks for a keyword but isn't in the top 3 and you want to know exactly what's missing.
SkillBFreshness: B★ 366Claude Code +9 - 0.761score
topic-cluster-planning
inhouseseo
Use when planning a topic cluster (hub + spokes) for a new content area.
SkillBFreshness: B★ 366Claude Code +9 - 0.761score
write-content
inhouseseo
Use when writing a complete SEO article.
SkillBFreshness: B★ 366Claude Code +9
Signals
- Stars
- 366
- Forks
- 45
- Open issues
- 1
- Last commit (this folder)
- Sep 3, 2026 (1 month ago)
- Last release
- Sep 3, 2026 (1 month ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- Apache-2.0
- Repository
- github.com/inhouseseo/superseo-skills
- Website
- inhouseseo.ai
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from inhouseseo
- 0.761score
content-brief
inhouseseo
Use when planning a new article.
SkillBFreshness: B★ 366Claude Code +9 - 0.761score
expert-interview
inhouseseo
Use when extracting first-party expertise from a subject-matter expert before writing content.
SkillBFreshness: B★ 366Claude Code +9 - 0.761score
featured-snippet-optimizer
inhouseseo
Use when you want to win a featured snippet for a keyword you already rank for.
SkillBFreshness: B★ 366Claude Code +9 - 0.761score
improve-content
inhouseseo
Use when rewriting or refreshing an existing page that's underperforming.
SkillBFreshness: B★ 366Claude Code +9 - 0.761score
keyword-deep-dive
inhouseseo
Use when planning to rank for a specific keyword.
SkillBFreshness: B★ 366Claude Code +9 - 0.761score
linkbuilding
inhouseseo
Use when planning link acquisition.
SkillBFreshness: B★ 366Claude Code +9
Cite this page
eeat-audit skill. Agent Mart. https://agentmart.dev/skills/inhouseseo-eeat-audit (last updated 2026-10-24)