apideck-libraries/jira-teams
providers/claude/plugin/skills/jira-teams/SKILL.md
Jira Teams via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Jira Teams's native API. Use when the user wants to call Jira Teams (no unified API resource mapping). Routes through Apideck with serviceId "jira-teams".
$ install --global
skillsauthnpx skillsauth add apideck-libraries/api-skills jira-teamsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 27, 2026, 4:41 AM83.5s1 file scanned
SKILL.md
- name:
- jira-teams
- description:
- |
- license:
- Apache-2.0
- alwaysApply:
- false
- author:
- apideck
- version:
- 1.0.0
- serviceId:
- jira-teams
- proxyOnly:
- true
- unifiedApis:
- []
- authType:
- basic
- tier:
- 2
- verified:
- true
- status:
- beta
Jira Teams (via Apideck Proxy)
Access Jira Teams through Apideck's Proxy API with managed Vault auth. Apideck stores credentials, refreshes tokens, and forwards your HTTP calls to Jira Teams's native API — you keep using Jira Teams's own request and response shapes, while Apideck eliminates per-tenant credential plumbing and gives you a single auth integration shared across every Apideck connector.
Auth-only / proxy-only connector. Apideck does not map Jira Teams to a unified-API resource model — your code talks Jira Teams's own API directly through the Proxy. You still get Vault credential storage, token refresh, retries, and a consistent request envelope.
Quick facts
- Apideck serviceId:
jira-teams - Mode: Proxy-only (no unified API resources)
- Auth type: basic
- Status: beta
- Apideck setup guide: Connection guide
- Gotchas: page
- Homepage: https://www.atlassian.com
When to use this skill
Activate this skill when the user wants to call Jira Teams via Apideck — for example, "call the Jira Teams API" or "fetch data from Jira Teams". This skill teaches the agent:
- That Jira Teams routes through Apideck's Proxy API, not a unified resource API
- The correct
serviceIdto pass on every call (jira-teams) - How to keep using Jira Teams's native request/response shapes while Apideck handles Vault auth
If you need a unified-API surface (one method shape across many vendors), see the connector skills in this catalog whose serviceId is mapped to a unified API.
Auth
- Type: Basic auth (username/password)
- Managed by: Apideck Vault — credentials are collected through the Vault modal and stored encrypted server-side.
- Note: basic auth connectors often require manual rotation by the end user. If auth fails persistently, prompt them to re-enter credentials in Vault.
Calling Jira Teams via the Proxy API
Send any HTTP request to https://unify.apideck.com/proxy. Apideck looks up the user's stored Jira Teams credentials by x-apideck-consumer-id + x-apideck-service-id, injects them on the way out, and returns Jira Teams's raw response.
curl 'https://unify.apideck.com/proxy' \
-H "Authorization: Bearer ${APIDECK_API_KEY}" \
-H "x-apideck-app-id: ${APIDECK_APP_ID}" \
-H "x-apideck-consumer-id: ${CONSUMER_ID}" \
-H "x-apideck-service-id: jira-teams" \
-H "x-apideck-downstream-url: <target endpoint on Jira Teams>" \
-H "x-apideck-downstream-method: GET"
For POST/PATCH/PUT/DELETE, change x-apideck-downstream-method and pass the body as you would to Jira Teams directly. Apideck does not transform the body — it forwards bytes.
See also
- Apideck connection guide for Jira Teams
- Jira Teams gotchas
- Apideck Proxy API reference
apideck-rest— REST patterns including the Proxyapideck-best-practices— Vault, error handling, retriesapideck-unified-api— when to use unified vs proxy
Related Skills
apideck-libraries/jira-service-desk
development
VerifiedTrustedCommunity
Jira Service Desk via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Jira Service Desk's native API. Use when the user wants to call Jira Service Desk (no unified API resource mapping). Routes through Apideck with serviceId "jira-service-desk".
2SKILL.mdUpdated Apr 27, 2026
apideck-libraries/jira-data-center
development
VerifiedTrustedCommunity
Jira Data Center via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Jira Data Center's native API. Use when the user wants to call Jira Data Center (no unified API resource mapping). Routes through Apideck with serviceId "jira-data-center".
2SKILL.mdUpdated Apr 27, 2026
apideck-libraries/jetbrains-youtrack
development
VerifiedTrustedCommunity
JetBrains YouTrack via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to JetBrains YouTrack's native API. Use when the user wants to call JetBrains YouTrack (no unified API resource mapping). Routes through Apideck with serviceId "jetbrains-youtrack".
2SKILL.mdUpdated Apr 27, 2026
apideck-libraries/intercom
development
VerifiedTrustedCommunity
Intercom via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Intercom's native API. Use when the user wants to call Intercom (no unified API resource mapping). Routes through Apideck with serviceId "intercom".
2SKILL.mdUpdated Apr 27, 2026