together-local-dev-loop
/together-local-dev-loop
Develop Together AI integrations with a fake transport, recorded response shapes, deterministic assertions, and an opt-in bounded live probe. Use when iterating without spending tokens on every test. Trigger with "Together local dev", "mock Together API", or "test Together client".
- Author
- jeremylongshore ↗
- Repository
- tons-of-skills-marketplace ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 3
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Develop Together AI integrations with a fake transport, recorded response shapes, deterministic assertions, and an opt-in bounded live probe. Use when iterating without spending tokens on every test. Trigger with "Together local dev", "mock Together API", or "test Together client".
Triggers from the description
Arguments
/together-local-dev-loop [repository-path] [test-command]
Original author description
Develop Together AI integrations with a fake transport, recorded response shapes, deterministic assertions, and an opt-in bounded live probe. Use when iterating without spending tokens on every test. Trigger with "Together local dev", "mock Together API", or "test Together client".
How it works
- Overview
- Prerequisites
- Tool Discipline
- Current Contract
- Authentication
- Instructions
- Approval Boundaries
- Output
- Error Handling
- Examples
SKILL.md preview
--- name: together-local-dev-loop description: >- Develop Together AI integrations with a fake transport, recorded response shapes, deterministic assertions, and an opt-in bounded live probe. Use when iterating without spending tokens on every test. Trigger with "Together local dev", "mock Together API", or "test Together client". argument-hint: "[repository-path] [test-command]" allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit version: 1.9.0 author: Jeremy Longshore <jeremy@intentsolutions.io> license: MIT tags: - saas - together-ai - testing model: inherit effort: medium compatibility: Designed for Claude Code; optional live probes require network access and a Together AI project key --- # Together AI Local Development Loop ## Overview This skill keeps ordinary development offline and deterministic while retaining one explicit live lane for detecting provider-contract drift. ## Prerequisites - The repository's test runner and client abstraction - Sanitized fixtures for success, streaming chunks, `401`, `404`, `429`, and `503` - A separate development project key for an opt-in live probe - A fixed token and request budget for that probe ## Tool Discipline Use `Read`, `Glob`, and `Grep` to discover the wrapper, tests, fixtures, and environment gates. Use `WebFetch` to confirm current response and error shapes. Use `Write` or `Edit` only after matching repository conventions; never save live prompts, outputs, or credentials as fixtures. ## Current Contract - Inject a client or transport rather than mocking SDK internals throughout the codebase. - Preserve the SDK response fields the application actually consumes: choices, deltas, finish reason, usage, and error status. - Make live tests opt-in, bounded, non-sensitive, and visibly skipped when no approved key exists. - Test dynamic limit-header handling without hard-coding permanent RPM or TPM values. ## Authentication Offline tests use no key. The live lane reads a development-only `TOGETHER_API_KEY` from the approved test secret store and must be unavailable to untrusted fork workflows. ## Instructions 1. Locate the narrowest Together client boundary and enumerate consumed fields. 2. Build typed fake responses for non-streaming, streaming, and each retry class. 3. Assert model selection, request bounds, idempotent reconciliation keys, and redaction. 4. Gate the live probe behind an explicit environment switch plus a development key. 5. Limit the live probe to one small request against a catalog-resolved model. 6. Compare shape-level behavior, update sanitized fixtures if approved, and record cost/cleanup. ## Approval Boundaries Do not expose a live key to pull requests from forks. Do not refresh fixtures from customer traffic or authorize an unbounded live test suite. ## Output Return fake-contract coverage, offline test results, live-lane disposition, model-resolution evidence, request budget, and any detected SDK or API drift. ## Error Handling | Condition | Response | |---|---| | SDK object is hard to fake | Introduce an application-owned adapter; do not patch deep internals. | | Live key absent | Mark the live lane skipped, not passed. | | Fixture contains sensitive text | Remove it and replace it with synthetic data. | | Live response shape changed | Preserve evidence and update the adapter before fixtures. | ## Examples The example below shows the minimum redacted evidence expected from a successful invocation of this operator workflow. ```text offline=34_pass; live=skipped(no-approved-key); fixtures=synthetic; token_budget=128 ``` ## Resources - [Skill-specific official documentation](references/official-docs.md) - [Python v2 client](https://github.com/togethercomputer/together-py) - [Chat API](https://docs.together.ai/reference/chat-completions) - [Error codes](https://docs.together.ai/docs/error-codes)
Files in this package (2)
- SKILL.md 4 KB
- references/official-docs.md 3 KB
Versions
The database has no other skills named together-local-dev-loop.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 8741882ff085 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100clickup-local-dev-loop
Develop ClickUp adapters with a fake transport, schema fixtures, deterministic clocks, and an opt-in bounded live probe. Use when iterating without mutating a real Workspace. Trigger with "ClickUp local dev", "mock ClickUp API", or "ClickUp fixtures". - 100bamboohr-local-dev-loop
Create a fast BambooHR development loop with synthetic fixtures, a recording- free fake transport, contract tests, and opt-in test-tenant reads. Use when developing safely without copying employee data onto laptops. Trigger with "BambooHR local dev", "mock BambooHR", or "BambooHR test fixtures". - 100linear-local-dev-loop
Set up local Linear development environment and testing workflow. Use when configuring local development, testing integrations, or setting up a development workflow with Linear. Trigger with phrases like "linear local development", "linear dev setup", "test linear locally",… - 100juicebox-local-dev-loop
Configure Juicebox local development workflow. Use when setting up local testing, mock data, or development environment for Juicebox integration work. Trigger with phrases like "juicebox local dev", "juicebox development setup", "juicebox mock data", "test juicebox locally".