CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

editorial-policy

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.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable audit/fix skill with excellent progressive disclosure to a real reference file. Its main weakness is redundancy: the Explain section and the Check/Code Review pair largely repeat content, and the body defers all concrete examples to the reference without a single inline snippet.

Suggestions

Cut or merge the 'Explain' section — it restates the E-E-A-T/quality-rater rationale already covered in the opening paragraph — or fold one clarifying sentence into the intro.

Merge 'Check' and 'Code Review' into a single verification section; both cover the same existence/coverage checks, differing only in the 200-status detail.

Inline one short concrete example in 'Fix' (e.g., a footer link snippet or one sample policy-section sentence) so the body is self-sufficient for the common case, with references/rule.md for the rest.

DimensionReasoningScore

Conciseness

Mostly efficient with actionable sections, but there is real duplication: the 'Explain' section restates the E-E-A-T/quality-rater rationale already given in the opening paragraph, and 'Code Review' overlaps heavily with 'Check' (both verify an editorial policy page exists and covers the same items). Fits 'mostly efficient but includes some unnecessary explanation or could be tightened'; not level 4 because two sections could be cut or merged without losing information.

3 / 5

Actionability

Concrete, specific guidance throughout: exact URL paths ('/editorial-policy', '/about/editorial-standards'), a five-item verification checklist, a numbered fix list enumerating required policy sections, and a concrete verification step ('returns a 200 status code'). Falls short of level 5 because no sample policy-page wording or markup is inline — the code examples live only in references/rule.md, leaving the body's fix steps high-level.

4 / 5

Workflow Clarity

The Check → Fix → Code Review structure forms a coherent audit-fix-verify sequence with an explicit validation checkpoint ('Verify the editorial policy URL returns a 200 status code and that the page contains substantive content'). Not level 5 because the loop back from a failed check to the fix steps is implicit rather than an explicit feedback loop; not level 3 since a concrete verification step is present.

4 / 5

Progressive Disclosure

The ~50-line body is a clear overview with well-organized sections and a single, well-signaled, one-level-deep pointer — 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — and that file actually exists in the bundle with the code examples it promises. Matches the clear-overview anchor exactly.

5 / 5

Total

16

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly defines a niche and answers both what and when with concrete, domain-appropriate trigger phrases. The only gaps are a few missing natural synonyms (E-E-A-T, editorial standards) and minor overlap potential with adjacent SEO trust-signal skills.

DimensionReasoningScore

Specificity

Names the domain and three concrete actions — 'auditing a blog, news site, or YMYL content site for trust signals', 'drafting editorial policy page content', 'evaluating whether a site meets Google's quality rater trustworthiness criteria' — but stops short of the skill's full coverage (e.g., verifying link placement or footer/About-page integration). Fits the 'several specific actions; minor gaps' anchor, not the level-5 comprehensive-action list nor the level-3 two-action limit.

4 / 5

Completeness

Explicitly answers both what (auditing for trust signals, drafting editorial policy content, evaluating against quality rater criteria) and when ('Use when auditing a blog, news site, or YMYL content site...'). Mirrors the level-5 anchor's 'concrete trigger phrases' structure; it is above level 4 because the when-clause is specific and multi-scenario rather than generic.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'editorial policy', 'trust signals', 'blog', 'news site', 'YMYL', 'Google's quality rater', 'trustworthiness' — phrases an SEO practitioner would actually say. A few natural terms are missing, notably 'E-E-A-T' and 'editorial standards', so it falls just below the comprehensive-synonym anchor at 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche (editorial policy / E-E-A-T trust signals) with distinct triggers, but sibling SEO skills like trust-signals or author-byline rules occupy adjacent territory, creating minor overlap risk. Not level 5 because 'trust signals' itself is shared vocabulary with those neighboring skills.

4 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/editorial-policy/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.