Improve any agent's Harness / Environment / Skills to use less tokens, perform evals stronger or create better traces
Built on Prime Intellect & NVIDIA Nemotron
Paste into your agent’s chat
Read https://techtree.sh/agents.md and help me test one of my Skills with Techtree. Ask me before any paid model call or before publishing anything.
Use the command line instead
Install, then look at your Skill
uv tool install --python 3.12 regents-cli==1.10.2
regents techtree forge inspect-skill path/to/your-skill
AgentWalletBench
Can a coding agent set up a wallet safely?
AgentWalletBench gives a coding agent a clean computer and asks it to install a wallet tool from the tool’s own page, set up a wallet it controls, say how its keys are kept, and prove control with a signature.
Everything the agent does is recorded, with secrets blanked before anything is kept. A judge model rules on each answer, and the bench checks any address and signature on Base itself. Use it to see which agents and wallet tools work together before you trust one with money.
- Agents
- Claude Code, Cline, Codex CLI, DeepSeek Harness, Hermes Agent, Kilo Code, OpenCode, Pi, Prime Agent, oh-my-pi
- Wallet tools
- Bankr, Circle, Coinbase Agentic Wallet, Foundry Cast, MetaMask Agent Wallet, MoonPay, Phantom, Privy, Safe, Splits, Turnkey, Zerion
- Each test
- Starts from the same identical cloud server on Fly.io Sprites
Turn know-how and real work into tasks agents can practice on, then see what actually helps them.
-
Skill2Env
ExperimentalWhat it does. Turns a Skill, the know-how written down for an agent, into a set of practice tasks with checks. Techtree reads the Skill without running it, plans tasks with you, builds and checks them on your computer, and you accept the final set.
Why. The task set is useful on its own: you can keep it, export it, or hand it to someone else to run, whether or not you go on to compare anything.
When to use it. You have a Skill and want to know whether agents follow it, or you want a fixed set of tasks to measure each change to it.
-
Repo2RLEnv
PlannedWhat it does. Turns a real repository and its history of fixes into practice environments, each one a past problem with a known good answer.
Why. Real bugs that were really fixed make realistic practice, and their own tests say whether an agent got it right.
When to use it. Your know-how lives in a codebase rather than a written Skill, or you want agents to practice on your own software’s real problems.
-
Tasksmith
What it does. The HF ML Tasksmith collection packages real changes to Hugging Face’s machine-learning libraries as tasks. Techtree’s Tasksmith Climb uses six of them to ask whether adding the Tasksmith Skill solves more.
Why. It is a ready-made test on serious code, so you can see a Skill comparison work without building tasks of your own first.
When to use it. You want to try Techtree on realistic machine-learning engineering, or measure your own Skill on the same six tasks.
-
FrontierSmith
ExperimentalWhat it does. Writes open-ended programming problems, each with its own checker that scores an answer from 0 to 1 rather than simply right or wrong. Techtree’s Frontier-CS Climb uses ten problems made with it.
Why. Open-ended problems have no single answer to memorise, so a better score means better work, and partial credit shows small gains a pass-or-fail test would miss.
When to use it. Your Skill is about solving hard problems well rather than following steps, and you want to see whether it raises the quality of the answers.
Only the Skill changes.
Techtree makes practice tasks from what your Skill teaches. Your agent then works the same tasks twice: once without the Skill, or with its earlier version, and once with it. The model, the tools and the limits stay the same, so any difference comes from the Skill.
Some tasks are held out from anyone improving the Skill. Their result is the one to trust when you ask “should I keep this change?”, because no revision could have studied them.
- 01 / TasksMade from your SkillYou review the plan and keep the tasks that work
- 02 / CompareRun twiceWithout the Skill or its earlier version, then with it
- 03 / DecideHeld-out tasksImproved, regressed, mixed or no difference
A quick look
See how a comparison runs.
The Hello World Climb ships with every release: a small, fixed set of tasks run once without a starter Skill and once with it. It shows how a run is approved, what it records and what a Result looks like. Its toy tasks say nothing about your own Skill.
It is Techtree Hello World, a small demonstration of how a Climb works rather than a measure of broad capability.
- Tasks
- 36 tasks, fixed before either run
- Harness
- hermes-agent v2026.9.24
- Checked
- 36 tasks validated
-
Frontier-CS Open-Ended
Ten open-ended optimisation problems with no known best answer, from Frontier-CS (MIT licence) as chosen by the FrontierSmith authors. With thanks to both.
-
Techtree Hello World
A toy introductory demonstration of the mechanism, not a measure of broad capability.
-
HF Tasksmith
Six real changes from Hugging Face's trl, transformers, diffusers, peft and accelerate repositories, from the HF ML Tasksmith collection. With thanks to its authors. Not a measure of broad capability.
Techtree is a working technical preview built from three independent parts: Prime Intellect’s Verifiers scores the tasks, Nous Research’s Hermes runs the agent, and Techtree runs the comparison and keeps the evidence.
Current release: v1.10.2 · sha256:7b1d88c51f7f… · Changelog
- Test a Skill: make tasks from it, then compare with and without it, or with its earlier version Experimental
- Revise a Skill once and compare the revision with it Experimental
- Try the Hello World Climb, a small fixed comparison with a starter Skill Available now
- Improve a Skill on ten open-ended Frontier-CS programming problems Experimental
- Tools for agents built into a browser (WebMCP) Available now
- Hosted environment building (Repo2RLEnv service) Planned
- An MCP connector for other agents Planned
- NVIDIA NeMo Fabric and NeMo Relay support Planned
Where the work goes
Your work stays local.
Techtree doesn’t watch your runs. Your work stays local unless you choose to publish the finished Result bundle. Model calls go to the model provider you run with, under that provider’s policies.