Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/together-install-auth

@820dfc8
Run it yourself

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".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/together-install-auth

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈76 tokens for metadata: the name and description. ≈858 when used: this file. ≈758 more on demand in 1 file.

Description uses 3.8% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈303 characters, or 3.8%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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:

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

Expected handoff:

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

Resources

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides standard instructions for installing the official Together AI SDK and configuring the environment for API access. It uses legitimate packages and adheres to security best practices for secret management.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 20 hours ago.

Activeupdated 2 months ago
What it can do
Reads files Network Edits files
Modelinherit
argument-hint
[repository-path] [python|typescript|rest]
version
1.9.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 6 allowed tools
ReadGlobGrepWebFetchWriteEdit
Other metadata
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

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/together-install-auth