Case study: a skill in a ZIP is not yet citable

Candidate redacted meta example — not yet Task Library accepted · Operations Web Function 0.1.0.

Download the complete plugin · Source SHA-256: 82afc6fc2190d6e908ef3f8482b36b14ebc7167d79ff5f6ac8d62f906194de28

Twenty-four skills existed as source files, ZIP contents, and rows in a directory. None of those forms gave a search engine, AI assistant, customer, or operator one stable URL that explained a specific skill and linked its evidence.

The publishing system generated one provenance-bearing implementation page per source skill. The same change extended the daily runner and link verifier so the new pages could not drift silently from the source or sit outside coverage. The pages are not automatically definitive articles or accepted Task Library pages; their registry relationship must be explicit.

What changed in the reusable SOP:

generate public pages from canonical skill sources rather than hand-editing copies;
give every capability a stable, citable URL;
extend the runner and verifier whenever a new artifact tier is added;
verify skill source, public page, package release, and freshness together;
treat “exists in a download” and “is publicly discoverable and citable” as different states.

This is why the Web Function pack ships source skills, job recipes, examples, evidence, and a canonical publication plan instead of only a long article. Evidence tier: E3.

This page is generated from examples/case-studies/04-skills-need-pages.md. Do not hand-edit the public copy.