API DESIGN / JetBrains
Integration Resilience Engineer
Designs resilient HTTP, messaging and scheduled integrations: timeout budgets derived from the caller’s SLO, retryable-versus-terminal failure classification, idempotency and deduplication, circuit breakers, DLQ behaviour, and distributed locking for scheduled jobs.
“Design resilient HTTP, messaging, and scheduled integrations for Kotlin plus Spring services with explicit timeout budgets, retries, idempotency, circuit breakers, DLQ behavior, and failure observability.”
01 / THE REASONING
Why this made the selection.
- Derives timeout budgets backward from the caller’s SLO and classifies every operation (read-only versus state-changing, idempotent versus not) before any retry policy is written.
- Covers the failure modes that only appear in production: multi-layer retry multiplication, scheduled-job overlap needing distributed locks plus business-level idempotency, at-least-once consumers, and DLQ replay discipline defined before the first poison message.
- Ends with guardrails and a quality bar that name the skill’s own failure mode: "a bad run adds retries and circuit breakers everywhere".
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- integration-resilience-engineer/SKILL.md (JetBrains mirror)
- upstream .agents/skills/integration-resilience-engineer/SKILL.md
- upstream LICENSE
- JetBrains/skills README mirror policy
- https://github.com/Kotlin/kotlin-backend-agent-skills (answers HTTP 301 to yalishevant/kotlin-backend-agent-skills)
- mirror SKILL.md diffed against the upstream SKILL.md at fd0ed521d22efd28221d532c9abab97af0b9bf0e
Our findings
- A diff against the upstream SKILL.md at fd0ed521d22efd28221d532c9abab97af0b9bf0e shows the mirror adds four frontmatter lines (metadata, short-description, author: Kotlin, source) and nothing else; the upstream file has no author field. agents/openai.yaml is identical in both.
- The mirror README states every skill keeps an exact metadata.source link to its upstream path and that the snapshot is JetBrains-filtered and JetBrains-verified.
- The boundary nuances separate outbox from inbox patterns: each solves a different half of reliability, and neither covers both publish and consume idempotency.
- Upstream health: https://github.com/Kotlin/kotlin-backend-agent-skills, which the mirror’s metadata.source and README name, now answers HTTP 301 to yalishevant/kotlin-backend-agent-skills, a personal account (https://api.github.com/repos/Kotlin/kotlin-backend-agent-skills returns full_name yalishevant/kotlin-backend-agent-skills, owner type User). fd0ed521d22efd28221d532c9abab97af0b9bf0e is still that repository’s head, and its LICENSE (MIT, copyright 2026 Anton Yalyshev) is unchanged (checked 2026-10-13).
Not established by this review
- No integration was designed or load-tested with this skill.
- The Spring-specific settings referenced by the rules were not compiled or run.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Add a skill to your workflow.
DOCUMENTED COMMAND
npx skills add JetBrains/skills/integration-resilience-engineer --skill integration-resilience-engineerRun in your terminal to choose your AI tools, project or global scope, and installation method. This short command follows the current upstream version; the review covers the revision shown above.
Optional: install the reviewed revision
Keeps the original source and installer version where recorded, while leaving your AI tools and installation scope for you to choose.
npx skills add https://github.com/JetBrains/skills/tree/e0f258b5cfed145015cb3e48da9a97947f7c4ed7/integration-resilience-engineer --skill integration-resilience-engineer- Install the skill from the JetBrains mirror, or from the upstream Kotlin backend skills repository if you prefer the origin.
- Bring the API or messaging contract, the SLA and the current client configuration; the skill’s output contract expects them as inputs.
Before you start
- Node.js/npm for the installer
- An agent that supports the Agent Skills format
- The contract, SLA and current client config of the integration being hardened
04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://github.com/JetBrains/skills/blob/e0f258b5cfed145015cb3e48da9a97947f7c4ed7/integration-resilience-engineer/SKILL.md
Supports: summary, upstreamDescription, whySelected, bestFor, limitations, review, access
https://github.com/yalishevant/kotlin-backend-agent-skills/blob/fd0ed521d22efd28221d532c9abab97af0b9bf0e/.agents/skills/integration-resilience-engineer/SKILL.md
Supports: review, whySelected, limitations
- Upstream license (MIT) ↗Checked
https://github.com/yalishevant/kotlin-backend-agent-skills/blob/fd0ed521d22efd28221d532c9abab97af0b9bf0e/LICENSE
Supports: license
https://github.com/Kotlin/kotlin-backend-agent-skills
Supports: review, limitations
https://github.com/JetBrains/skills/blob/e0f258b5cfed145015cb3e48da9a97947f7c4ed7/README.md
Supports: review, install, limitations
https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/README.md
Supports: install