tt-studio: Skill for Claude Code

.claude/skills/draft-release-notes/SKILL.md

draft-release-notes is a skill for Claude Code from tenstorrent/tt-studio. It costs 121 tokens per session (1,290 once invoked), scanned A, original, Apache-2.0.

A workflow for drafting TT-Studio GitHub release notes by studying earlier releases and comparing the current release branch with the previous version. Release notes summarize changes shipped in a software version.

In plain words
What is it for?
Use it when preparing notes for a specified TT-Studio release, grouping changes into features, bug fixes, and technical improvements, and matching the project’s house style.
Why use it?
It keeps new release notes consistent with the project’s established structure and ties them to actual code changes.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is tenstorrent/tt-studio's own configuration. It tells Claude Code how to work on tt-studio 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 tt-studio configures β†’

Reuse

Borrowing it

Nothing to install: this file belongs to tenstorrent/tt-studio. 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/tenstorrent/tt-studio/main/.claude/skills/draft-release-notes/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/tenstorrent/tt-studio

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 draft-release-notes

README.md
[![agentmods](https://agentmods.dev/badge/skills/tenstorrent/tt-studio/draft-release-notes/github.svg)](https://agentmods.dev/skills/tenstorrent/tt-studio/draft-release-notes)
Your own site
<a href="https://agentmods.dev/skills/tenstorrent/tt-studio/draft-release-notes"><img src="https://agentmods.dev/badge/skills/tenstorrent/tt-studio/draft-release-notes/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 draft-release-notes

Your own site Β· 80Γ—15
<a href="https://agentmods.dev/skills/tenstorrent/tt-studio/draft-release-notes"><img src="https://agentmods.dev/badge/skills/tenstorrent/tt-studio/draft-release-notes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 121 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,290 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.00121 $0.01290
Opus 5.5 $0.00048 $0.00516
Sonnet 5.5 $0.00024 $0.00258
Haiku 4.5 $0.00012 $0.00129

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

Security

Grade A, and why

draft-release-notes 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 2mo 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.

.claude/skills/draft-release-notes/SKILL.md Β· 134 lines

How it starts

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

TT-Studio Release Notes Drafting

Follow this when asked to draft release notes for a new TT-Studio version. The goal is notes that read exactly like the previous few releases β€” same sections, same voice, same level of detail β€” built from the actual changes on the release branch.

Inputs to confirm

  • New version (e.g. v2.9.0) and the release branch (e.g. rc-v2.9.0).
  • Previous version it ships after (e.g. v2.8.0). If not given, it's the most recent published GitHub release.

If the user names a branch, use it. Don't guess a version β€” ask if unclear.

The release PR into main is titled Rc vX.Y.Z (the Lint PR title check is skipped for rc-* head branches) or release: vX.Y.Z β€” see CONTRIBUTING β†’ Release Process. Step 2 relies on that Rc vX.Y.Z merge-commit title as the cutoff.

Step 1 β€” Study the previous releases (match the style, don't invent it)

Read the most recent two or three published release descriptions so the new one matches their structure and voice:

# needs no auth:
WebFetch https://github.com/tenstorrent/tt-studio/releases

The established house style is:

  • A header line: ## :rocket: TT Studio <version> is out!
  • A lead-in: A few highlights since <previous version>:
  • Three sections, in this order, each only if it has content:
    • ### πŸš€ New Features β€” bold feature name + one-line description
    • ### πŸ› Bug Fixes β€” one line each, past tense ("Fixed…", "Resolved…")
    • ### πŸ”§ Technical Improvements β€” internal/infra/CI/refactor/dep bumps
  • A closing Full changelog β†’ <link> line.

Bold-name-plus-description is the signature of the New Features section β€” keep it. Bug Fixes and Technical Improvements are plain one-liners.

Step 2 β€” Gather the actual changes

Fetch the release branch and list every commit since the previous release. Each release's RC merge commit is titled like Rc vX.Y.Z (#NNNN) β€” the previous release's merge commit is the cutoff; everything above it is new.

git fetch origin <release-branch>
git log origin/<release-branch> --oneline -60

Read the full file on GitHub Β· 134 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. 2mo ago First seen Β· 134 lines Β· 121 tokens per session scan A f365611f9ad9

Subscribe to this mod's changes

draft-release-notes is a skill published in the GitHub repository tenstorrent/tt-studio (52 stars, last pushed yesterday), licensed Apache-2.0. It adds 121 tokens to every session and 1,290 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

draft-release-notes compared with skills from other repositories

draft-release-notes next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
draft-release-notestenstorrent/tt-studioSkill52yesterdayApache-2.0A121Claude Code
material-ui-nextjsmui/material-uiSkill99kyesterdayMITA76Claude Code, Codex
git-safetytamagui/tamaguiSkill14ktodayMITA0Claude Code
release-safetytamagui/tamaguiSkill14ktodayMITA0Claude Code
dev-fixHoangNguyen0403/agent-skills-standardSkill583yesterdayMITA43Codex
triaging-merge-queue-failuresPostHog/posthogSkill41kyesterdaynoneA180Claude Code, Codex
debugging-table-access-deniedPostHog/posthogSkill41kyesterdaynoneA73Claude Code, Codex