Content
71%Weight 40%Scale 1-5Reviews 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.
| Dimension | Reasoning | Score |
|---|---|---|
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 |