---
name: website-content-management
description: "Update CMS content with a reversible change plan and published-state verification. Use when the user requests website content management. Select relevant methods for the requested outcome; unrelated tasks do not require this skill."
metadata:
  version: "1.0.0"
---

# Website Content Management

Update CMS content with a reversible change plan and published-state verification.

## OLLIE Runtime integration

Use this capability under the active OLLIE Operator. Read live Workspace Context and tenant bindings for client facts and required inputs. This generic package contains no client configuration. Consume ask-ollie-authority-core for authority, outloop-access-fallback for access and recovery, email-lifecycle-core for communication, and the bootstrapper Runtime Contract for ownership, scheduling and completion. Preserve domain constraints; this Skill creates no competing execution path. Use one method, combine skills, or fill missing steps with authorized tools as the task requires.

External access uses the active Workspace’s approved Outloop capabilities. Never request, read, embed or expose credentials. A service named in a method is a possible dependency, not an access grant. Local file and application work uses the host’s authorized tools.

## Required inputs

- Approved site and CMS
- Content change request
- Current page
- Publishing authorization

## Methods

### Inspect the content model

Identify the exact site, page and content model. Inspect current fields, relationships, localization and preview behavior before writing.

### Stage content

Stage copy and assets while preserving canonical URLs, internal links, metadata and required disclosures. Distinguish drafts from published records.

### Plan migration

For migrations, map old and new fields and preserve original content until the replacement is verified. Do not alter shared components from a page-local request without assessing impact.

### Verify publication

Verify both stored CMS values and the rendered page after authorized publication, including caches, links and responsive behavior. A save confirmation alone is not evidence of a live update.

## Completion

Verify findings against source evidence and read back the resulting artifact or authorized change. Report inputs used, methods selected, output location, assumptions and unresolved dependencies. Do not report a plan, queue entry, draft, test fixture or accepted request as a completed external action. Use the task’s requested format; if a tool is unavailable, finish independent work and identify the exact unfulfilled deliverable.

## Test before relying on it

Read [the synthetic evaluation cases](references/evaluation.md) for activation, output and isolation checks. These cases are test instructions, not evidence that a host or provider test has passed.