confluence-api-doc
Confluence API Doc Sync
Sync API documentation from a multi-file docs/api/ directory to Confluence — one endpoint file = one Confluence page. The directory structure maps directly to a Confluence page tree, so no heading-based splitting is needed.
Uses acli for authentication verification and page reading (to get current version), and Confluence REST API via curl for page updates.
Core Principle: Directory Structure = Confluence Page Tree
The docs/api/ directory (generated by api-doc-gen) already organizes endpoints as individual files grouped by domain. This skill maps that structure directly to Confluence:
docs/api/ Confluence Page Tree
├── index.md → Parent Page (overview + common errors)
├── consent/ → ├── Consent (domain group page)
│ ├── accept-consent.md → │ ├── Accept Consent
│ ├── get-consent.md → │ ├── Get Consent
│ └── revoke-consent.md → │ └── Revoke Consent
├── channel/ → ├── Channel (domain group page)
│ ├── create-channel.md → │ ├── Create Channel
More from jojious/ada-skills
brainstorm
>-
35improve
Iteratively improve any output until measurable criteria are met. Use when the user wants to refine existing work against specific standards — whether it's code, prose, data, config, or any other artifact. Triggers on phrases like "improve this", "make it better", "iterate", "refine", "keep improving", "not good enough yet", "optimize this", "polish this", "tighten this up", "ปรับปรุง", "ทำให้ดีขึ้น", "ยังไม่ดี", "แก้ให้ดีกว่านี้", "iterate ต่อ", or when the user provides criteria and wants repeated improvement until they're satisfied. Also use when the user gives feedback on output and expects you to keep refining, even if they don't say "improve" explicitly.
32api-doc-gen
>
11neo-team-kiro
>
7neo-team-claude
>
7commit
>-
5