agy-delegation
Skill61 starsChanged 5 months agoMITView on GitHub
Use when analyzing large files (>200 lines), more than 3 files at once, deep git/grep searches, web lookups, or adversarial reviews - delegates to the Antigravity CLI via agy-bridge MCP tools to save context.
3 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- Haruhiko-Joe/skillstheir own version, first seen Nov 15, 2026
- PyModel/claude-agy-mcpedited, first seen Nov 15, 2026
- papagrationbiz-sketch/token-scroogetheir own version, first seen Oct 15, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- PyModel/claude-agy-mcp★ 817% same
Wrote their own version · 2
- Haruhiko-Joe/skills★ 6same name
- papagrationbiz-sketch/token-scrooge★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repositoryOne other file it gives its agents.
- CLAUDE.mdCLAUDE.md
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use the agy-bridge MCP tools instead of doing heavy work yourself:
- Very specific: line 20
Every response ends with [agy-bridge] model: … | session: ….
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Delegating to Antigravity CLI
Use the agy-bridge MCP tools instead of doing heavy work yourself:
| Situation | Tool |
| File >200 lines, logs, dumps, generated code | analyze_files |
| >3 files in one task | analyze_files |
| Git history / repo-wide search | deep_search |
| Docs or external knowledge | web_lookup |
| Plan critique, code review | adversarial_review |
| Follow-up on a prior delegation | follow_up (use the returned session id) |
| Anything else heavy | delegate |
Every response ends with [agy-bridge] model: … | session: …. Reuse the
session id with follow_up for iterative work — the context stays on agy's
side. Pass cwd as the project root so agy can read files and run git.
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.

