agent-feedback
Skill5 starsChanged 53 days agoMITView on GitHub
Use when locating the boss-assistant, or when the directory has none live and one needs to be opened.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- cypher0n3/dotagentstheir own version, first seen Oct 11, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- cypher0n3/dotagents★ 3same 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 repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- asking-peer-agentsSkill
- boss-assistantSkill
- boss-saySkill
- bringing-coworkerSkill
- choosing-graphSkill
- contacting-orchestratorsSkill
- create-great-harnessSkill
- dispatching-workSkill
- handoff-orchestratorSkill
- i-am-orchestratorSkill
- initSkill
- notifying-main-agentSkill
- peeking-workSkill
- reporting-to-userSkill
- resolving-appSkill
- shipping-taskSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Ask whether this session should take the role, unless the user already named a session for it.
≈ “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
Find it
List the directory through contacting-orchestrators.
The current assistant is the row with role set to boss-assistant and live: true.
A row that carries the role but is not live is a dead claim; treat the role as unclaimed, not as identifying that row.
More than one live row carrying the role is a registration race: ask the user which one to keep, and release the others with --release-role from their own sessions.
Open one when none exists
Ask whether this session should take the role, unless the user already named a session for it. This session claims it, alongside its own scope:
uv run --script "${CLAUDE_PLUGIN_ROOT}/scripts/register-orchestrator.py" \
--scope '<one line describing this session's main work>' --role boss-assistantFor a separately approved window instead, use handoff-orchestrator; the receiver claims the role with the same command once it accepts.
Release it
A session that stops holding the role drops it without rewriting its scope:
uv run --script "${CLAUDE_PLUGIN_ROOT}/scripts/register-orchestrator.py" --release-roleComplete when: the assistant is identified live and reachable, or a fresh claim is registered and confirmed in the directory.
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.