agentsclimarketplace

Brief me

Skill tmusser/context-to-action-skills/skills/brief-me

Claude skills for turning messy business context into clear asks, decisions, owners, updates, and follow-ups.

Install
npx -y skills add tmusser/context-to-action-skills --skill brief-me

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Catch the user up from messy workplace context and surface what needs attention.

SKILL.md

2.0 KB, as published. Nobody here has run it

brief-me

Purpose

Turn messy connected or pasted context into a short conversation-state brief the user can act on quickly.

Use For

  • "What did I miss?"
  • "Brief me before this meeting."
  • "What changed since Monday?"
  • "What needs my response?"

Inputs

  • Slack
  • Gmail
  • Calendar
  • Zoom transcript
  • Atlassian
  • Hex or other data output
  • Pasted notes
  • Any combination of the above
  • A reduce-to-facts ledger or conversation-state record

Guardrails

  • Read before write.
  • Do not send messages, create events, update tickets, or publish outputs unless explicitly asked.
  • Separate source-backed facts from assumptions and suggestions.
  • Prefer small source windows.
  • Surface source gaps.
  • Do not dump raw transcript content by default.
  • Keep the output workplace-user friendly.

Portable Output Contract

  • Use only the useful subset of source-backed facts, assumptions, source gaps, stakeholder sensitivities, potential misreads, and the suggested next action.
  • Use the smallest useful output.
  • Label assumptions and preserve source gaps, source anchors, and confidence labels.
  • When consuming upstream state, do not promote an assumption, inference, open question, proposed action, or stakeholder position into a fact, decision, commitment, owner, or deadline without new source support.
  • Keep unresolved approvals, owners, timing, and blockers explicit in the brief.
  • Do not send, publish, update tickets, create events, or mutate systems unless explicitly asked.

Output

  • Conversation state
  • What changed
  • What needs response
  • Action state
  • Source confidence
  • Suggested next response
  • Meetings to prep for
  • Suggested follow-ups
  • Source gaps

When the user wants a fuller record, use the optional CONVERSATION_STATE.md template from this pack when it is available.

Success Standard

The user should be able to scan the brief and know what matters within 5 minutes.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.