Tinker Ai Skill logo

Tinker Ai Skill

Community
drost-ai
tinker-ai-skill

Turn your own coding-agent session transcripts (Claude Code JSONL) into a supervised fine-tuning dataset and train a LoRA on Tinker with the tinker-cookbook. Use when the user wants to fine-tune a model on their agent sessions, build an SFT dataset from transcripts, anonymize or de-identify transcripts, slice long sessions to a context length with compaction context, or train and evaluate on Tinker. Covers collection, cleaning (secrets, PII, paths), chunking, train/val splits, training, sampling, and the pitfalls that cost us runs.

Overview

Publisherdrost-ai
Repositorytinker-ai-skill
Skill nametinker-ai-skill
Stars
318
Forks
39
Bundled files
20
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 20 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by drost-ai on GitHub. Read the source before you install it.

Installation

Install the Tinker Ai Skill AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/drost-ai/tinker-ai-skill/tree/main
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/drost-ai/tinker-ai-skill.git \
  .claude/skills/tinker-ai-skill
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Tinker Ai Skill in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Tinker Ai Skill on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Tinker Ai Skill is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Fine-tune a coding model on your own agent transcripts (Tinker)

You are helping someone turn the sessions they already ran with a coding agent into training data, and fine-tune an open model on it with Tinker. This skill distils a pipeline that shipped several public models. Follow the steps in order; each script is small, offline unless stated, and prints what it did.

All commands below run from this skill's directory (tinker-ai-skill). Read references/ when a step needs judgement; the scripts' docstrings (python scripts/<name>.py --help) explain every flag.

Before you start

  1. Keep the transcripts. Claude Code deletes transcripts after 30 days by default. Tell the user to add "cleanupPeriodDays": 3650 to ~/.claude/settings.json now.
  2. Keys. Copy .env.example to .env and fill in TINKER_API_KEY (console at tinker.thinkingmachines.ai) and WANDB_API_KEY (wandb.ai/authorize). Never print, commit, or paste these values anywhere; the scripts read .env.
  3. Environment. uv venv && uv pip install -r requirements.txt (or pip install -r requirements.txt). Python 3.11+. Use that interpreter for every script.
  4. Budget. Training costs tokens x price. Always run a script's default (offline) mode first; only --train, sample_checkpoint.py and export_checkpoint.py touch the service. Confirm the estimated cost with the user before launching.
  5. For local serving (steps 8-9). A built llama.cpp checkout recent enough for the model's architecture, disk for the base model plus the merged copy (about 2 bytes per parameter each), and RAM for the largest shard.

The workflow

Step 1. Collect transcripts into a dataset location

python scripts/collect_sessions.py --data-dir ./data            # ~/.claude/projects by default
python scripts/collect_sessions.py --data-dir ./data --project my-repo --since 2026-01-01

Copies main-session files verbatim (no subagent sidechains), skips tiny sessions, records sha256s in data/originals/manifest.json. Use --exclude-slug for projects that must never leave the machine (client work, security research).

Step 2. Clean: normalize, then remove secrets and identity

python scripts/normalize_sessions.py --data-dir ./data
python scripts/anonymize_sessions.py --data-dir ./data --identity-file identity.json

normalize_sessions.py turns the raw records into OpenAI-style messages: user text the person typed, assistant text and plaintext thinking, tool calls with their JSON arguments, tool results clipped to head+tail. It drops harness-injected text, sidechains, API-error placeholders, thinking signatures and image bytes, and verifies every tool call is answered. See references/claude-code-transcripts.md.

anonymize_sessions.py first replaces credentials by value across the whole corpus (one marker per value), then de-identifies each session with its OWN random identity: home username, top-level folders under the home directory, project slugs, and every name/email/handle/org/domain listed in the identity file. Write that file with the user (their username, full name, emails, GitHub handle, company). The run fails if any listed string or credential candidate survives. Read the printed list of detected usernames; pass --keep-username for service accounts that are not a person. Why per-session randomization and not one fixed fake world: references/anonymization.md.

Inspect a few anonymized rows with the user before continuing. Only the user can judge whether something is still sensitive.

Step 3-5. Slice to the context length, add compaction context, split train/val

python scripts/build_dataset.py --data-dir ./data --model Qwen/Qwen3.6-35B-A3B --max-len 65536 \
    --system-prompt-file assets/system-prompt.md

Pick --model from Tinker's model list and --max-len from that model's context column (64K base variants; :peft:262144 variants take 256K). The builder measures every row with the real renderer and tokenizer of that model, so rebuild when you change models: a tokenizer change moved our rows by 14% and overflowed the budget.

  • Windows never split a tool call from its result and never open on a tool message.
  • Slice 0 carries the system prompt plus the working directory. Every later slice carries the same prompt followed by a deterministic <working_context> block (original request, recent requests, files touched, commands, task state, a trace of the last few messages) and, when the window opens mid-turn, a short "continuation" user message. This is the compaction the model will see in a real long session. Details: references/chunking-and-compaction.md.
  • Tool definitions are declared on every row. Pass --tools-file with the real definitions of the harness the model will serve in; without it, minimal schemas are inferred from usage. Rows without tool definitions regressed tool use for us.
  • Hybrid-thinking renderers are rebuilt to keep thinking in history (otherwise earlier turns train on empty think blocks). For Inkling models pass --effort (default 0.9) and use the same value at serving time.
  • The split is by whole session, seeded, so rebuilds hold out the same sessions.

