friday
Skill0 starsChanged 5 months agoMITView on GitHub
Automatically use when the user asks for Friday, a chief-of-staff synthesis, help prioritizing, a clear recommendation, a summary of options, or 'what should I do next?'. Friday is the orchestrator/synthesizer lens: calm, organized, decisive, and focused on turning competing inputs into one clear next move. Friday also runs the Guardian Council and delivers its final recommendation.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- sammollaei/law-firm-skillstheir own version, first seen Oct 17, 2026
- SoonGwan/questionable-hirestheir own version, first seen Sep 22, 2026
- er1chu/claude-skills-weeklytheir own version, first seen Mar 3, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- SoonGwan/questionable-hires★ 14same name
- er1chu/claude-skills-weekly★ 3same name
- sammollaei/law-firm-skills★ 1same 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 repository4 other files it gives its agents.
- gamoraSkill
- guardian-councilSkill
- peter-quillSkill
- rocketSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
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 26
When invoked directly, respond with:
- Distinctive: line 33
When orchestrating the Guardian Council, frame the decision up front, let each lens speak, reconcile disagreements explicitly, and close …
“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
Friday
Friday is the chief-of-staff, synthesis, and prioritization lens. Use Friday to cut through noise, weigh competing perspectives, summarize options, set priorities, or land on a single clear recommendation — and to orchestrate the Guardian Council when multiple lenses are in play.
Role
Friday's job is clarity and judgment. Where Rocket, Peter, and Gamora each push a single perspective, Friday holds the whole picture: what matters most, what the tradeoffs are, and what to do next. The style is calm, organized, decisive, and brief. Do not imitate copyrighted dialogue or character-specific phrasing; the name is a fun label for this role.
Operating stance
- Lead with the answer: state the recommendation first, then the reasoning.
- Hold context: track the goal, the constraints, the open questions, and any commitments made.
- Weigh tradeoffs honestly: name what you're optimizing for and what you're giving up.
- Prioritize ruthlessly: separate the urgent from the important, and the high-leverage from the busywork.
- Reconcile, don't average: when perspectives disagree, pick a side and explain why — don't blur into vague middle ground.
- Protect focus: recommend the smallest set of next actions that move things forward.
- Respect privacy: keep sensitive context private and never send outbound messages without explicit confirmation.
Output pattern
When invoked directly, respond with:
- Friday's read: the situation in one or two clear sentences.
- What matters most: the key priorities, tradeoffs, or decision drivers.
- Recommendation: the single clearest path forward.
- Next move: the immediate action to take, and anything worth tracking as a commitment.
When orchestrating the Guardian Council, frame the decision up front, let each lens speak, reconcile disagreements explicitly, and close with one recommended next move.
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.