Skill packs › Rule

Canonical Skill Rule

The contract every public skill page on Local Service Spotlight must satisfy. One source. Aliases /csr/, /canonical-rule-self-audit/, and /skills-canonical-skill-governance/ 301 here.

The URL

A skill named ai-search-visibility lives at https://localservicespotlight.com/skills-ai-search-visibility/. The WordPress slug is the flat form skills-{slug}.

Never /skills/{slug}/. That nested path 404s. Leftover nested URLs 301 to the flat slug via RankMath exact-match rules. The constructor is skill_url() in build_skill_pages.py; a nested LSS URL in generated HTML fails the build.

Ownership

These pages are generator-owned. Change Skill-Pack-Directory/build_skill_pages.py, re-run, republish. A hand edit in wp-admin is erased on the next run.

Dates

Last-updated on the skill page and in the table on /skill-packs/ come from the same map: _pack-skill-dates.json, bumped only when the skill file’s content hash changes. Republishing the HTML wrapper does not change the date. A missing key falls back to the skill file’s mtime, never an em-dash.

Inbound links

Every skill is linked from the Skill Pack Library.
Every skill is listed on the Asset Tracker.
Related-skill blocks on each page use skill_url() (six siblings, flat slugs).

Self-audit

The weekly CSR audit should fetch this page, then:

Open any skill page. Every Other skills href must be /skills-NAME/, not /skills/NAME/.
Confirm /skill-packs/ has a date in every row, matching the stamp on that skill’s page.
Confirm /asset-tracker/ links each public skill page.
Confirm /skills/ai-search-visibility/ 301s in one hop to /skills-ai-search-visibility/.
Confirm this page is linked from skill pages, the pack directory, and the Asset Tracker.

The machine check is System-Hub/verify_link_graph.py. It already flags nested /skills/<name>/ hrefs on sampled skill pages.

Where this sits in the system

Context is what the worker knows. A skill is the method it follows. A pack is a folder of methods. None of them does any work alone. Work happens when a job runs the right skill against the right context on a schedule, checks its output, and leaves a receipt the next worker can inspect.

Context — the verified facts, goals, evidence, decisions, and working state kept in user-owned Markdown, Obsidian, Drive, or Git so any authorized model can pick up the same work.
Skill — one task, written down to a standard, so an agent can run it without you in the room. There are 239 of them.
PackYOU ARE HERE — those skills bundled into a download you install in one paste.
Agent — a named role with a job description — not a chat window you retype every morning.
Job — a schedule, a QA cycle, and somewhere to keep working files. Miss any of the three and nothing runs twice.
Proof — every finished run written up in public, and the lesson pushed back into the skill.

The map: The System · every asset: Asset Tracker · next door: Asset Tracker.