Brief Me
Turn messy workplace context into a concise, source-aware brief of what changed and what needs attention.
Free
Works with the AI tools you already use
Claude Code
Cursor
Codex CLI
GitHub Copilot
Gemini CLI+20 moreClaude CodeCursorCodex CLIGitHub CopilotGemini CLI
OpenClaw
Manus
Grok+17 agentsBrief Me
Example session with this skill installed
Brief me on this thread before I respond. Alex: Can we still send the customer note today? Sam: I’d rather not wait; support can catch up after. Priya: Support needs the enterprise wording before anything goes out. Jordan: Legal has not approved the banner copy. Alex: The send queue closes at 3pm. Who owns the call? Include what changed, what needs my response, and any gaps.
- Read your context and instructions
- Compiled the brief me
- Generated the document
Conversation-state brief
What changed
- The team is deciding whether to send the customer note today or move it.
- Support says it needs the enterprise wording before anything goes out.
- Legal approval for the banner copy is still missing.
- The send queue closes at 3pm.
What is supported by the source
- Alex asked about sending today.
- Sam prefers not to wait.
- Priya raised a support-readiness dependency.
- Jordan reported that legal has not approved the banner copy.
- No final decision owner is named.
What needs attention
- Name the decision owner.
- Decide whether legal or support readiness blocks today’s send.
- Confirm the decision before 3pm.
Open questions
- Is legal approval a hard gate, or can the copy be revised after the send?
- Who can confirm support readiness?
- If the send moves, what is the next committed time?
Suggested next move
Ask the team to name the decision owner and confirm by 3pm whether legal or support readiness blocks today’s send.
Assumptions and gaps
I am not inferring that the note must be delayed; the source only says legal approval and support wording are unresolved. No owner or fallback date is provided.
Next steps
- Name an accountable decision owner.
- Confirm the legal and support readiness gates.
- Record the send decision and fallback time in the working thread.
brief-me.pdf
PDF · document
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
About this skill
Brief Me turns a long Slack thread, email chain, meeting transcript, ticket discussion, or pasted notes into a compact conversation-state brief. It helps an agent catch someone up quickly without dumping raw transcripts or pretending uncertainty is resolved.
Use it when someone asks “What did I miss?”, “Brief me before this meeting,” or “What needs my response?” The skill separates source-backed facts from assumptions, suggestions, open questions, owners, timing, and risks. It supports workplace context from Slack, Gmail, Calendar, Zoom transcripts, Atlassian, Hex, and pasted notes.
Best for managers, operators, chiefs of staff, and teams joining work midstream. It is designed for read-before-write workflows: it drafts the next clear move but does not send messages, create events, update tickets, or publish outputs unless explicitly asked.
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.
Skills folder by agent
Click the path to copy it. Create the folder if it does not exist yet.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scanned
Verified clean 1 day ago
- Free to download with an account