Several illuminated work lanes converge through a gated operational release path.

// CUSTOM SKILLS · CALLABLE WORK

Reusable work, not reusable prompts.

A custom skill packages one job—its inputs, method, evidence, limits, and output—so an agent can perform it again without rebuilding the thinking from scratch.

01 / MODEL

One contract. Two operating modes.

The command is only the handle. The useful part is the behavior behind it.

A · FUNCTION

Run a defined job on demand.

A repeatable function starts when it is called, follows the same evidence contract, and returns a named result. It can be used at any point when its inputs are available.

Example: inspect the live surface and return the exact source that owns it.
B · LOOP

Repeat until an exit condition is true.

A bounded loop runs the function again after a schedule, change, or failed check. It stops on a clear success, risk, time, cost, or approval condition.

Example: audit, repair, verify, and recheck until every owned route passes.

02 / CATALOG

Work that is worth calling again.

These examples expose the reusable shell while keeping the underlying project context private.

/seo-cluster-auditAUDIT LOOP

Map a topic before publishing more pages.

Compare queries, existing URLs, search intent, overlap, content gaps, internal links, and available evidence before assigning one owner to each opportunity.

Returns keyword-owner map · cannibalization risks · ranked action queue
/live-truth-checkFUNCTION

Find the version that represents reality.

Trace the public result through redirects, headers, deploy state, revisions, source files, generated output, and cache identity before any edit begins.

Returns live surface · owning source · safe edit point · proof window
/content-refreshMAINTENANCE LOOP

Recheck an established page without erasing what works.

Review claims, sources, freshness, metadata, structured data, internal links, and the page’s current search job; change only what new evidence supports.

Returns keep/change ledger · source-backed edits · next review trigger
/mobile-site-auditQUALITY LOOP

Test the complete mobile surface, not a sample.

Inventory every route and check real viewports, overflow, tap targets, navigation, modals, forms, keyboard behavior, accessibility, images, and performance.

Returns route matrix · severity-ranked findings · verified fixes
/release-verificationBOUNDED LOOP

Carry a change from source to observed outcome.

Build, inspect the blast radius, test a hosted preview, release to the intended target, and independently verify the live user path. Stop on any red gate.

Returns release verdict · deployed identity · live evidence · rollback point
/handoff-packetFUNCTION

Transfer the plot without transferring the whole history.

Compress current state, decisions, evidence, scope boundaries, unresolved risks, and the smallest safe next action into a continuation another agent can trust.

Returns state · decisions · proof · stop conditions · next move

03 / CONTRACT

What makes a skill safe to repeat.

A memorable slash command is useful. A visible evidence and exit contract is what makes it dependable.

  1. 01

    Trigger

    The request, schedule, change, or failure that starts the skill.

  2. 02

    Inputs

    The exact sources, state, and authority the skill is allowed to use.

  3. 03

    Method

    The ordered checks and actions that make the work reproducible.

  4. 04

    Evidence

    The observable proof required before the skill may claim success.

  5. 05

    Exit

    The success, approval, risk, time, cost, or rollback condition that ends it.

// CONTRACT → PRACTICE

Use the shell without losing the evidence rules.

Templates make the inputs and outputs concrete. The Library explains the methods behind the callable work.

Choose a template Browse the Library