courier
Reach Jira and Slack where the Atlassian and Slack MCPs stop, via the `jira` and `slack` CLIs. Use to download a ticket's or thread's attachments, upload a file to a Jira issue or Slack message, delete a Slack post, or write a Jira description with checkboxes or embedded images.
70
86%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Low
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
The courier skill’s runtime workflow uses the local `jira` and `slack` CLIs to read specific Slack channel history (only after the user invites the bot) and specific Jira ticket/thread content via those tool invocations, not by ingesting arbitrary outsider-authored free text without an explicit user-selected target.
- Repository
- aabuhijleh/abed-hub
- Commit
5e27c8c
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.