New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Editorial Policy

by thedaviddias in thedaviddias/Front-End-Checklist

A skill your agent uses when auditing a blog, news site, or YMYL content site for trust signals, drafting editorial policy page content, or evaluating whether a site meets Google's quality rater…

MITAuto-check passed

Install Editorial Policy

skills CLI
$ npx skills add thedaviddias/Front-End-Checklist --skill editorial-policy -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install thedaviddias/Front-End-Checklist editorial-policy --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/editorial-policy .claude/skills/editorial-policy && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
editorial-policy
GitHub stars
74k
Token cost
~763 tokens
SKILL.md length
344 words
Files
2 (incl. references)
Skills in repo
390
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when auditing a blog, news site, or YMYL content site for trust signals, drafting editorial policy page content, or evaluating whether a site meets Google's quality rater…

  • Works in 4 steps: Create a page at /editorial-policy (or… → Include these sections → Link to this page from your About page,… → …
  • Auditing a blog
  • SKILL.md covers Quick Reference, Check, Fix and Explain, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Editorial Policy is an agent skill from thedaviddias/Front-End-Checklist. Use when auditing a blog, news site, or YMYL content site for trust signals, drafting editorial policy page content, or evaluating whether a site meets Google's quality rater trustworthiness criteria.

Its SKILL.md is about 760 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/rule.md`).

The repository describes itself as: 🗂 The essential checklist for modern web development, for humans and AI agents. The licence is MIT.

When your agent uses it

  • Auditing a blog
  • YMYL content site for trust signals
  • Drafting editorial policy page content
  • Evaluating whether a site meets Googles quality rater trustworthiness criteria

Example prompts

  • “/editorial-policy”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Create a page at /editorial-policy (or /about/editorial-standards).
  2. Include these sections
  3. Link to this page from your About page, site footer, and individual article bylines.
  4. Name specific authors with credentials rather than using "Editorial Team" as a generic author.

What it can do on your machine

Read from SKILL.md and the folder at commit e8d14d0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • frontendchecklist.io

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Editorial Policy loads about 763 tokens when it runs, and up to ~2k if it reads all its reference files. Until then it costs about 54 tokens; SKILL.md has 344 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~54
When it runs · the whole SKILL.md, loaded when a task matches
~763
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from thedaviddias/Front-End-Checklist at commit e8d14d0, republished under its MIT licence (© thedaviddias). 344 words, ~763 tokens.

Download SKILL.mdSave it as .claude/skills/editorial-policy/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
editorial-policy
description
Use when auditing a blog, news site, or YMYL content site for trust signals, drafting editorial policy page content, or evaluating whether a site meets Google's quality rater trustworthiness criteria.
metadata.category
seo
metadata.priority
medium
metadata.difficulty
intermediate
metadata.estimatedTime
10
metadata.source
frontendchecklist.io
metadata.url
https://frontendchecklist.io/rules/seo/editorial-policy

Publish an editorial policy page

Google's E-E-A-T framework rates sites on Expertise, Authoritativeness, and Trustworthiness. Quality raters look for editorial standards pages as evidence of a trustworthy publication. Sites without visible editorial policies — especially YMYL sites — receive lower trust ratings, which suppresses search rankings.

Quick Reference

  • Publish a dedicated editorial policy page explaining how content is researched, written, reviewed, and updated
  • Link to the editorial policy from your About page and from individual articles (byline or footer)
  • Include information on author qualifications, fact-checking processes, and correction policies

Check

Check if the site has a publicly accessible editorial policy page (commonly at /editorial-policy, /about/editorial-standards, or linked from the About page). Verify it covers: (1) how topics are chosen, (2) author qualifications, (3) fact-checking or review process, (4) how corrections are handled, and (5) conflicts of interest or funding disclosures.

Fix

  1. Create a page at /editorial-policy (or /about/editorial-standards).
  2. Include these sections:
    • Mission: what topics you cover and why
    • Author standards: credentials, expertise required of contributors
    • Research and fact-checking: sources used, review by subject matter experts
    • Update policy: how often content is reviewed, how errors are corrected
    • Conflict of interest: advertising, affiliate relationships, funding sources
  3. Link to this page from your About page, site footer, and individual article bylines.
  4. Name specific authors with credentials rather than using "Editorial Team" as a generic author.

Explain

Google's Search Quality Rater Guidelines specifically look for editorial standards as part of evaluating a site's Trustworthiness. For YMYL topics especially, the absence of an editorial policy is a clear signal to quality raters that the site cannot be trusted to publish accurate, expert-reviewed content, leading to lower quality ratings and reduced search visibility.

Code Review

Check the site's footer links, About page, and individual article templates for a link to an editorial policy page. Verify the editorial policy URL returns a 200 status code and that the page contains substantive content — not just a boilerplate paragraph — covering research methodology, author qualifications, and correction policies.

For full implementation details, code examples, and framework-specific guidance, see references/rule.md.

Rule page: https://frontendchecklist.io/rules/seo/editorial-policy

© thedaviddias, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/editorial-policy of thedaviddias/Front-End-Checklist.

  • SKILL.md
  • references/rule.md

Open the folder on GitHubat commit e8d14d0

Compare with similar skills

Editorial Policy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Editorial Policy compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Editorial Policy this skillthedaviddias/Front-End-Checklist74k—~763Automated safety check: PassMIT
OmniRoute Audit and Policy CLIdiegosouzapw/OmniRoute75k—~733Automated safety check: PassMIT
Blog AuditAgriciDaniel/claude-blog2.3k—~2.4kAutomated safety check: NotesMIT
Implementing Policy As Code With Open Policy Agentmukul975/Anthropic-Cybersecurity-Skills34k—~2.6kAutomated safety check: NotesApache-2.0
Blog Locale AuditAgriciDaniel/claude-blog2.3k1 repos~2.1kAutomated safety check: PassMIT
BlogAgriciDaniel/claude-blog2.3k—~6.2kAutomated safety check: PassMIT

Similar skills

  • OmniRoute Audit and Policy CLI

    diegosouzapw/OmniRoute

    Command reference for omniroute's audit, logs, policy and telemetry commands: search and export audit trails, manage access policies and review request history for compliance work.

    75k GitHub stars~733 tokensUpdated today
    SecurityAuto-check passed

  • Blog Audit

    AgriciDaniel/claude-blog

    Full-site blog health assessment scanning all blog files for quality scores, orphan pages, topic cannibalization, stale content, and AI citation readiness.

    2.3k GitHub stars~2.4k tokensUpdated 2 days ago
    Marketing & SEOAuto-check: notes

  • Implementing Policy As Code With Open Policy Agent

    mukul975/Anthropic-Cybersecurity-Skills

    Implements policy-as-code enforcement with Open Policy Agent (OPA) and Gatekeeper for Kubernetes and CI/CD pipelines, covering writing Rego policies, deploying OPA Gatekeeper as a Kubernetes…

    34k GitHub stars~2.6k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check: notes

  • Blog Locale Audit

    AgriciDaniel/claude-blog

    Audit a directory of multilingual blog content for completeness, consistency, hreflang correctness, meta-tag parity, and freshness.

    2.3k GitHub starsUsed in 1 repo~2.1k tokens
    Writing & ContentAuto-check passed

  • Blog

    AgriciDaniel/claude-blog

    Full-lifecycle blog engine with 31 sub-skills, 12 templates, 100-point scoring, and 5 agents.

    2.3k GitHub stars~6.2k tokensUpdated 2 days ago
    Writing & ContentAuto-check passed

  • Blog

    AgriciDaniel/claude-blog

    Full-lifecycle blog engine with 31 sub-skills, 12 content templates, 5-category 100-point scoring, and 5 specialized agents.

    2.3k GitHub starsUsed in 1 repo~8.6k tokens
    Writing & ContentAuto-check: warnings

More from thedaviddias/Front-End-Checklist

All 390 skills in this repo

  • Content Dates Audit

    thedaviddias/Front-End-Checklist

    Audits article and blog pages for visible publish dates, Article JSON-LD with datePublished and dateModified, and Open Graph time tags, then fixes what is missing.

    74k GitHub stars~691 tokensUpdated 4 days ago
    Auto-check passed

  • FAQPage Schema Markup

    thedaviddias/Front-End-Checklist

    Adds, checks and fixes FAQPage JSON-LD on pages with visible question-and-answer sections so it matches what readers see and can qualify for rich results.

    74k GitHub stars~774 tokensUpdated 4 days ago
    Auto-check passed

  • Favicon Audit and Setup

    thedaviddias/Front-End-Checklist

    Checks that a site's favicon is linked, reachable and large enough for Google search results, and sets up ICO, SVG and Apple touch icon files when they are missing.

    74k GitHub stars~731 tokensUpdated 4 days ago
    Auto-check passed

  • Content Freshness Signals

    thedaviddias/Front-End-Checklist

    Audits article pages for freshness signals, covering the Last-Modified header, Article JSON-LD dateModified and a visible last-updated date, and fixes mismatches.

    74k GitHub stars~741 tokensUpdated 4 days ago
    Auto-check passed

  • Geo Meta Tags Audit

    thedaviddias/Front-End-Checklist

    Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google).

    74k GitHub stars~763 tokensUpdated 4 days ago
    Auto-check passed

  • Improve a Front-End Checklist Rule

    thedaviddias/Front-End-Checklist

    Scores and rewrites a Front-End Checklist rule MDX file against a scored quality rubric, replacing generic stub prompts with specific, actionable ones.

    74k GitHub stars~1.3k tokensUpdated 4 days ago
    Auto-check passed

Questions about Editorial Policy

What does Editorial Policy do?

A skill your agent uses when auditing a blog, news site, or YMYL content site for trust signals, drafting editorial policy page content, or evaluating whether a site meets Google's quality rater…. Editorial Policy is an agent skill from thedaviddias/Front-End-Checklist. Use when auditing a blog, news site, or YMYL content site for trust signals, drafting editorial policy page content, or evaluating whether a site meets Google's quality rater trustworthiness criteria.

When should I use Editorial Policy?

Editorial Policy fits situations like: auditing a blog; YMYL content site for trust signals; drafting editorial policy page content; evaluating whether a site meets Googles quality rater trustworthiness criteria.

How do I install Editorial Policy in Claude Code?

Run `npx skills add thedaviddias/Front-End-Checklist --skill editorial-policy -a claude-code`. Or copy the skill folder (skills/editorial-policy in thedaviddias/Front-End-Checklist) into .claude/skills/editorial-policy in your project. Claude Code loads it when a task matches its description.

How do I install Editorial Policy in Codex?

Run `npx skills add thedaviddias/Front-End-Checklist --skill editorial-policy -a codex`. Or copy the skill folder (skills/editorial-policy in thedaviddias/Front-End-Checklist) into .agents/skills/editorial-policy in your project. Codex loads it when a task matches its description.

Can I use Editorial Policy in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add thedaviddias/Front-End-Checklist --skill editorial-policy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/editorial-policy, .gemini/skills/editorial-policy, .github/skills/editorial-policy and .opencode/skills/editorial-policy in your project.

What does Editorial Policy need to run?

SKILL.md names no scripts, command-line tools or credentials: Editorial Policy is instructions for the agent only.

Does Editorial Policy access the network?

SKILL.md names 1 domain. As links in the text: frontendchecklist.io. This is read from the text; nothing was executed.

Is Editorial Policy safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Editorial Policy use?

Editorial Policy is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Editorial Policy use?

About 763 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.2k tokens, read only when the agent opens those files.

What are the alternatives to Editorial Policy?

Skills that share tags, products or a category with Editorial Policy: OmniRoute Audit and Policy CLI (diegosouzapw/OmniRoute, 75k stars), Blog Audit (AgriciDaniel/claude-blog, 2.3k stars), Implementing Policy As Code With Open Policy Agent (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Blog Locale Audit (AgriciDaniel/claude-blog, 2.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Editorial Policy?

thedaviddias (a GitHub user) maintains it in thedaviddias/Front-End-Checklist, which has 74,421 GitHub stars. The repository holds 390 skills in this directory. The repository was last updated on October 6, 2026.

Source: thedaviddias/Front-End-Checklist on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.