providers/claude/plugin/skills/jetbrains-youtrack/SKILL.md
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".
npx skillsauth add apideck-libraries/api-skills jetbrains-youtrackInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Access JetBrains YouTrack through Apideck's Proxy API with managed Vault auth. Apideck stores credentials, refreshes tokens, and forwards your HTTP calls to JetBrains YouTrack's native API — you keep using JetBrains YouTrack'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 JetBrains YouTrack to a unified-API resource model — your code talks JetBrains YouTrack's own API directly through the Proxy. You still get Vault credential storage, token refresh, retries, and a consistent request envelope.
jetbrains-youtrackActivate this skill when the user wants to call JetBrains YouTrack via Apideck — for example, "call the JetBrains YouTrack API" or "fetch data from JetBrains YouTrack". This skill teaches the agent:
serviceId to pass on every call (jetbrains-youtrack)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.
Send any HTTP request to https://unify.apideck.com/proxy. Apideck looks up the user's stored JetBrains YouTrack credentials by x-apideck-consumer-id + x-apideck-service-id, injects them on the way out, and returns JetBrains YouTrack'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: jetbrains-youtrack" \
-H "x-apideck-downstream-url: <target endpoint on JetBrains YouTrack>" \
-H "x-apideck-downstream-method: GET"
For POST/PATCH/PUT/DELETE, change x-apideck-downstream-method and pass the body as you would to JetBrains YouTrack directly. Apideck does not transform the body — it forwards bytes.
See JetBrains YouTrack's API docs for available endpoints.
apideck-rest — REST patterns including the Proxyapideck-best-practices — Vault, error handling, retriesapideck-unified-api — when to use unified vs proxydevelopment
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".
development
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".
development
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".
development
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".