briefing
Skill0 starsChanged 8 months agoMITView on GitHub
Monday morning intelligence briefing. Scans competitors, news, market signals, customer data. Synthesizes into a 2-minute ranked summary with recommended actions. Octopus colors: Yellow (research) + Purple (synthesis).
19 other projects use a version of this.
Adopted by
Most recently taken up by
- PatrickSUDO/fadacai-portfoliotheir own version, first seen Nov 13, 2026
- adeonir/agent-skillstheir own version, first seen Nov 10, 2026
- gustaferiksson/skillstheir own version, first seen Nov 8, 2026
- parker-brown-family/agent-skillstheir own version, first seen Nov 8, 2026
- Getty/briefingtheir own version, first seen Nov 8, 2026
- flopperj/dotfiles-coretheir own version, first seen Nov 5, 2026
Used with
Projects with it also use handoff and grill-me.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- garrytan/gbrain★ 33ksame name
- PatrickSUDO/fadacai-portfolio★ 145same name
- google-gemini/gemini-managed-agents-templates★ 99same name
- norrietaylor/distillery★ 25same name
- bks-lab/open-bridge★ 13same name
- adeonir/agent-skills★ 8same name
- GavinGreenwood/agentic-workflow-template★ 5same name
- Getty/briefing★ 5same name
- Erionis/Jarvis-Lite★ 3same name
- flopperj/dotfiles-core★ 3same name
9 more not listed
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.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
3
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 14
Read .chairman/config.json for organization context and industry
- Distinctive: line 15
Read department knowledge bases for current priorities and active deals
- Distinctive: line 46
If using web search, cite sources.
- Distinctive: line 47
If $ARGUMENTS provided, focus the briefing on that area.
- Very specific: line 49
Update .chairman/state.json with last_session date.
“Common” is measured: kept by at least 6 in 10 of the 16 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
/briefing: Monday Intelligence Briefing
Octopus Colors: Yellow (Researcher) + Purple (Manager)
Process
- Read
.chairman/config.jsonfor organization context and industry - Read department knowledge bases for current priorities and active deals
- Research (Yellow agent work):
- Competitor activity (social, pricing, product launches)
- Industry news relevant to this business
- Market signals (trends, regulatory changes, opportunities)
- Customer signals from any available data (CRM notes, recent interactions)
- Synthesize (Purple agent work):
- Rank findings by urgency and business impact
- Filter noise: only include items that require awareness or action
- Format as a scannable briefing
Output Format
# Intelligence Briefing: [Date]
## Action Required (respond today)
- [Item]: [Why it matters]. Recommended: [action]
## Awareness (no action needed yet)
- [Item]: [Brief context]
## Signals to Watch
- [Emerging pattern or trend]
## Suggested Follow-ups
- [Skill to run next, e.g., /competitive if a competitor moved]Rules
- Maximum 5 items total. Quality over quantity.
- If using web search, cite sources.
- If $ARGUMENTS provided, focus the briefing on that area.
- Write to
.chairman/reports/briefing-YYYY-MM-DD.md - Update
.chairman/state.jsonwith last_session date.
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.

