CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

freshness

Use when auditing content pages for freshness signals, setting up HTTP Last-Modified headers in a web server config, or ensuring Article JSON-LD dateModified is updated when CMS content changes.

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/freshness/SKILL.md
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.

The skill body is well structured — a concrete Check/Fix workflow with a closing verification section and an exemplary one-level-deep pointer to references/rule.md. Its weaknesses are redundancy (the QDF explanation appears in both the intro and a near-duplicate Explain section, and Claude already knows this background) and a couple of softer spots in actionability (a dubious Nginx directive, no CMS-hook example).

Suggestions

Remove the duplicated QDF explanation: either drop the intro paragraph or the entire Explain section, since Claude already knows what content freshness/QDF is — this redundancy is the lowest-scoring dimension (conciseness).

Fix or replace the Nginx directive: `add_header Last-Modified $date_gmt;` sets the current request time, not the file modification time the step promises; note that static files already emit Last-Modified automatically, as the Apache bullet does.

Add a one-line concrete example of the CMS hook (e.g., a pseudo-handler that compares content hashes before updating dateModified) so Fix step 4 is as executable as the others.

DimensionReasoningScore

Conciseness

The QDF concept is explained twice — the intro ("Google's Query Deserves Freshness (QDF) algorithm boosts recent or recently updated content for time-sensitive queries") and again almost verbatim in the Explain section ("Google's freshness algorithm (QDF — Query Deserves Freshness) actively boosts recently published or updated content...") — and this is background knowledge Claude already has, so both passages are unnecessary. The Quick Reference also restates bullets from Check/Fix. The actionable Check/Fix sections themselves are lean, which keeps this above a 2.

3 / 5

Actionability

Mostly executable guidance: a concrete Nginx directive (`add_header Last-Modified $date_gmt;`), an Apache mod_headers note, a copy-paste JSON-LD snippet, and a specific SSG instruction ("pass the frontmatter `updatedAt` field through to the JSON-LD and `<time>` elements"). Minor gaps: the Nginx line sets the current request time rather than the file modification time the step promises, and the CMS-hook step ("Hook your CMS to update `dateModified` only when content is substantively changed") has no example of how.

4 / 5

Workflow Clarity

A clear Check → Fix → verify sequence: the Check section enumerates four concrete inspection points, the Fix section gives five ordered remediation steps, and the Code Review section serves as an explicit validation pass ("Check that the `Last-Modified` response header is present... Verify Article JSON-LD includes `dateModified`... Confirm that the build or deployment system updates `dateModified` only for content files that actually changed"). Not a 5 because there is no feedback loop stating to re-run the checks after applying fixes.

4 / 5

Progressive Disclosure

The body is a ~43-line overview with well-organized sections, and implementation details are appropriately deferred to a clearly signaled, one-level-deep reference that exists in the bundle: "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" (verified present, 118 lines). Nothing that belongs in the reference is inlined, and navigation is trivial.

5 / 5

Total

16

/

20

Passed

Description

75%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 solid trigger-focused description: all three "Use when" scenarios are concrete and technology-specific, giving it good distinctiveness and keyword quality. Its main weakness is the absence of an explicit capability ("what") statement — everything is conveyed through when-clauses — plus a few missing natural synonyms.

DimensionReasoningScore

Specificity

The description lists three concrete action scenarios — "auditing content pages for freshness signals", "setting up HTTP Last-Modified headers in a web server config", "ensuring Article JSON-LD dateModified is updated when CMS content changes" — naming specific technologies (Last-Modified, Article JSON-LD, CMS). It falls short of a 5 because coverage has minor gaps, e.g. the visible "Last updated" date and stale-content detection covered in the body are absent, and the actions are phrased as trigger scenarios rather than capability statements.

4 / 5

Completeness

The "when" is explicit and specific (three well-differentiated "Use when" trigger scenarios). The "what" is not stated as a direct capability sentence but is functionally conveyed through the embedded action verbs (auditing, setting up, ensuring), so a reader knows what the skill does. It sits between anchor 3 (clear what, weak when — the inverse case) and anchor 5 (both fully explicit), so 4 fits; 5 would require a leading what-statement.

4 / 5

Trigger Term Quality

Good natural keyword coverage: "auditing content pages", "freshness signals", "HTTP Last-Modified headers", "web server config", "Article JSON-LD dateModified", "CMS content changes" are phrases a user working on SEO freshness would plausibly say. Not a 5 because common synonyms like "last updated date", "stale content", "content recency", or a plain "SEO" mention are missing.

4 / 5

Distinctiveness Conflict Risk

The freshness/Last-Modified/dateModified niche is well differentiated from generic SEO or structured-data skills, with distinct trigger terms like "freshness signals" and "HTTP Last-Modified headers". Minor overlap risk remains with closely related skills such as a content-dates markup or general JSON-LD skill, which keeps it below a 5.

4 / 5

Total

16

/

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/freshness/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.