davila7/claude-code-templates/simpy
- community
Checking that the SKILL.md file is still in the repository.
Process-based discrete-event simulation framework in Python. Use this skill when building simulations of systems with processes, queues, resources, and time-based events such as manufacturing systems, service operations, network traffic, logistics, or any system where entities interact with shared resources over time.
Install
npx vskill@latest install davila7/claude-code-templates/simpySKILL.md
SimPy - Discrete-Event Simulation
Overview
SimPy is a process-based discrete-event simulation framework based on standard Python. Use SimPy to model systems where entities (customers, vehicles, packets, etc.) interact with each other and compete for shared resources (servers, machines, bandwidth, etc.) over time.
Core capabilities:
- Process modeling using Python generator functions
- Shared resource management (servers, containers, stores)
- Event-driven scheduling and synchronization
- Real-time simulations synchronized with wall-clock time
- Comprehensive monitoring and data collection
When to Use This Skill
Use the SimPy skill when:
- Modeling discrete-event systems - Systems where events occur at irregular intervals
- Resource contention - Entities compete for limited resources (servers, machines, staff)
- Queue analysis - Studying waiting lines, service times, and throughput
- Process optimization - Analyzing manufacturing, logistics, or service processes
- Network simulation - Packet routing, bandwidth allocation, latency analysis
- Capacity planning - Determining optimal resource levels for desired performance
- System validation - Testing system behavior before implementation
Not suitable for:
- Continuous simulations with fixed time steps (consider SciPy ODE solvers)
- Independent processes without resource sharing
- Pure mathematical optimization (consider SciPy optimize)
Quick Start
Basic Simulation Structure
Resource Usage Pattern
Core Concepts
1. Environment
The simulation environment manages time and schedules events.
2. Processes
Processes are defined using Python generator functions (functions with yield statements).
3. Events
Events are the fundamental mechanism for process synchronization. Processes yield events and resume when those events are triggered.
Common event types:
env.timeout(delay)- Wait for time to passresource.request()- Request a resourceenv.event()- Create a custom eventenv.process(func())- Process as an eventevent1 & event2- Wait for all events (AllOf)event1 | event2- Wait for any event (AnyOf)
Resources
SimPy provides several resource types for different scenarios. For comprehensive details, see references/resources.md.
Resource Types Summary
| Resource Type | Use Case | |
|---|---|---|
| Resource | Limited capacity (servers, machines) | |
| PriorityResource | Priority-based queuing | |
| PreemptiveResource | High-priority can interrupt low-priority | |
| Container | Bulk materials (fuel, water) | |
| Store | Python object storage (FIFO) | |
| FilterStore | Selective item retrieval | |
| PriorityStore | Priority-ordered items |
Quick Reference
Common Simulation Patterns
Pattern 1: Customer-Server Queue
Pattern 2: Producer-Consumer
Pattern 3: Parallel Task Execution
Workflow Guide
Step 1: Define the System
Identify:
- Entities: What moves through the system? (customers, parts, packets)
- Resources: What are the constraints? (servers, machines, bandwidth)
- Processes: What are the activities? (arrival, service, departure)
- Metrics: What to measure? (wait times, utilization, throughput)
Step 2: Implement Process Functions
Create generator functions for each process type:
Step 3: Set Up Monitoring
Use monitoring utilities to collect data. See references/monitoring.md for comprehensive techniques.
Step 4: Run and Analyze
Advanced Features
Process Interaction
Processes can interact through events, process yields, and interrupts. See references/process-interaction.md for detailed patterns.
Key mechanisms:
- Event signaling: Shared events for coordination
- Process yields: Wait for other processes to complete
- Interrupts: Forcefully resume processes for preemption
Real-Time Simulations
Synchronize simulation with wall-clock time for hardware-in-the-loop or interactive applications. See references/real-time.md.
Comprehensive Monitoring
Monitor processes, resources, and events. See references/monitoring.md for techniques including:
- State variable tracking
- Resource monkey-patching
- Event tracing
- Statistical collection
Scripts and Templates
basic_simulation_template.py
Complete template for building queue simulations with:
- Configurable parameters
- Statistics collection
- Customer generation
- Resource usage
- Report generation
Usage:
resource_monitor.py
Reusable monitoring utilities:
ResourceMonitor- Track single resourceMultiResourceMonitor- Monitor multiple resourcesContainerMonitor- Track container levels- Automatic statistics calculation
- CSV export functionality
Usage:
Reference Documentation
Detailed guides for specific topics:
- `references/resources.md` - All resource types with examples
- `references/events.md` - Event system and patterns
- `references/process-interaction.md` - Process synchronization
- `references/monitoring.md` - Data collection techniques
- `references/real-time.md` - Real-time simulation setup
Best Practices
- Generator functions: Always use
yieldin process functions - Resource context managers: Use
with resource.request() as req:for automatic cleanup - Reproducibility: Set
random.seed()for consistent results - Monitoring: Collect data throughout simulation, not just at the end
- Validation: Compare simple cases with analytical solutions
- Documentation: Comment process logic and parameter choices
- Modular design: Separate process logic, statistics, and configuration
Common Pitfalls
- Forgetting yield: Processes must yield events to pause
- Event reuse: Events can only be triggered once
- Resource leaks: Use context managers or ensure release
- Blocking operations: Avoid Python blocking calls in processes
- Time units: Stay consistent with time unit interpretation
- Deadlocks: Ensure at least one process can make progress
Example Use Cases
- Manufacturing: Machine scheduling, production lines, inventory management
- Healthcare: Emergency room simulation, patient flow, staff allocation
- Telecommunications: Network traffic, packet routing, bandwidth allocation
- Transportation: Traffic flow, logistics, vehicle routing
- Service operations: Call centers, retail checkout, appointment scheduling
- Computer systems: CPU scheduling, memory management, I/O operations
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingcli-tool/components/skills/scientific/simpy/SKILL.md
Popularity
- Repository stars
- 22,525
- Repository forks
- 2,143
- Repository npm downloads, 7 days
- 5,078
- 7-day trend score
- 70
Stars and forks are for the whole GitHub repository, not this skill alone. Downloads are for the repository's npm package. Refreshed 16 Mar 2026, 7 months ago.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/davila7/claude-code-templates/simpy)