Operate Web Function Skill

← Operations Web Function

Operate Web Function Skill

CANDIDATE INTERFACE · Operations Web Function 0.1.0. Route Web Function work through the existing canonical build, access, security, measurement, MAA, learning, and bounded Task Library methods without copying them. Use for broad website operations requests, Web Function control-plane design, cross-skill orchestration, recurring web work, fleet ownership, or when a request must be split into linked scheduled and event-triggered jobs.

Canonical owner: operations-web-function:operate-web-function · Task registration: NOT_A_BOUNDED_TASK

Broader definitive hub · Exact Task Library page: NOT_A_BOUNDED_TASK

Download the complete plugin · Source skill SHA-256: 4eb55a03c3b8ace5d5e8d3b457be74f3ff51e82d05995c4382f62cfdeb853de4

Candidate source: dennisyu/blitzmetrics-skills · commit: PENDING_MERGE · path: skills/operate-web-function/SKILL.md

The Web Function keeps every declared web property reachable, trustworthy, measurable, changeable, recoverable, and documented. It is an Operations sub-function because its work is ongoing production responsibility.

This is a control-plane candidate, not a replacement for the master skill pack or the Task Library. An adopter must resolve the external dependencies declared in registry/external-skills.json before this orchestrator is runnable.

Route the request

Need Primary skill Typical next skill
Build or migrate a site canonical business-website-agent plus the exact Task Library task $change-web-production control envelope
Build or reconcile the roster $inventory-web-properties $monitor-web-fleet
Scheduled external observation canonical security-audit through $monitor-web-fleet $triage-web-incidents on a finding
Classify an outage, block, drift, or compromise signal $triage-web-incidents $preserve-web-incident when evidence is volatile
Preserve a suspected compromise $preserve-web-incident approved repair or owner handoff
Publish, update, migrate, repair, redirect, or retire exact Task Library execution task inside $change-web-production $verify-web-outcome
Prove a deploy or repair exact QA task plus $verify-web-outcome monitor, roll back, or close
Collect or gate access canonical client-access-checklist $govern-web-access for expiry/review/revocation
Measure calls, leads, bookings, and analytics canonical measurement-analytics canonical weekly-brand-maa
Convert work into a better system and public example $document-web-lessons routing to canonical learning skills skill/page/release verification

Split a request with several independent outcomes. Each child job gets one target, one owner, one due time, one permission ceiling, and one observable Definition of Done.

Run contract

  1. Resolve the property and lifecycle state from the authoritative roster.
  2. Identify the service, risk, desired result, source event or schedule window, and current owner.
  3. Load the narrowest skill and versioned job from jobs/jobs.json at the plugin root.
  4. Compile fresh context; include source timestamps and hashes.
  5. Resolve capability references without reading secret values into the prompt or receipt.
  6. Enforce the job’s permission ceiling and required human approval.
  7. Calculate the idempotency key and acquire the correct lease.
  8. Observe or execute one bounded action.
  9. Invoke $verify-web-outcome through a path independent of the writer.
  10. Write an immutable receipt; project it into the task system and evidence ledger.
  11. Invoke $document-web-lessons for a novel failure, false positive, blind spot, repeated chase, or meaningful new control; it must route into the canonical recursive-self-improvement-qa, definitive-article-writer, skill-registry, and Task Library methods.

Hard invariants

  • checked / declared appears in every coverage result.
  • UNKNOWN never renders as clean.
  • Public observation does not establish internal cleanliness.
  • Preserve suspected compromise evidence before remediation.
  • Read-only monitors do not become repair bots.
  • A timeout does not prove a process stopped or a target went down.
  • Mutations are not blindly retried; read production back first.
  • A production writer does not verify itself solely from its own success response.
  • Fleet changes proceed canary → bounded cohort → fleet and halt on failed verification.
  • Secrets never enter skill files, examples, comments, public pages, or receipts.

From the plugin root, read docs/WEB-FUNCTION-SOP.md for the complete service catalog, state model, cadence, approval policy, Definitions of Done, evidence tiers, and publication boundary.

This is a generated candidate implementation page, not automatically a definitive article or accepted Task Library task. It delegates to the named canonical owner until reviewed registration and merge receipts exist.

Scroll to Top