Synaptic-Tuner: Skill for Claude Code

.agents/skills/case-studies/SKILL.md

case-studies is a skill for Claude Code from ProfSynapse/Synaptic-Tuner. It costs 128 tokens per session (1,631 once invoked), scanned A, original, MIT.

A set of complete examples for building and training AI capabilities from start to finish. It covers tool-calling models, essay-writing models, and agentic search, where an AI searches documents before answering.

In plain words
What is it for?
Use it as a practical reference when designing datasets, generating training examples, fine-tuning models, evaluating results, and deploying trained capabilities.
Why use it?
It shows how data creation, training, testing, and deployment fit together, including the decisions and revisions between those stages.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: installed under .agents/ (shared by several agents).

This is ProfSynapse/Synaptic-Tuner's own configuration. It tells Claude Code how to work on Synaptic-Tuner itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Synaptic-Tuner configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ProfSynapse/Synaptic-Tuner. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ProfSynapse/Synaptic-Tuner/main/.agents/skills/case-studies/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/ProfSynapse/Synaptic-Tuner

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for case-studies

README.md
[![agentmods](https://agentmods.dev/badge/skills/profsynapse/synaptic-tuner/case-studies/github.svg)](https://agentmods.dev/skills/profsynapse/synaptic-tuner/case-studies)
Your own site
<a href="https://agentmods.dev/skills/profsynapse/synaptic-tuner/case-studies"><img src="https://agentmods.dev/badge/skills/profsynapse/synaptic-tuner/case-studies/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for case-studies

Your own site · 80×15
<a href="https://agentmods.dev/skills/profsynapse/synaptic-tuner/case-studies"><img src="https://agentmods.dev/badge/skills/profsynapse/synaptic-tuner/case-studies.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 128 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,631 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00128 $0.01631
Opus 5.5 $0.00051 $0.00652
Sonnet 5.5 $0.00026 $0.00326
Haiku 4.5 $0.00013 $0.00163

Measured 22d ago against content hash f4d4bcb5d2d9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

case-studies scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 22d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/case-studies/SKILL.md · 125 lines

How it starts

The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Case Studies: Implementing the Training Pipeline

Four end-to-end worked examples showing how to take a capability from concept to trained model.

Why Case Studies?

The other skills teach you how to use individual tools:

  • synthetic-data-generation — how to run SynthChat
  • fine-tuning — how to run trainers
  • evaluation — how to run evals
  • upload-deployment — how to ship models

This skill shows you how they all connect — the decisions, the iteration, and the order of operations that turn an idea into a trained capability.

The Four Case Studies

Case Study What It Teaches Reference
Tool Calling Structured output training — teaching a model to call APIs with correct syntax, context objects, and parameters reference/tool-calling-pipeline.md
Essay Style Creative output training — teaching a model to transform messy brainstorms into structured outlines with voice and personality reference/essay-style-pipeline.md
Agentic Search RAG agent training — teaching a model to search a corpus, select relevant documents, and answer grounded in sources reference/agentic-search-pipeline.md
Harness Distillation On-policy agent training — a small student acts, a reviewer passes or minimally corrects each step before it runs, and the result becomes per-turn SFT plus DPO pairs reference/harness-distillation-pipeline.md

The Universal Pipeline

All four case studies follow the same high-level pipeline, but diverge in dataset design and validation:

┌──────────────────────────────────────────────────────────┐
│  1. DEFINE THE CAPABILITY                                 │
│     What should the model do? What does good look like?   │
│     → Rubrics, schemas, specifications                    │
└────────────────────┬─────────────────────────────────────┘
                     │
                     ▼
┌──────────────────────────────────────────────────────────┐
│  2. CREATE TRAINING DATA                                  │
│     How do we generate enough high-quality examples?      │
│     → SynthChat scenarios, handcrafted seeds, self-play   │
└────────────────────┬─────────────────────────────────────┘
                     │
                     ▼
┌──────────────────────────────────────────────────────────┐
│  3. VALIDATE & IMPROVE                                    │
│     How do we ensure quality before training?             │
│     → Schema validation, rubric scoring, manual review    │
└────────────────────┬─────────────────────────────────────┘
                     │
                     ▼
┌──────────────────────────────────────────────────────────┐
│  4. TRAIN                                                 │
│     SFT first (learn the format), then KTO (learn         │
│     preferences), optionally GRPO (optimize rewards)      │
│     → Trainers with YAML config                           │
└────────────────────┬─────────────────────────────────────┘
                     │
                     ▼
┌──────────────────────────────────────────────────────────┐
│  5. EVALUATE                                              │
│     Does the model do what we trained it to do?           │
│     → Evaluator with YAML scenarios                       │
└────────────────────┬─────────────────────────────────────┘
                     │
                     ▼
┌──────────────────────────────────────────────────────────┐
│  6. ITERATE                                               │
│     What failed? Generate more data targeting weaknesses. │
│     → Failure analysis → targeted generation → retrain    │
└──────────────────────────────────────────────────────────┘

Read the full file on GitHub · 125 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 22d ago Changed · +3 lines · +14 tokens per session f4d4bcb5d2d9
  2. 2mo ago First seen · 122 lines · 114 tokens per session scan A 378235e6d6f1

Subscribe to this mod's changes

case-studies is a skill published in the GitHub repository ProfSynapse/Synaptic-Tuner (28 stars, last pushed 3d ago), licensed MIT. It adds 128 tokens to every session and 1,631 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

case-studies compared with skills from other repositories

case-studies next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
case-studiesProfSynapse/Synaptic-TunerSkill283d agoMITA128Claude Code
agent-platform-model-registrygoogle/skillsSkill22kyesterdayApache-2.0A60Claude Code, Codex
foundry-config-setupmicrosoft/agent-frameworkSkill15kyesterdayMITA65Claude Code, Codex
google-cloud-solution-agentic-analytics-spark-knowledge-cataloggoogle/skillsSkill22kyesterdayApache-2.0A132Claude Code, Codex
training-checkwanshuiyin/Auto-claude-code-research-in-sleepSkill19k3d agoMITA35Claude Code
nemo-automodel-launcher-configNVIDIA/skillsSkill3.9kyesterdayApache-2.0A30Claude Code
finetuningmicrosoft/skillsSkill3.2kyesterdayMITA132Claude Code