confluence-propertylisted

# 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 | Use This Skill | Use Instead | |----------------|-------------| | Get/set custom metadata | - | | Store structured data | - | | Edit page content | `confluence-page` | | Add labels/tags | `confluence-label` | | Set permissions | `confluence-permission` | --- ## Risk Levels | Operation | Risk | Notes | |-----------|------|-------| | Get properties | - | Read-only | | Set property | - | Can be overwritten | | Delete property | ⚠️ | Data loss | --- ## 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 subcomman