agentleFS
Sign inStart free
tmussertmusser/context-to-action-skills/skills/brief-me/SKILL.md

brief-me

Skill2 starsChanged 59 days agoMITView on GitHub

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

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. jinhanbuilds/brief-me★ 37same name
    2. adamlinscott/claude-skills★ 3same name
    3. MyAiFreedomSystems/incredagents★ 0same 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 repository7 other files it gives its agents.

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. About 0 are common, 13 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈13

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not infer preferences from connected data when the user has not stated them.

    line 43
  2. Distinctive:

    Treat the user's current request as higher priority than profile defaults.

    line 44
  3. Distinctive:

    If no profile is available, use the standard output contract below.

    line 45
  4. Distinctive:

    Do not send messages, create events, update tickets, or publish outputs unless explicitly asked.

    line 50
  5. Distinctive:

    Prefer small source windows.

    line 52
  6. Distinctive:

    Do not dump raw transcript content by default.

    line 54
  7. Distinctive:

    Keep the output workplace-user friendly.

    line 55
  8. Distinctive:

    Use only the useful subset of source-backed facts, assumptions, source gaps, stakeholder sensitivities, potential misreads, and the …

    line 59
  9. Distinctive:

    Use the smallest useful output.

    line 61
  10. Distinctive:

    When consuming upstream state, do not promote an assumption, inference, open question, proposed action, or stakeholder position into a …

    line 63
  11. Distinctive:

    Keep unresolved approvals, owners, timing, and blockers explicit in the brief.

    line 66
  12. Distinctive:

    Do not send, publish, update tickets, create events, or mutate systems unless explicitly asked.

    line 67
  13. Distinctive:

    Use the smallest useful subset of:

    line 71
  14. Very specific:

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

    line 83

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Optional Operator Setup

brief-me works without setup. When the user wants recurring briefs tailored to how they operate, use the bundled OPERATOR_PROFILE.md flow.

An operator profile may tune prioritization, compression, section order, terminology, meeting-prep behavior, and when suggested replies appear. It must not change source truth, confidence, unresolved gaps, or authorization boundaries.

  • Opt in; never require setup before producing a useful brief.
  • Do not infer preferences from connected data when the user has not stated them.
  • Treat the user's current request as higher priority than profile defaults.
  • If no profile is available, use the standard output contract below.

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

Use the smallest useful subset of:

  • 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. With an operator profile, the brief should feel better prioritized for that user without becoming less grounded or less portable.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free