Local Service Spotlight · Living Registry
The Skill Pack Library
Every place we publish downloadable agent-skill packs: curated distributions of reusable methods for supported runtimes. This registry links the artifacts and preserves their build dates without treating a ZIP, plugin, installed copy, or vendor memory as the source.
Sibling of the Spotlight Network registry and the Asset Tracker; this is the list of our packs. Shared standards are synchronized and tested in the canonical repository. Ordinary field-learning ingestion is still being migrated from the legacy pack folders, so do not infer propagation from a date alone. The operating map is The System.
Newest listed artifact build: Aug 20, 2026. Architecture verified Aug 22, 2026.
The core system
The flagship packs — the Business pack for local companies (our main pack), the Entrepreneur agent team, and the canonical personal-brand system every edition below is built from.
THE master pack (Company Edition): the 10-step authority build plus the scheduled automation tier — daily selling, weekly measurement, the quarterly subscription audit.
The agent team for coaches, consultants, course creators, authors & founders — the general edition of the team our member programs run, in run order.
The canonical starter system + the prompt you paste into Claude.
Workshop & event editions
Tuned handouts we hand to the room at live events. Same engine, audience-specific examples.
The DealCon workshop pack for agency owners & acquirers.
The Wichita mastermind edition of the skill library.
The JVA edition, tuned for its audience.
The DigiMarCon business-authority pack + the DealCon skills.
Vertical Spotlight editions
Every Spotlight site ships the pack, retuned for its niche. See the whole network in the registry.
The pack retuned for AI builders — 1-click install.
The dunker edition — buy box = sponsors, coaching, bookings.
The quick-start starter pack for new members.
The deep library
When the starter pack isn’t enough — the full operational library and how we build agents.
A dated distribution of atomic task files. Use the live dashboard for current inventory, readiness, and ownership.
The living hub documenting how we build agents and keep them current.
How you give an agent the keys to WordPress without sharing your password — mint one revocable Application Password, no login every time. Paste-in bootstrap block sets a new teammate’s Claude up to publish login-free.
Program & partner packs
Client-program and partner libraries built on the same method.
The franchisee agent pack built for the Pure Green program.
Sigrún Gudjónsdóttir’s SOMBA member library, on the same method and now on the same daily loop — every agent carries dated lessons from real runs, plus the scheduled automation tier (daily selling, weekly measurement, quarterly subscription audit) and one member one-pager per agent.
The single-skill Content Agent — one recording into a week of content. Also on LSS & dennisyu.com.
What’s inside — the skills, and when each was last updated
The core pack runs these in order. Every skill name links to its own page — what it is, when to use it, what it needs, and what good looks like. Each skill carries its own last-updated date; where a skill hasn’t changed, it keeps its prior date. (Where a per-skill date isn’t tracked, the pack’s date is used.)
How this stays current
What works now: shared standards synchronize into applicable marketplace skills and CI checks drift. A reusable field lesson is current only after it lands in the canonical repository through review, the distribution is rebuilt, the target installation is synced, and a fresh-task canary proves activation. The older automatic harvester still targets legacy pack folders and is not evidence that every artifact inherited a lesson. See the propagation model.
Directory maintained as a distribution registry. Treat every pack as a dated projection and verify source, installation, and activation. Related: agent memory and coordination · The System · the Asset Tracker · canonical skill rule · the Spotlight Network · How we build agents · Login-free publishing.
Where this sits in the system
Context is the relevant slice an agent retrieves from records with defined owners. A skill is the method it follows. A pack is a curated distribution. 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 retrieved from the authoritative record for that class.
- Skill — one task, written down to a standard, so an agent can run it without you in the room.
- PackYOU ARE HERE — a curated distribution of skills for a supported runtime, not a second canonical source.
- 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 — a private receipt after substantive work; selected approved runs become public examples, and reusable lessons enter the canonical source through review.
The map: The System · every asset: Asset Tracker · next door: Asset Tracker.