pi-agents-config: Skill for Claude Code

.pi/agent/skills/seo-content/SKILL.md

seo-content is a skill for Claude Code, Codex from niclejeune/pi-agents-config. It costs 49 tokens per session (1,482 once invoked), scanned A, a copy of seo-content, MIT.

A content review guide for checking website quality, readability, search visibility, and E-E-A-T—the evidence of first-hand experience, expertise, authority, and trust.

In plain words
What is it for?
Use it for content audits, readability checks, E-E-A-T reviews, and assessments of whether content is ready for citations by AI search tools.
Why use it?
It helps find weak, thin, poorly sourced, or hard-to-read content before it harms user confidence or search performance.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

This is niclejeune/pi-agents-config's own configuration. It tells Claude Code and Codex how to work on pi-agents-config itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything pi-agents-config configures →

Reuse

Borrowing it

Nothing to install: this file belongs to niclejeune/pi-agents-config. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/niclejeune/pi-agents-config/main/.pi/agent/skills/seo-content/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/niclejeune/pi-agents-config

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for seo-content

README.md
[![agentmods](https://agentmods.dev/badge/skills/niclejeune/pi-agents-config/seo-content/github.svg)](https://agentmods.dev/skills/niclejeune/pi-agents-config/seo-content)
Your own site
<a href="https://agentmods.dev/skills/niclejeune/pi-agents-config/seo-content"><img src="https://agentmods.dev/badge/skills/niclejeune/pi-agents-config/seo-content/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for seo-content

Your own site · 80×15
<a href="https://agentmods.dev/skills/niclejeune/pi-agents-config/seo-content"><img src="https://agentmods.dev/badge/skills/niclejeune/pi-agents-config/seo-content.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,482 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 88% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00049 $0.01482
Opus 5 $0.00024 $0.00741
Sonnet 5 $0.00010 $0.00296
Haiku 4.5 $0.00005 $0.00148

Measured 10d ago against content hash f9375cfc84e7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

seo-content scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

88% identical to seo-content — 31 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.pi/agent/skills/seo-content/SKILL.md · 162 lines

How it starts

The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Content Quality & E-E-A-T Analysis

E-E-A-T Framework (updated Sept 2025 QRG)

Read seo/references/eeat-framework.md for full criteria.

Experience (first-hand signals)

  • Original research, case studies, before/after results
  • Personal anecdotes, process documentation
  • Unique data, proprietary insights
  • Photos/videos from direct experience

Expertise

  • Author credentials, certifications, bio
  • Professional background relevant to topic
  • Technical depth appropriate for audience
  • Accurate, well-sourced claims

Authoritativeness

  • External citations, backlinks from authoritative sources
  • Brand mentions, industry recognition
  • Published in recognized outlets
  • Cited by other experts

Trustworthiness

  • Contact information, physical address
  • Privacy policy, terms of service
  • Customer testimonials, reviews
  • Date stamps, transparent corrections
  • Secure site (HTTPS)

Content Metrics

Word Count Analysis

Compare against page type minimums:

Page Type Minimum
Homepage 500
Service page 800
Blog post 1,500
Product page 300+ (400+ for complex products)
Location page 500-600

Important: These are topical coverage floors, not targets. Google has confirmed word count is NOT a direct ranking factor. The goal is comprehensive topical coverage — a 500-word page that thoroughly answers the query will outrank a 2,000-word page that doesn't. Use these as guidelines for adequate coverage depth, not rigid requirements.

Readability

  • Flesch Reading Ease: target 60-70 for general audience

Note: Flesch Reading Ease is a useful proxy for content accessibility but is NOT a direct Google ranking factor. John Mueller has confirmed Google does not use basic readability scores for ranking. Yoast deprioritized Flesch scores in v19.3. Use readability analysis as a content quality indicator, not as an SEO metric to optimize directly.

  • Grade level: match target audience
  • Sentence length: average 15-20 words
  • Paragraph length: 2-4 sentences

Read the full file on GitHub · 162 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 162 lines · 49 tokens per session scan A f9375cfc84e7

Subscribe to this mod's changes

seo-content is a skill published in the GitHub repository niclejeune/pi-agents-config (1 stars, last pushed 4mo ago), licensed MIT. It adds 49 tokens to every session and 1,482 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to seo-content, differing in 31 lines, and is treated as a copy.

Related

Other skills, from other repositories

exa-research-planner

Plan, draft, and execute Exa deep-research workflows. Use when the user wants staged research planning, cost-aware discovery before deep synthesis, or an explicit deep-research report. Also use when the user asks to refine a research question, compare options, explore a market or technical landscape, gather sources…

feniix/pi-extensions · 79 tokens

brpr

(devtools plugin) Create a branch, commit changes, push, and open a PR — or just commit+push+PR if already on a feature branch. Links related issues from GitHub or Linear based on project tracker config.

feniix/pi-extensions · 49 tokens

workspace-explorer

Explore and navigate Notion workspaces via MCP. Use when searching for pages, understanding database structure, finding content, creating or updating pages/databases, or managing Notion workspace content. Triggers when user asks about Notion, mentions Notion pages/databases, wants to find something in their wiki…

feniix/pi-extensions · 123 tokens

merge

Merge or squash-merge a pull request and report best-effort remote and local source-branch cleanup. Use when user says "merge this PR", "squash merge", "md", "smd", or anything about merging pull requests.

feniix/pi-extensions · 52 tokens

release

Automate the release process. Use when user says "cut a release", "new version", "bump version", "publish release", or anything about versioning and publishing.

feniix/pi-extensions · 38 tokens

setup-oauth

Guide the user through setting up Notion MCP with OAuth authentication.

feniix/pi-extensions · 16 tokens