---
author: 'Marcos Silva'
description:
  'Create or update a reviewed Confluence page from a local storage-format
  draft. Use when the user asks to prepare or publish through an available,
  approved Confluence connector; require confirmation immediately before
  publication.'
extras:
  'Add test fixtures for title collisions, unavailable connectors, unsafe
  content, and a failed PlantUML check.'
focus:
  'Prepare and publish reviewed Confluence storage-format pages through an
  approved connector.'
id: 'confluence-page'
improve:
  - 'Require explicit user confirmation immediately before every create or
    update action.'
  - 'Replace user-specific local paths with a configured draft root or
    repository-relative paths.'
  - 'Treat connector availability and approval as runtime checks, not
    assumptions.'
name: 'confluence-page'
path: '../submitted-skills/Marcos%20Silva/skills/confluence-page/SKILL.md'
status: 'Strong publishing workflow'
title: 'Confluence page'
wins:
  - 'Detailed storage-format guidance, templates, preflight scripts, and
    attachment rules.'
  - 'Safeguards around drafts, title collisions, and server-side diffs are
    thoughtful.'
---

# confluence-page

## Inputs

Draft file, target space and title, parent or page ID when applicable, and the
requested publication intent.

## Workflow

1. Check that the configured connector is available and approved. If it is not,
   prepare the draft and report the exact next step.
2. Create one storage-format draft per page, using a configured draft root or a
   repository-relative path.
3. Run the package preflight checks; resolve title collisions and compare
   updates with the current server body.
4. Show the destination, operation, and content summary. Request explicit
   confirmation for this create or update.
5. Publish only after confirmation, then return the page ID, URL, and version.

## Rules

- Never include secrets, tokens, PII, or local-machine paths in page content.
- Do not delete pages or attachments.
- Keep the local mirror read-only until the user requests a publication.

## Output

Return the draft path, validation results, target, confirmation status,
and—after publication—the page identifier and URL.
