tinyml-workflow-agent

A guided workflow for creating machine-learning models that run on small embedded devices such as microcontrollers. It covers preparing data, training and compiling a model, and deploying it to the device.

In plain words
What is it for?
Use it to validate datasets, extract features, create configuration files, train models, compile them, and deploy them to embedded hardware such as TI devices.
Why use it?
It organizes the many steps needed to move from a dataset to an embedded model, reducing setup mistakes and confusion about configuration and file locations.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/texasinstruments/tinyml-tensorlab/tinyml-workflow-agent
Any agent
npx skills add TexasInstruments/tinyml-tensorlab --skill tinyml-workflow-agent
Clone the repo
git clone --depth 1 https://github.com/TexasInstruments/tinyml-tensorlab

Made for: Claude Code, Codex.

Per session 86 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 8,681 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
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 $0.00086 $0.08681
Opus 5 $0.00043 $0.04340
Sonnet 5 $0.00017 $0.01736
Haiku 4.5 $0.00009 $0.00868

Measured 2d ago against content hash 1181835897d1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

tinyml-workflow-agent scanned grade C with 1 finding 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 2d ago.

The scan reads SKILL.md. This mod also ships 18 executable files (scripts/__init__.py, scripts/common_section_tools.py, scripts/compilation.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

- Delete the project: `rm -rf "$CCS_PROJECT_PATH"`
tinyml-agent-skills/plugins/tinyml-agent-skills/skills/tinyml-workflow-agent/SKILL.md · 789 lines

How it starts

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

Tiny ML Tensorlab Skill

Overview

Build, train, compile, and deploy ML models to embedded MCUs using Tiny ML tensorlab.


CRITICAL: Script and Path Locations

runner.py and SCRIPTS_DIR are in THIS SKILL directory, NOT in tinyml-tensorlab.

When setting up:

SCRIPTS_DIR=<path-to-this-skill>/scripts

# runner.py is at:
$SCRIPTS_DIR/runner.py

Do NOT use:

  • ~/tinyml-tensorlab/scripts/ (wrong — this doesn't exist)
  • ~/tinyml-tensorlab/tinyml-modelmaker/scripts/ (wrong)

Use:

  • ~/.claude/plugins/marketplaces/<plugin_name>/skills/<skill_name>/scripts/ (correct — this is the skill)

Workflow (13 steps):

  1. Session setup — load .env, activate venv, check for updates. If not set up, run /tinyml-agent-skills:setup first.
  2. Requirements — task type, device, data type, channel count
  3. Common section — task_type + target_device → save to WORK_DIR
  4. Dataset validation — validate format, get effective path
  5. Dataset section — generate YAML → save to WORK_DIR
  6. Feature extraction and Data Processing transforms
    • Step 6A: Analyze dataset for statistical insights
    • Step 6B: Get recommendations → generate YAML → save to WORK_DIR
  7. Model selection — analyze dataset size → rank models
  8. Training section — model name + hyperparams → save to WORK_DIR
  9. Testing section — testing config → save to WORK_DIR
  10. Compilation section — preset selection → save to WORK_DIR
  11. Assemble config — combine all sections → write config.yaml
  12. Run training — execute run_tinyml_modelzoo.sh
  13. Deploy to device — create CCS project → flash IMPORTANT: After EACH step which generates a section of the config file, pause and show the user the config file (created thus far) and proceed only with user's approval of the config. Reference guides (read on demand, not upfront):
  • references/config_creation_guide.md — task types, devices, YAML rules
  • references/example_running_guide.md — run commands, monitoring, troubleshooting
  • references/device_deployment_guide.md — CCS project, flashing, validation

Read the full file on GitHub · 789 lines

Files

What ships with it

31 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 2d ago First seen · 789 lines · 86 tokens per session scan C 1181835897d1

Subscribe to this mod's changes

tinyml-workflow-agent is a skill published in the GitHub repository TexasInstruments/tinyml-tensorlab (51 stars, last pushed 18d ago), licensed BSD-3-Clause. It adds 86 tokens to every session and 8,681 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens