t3-get-output
Skill110 starsChanged 18 days agoMITView on GitHub
Have a T3 thread make an artifact (image, HTML, video, doc) or fetch the files or diff a thread produced, and bring them into chat. Use for "make me a <thing> and send it here", "get me the file from <thread>", "send me what <thread> made", "diff of <thread>".
- Reads credentials
In this repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- t3-checkupSkill
- t3-cleanupSkill
- t3-digestSkill
- t3-getting-startedSkill
- t3-handoffSkill
- t3-install-toolsSkill
- t3-new-threadSkill
- t3-phone-answersSkill
- t3-pm-threadSkill
- t3-project-reportSkill
- t3-project-trackerSkill
- t3-save-learningsSkill
- t3-statusSkill
- t3-syncSkill
- t3-templatesSkill
- t3-thread-actionsSkill
- t3-tots-rulesSkill
- t3-updateSkill
- t3-usageSkill
- t3-waitingSkill
- t3-watchSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Follow the t3-tots-rules skill (skills/t3-tots-rules/SKILL.md).
- Very specific: line 13
Write the prompt to a file (t3-tots-rules "Sending into threads").
- Very specific: line 14
Start it: t3ctl new --project '<P>' --model <m> --effort <e> --title '<short>' --prompt-file <file> --wait --timeout 600.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Follow the t3-tots-rules skill (skills/t3-tots-rules/SKILL.md). Steps that use the box, ListMachines, routines, cards or SendToUser are Grok Bot only; other agents follow t3-tots-rules "Grok Bot only". Send only the prompt the user asked for.
1. Make it (skip when fetching)
- Resolve the computer, project and model as in t3-new-thread. Throwaway asks go to the user's sandbox project, from memory (ask once and save it if unknown), with
--model haiku --effort low. - Write the prompt to a file (t3-tots-rules "Sending into threads"). Ask for one output path and no other changes: "
<ask>. Save it as<subdir>/<name>.<ext>in this project. Do not change any other files. Reply with the path." - Start it:
t3ctl new --project '<P>' --model <m> --effort <e> --title '<short>' --prompt-file <file> --wait --timeout 600. For long renders, leave out--waitand check later witht3ctl read.
2. Fetch
t3ctl files --thread '<t>' --last-turncopies the files the last turn created or changed into<tools folder>/out/, keeping each file's path inside the project (out/src/index.ts), so files with the same name don't overwrite each other. Leave out--last-turnfor the whole thread. It never copies dotfiles or dot folders (.env,.ssh,.gnupg), files whose path names a token, auth or oauth (as a word:author.mdis fine), secret, credential, password, keychain or private key, key files (id_rsa,id_ed25519,.pem,.p12,.key), symlinks, or files outside the project; it lists them as not copied.- A file that only changed while the run was going, with nothing showing this thread made it, is also listed as not copied, because another session may have made it. So is a hard link, because its content may live outside the project. Show those to the user and copy only the ones they pick:
t3ctl files --thread '<t>' --include '<path>[,<path>]'. - Files outside the project appear only if a reply names them. Take the path from
t3ctl read. t3ctl diff --thread '<t>'gives the diff in a git project.- For videos and other files already on the computer, CopyToBox them directly.
3. Send
- CopyToBox to
/workspace/t3-out/<name>. - For HTML or SVG, make a preview:
google-chrome --headless=new --no-sandbox --disable-gpu --window-size=1000,700 --virtual-time-budget=1500 --screenshot=/workspace/t3-out/<name>.png file:///workspace/t3-out/<name>.html. - SendToUser the files and the preview, then one line: the thread, the model, and the path on their computer.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

