---
name: together-install-auth
description: >-
  Install Together AI SDK v2 and configure a project-scoped API key with least-privilege storage and a read-only model-list verification. Use when connecting a service or workstation to Together AI. Trigger with "Together auth", "install Together SDK", or "TOGETHER_API_KEY setup".
argument-hint: "[repository-path] [python|typescript|rest]"
allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit
version: 1.9.0
author: Jeremy Longshore <jeremy@intentsolutions.io>
license: MIT
tags:
  - saas
  - together-ai
  - authentication
model: inherit
effort: high
compatibility: Designed for Claude Code; live verification requires network access and a Together AI project key
title: together-install-auth
canonical_url: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/together-install-auth
last_updated: 2026-10-07T06:06:28.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [references/official-docs.md](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/together-install-auth/references/official-docs.md).
>
> If the user asked to install this Skill, run `npx skilld install jeremylongshore/tons-of-skills-marketplace/together-install-auth`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/together-install-auth`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/jeremylongshore/tons-of-skills-marketplace/together-install-auth) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/together-install-auth`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/together-install-auth --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/together-install-auth --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Together AI Installation and Authentication

## Overview

This skill selects the current Together client, keeps credentials outside source control, and proves access with a non-generating model-list request.

## Prerequisites

- A Together AI project and an administrator-approved key owner
- Python 3.10+ for `together>=2.0.0`, Node.js for the TypeScript SDK, or an HTTPS client
- An approved secret manager for deployed environments
- The repository and runtime that will consume the credential

## Tool Discipline

Use `Read`, `Glob`, and `Grep` to inspect dependency manifests, environment-variable names, and existing client wrappers. Use `WebFetch` only for current Together documentation. Use `Write` or `Edit` only after confirming the target files; never write a real key or `.env` value.

## Current Contract

- New Python integrations target the v2 SDK: `together>=2.0.0`.
- SDK clients read `TOGETHER_API_KEY` by default; REST uses `Authorization: Bearer <token>`.
- API keys are scoped to a Together project. Separate development, CI, and production keys.
- Verify with `client.models.list()` or `GET /v1/models`; do not spend inference tokens for an auth probe.

## Authentication

Create the key in the intended Together project, copy it once into the approved secret store, and inject it at runtime as `TOGETHER_API_KEY`. Redact the value, authorization header, and secret-manager path from logs and examples. Rotation means creating a replacement, deploying it, verifying, and revoking the old key.

## Instructions

1. Inventory the language, package manager, existing OpenAI-compatible client, and deployment environments.
2. Pin the current major SDK and record the resolved version in the lockfile.
3. Define `TOGETHER_API_KEY` in local documentation and deployment configuration without adding a value to the repository.
4. Initialize the native Together client, or configure an OpenAI client with `https://api.together.ai/v1`.
5. Run or hand off one read-only model-list probe and record only status, project alias, SDK version, and model count.
6. Document key ownership, rotation, revocation, and environment separation.

## Approval Boundaries

Do not create, reveal, broaden, rotate, or revoke a production key without the owning project administrator. Do not add a credential to tracked files, command history, test fixtures, or CI available to untrusted forks.

## Output

Return the selected client, pinned version, environment-variable contract, secret reference, read-only verification result, and rotation owner.

## Error Handling

| Condition | Response |
|---|---|
| `401` | Confirm injection and project selection; never print the key. |
| `402` | Report the billing/spend-limit condition to the project owner. |
| `404` on an OpenAI model ID | Resolve a current Together model ID; do not retry the foreign name. |
| Key exposed | Revoke or rotate it and scrub retained logs immediately. |

## Examples

Input:

```text
runtime=python; environment=ci; probe=GET /v1/models; secret=approved-reference
```

Expected handoff:

```text
sdk=together-v2; auth=bearer-project-key; probe=pass; secret-value=redacted
```

## Resources

- [Skill-specific official documentation](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/together-install-auth/references/official-docs.md)
- [Authentication](https://docs.together.ai/docs/api-keys-authentication)
- [Quickstart](https://docs.together.ai/docs/quickstart)
- [Model-list API](https://docs.together.ai/reference/models)
