Confluence collaborate
Skill ngocsangyem/MeowKit/.claude/skills/confluence-collaborate
Production ready. AI Agent Workflow System for Claude Code
npx -y skills add ngocsangyem/MeowKit --skill confluence-collaborateAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 15 stars15 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Manage Confluence collaboration surface via the confluence-as wrapper: comments, attachments, labels, watchers. Triggers: 'add comment to page 12345', 'upload attachment to page 12345', 'label page 12345 as urgent', 'watch page 12345'. Inline-vs-footer comment safety enforced. NOT for page CRUD (mk:confluence-page); NOT for bulk ops (mk:confluence-bulk).
SKILL.md
2.9 KB, as published. Nobody here has run it
mk:confluence-collaborate
Forks to the confluence-collaborate agent. The agent prefers footer comments over inline; asks before posting an inline comment.
Triggers
- "add comment to page 12345: '<text>'"
- "list comments on page 12345"
- "upload screenshot.png to page 12345"
- "label page 12345 as 'urgent'"
- "remove label 'draft' from page 12345"
- "watch page 12345" / "stop watching page 12345"
- "list watchers of page 12345"
Examples
- Footer comment: "add comment to 12345: 'awaiting backend fix'"
- Attachment upload: "attach /tmp/repro.mp4 to page 12345"
- Label add: "label 12345 as 'rfc'"
- Watcher list: "who watches page 12345?"
See also
- Agent:
../../agents/confluence-collaborate.md - Shared:
../confluence/references/{install-and-auth,cli-idioms,safety-framework}.md - Domain refs:
references/comment-formats.md— inline vs footer, markdown vs storage formatreferences/attachment-conventions.md— file size limits, allowed types, download paths
- Peer leaves:
mk:confluence-page(page CRUD; create-with-attachment),mk:confluence-bulk(bulk-label across 10+ pages),mk:confluence-spec-analyst(downloads attachments for image analysis)
Gotchas
validate_file_pathinconfluence-asrejects..traversal but delegates to opaqueassistant-skills-lib. Don't trust delegation alone — the agent independently validates upload paths at the agent boundary too. [from research]- Confluence Cloud comments do NOT have a strict internal/public flag like Jira Service Management. Inline vs footer is the closest semantic boundary — agent prefers footer. [from jira-collaborate parallel pattern]
- Inline comment requires an anchor selection. If the selection text doesn't match unique content on the page, the comment fails with a 400-class error.
- Bulk-label across 10+ pages goes through
mk:confluence-bulk, NOT this skill. Single-page label add/remove only here. - Grow this list as new edge cases surface.