t3-templates
Skill110 starsChanged 18 days agoMITView on GitHub
Saved T3 prompt templates with {vars}. Use for "run template <name>", "list templates", "save this as a template", "use my <name> template on <project>", "edit my <name> template".
In this repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- t3-checkupSkill
- t3-cleanupSkill
- t3-digestSkill
- t3-get-outputSkill
- 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-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
1 rule. About 0 are common, 0 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Follow the t3-tots-rules skill (skills/t3-tots-rules/SKILL.md).
≈ “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). Run only the template the user names.
Templates live in <tools folder>/templates.md. Each template is one ## <name> section with project:, model:, effort:, status: suggested|active and a fenced prompt that uses {vars}.
- Run: fuzzy-match the name and fill the {vars} from the message. Ask for any that are missing. Project, model or effort in the message override the template. Write the filled prompt to a file (t3-tots-rules "Sending into threads") and send it with t3-new-thread, with
--title '<template>: <short>'. Reply with the thread title and id. If the template wassuggestedand the run went fine, ask whether to mark itactive. - List: name, purpose, model and status.
- Save: turn the given prompt, or a named thread's first prompt, into a template with {vars}. Show it and write it after an OK.
- Suggest: when the user sends the same kind of prompt 3 or more times, offer a template with
status: suggested. - Edit or remove a template only when the user asks.
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.