Agent skill
concurrency-control
Prevent workflow conflicts with mutex synchronization, semaphores for limited parallelism, and TTL strategies for automatic cleanup of completed workflows.
Install this agent skill to your Project
npx add-skill https://github.com/adaptive-enforcement-lab/claude-skills/tree/main/plugins/patterns/skills/concurrency-control
SKILL.md
Concurrency Control
When to Use This Skill
When multiple workflows operate on shared resources, conflicts are inevitable. Two builds writing to the same output directory corrupt each other. Two deployments running simultaneously leave the system in an undefined state. Two cache rebuilds compete for the same ConfigMap.
Concurrency control prevents these conflicts. Argo Workflows provides several mechanisms: mutexes for exclusive access, semaphores for limited parallelism, and TTL strategies for cleanup.
Implementation
- Identify shared resources - What can only be accessed by one workflow at a time?
- Choose the right pattern - Mutex for exclusive access, semaphore for limited parallelism
- Configure TTL - Prevent unbounded growth of completed workflows
- Test under load - Verify behavior when multiple workflows trigger simultaneously
Start with Mutex
When in doubt, start with a mutex. It's simpler to configure and debug. Only switch to semaphores when you need controlled parallelism.
Techniques
Patterns
| Pattern | Description |
|---|---|
| Mutex Synchronization | Exclusive access to shared resources |
| Semaphores | Limited concurrent access |
| TTL Strategy | Automatic cleanup of completed workflows |
Anti-Patterns to Avoid
| Pattern | Description |
|---|---|
| Mutex Synchronization | Exclusive access to shared resources |
| Semaphores | Limited concurrent access |
| TTL Strategy | Automatic cleanup of completed workflows |
Related Patterns
- Mutex Synchronization
- Semaphores
- TTL Strategy
References
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
github-token-permissions-overview
Understanding GITHUB_TOKEN scope, default permissions, and implementing least-privilege principle for GitHub Actions workflows.
secure
Find and fix security issues before they become incidents. Vulnerability scanning, SBOM generation, supply chain security, and secure authentication workflows.
complete-workflow-examples
Copy-paste hardened CI/CD workflows with SHA-pinned actions, minimal GITHUB_TOKEN permissions, OIDC authentication, and comprehensive security scanning for GitHub Actions.
ephemeral-runner-patterns
Disposable runner patterns for GitHub Actions. Container-based, VM-based, and ARC deployment strategies with complete state isolation between jobs.
action-pinning-overview
Why pinning GitHub Actions to SHA-256 commits matters for supply chain security. Attack vectors from unpinned actions and comparison of tag vs SHA pinning.
github-actions-security-patterns-hub
Complete security patterns for GitHub Actions covering action pinning, GITHUB_TOKEN permissions, third-party action risks, secret management, and runner security.
Didn't find tool you were looking for?