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
Execution risk：High
Threat tags：unexpected code execution, data exfiltration, human approval gap
Control gaps：missing license, broad permissions, shell without guardrails
| Dimension | atlassian | ticket |
|---|---|---|
| Source & provenance | ||
Provenance | full-chaos/atlassian | ishanborah43/ticket |
Category | Automation & Workflows | Agent & Tools |
Freshness | 2026-04-04 | 2026-04-14 |
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: knowledge-work-plugins
Author: anthropics · Source status: Clear source
Triage incoming support tickets by categorizing issues, assigning priority (P1-P4), and recommending routing.
Score basis：Clear source · Low risk signals · Claude
