# Agent Skill Bundle — Public-safe Publishing

> Generated from the canonical public Skill source. This bundle is an invocation artifact, not a separate editable source.

## Agent instruction

Apply this Skill to the user’s actual task. Follow its inputs, behavior, guardrails, outputs, and verification criteria. Do not merely explain or summarize the Skill. If required task context is missing, ask only for the missing information that blocks correct execution.

## Skill identity

- source: skills/public-safe-publishing
- canonical human page: https://wbeen-personal-kb.vercel.app/skills/public-safe-publishing/
- version: 0.1.0
- workflow phase: publish-operate
- invocation: either

## Skill contract

Move a reviewed public-ready asset through a repeatable publishing gate without leaking private context or overstating verification.

### Inputs

- Reviewed content asset
- Public/private boundary decision
- Metadata and relation requirements
- Canonical build and live verification commands

### Outputs

- Published public asset
- Generated mirrors or indexes updated by canonical scripts
- Release evidence and residual limitations
- Explicit blocked result when a gate cannot be verified

### Guardrails

- Never publish content merely because it is well-written or machine-generated.
- Do not bypass sanitization, generated-output, or live-route checks.
- Keep private registry, credentials, internal paths, and company source outside the public layer.
- Report blocked verification instead of substituting assumptions.

### Verification

- Public/private checks pass for source and generated outputs.
- Canonical build and validators pass with a clean working tree.
- Critical public routes and machine-readable endpoints resolve.
- The release record states what was verified and what was not.

### Source instructions

## What it does

Public-safe Publishing is a release gate for a reviewed asset. It checks that the content boundary, metadata, relations, generated representations, and live behavior agree before publication is treated as complete.

## When to reach for it

Use it when a public-ready asset is about to move from staging or a working branch into a public site, feed, mirror, or other explicitly public surface.

## What one run does

1. Confirm the accountable owner and public boundary.
2. Run sanitization and content validators.
3. Regenerate mirrors and machine-readable outputs through canonical scripts.
4. Build and inspect critical routes and links.
5. Record evidence, limitations, and the release decision.

## Common failure modes

- Treating a draft approval as proof that generated outputs are safe.
- Hand-editing a mirror instead of regenerating it from source.
- Assuming a successful build proves the live route is correct.
- Publishing ambiguous material because the release deadline is near.

## It’s working if

The release can be reproduced from public source, every critical check has evidence, and a reviewer can see exactly why the asset is safe to publish.

## Where it fits

This is a **Publish & Operate**-phase skill. It follows clarification, execution, and evidence-first review; it is an editorial release boundary, not an executable package installer or marketplace workflow.

## Completion rule

Return the useful task result first. Then state briefly which verification criteria passed, which could not be checked, and any stop/escalation condition that remains.