DeepusleepyDeepusleepy/t3-tots/skills/t3-project-report/SKILL.md

t3-project-report

Skill110 starsChanged 18 days agoMITView on GitHub

Full HTML briefing of one T3 project. Use only for "catch me up on <project>", "what all happened in <project>", "brief me on <project>", "project report".

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-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

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:
Follow the t3-tots-rules skill (skills/t3-tots-rules/SKILL.md).
line 7

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

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". Read-only. The report is built on the box.

Computer: the one the user names, else the one the message came from. "Everywhere" means each connected computer.
Export from the tools folder: node export.js --project '<name|path|all>' --days 14 --out out/<Project>-export.json. Use --days 7 for "this week" and --days 30 for "this month". If the project isn't found, run t3ctl projects and ask. The export redacts keys and home paths.

CopyToBox the export to /workspace/t3-out/<Project>-export.json. If /workspace/t3-tots-tools/report/report.py is missing, run t3-install-tools "Box copy" first. Then, on the box:

python3 /workspace/t3-tots-tools/report/report.py /workspace/t3-out/<Project>-export.json /workspace/t3-out/<Project>-report.html --tz <user IANA tz>
google-chrome --headless=new --no-sandbox --disable-gpu --hide-scrollbars --window-size=1100,2400 --screenshot=/workspace/t3-out/<Project>-report.png file:///workspace/t3-out/<Project>-report.html

SendToUser the HTML and the PNG, then 3 to 5 lines: what moved, what's waiting on the user, and what's running or failing.

Download now (ZIP)

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

What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free