together-dedicated-endpoints
Single-tenant GPU endpoints on Together AI with autoscaling and no rate limits. Deploy fine-tuned or uploaded models, size hardware, and manage endpoint lifecycle. Reach for it whenever the user needs predictable always-on hosting rather than serverless inference, custom containers, or raw clusters.
What this skill does
# Together Dedicated Endpoints ## Overview Use dedicated endpoints for managed single-tenant model hosting with predictable performance and no shared serverless pool. Typical fits: - production inference with stable latency - fine-tuned model hosting - uploaded custom model hosting - autoscaled model APIs ## When This Skill Wins - The user needs always-on or single-tenant hosting - The model is supported for dedicated deployment - Fine-tuned or uploaded models must be served as endpoints - Hardware, scaling, or idle-time settings need explicit control ## Hand Off To Another Skill - Use `together-chat-completions` for serverless chat inference - Use `together-dedicated-containers` for custom runtimes or nonstandard inference pipelines - Use `together-gpu-clusters` for raw infrastructure or cluster orchestration ## Quick Routing - **Create and manage a standard endpoint** - Start with [scripts/manage_endpoint.py](scripts/manage_endpoint.py) or [scripts/manage_endpoint.ts](scripts/manage_endpoint.ts) - Read [references/api-reference.md](references/api-reference.md) - **Lifecycle tuning or troubleshooting** - Read [references/api-reference.md](references/api-reference.md) - **Deploy a fine-tuned model** - Start with [scripts/deploy_finetuned.py](scripts/deploy_finetuned.py) - Read [references/dedicated-models.md](references/dedicated-models.md) - **Upload and deploy a custom model** - Start with [scripts/upload_custom_model.py](scripts/upload_custom_model.py) - Read [references/dedicated-models.md](references/dedicated-models.md) - **Hardware and sizing choices** - Read [references/hardware-options.md](references/hardware-options.md) ## Workflow 1. Confirm that the task needs dedicated hosting instead of serverless or containers. 2. Verify model eligibility and inspect available hardware. 3. Create the endpoint with explicit scaling and timeout settings. 4. Wait for readiness before sending inference traffic. 5. Stop or delete the endpoint when the workload no longer needs to run. ## 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"`. - Model eligibility and hardware availability are gating constraints; check them early. - Endpoint management uses endpoint IDs, while inference usually uses the endpoint name as `model`. - Autoscaling, auto-shutdown, prompt caching, and speculative decoding materially affect operations and cost. - For custom or fine-tuned models, do not skip the intermediate verification steps before deployment. ## Resource Map - **API reference**: [references/api-reference.md](references/api-reference.md) - **Operational controls and troubleshooting**: [references/api-reference.md](references/api-reference.md) - **Dedicated model guide**: [references/dedicated-models.md](references/dedicated-models.md) - **Hardware guide**: [references/hardware-options.md](references/hardware-options.md) - **Python endpoint lifecycle**: [scripts/manage_endpoint.py](scripts/manage_endpoint.py) - **TypeScript endpoint lifecycle**: [scripts/manage_endpoint.ts](scripts/manage_endpoint.ts) - **Fine-tuned deployment**: [scripts/deploy_finetuned.py](scripts/deploy_finetuned.py) - **Custom model upload and deployment**: [scripts/upload_custom_model.py](scripts/upload_custom_model.py) ## Official Docs - [Dedicated Endpoints](https://docs.together.ai/docs/dedicated-inference) - [Endpoints API](https://docs.together.ai/reference/createendpoint) - [Upload and Deploy Custom Models](https://docs.together.ai/docs/custom-models)
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.