buddy
/buddy
Wskazuje, które skille tt-buddy użyć przy zadaniach tt-metal, tt-inference i vllm oraz jakie artefakty powstają.
- Autor
- tenstorrent ↗
- Repozytorium
- skills ↗
- Licencja
- Apache-2.0
- Ostatnia zmiana repozytorium
- 23.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 4
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 23.10.2026, bez odwołań do wycofanych modeli i API.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
Co robi i kiedy
Wskazuje, które skille tt-buddy użyć przy zadaniach tt-metal, tt-inference i vllm oraz jakie artefakty powstają.
Oryginalny opis (EN)
Use when starting any tt-metal, tt-inference, or vllm-tt-plugin task — a coding agent with Tenstorrent operating principles. Lists the tt-buddy skills, when to invoke each, and the artifacts they produce.
Jak działa
- The Rule
- Dispatch Table
- Plugin root
- Repo recipes
- Red Flags
- Artifacts
- Host mapping
- Skill Invocation Pattern
- Always-on writing rules
- Source of Truth
Podgląd SKILL.md
--- name: buddy description: Use when starting any tt-metal, tt-inference, or vllm-tt-plugin task — a coding agent with Tenstorrent operating principles. Lists the tt-buddy skills, when to invoke each, and the artifacts they produce. --- <EXTREMELY-IMPORTANT> If you work in tt-metal, tt-inference-server, or vllm-tt-plugin, and a tt-buddy skill has even a 1% chance to apply: you MUST invoke it (§ Host mapping). This is not optional. You cannot rationalize your way out of it. </EXTREMELY-IMPORTANT> ## The Rule - **Invoke the matching skill BEFORE any response or action.** - A 1% match is enough. - Wrong skill for the situation: you are released. - NEVER skip the check. ## Dispatch Table Invoke per § Host mapping. | Task signal | Skill | |---|---| | Run/test on device, `pytest`, vllm-tt-plugin server lifecycle | `tt-buddy:run` | | "How does X work" / "what are the knobs for Y" | `tt-buddy:learn` | | Finding, observation, plan, or status update | `tt-buddy:note` | | Create, edit, or audit a tt-buddy skill | `tt-buddy:skill-creator` | No row matches: not tt-buddy work. Use default tools. ## Plugin root - `<plugin-root>` is the tt-buddy plugin directory. - The session hook states its absolute path. - No hook output: two directories above this skill's base directory. - Resolve every `<plugin-root>/...` path against it. ## Repo recipes - `<plugin-root>/recipes/<repo>/` holds build, test, env steps. - **MUST Read** the matching recipe before acting. - NEVER use `cmake`, `ninja`, `make`, or direct C++ binaries. ## Red Flags These thoughts mean STOP: | Thought | Reality | |---|---| | "I'll just grep the codebase quickly" | Use `tt-buddy:learn`. It writes a reusable note. | | "I'll put my notes in chat" | Use `tt-buddy:note`. Future sessions resume from notes. | | "Not worth a note" | Note it. Notes are cheap; lost findings are not. | | "I'll run pytest directly" | Use `tt-buddy:run`. Bare pytest skips the device queue. | | "I'll run pkill / tt-smi -r myself" | Use `tt-buddy:run` recovery. Wrong order wedges the device. | | "I'll also clean this up" | NEVER. Keep the diff minimal. | | "This is a simple question" | Questions are tasks. Check the table. | | "Let me explore first" | Skills tell you how to explore. Check first. | | "I remember this skill" | Skills change. Load the current version. | | "I'll skip the discipline once" | The discipline is the value. | ## Artifacts - All work product lives in `~/.tt-buddy/notes/`. - It is a git-tracked timeline, one file per topic. - Write entries only via `tt-buddy:note`. - Notes point to source-repo branches and commits. - Branch names: `<user>/<workflow>/<scope>-<date>`. - Skills NEVER push commits. ## Host mapping | Action | Do | |---|---| | Invoke a skill | Host skill tool. None: read its whole `SKILL.md`, follow it | | Subagent | Host subagent tool, general-purpose type. None: run inline | | MCP tool `<tool>` on server `<server>` | The host's tool for `<tool>` from `<server>`, whatever its prefix | ## Skill Invocation Pattern When a skill says "invoke `tt-buddy:learn`" or similar: 1. **Invoke per § Host mapping.** NEVER paraphrase the skill. 2. **Pass the args** the skill specifies. 3. **Wait for its output** before the next step. 4. **Record the result** via `tt-buddy:note` when required. ## Always-on writing rules Apply to every artifact: chat, commits, code. - **Tone & Voice:** `tone.md`. The session hook loads it every prompt. No hook output: MUST Read it now. - **Commit Messages:** before any `git commit`, MUST Read `commit-messages.md`. - **Code Comments:** before editing source code, MUST Read `code-comments.md`. Paths are relative to this skill's directory. ## Source of Truth - Canonical content: the installed `<plugin-root>/skills/<name>/`. - NEVER fetch skill content from the web. - Installed skill unreadable: stop and report. - A skill conflicts with this primer: the skill wins. - User instructions (host instruction files, messages) override everything.
Pliki w paczce (4)
- SKILL.md 4 KB
- code-comments.md 1 KB
- commit-messages.md 1 KB
- tone.md 1 KB
Wersje
W bazie nie ma innych skilli o nazwie buddy.
Migawka bazy z 13.11.2026 · wersja paczki 47b17367b4d1 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100skill-creator
Projektuje skille systemu tt-buddy: najpierw uzgadnia założenia, potem pisze je według konwencji TT, także przy przeglądzie. - 90tt-vllm-serving-review
Przegląda ścieżkę serwowania vLLM i tt-inference-server: kontrakty generator_vllm.py, rejestrację wtyczki i konwencje gałęzi i konfiguracji. - 90om-merge-buddy
Tylko do odczytu wskazuje, które pull requesty można scalić, oceniając etykiety, recenzje, CI i możliwość scalenia oraz zgłaszając te prawie gotowe. - 100buddy-program-manager
Prowadzi rejestr programu buddy dla onboardingu: nowy pracownik, przypisany buddy, dział, daty początku i końca, zaplanowane i odbyte spotkania oraz ocena opinii. - 100buddy-program-manager
Prowadzi rejestr programu buddy dla onboardingu: nowy pracownik, przypisany buddy, dział, daty początku i końca, zaplanowane i odbyte spotkania oraz ocena opinii. - 100code-buddy
Obsługuje Code Buddy, wielodostawcze CLI agenta kodowania buddy: tryb headless dla pojedynczego promptu, lokalne modele Ollama lub płatne, autonomiczna edycja plików, serwer HTTP i pętla floty agentów.