Jira
Repository: openclaw/skills
Author: membranedev · Source status: Clear source
Score 79Clear source
Manual reviewJira integration.
Score basis：Clear source · High risk signals · Universal
Author unclaimed
Universal
2026-03-04
Compare skills
Pick 2–4 skills and compare what really matters: fit, risk, install effort, and community signal.
This comparison came from collection: Jira project work
Compare permissions, write capabilities, and project-field support.
Selected skills (2/4)
Comparison matrix
Highlights show current best; tooltip explains diff/best rules.
SAS-v2.1 diff rules / risk tag notes
Start with the matrix. Open this section when you need to understand audit grades, top threats, control gaps, and best-value highlights.
Suggested baseline
Search to add skills, or paste 2–4 comma-separated slugs.
How differences are detected
A row is marked different when selected skills have distinct values. Only-differences mode hides rows that are identical.
How best values are highlighted
Audit score, evidence confidence, trust score, and community signal prefer higher values; execution risk and install friction prefer lower values.
How to read risk tags
Risk tags come from SAS-v2.1 public-evidence signals and point to command, network, secret, context, or supply-chain items to review before install.
Selected audit signals
atlassian
Execution risk：High
Threat tags：unexpected code execution, data exfiltration, human approval gap
Control gaps：missing license, broad permissions, shell without guardrails
ticket-triage
Execution risk：High
Threat tags：data exfiltration, memory context poisoning, human approval gap
Control gaps：missing license, network without allowlist, no human approval
| Dimension | atlassian | ticket-triage |
|---|---|---|
| SAS-v2.1 pre-install audit | ||
Audit grade | C · Review first | C · Review first |
Execution risk | High | High |
Threat tags | unexpected code execution, data exfiltration, human approval gap | data exfiltration, memory context poisoning, human approval gap |
Control gaps | missing license, broad permissions, shell without guardrails | missing license, network without allowlist, no human approval |
Permission summary | Permission review, Network, Command | Network, Command |
Evidence confidence | 65% | 65% |
| Source & provenance | ||
Provenance | mappedbyte/atlassian | anthropics/knowledge-work-plugins/tree/main/customer-support/skills/ticket-triage |
Category | Automation & Workflows | Dev & Engineering |
Freshness | 2025-06-17 | |
| Risk & trust | ||
Trust score | 79 | 76 |
Audit signals | metadata-only | No explicit signals |
Permission hints | ||
| Install & compatibility | ||
Supported tools | Universal | Claude, Codex, Cursor, Universal |
Install method | script-backed | registry-install |
Install friction | ||
| Community | ||
Stars | 43 | 6.6K |
Repository: atlassian
Author: full-chaos · Source status: Clear source
Atlassian CLI and Graph client(s) generated from openai and graphql schemas with a terraform package
Score basis：Clear source · Risk needs review · Universal
Repository: ticket
Author: ishanborah43 · Source status: Clear source
🗂️ Track issues effortlessly with this git-backed tool for AI agents, combining simplicity and powerful features for managing complex dependencies.
Score basis：Clear source · Risk needs review · Universal
Repository: jira-assistant
Author: shridhar-tl · Source status: Clear source
Repository containing source code of Jira Assistant browser extension.
Score basis：Clear source · Risk needs review · Universal
repository clone |
registry access, remote metadata pull, runtime dependencies may be required |
50 |