Report: data/datasets/<name>.report.json (rows, tokens, loss tokens, sha256s, rendering provenance). The trainer refuses a dataset whose provenance differs.

Step 6. Fine-tune on Tinker

python scripts/train_tinker.py --data-dir ./data --name qwen3.6-35b-a3b-64k            # offline smoke test
python scripts/train_tinker.py --data-dir ./data --name qwen3.6-35b-a3b-64k --train    # launch

The smoke test renders every row, prints the decoded head of a row (read it: system prompt, tool declaration, user turn), steps per epoch and total tokens. Multiply tokens by the model's train price from Tinker's pricing page and tell the user the estimate before --train.

Defaults: LoRA rank 32, batch 8 rows, 2 epochs, linear decay, eval and checkpoint every 20 steps, W&B project agent-transcript-sft. Learning rate comes from Tinker's calibrated get_lr for Qwen/Llama; for Inkling, Nemotron, DeepSeek, Kimi and GLM you must pass --learning-rate (ranges and evidence in references/tinker-training.md). When in doubt run two short runs, 1e-4 and 3e-4, and compare behaviour, not loss.

While it runs: confirm the first metrics reach W&B, watch test/nll at steps 20 and 40 (a dip then a rise means the LR is too hot for this batch; stop and lower it), and never wrap Tinker calls in your own timeouts or retries.

Step 7. Check behaviour and pick a checkpoint

python scripts/sample_checkpoint.py --data-dir ./data --name qwen3.6-35b-a3b-64k \
    --checkpoint tinker://<run-id>/sampler_weights/000100 --prompt "Find and fix the failing test."

Compare base vs checkpoints on prompts from the user's real work. Judge by behaviour (valid tool calls, non-empty thinking, follows the system prompt), not by NLL: a falling loss hid a behaviour regression for us twice. Pick the checkpoint by an eval.

Step 8. Download the LoRA and merge it into the base model

python scripts/export_checkpoint.py --run-dir ./runs/<run> --checkpoint 000100 \
    --base-model Qwen/Qwen3.6-35B-A3B --out ./export/my-coder --trust-remote-code

Reads checkpoints.jsonl, downloads the training checkpoint (sampler checkpoints cannot be downloaded; periodic ones expire after 7 days, so export before then), merges it with the cookbook's build_hf_model into a standalone bf16 HuggingFace directory, copies generation_config.json, and prints the chat-template kwarg that restores the training conditioning (earlier-turn thinking kept). --peft additionally writes a PEFT adapter for vLLM or SGLang. --dry-run shows the plan without contacting Tinker. Details and memory needs: references/export-and-serve.md.

Step 9. Convert to GGUF and run with llama.cpp

LLAMA_CPP=~/src/llama.cpp scripts/make_gguf.sh ./export/my-coder/hf-merged ./export/my-coder/gguf my-coder Q4_K_M Q8_0
scripts/serve_gguf.sh ./export/my-coder/gguf/my-coder-Q4_K_M.gguf

make_gguf.sh converts to BF16 GGUF with the checkout's convert_hf_to_gguf.py, quantizes with the llama-quantize built from the same commit, exports the vision projector when the model has one, and optionally the MTP draft head (MTP=1). serve_gguf.sh starts llama-server with the settings that match training: --jinja, --reasoning-preserve, the template kwarg for preserved thinking, a context of at least the training window, and the base model's sampling defaults (temperature 1.0, top-p 0.95, top-k 20, min-p 0). Smoke-test one prompt with a tool before trusting it, then benchmark against a same-recipe base GGUF.

Rules that saved us the most time

  • Never hardcode a renderer name; resolve it from the model with model_info.get_recommended_renderer_name. Never reuse a dataset rendered for one model with another model.
  • Never anonymize with one constant fake world. Randomize per session.
  • Never train rows without the system prompt and tool definitions the model will be served with.
  • Never trust a loss curve alone. Sample.
  • Never serve with a chat template that strips earlier-turn thinking when training kept it, and never with llama.cpp's default min-p: match the template kwarg and the base model's sampling defaults.
  • Never put data, .env, run or export directories in a public repo: the pack's .gitignore covers data/, runs/, export/, wandb/, .env.

Adapting to other agents

The normalizer reads Claude Code's JSONL. For Codex, OpenCode or your own harness, write a normalizer that emits the same per-session file (references/claude-code-transcripts.md documents the message schema); every later step is format-independent.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Tinker Ai Skill AI skill do?

Turn your own coding-agent session transcripts (Claude Code JSONL) into a supervised fine-tuning dataset and train a LoRA on Tinker with the tinker-cookbook. Use when the user wants to fine-tune a model on their agent sessions, build an SFT dataset from transcripts, anonymize or de-identify transcripts, slice long sessions to a context length with compaction context, or train and evaluate on Tinker. Covers collection, cleaning (secrets, PII, paths), chunking, train/val splits, training, sampling, and the pitfalls that cost us runs.

Why use Tinker Ai Skill on TypingMind?

Because you install it once and use it with any model. Tinker Ai Skill is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Tinker Ai Skill in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/drost-ai/tinker-ai-skill/tree/main. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Tinker Ai Skill?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Tinker Ai Skill?

As many as you like. As long as a model supports skills, you can use Tinker Ai Skill with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Tinker Ai Skill AI skill free?

Yes. It is published on GitHub by drost-ai under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