nesting-review
Skill0 starsChanged 19 days agoMITView on GitHub
Review a new agent's nesting or onboarding week (volume, QA, AHT, CSAT, escalations), decide on_track / at_risk / extended / graduate, and draft the weekly feedback email. Use when the user mentions nesting, onboarding week, new hire ramp, graduation to production, or shares the nesting tracker.
In this repository3 other files it gives its agents.
- calibrationSkill
- coaching-noteSkill
- qa-reviewSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 12
Read this week's row and the previous weeks for the same agent.
- Distinctive: line 18
Keep the email under 200 words.
≈ “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
Nesting review
Playbook and targets: ${CLAUDE_PLUGIN_ROOT}/templates/nesting-playbook.md. Tracker format: ${CLAUDE_PLUGIN_ROOT}/templates/nesting-tracker.csv.
Procedure
- Read this week's row and the previous weeks for the same agent. Trend matters more than one number.
- Compare to the week's targets from the playbook, or to the user's own targets if they give them.
- Decide the status with the playbook rule: all targets met → on_track; one missed with a plan → at_risk; week 4 with one target missing → extended (one week, one plan); week 4 with two or more missing → escalate to the manager, do not extend silently.
- Draft the weekly feedback email in the playbook's shape: verdict in the first paragraph and the last line, two specifics that went well with ticket ids, one thing to work on, the numbers, next week's plan.
- Append the tracker row the user should paste, including status and blocker.
Keep the email under 200 words. Agents in their second week do not need a performance review, they need to know whether they are okay and what one thing to do next.
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.