Results for “service-container”
9 skillsMore results
containerization
`task-agent`/`review-agent`: use when image layers, build context, runtime user, secrets, health checks, shutdown, or provenance change; skip when container behavior is unaffected.
4 · bundle
hf-cloud-serving-image-selection
Selects the correct SageMaker serving container image URI for HuggingFace model deployments, prioritizing HuggingFace-curated Deep Learning Containers over generic alternatives.
10.8k · bundle
delivery
Adaptive, resumable Git delivery across repositories and agent runtimes — probe policy, checkpoint coherent work, publish, review, integrate, and verify cleanup
8 · bundle
nosql-database
`task-agent`: use when document, key-value, wide-column, or graph storage changes access, partitioning, consistency, or evolution; skip vendor-only mentions and unchanged storage.
4 · bundle
file-storage-processing
`analysis-agent`/`task-agent`/`review-agent`: use when uploads, object storage, streaming, MIME, scanning, access, retention, or cleanup changes; skip without file/storage impact.
4 · bundle
scepticagent-architecture
ScepticAgent internal architecture reference. Use whenever the user asks how the extension works, wants to add a new AI provider, add a new highlight category, debug communication between components, understand the agent loop or streaming, or work with provider routing and the Gemini CORS proxy.
2
sse
Server-Sent Events for real-time server-to-client streaming. Express, Fastify, FastAPI, Spring WebFlux SSE implementations. Event streams, reconnection, and EventSource API. USE WHEN: user mentions "SSE", "Server-Sent Events", "EventSource", "event stream", "text/event-stream", "live feed", "streaming updates" DO NOT USE FOR: bidirectional communication - use `socket-io`; WebRTC - use `webrtc`; LLM streaming - use AI SDK skills
28
simpy-python
Use for writing, reviewing, debugging, testing, or analyzing Python SimPy discrete-event simulations. Trigger on Environment, Event, Process, timeout, Resource, PriorityResource, PreemptiveResource, Container, Store, queues, interrupts, simulation clocks, replications, or SimPy monitoring. Do not use for asyncio services, wall-clock schedulers, continuous ODE solvers, or Monte Carlo code without an event-process model.
0 · bundle