---
author: 'Marcos Silva'
description:
  'Review a Confluence-ready draft and its posting context before publication.
  Use when a user wants an evidence-backed PASS, REVISE, or BLOCK verdict; this
  skill never publishes or edits a page.'
extras:
  'Publish a compact machine-readable finding schema so the dry-run script and
  human review agree.'
focus:
  'Review a Confluence draft before publishing and provide an evidence-backed
  verdict.'
id: 'page-reviewer'
improve:
  - 'Make connector-dependent checks conditional and state the fallback when the
    connector is unavailable.'
  - 'Clarify which internal links and hostnames are permitted instead of using a
    broad suffix exception.'
  - 'Add deterministic fixtures for secrets, title collisions, and invalid
    macros.'
name: 'page-reviewer'
path: '../submitted-skills/Marcos%20Silva/skills/page-reviewer/SKILL.md'
status: 'Strong non-mutating gate'
title: 'Page reviewer'
wins:
  - 'Clear PASS / REVISE / BLOCK model with anchored findings.'
  - 'Non-mutating scope and optional PlantUML checks are well defined.'
---

# page-reviewer

## Inputs

Draft body, intended space/title/parent, and any available approved connector
context.

## Workflow

1. Run deterministic local checks for content safety, storage structure, links,
   and diagram markup.
2. If an approved connector is available, check title and target context;
   otherwise report that check as unavailable.
3. Anchor every finding to a line or section and issue PASS, REVISE, or BLOCK.

## Rules

- Never publish, edit, or treat placeholders as safe secrets.
- Distinguish allowed internal destinations from unverified hosts using the
  project policy.
- A missing required validation is a stated limitation, not a pass.

## Output

Return verdict, scope, findings (severity, anchor, evidence, action), checks
run, and the next safe step.