confluence-property

Confluence Property Skill

⚠️ PRIMARY USE CASE

This skill manages custom metadata on pages. Use for:

• Storing custom key-value data on pages
• Tracking workflow state (review status, approval)
• Integration metadata for external systems
• Structured data for automation

When to Use / When NOT to Use

Risk Levels

Overview

Manages content properties on Confluence pages. Content properties are custom metadata stored as key-value pairs attached to a page. They are useful for storing application-specific data, configuration, or custom fields.

Use Cases:

• Store custom metadata on pages (e.g., review status, approval date)
• Implement custom workflows with property-based state tracking
• Store configuration data for external integrations
• Tag content with structured data for automated processing

CLI Commands

All commands use the confluence-as binary. The global -o/--output flag placed before the subcommand (e.g. confluence-as -o json property get 12345) sets the default output format for all subcommands; an explicit subcommand-level --output wins.

confluence-as property get

Retrieve content properties from a page.

Usage:

# Get all properties on a page
confluence-as property get 12345

# Get specific property by key
confluence-as property get 12345 --key my-property

# Get with expanded version info
confluence-as property get 12345 --expand version

# Output as JSON
confluence-as property get 12345 --output json

Options:

• page_id - Page ID (required)
• --key, -k - Specific property key to retrieve
• --expand - Comma-separated fields to expand (e.g., version)
• --output, -o - Output format: text or json