Manage JIRA collaboration surface via the jira-as wrapper: comments, attachments, watchers, notify. Triggers: 'comment on KEY', 'add attachment to KEY', 'watch KEY', 'notify KEY watchers'. Internal-vs-public comment safety enforced. NOT for issue CRUD (mk:jira-issue); NOT for issue links (mk:jira-relationships).
The exact command may vary by repository. Check the README on GitHub.
For the skill author
Drop this on your repo README
Shows your skill is listed on Skillteca, generates a backlink and trackable traffic.
[](https://www.skillteca.com.br/skills/mk-jira-collaborate?utm_source=badge&utm_medium=readme&utm_campaign=badge)
One short email with only the new Automação skills. 4 minutes of reading, no spam, unsubscribe with one click.
You confirm your email on the first send. No spam. Unsubscribe with one click.
mk:jira-collaborate
Forks to the jira-collaborate agent. The agent confirms internal-vs-public for any comment that could be customer-facing (default internal if uncertain).
Triggers
"add comment to PROJ-123: '<text>'"
"list comments on PROJ-123"
"upload screenshot.png to PROJ-123"
"watch PROJ-123" / "stop watching PROJ-123"
"notify PROJ-123 watchers about <message>"
Examples
Internal comment: "add internal comment to PROJ-123: 'awaiting backend fix'"
Attachment upload: "attach /tmp/repro.mp4 to PROJ-123"
