together-evaluations
LLM-as-a-judge evaluation framework on Together AI. Classify, score, and compare model outputs, select judge models, use external-provider judges or targets, poll results and download reports. Reach for it whenever the user wants to benchmark outputs, grade responses, compare A/B variants, or operationalize automated evaluations.
What this skill does
# Together AI Evaluations ## Overview Use Together AI evaluations when the user wants a managed LLM-as-a-judge workflow rather than an ad hoc prompt loop. Core evaluation types: - **Classify**: assign outputs to labels - **Score**: grade outputs on a numeric scale - **Compare**: compare two candidate outputs with bias controls This skill also covers external providers used as judges or targets when the workflow still runs through Together AI's evaluation system. ## When This Skill Wins - Benchmark prompt variants, models, or product responses - Grade quality, safety, policy compliance, or task success - Run A/B comparisons between model outputs - Build repeatable evaluation jobs with uploaded datasets - Pull results programmatically after asynchronous execution ## Hand Off To Another Skill - Use `together-chat-completions` for one-off inference or manual judge prompts - Use `together-batch-inference` for bulk offline generation rather than evaluation - Use `together-fine-tuning` when the user wants to improve the model instead of just measure it - Use `together-dedicated-endpoints` only if the evaluation target itself is a dedicated endpoint ## Quick Routing - **Classify / Score / Compare job setup** - Start with [scripts/run_evaluation.py](scripts/run_evaluation.py) or [scripts/run_evaluation.ts](scripts/run_evaluation.ts) - Read [references/api-reference.md](references/api-reference.md) for exact request shapes - **Dataset formatting** - Read the dataset sections in [references/api-reference.md](references/api-reference.md) - **Dataset columns, Jinja2 templates, or pre-generated responses** - Read the dataset and template sections in [references/api-reference.md](references/api-reference.md) - Use `--eval-column`, `--model-a-column`, or `--model-b-column` in the scripts - **External providers as judge or target** - Read the model-source and provider sections in [references/api-reference.md](references/api-reference.md) - Use the scripts with `--judge-model-source external`, `--eval-model-source external`, or compare-side source flags - **Polling, listing, or downloading results** - Use the retrieval endpoints documented in [references/api-reference.md](references/api-reference.md) - Use `--download-results` in the scripts when you want the per-row JSONL locally ## Workflow 1. Identify whether the user needs classify, score, or compare. 2. Define the dataset schema before writing code. 3. Upload the dataset as an eval file and keep the returned file ID. 4. Configure judge and target models explicitly, especially when mixing providers. 5. Poll status until completion, then download the result file for analysis. ## 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"`. - The current SDK examples in this repo use `check=False` for eval uploads because local file validation can misclassify eval datasets. - Treat dataset schema as part of the product contract; inconsistent fields cause downstream confusion. - Compare evaluations are best when both candidate responses are already present in the dataset. - Keep judge configuration explicit. Hidden defaults make benchmark interpretation harder. - Use Together AI's managed evaluation job instead of rebuilding a manual judge loop when repeatability matters. ## Resource Map - **Full API reference**: [references/api-reference.md](references/api-reference.md) - **Dataset formats, Jinja2 templates, and provider shortcuts**: [references/api-reference.md](references/api-reference.md) - **Python workflow**: [scripts/run_evaluation.py](scripts/run_evaluation.py) - **TypeScript workflow**: [scripts/run_evaluation.ts](scripts/run_evaluation.ts) ## Official Docs - [AI Evaluations](https://docs.together.ai/docs/ai-evaluations) - [Evaluations API](https://docs.together.ai/reference/create-evaluation)
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.