agentleFS
Sign inStart free
jaskiel123jaskiel123/operators-brain/.claude/skills/brief/SKILL.md

brief

Skill0 starsChanged 5 months agoMITView on GitHub

Runs your morning — calendar, tasks, priorities, and the single most important thing.

80 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use capture, strategy and 10 more.

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.
  • toneron2Skill

    capture

    Capture thoughts to inbox with automatic classification

    Also in 6 projects that use this

  • EpistatesSkill

    strategy

    Plan weekly or monthly X content strategy. Use when the user wants to plan their content calendar, set growth goals, build a content pipeline, or think strategically about their X presence.

    Also in 4 projects that use this

  • aleksander-dytkoSkill

    decision

    Make a product decision with full context from the vault and available sources

    Also in 3 projects that use this

  • dirienSkill

    decide

    Three-agent adversarial debate protocol for strategic decisions. Two advocates steelman opposing positions while a moderator identifies risks and synthesizes a binding consensus. Use when choosing between alternatives, evaluating tradeoffs, or making high-stakes decisions.

    Also in 5 projects that use this

  • JaimeGBASkill

    ingest

    Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base

    Also in 7 projects that use this

  • howellsSkill

    reconcile

    Audit a project against current plugin conventions and offer to update structure.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 73 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read context/about-you.md (working hours, energy patterns) and context/about-business.md (current priorities).

    line 11
  2. Very specific:

    Read context/clients.md to know what is live and what is waiting on the user.

    line 12
  3. Very specific:

    If a calendar connection is configured (see connections/README.md), pull today's events.

    line 13
  4. Distinctive:

    Never schedule more than ~6 hours of deep work.

    line 28
  5. Distinctive:

    If 3+ urgent items exist, flag overload and suggest what to drop or delegate.

    line 29
  6. Distinctive:

    Always lead with the single most important task.

    line 30
  7. Distinctive:

    Do not invent calendar events.

    line 31

“Common” is measured: kept by at least 6 in 10 of the 73 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.

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

Goal

Produce a focused daily plan with time blocks, pulled from the user's calendar, tasks, and priorities, with one clear "most important thing" at the top.

Process

  1. Read context/about-you.md (working hours, energy patterns) and context/about-business.md (current priorities).
  2. Read context/clients.md to know what is live and what is waiting on the user.
  3. If a calendar connection is configured (see connections/README.md), pull today's events. If not, ask the user to paste today's calendar or proceed with tasks only.
  4. Pull or ask for today's open tasks and anything due.
  5. Draft the plan:
    • The one thing — single most important task today, stated first.
    • Morning block: deep work on the highest-priority item.
    • Afternoon block: meetings and comms.
    • 30% buffer for the unexpected.
    • Flag anything overdue or any client waiting on the user.
  6. Output as markdown with checkboxes. Save to outputs/briefs/{{date}}-brief.md.

References

  • context/about-you.md, context/about-business.md, context/clients.md
  • connections/README.md — optional calendar connection.

Rules

  1. Never schedule more than ~6 hours of deep work.
  2. If 3+ urgent items exist, flag overload and suggest what to drop or delegate.
  3. Always lead with the single most important task.
  4. Do not invent calendar events; if no connection and no paste, say so and work from tasks.

Improvement

  • Last updated: 2026-06-13
  • Next: pull energy patterns to time-block deep work to the user's peak hours.

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