together-dedicated-containers
Custom Dockerized inference workers on Together AI's managed GPU infrastructure. Build with Sprocket SDK, configure with Jig CLI, submit async queue jobs, and poll results. Reach for it whenever the user needs container-level control rather than a standard model endpoint or raw cluster.
What this skill does
# Together Dedicated Containers ## Overview Use Dedicated Container Inference when the user needs a custom runtime, not just managed model hosting. Core building blocks: - **Jig CLI** for build and deployment - **Sprocket SDK** for request handling inside the container - **Queue API** for async jobs ## When This Skill Wins - Deploy a custom inference worker - Bundle custom dependencies or runtime logic into a container - Use queue-based async processing with progress tracking - Run a specialized image, video, or multimodal pipeline ## Hand Off To Another Skill - Use `together-dedicated-endpoints` for standard model hosting without custom containers - Use `together-gpu-clusters` for full cluster ownership and orchestration control - Use `together-chat-completions`, `together-images`, or `together-video` when a serverless product already covers the task ## Quick Routing - **Minimal worker template** - Start with [scripts/sprocket_hello_world.py](scripts/sprocket_hello_world.py) - Read [references/sprocket-sdk.md](references/sprocket-sdk.md) - **Build, deploy, logs, queue, and secrets** - Read [references/jig-cli.md](references/jig-cli.md) - **Queue submission and polling** - Start with [scripts/queue_client.py](scripts/queue_client.py) or [scripts/queue_client.ts](scripts/queue_client.ts) ## Workflow 1. Confirm that the user truly needs a custom container runtime. 2. Implement the worker with Sprocket's request lifecycle. 3. Configure `pyproject.toml` for image, runtime, autoscaling, and mounts. 4. Deploy with Jig. 5. Submit jobs through the queue API and poll until completion. ## High-Signal Rules - Python scripts require the Together v2 SDK (`together>=2.0.0`). If the user is on an older version, they must upgrade first: `uv pip install --upgrade "together>=2.0.0"`. - Prefer dedicated endpoints over containers unless the runtime or pipeline is genuinely custom. - Treat the worker contract and `pyproject.toml` as the source of truth for deployment behavior. - Parameterize deployment name, queue inputs, and resource sizing instead of hardcoding them. - Queue-based jobs are asynchronous by default; account for polling and result retrieval in client code. ## Resource Map - **Jig CLI**: [references/jig-cli.md](references/jig-cli.md) - **Sprocket SDK**: [references/sprocket-sdk.md](references/sprocket-sdk.md) - **Python queue client**: [scripts/queue_client.py](scripts/queue_client.py) - **TypeScript queue client**: [scripts/queue_client.ts](scripts/queue_client.ts) - **Worker template**: [scripts/sprocket_hello_world.py](scripts/sprocket_hello_world.py) ## Official Docs - [Dedicated Container Inference](https://docs.together.ai/docs/dedicated-container-inference) - [Containers Quickstart](https://docs.together.ai/docs/containers-quickstart) - [Deployments API](https://docs.together.ai/reference/deployments-create)
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.