How do I install the Mk:confluence Collaborate skill?

Run npx skillmds@latest add ngocsangyem/mk-confluence-collaborate in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Mk:confluence Collaborate safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Mk:confluence Collaborate?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Mk:confluence Collaborate free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Mk:confluence Collaborate?

ngocsangyem (@ngocsangyem) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Mk:confluence Collaborate by ngocsangyem

Name: Mk:confluence Collaborate
Author: ngocsangyem

Mk:confluence Collaborate

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).

ngocsangyem Updated Sep 17, 2026

File contents

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: ''"
"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?"

Gotchas

validate_file_path in confluence-as rejects .. traversal but delegates to opaque assistant-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.

---name: mk-confluence-collaboratedescription: 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).---# mk:confluence-collaborateForks 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 format - `references/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_path` in `confluence-as` rejects `..` traversal but delegates to opaque `assistant-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.

Frequently asked questions