agentleFS
Sign inStart free
DeepusleepyDeepusleepy/t3-tots/skills/t3-handoff/SKILL.md

t3-handoff

Skill110 starsChanged 18 days agoMITView on GitHub

Hand a T3 thread's work to a Cursor cloud agent that returns a branch and a PR. Use for "send to cursor", "hand off <thread> to cursor", "let a cloud agent finish <thread>", "run this in the cloud", "make a PR from <thread>".

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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
  1. Very specific:

    Follow the t3-tots-rules skill (skills/t3-tots-rules/SKILL.md).

    line 8
  2. Distinctive:

    Stop and tell the user when there's no GitHub remote, or when the task needs uncommitted changes.

    line 13

≈ “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 on the user's computers. Launch only after the user confirms the brief.

1. Gather

  1. Find the thread as in t3-tots-rules "Finding a thread", with T3_LAST=20. An empty T3_Q picks the most recent user thread.
  2. In the working folder, run git -C <dir> status --porcelain, git -C <dir> remote get-url origin and git -C <dir> log -1 --oneline. On a detached HEAD, ask for the base branch.
  3. Stop and tell the user when there's no GitHub remote, or when the task needs uncommitted changes. The cloud agent can't see them, so ask the user to commit and push first.

2. Brief

Repo: <owner/name>   Base branch: <branch>
Goal: <1 or 2 sentences from the whole thread>
Context: <decisions, constraints, files and areas, conventions from AGENTS.md or CLAUDE.md>
Current state: <what's done, the head commit>
Task: <the next concrete steps>
Done when: <checks that must pass>
Deliver: a new branch and a PR against <base>. Do not merge.

Strip secrets, tokens, personal paths and personal data from the brief.

3. Launch

  1. Show the brief and ask "Send this to Cursor?".
  2. On yes, start a CloudAgent on the full GitHub URL and the base branch. Set project: true only if the user asks for a project. If source control isn't connected, ask the user to connect GitHub.
  3. Report the agent link. When it's done, report the branch, the PR and a 3-line summary. Never merge.

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