Skip to content

Verification

On October 7, 2026, Sam’s Gen Writing passed the structural and manifest checks below. Network-dependent installation, the docs build, and the docs-spec gate could not run in the publishing environment. No behavioral evaluation has been run, so the skill’s status is awaiting-evals.

SurfaceCheckResult
Skill structureOfficial quick_validate.py against skills/sams-gen-writingPassed: Skill is valid!
Agent metadataYAML parse of agents/openai.yamlPassed
Smoke scenariosJSON parse of evals/evals.jsonPassed; five scenarios
Distribution manifestsJSON parsing plus claude plugin validate . --strictPassed
Docs confignode --check astro.config.mjs and internal-link scan of src/content/docsPassed
Docs scriptsnode --test src/scripts/*.test.mjsPassed: 3 tests
Portable installSkills CLI install into a clean targetNot run: the npm registry was unreachable
Docs buildbun run buildNot run: dependencies could not be downloaded
Docs-spec gateCanonical docs-spec/scripts/check.shUnavailable: the checker is not installed in the publishing environment
Forward useFresh-context runs of the smoke scenariosNot run

The formal policy reference was read directly from Search Central on October 7, 2026. The podcast reference was built from Google’s published Search Off the Record transcripts, with each finding checked against its speaker label and linked to the public episode page. The February 2023 and March 2024 Search Central blog posts could not be retrieved, so the skill cites them by title and date and relies on the current documentation for requirements.

  1. Run bun run build and the docs-spec gate in apps/docs, then confirm the new route appears in dist/llms-full.txt.
  2. Install the skill with the Skills CLI into a clean target and compare it with skills/sams-gen-writing.
  3. Run the five smoke scenarios in fresh conversations and record the model, date, web access, and which expectations passed.