Skip to content

mk:jira-collaborate

What This Skill Does

Forks the jira-collaborate agent to manage the per-issue collaboration layer — comments, attachments, watchers, notifications. The agent confirms internal-vs-public for any comment that could be customer-facing.

When to Use

Internal-vs-Public Safety

Atlassian Cloud distinguishes internal (team-only) vs public (visible to customers / external watchers) comments. JSM tickets surface this distinction explicitly. Before posting any customer-facing comment:

"Should this comment be internal (team-only) or public (visible to all watchers)?"

Default to internal if uncertain. Misposting an internal comment as public has reputational + privacy consequences.

Verified Wrapper Invocations

OperationTierInvocation
Comment add2... collaborate comment add PROJ-123 --body "text"
Comment list1... collaborate comment list PROJ-123
Comment delete4... collaborate comment delete PROJ-123 --comment-id <ID> (irreversible)
Attachment upload2... collaborate attachment upload PROJ-123 --file /path/to/file
Attachment download1... collaborate attachment download PROJ-123 --attachment-id <ID> --output /tmp/...
Watcher add2... collaborate watcher add PROJ-123 --user <username>
Notify2... collaborate notify PROJ-123 --message "..."

ADF Conversion

Pass markdown to --body and jira-as handles ADF conversion server-side. For raw ADF, pass --format adf with a JSON ADF document.

Domain References

  • references/comment-templates.md — copy-paste comment templates (progress, blocker, handoff, evidence)
  • references/comment-formats.md — text / markdown / ADF format reference

Peer Leaves

mk:jira-issue (create-with-attachment) · mk:jira-jsm (internal-vs-public on JSM tickets) · mk:jira-analyst (post-analysis comment patterns)

Agent

jira-collaborate — A + C, NOT B.

Released under the MIT License.