How to use the Editorial Policy Page Auditor agent skill

What does the editorial-policy skill make the agent do?

The skill is built around a checklist for editorial policy pages. Its description says it applies when you audit a blog, news site or YMYL (health, finance, legal) content site for trust signals, draft editorial policy page content, or evaluate whether a site meets Google's quality rater trustworthiness criteria.

Once installed, the agent can check whether a site has a publicly accessible editorial policy page, commonly at /editorial-policy or /about/editorial-standards, or linked from the About page. It then checks whether that page covers how topics are chosen, author qualifications, the fact-checking or review process, how corrections are handled, and conflicts of interest or funding disclosures. It can also draft a policy page from a set of suggested sections: mission, author standards, research and fact-checking, update policy, and conflict of interest.

How do you install the editorial-policy skill?

There are two routes. The first is manual: download the skill ZIP from the page where you found this guide, then unzip it into your personal skills folder at ~/.claude/skills/, or into a project's .claude/skills/ folder if you want the skill to apply only to that project.

The second route is through the Claude apps. Upload the ZIP under Settings → Capabilities → Skills.

• Personal install: unzip into ~/.claude/skills/
• Project install: unzip into the project's .claude/skills/ folder
• Claude apps: upload the ZIP under Settings → Capabilities → Skills

How do you trigger the skill with natural requests?

You do not need a special command. Describe the task in ordinary language, and the agent will use the skill when your request matches its description. The skill's description mentions auditing blogs, news sites and YMYL sites for trust signals, drafting editorial policy page content, and checking against Google's quality rater trustworthiness criteria, so requests that use those ideas are the most likely to match.

Be specific about the site and the goal. Naming the page you want reviewed, or pasting the policy text, gives the agent more to work with.

• Check whether our site has a visible editorial standards page and what it is missing.
• Draft an editorial policy page for our health information blog, covering author credentials, fact-checking and corrections.
• Review this About page and tell me whether it links to an editorial policy and mentions conflicts of interest.
• Evaluate our finance news site against the trustworthiness criteria used by Google's quality raters.

What does the skill check and what should you expect from it?

The skill's checks come from a short list of expectations. A good policy page explains how content is researched, written, reviewed and updated. Author pages should name specific people with credentials instead of a generic 'Editorial Team'. Articles should link to the policy from their byline or footer, and the About page and site footer should link to it too.

The skill also describes a code review step: check footer links, the About page and article templates for a link to the policy, confirm the URL returns a 200 status code, and confirm the page has substantive content rather than a boilerplate paragraph. The skill declares that it does not use the network, so any live check of a URL depends on what the agent can already access in your setup.

The skill frames its advice around Google's E-E-A-T criteria. Treat its statements about how Google's raters judge sites as general guidance. The files do not let you verify them, and the skill does not change search rankings by itself.

What do you need before you start, and what are the safety notes?

The skill lists no requirements. It does not run scripts and does not use the network. Its files are SKILL.md and references/rule.md, which are plain instructions and reference material. Read them before installing if your organisation reviews skills, as with any third-party instruction set.

The skill is released under the MIT licence, as listed on its source page.

• Requires: nothing listed
• Runs scripts: no
• Uses network: no
• Files: SKILL.md and references/rule.md

What tips make the results more useful?

Give the agent the real content to review. A policy page can only be judged on the text the agent can see. Ask for one part at a time if the page is long, such as only the corrections section. When drafting, replace the example details with your real authors, sources and funding information, since the skill is a structure, not a source of facts about your organisation.

• Paste the actual policy text or give the agent the page it should review.
• Name real authors and credentials instead of placeholders.
• Confirm every factual claim in a draft before publishing it.
• Review the output against your own editorial process, not only the checklist.