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

context-load

Skill0 starsChanged 5 months agoMITView on GitHub

Pulls full client/project context before a call so you walk in ready, not re-reading.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. s977043/PlanGate★ 3same name
    2. VECTORG99/acf★ 2same 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 repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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 that client's section in context/clients.md: status, history, concerns, decision-maker, budget, last interaction.

    line 12
  2. Very specific:

    If connections are configured (connections/README.md), pull recent emails/calendar/notes for that client.

    line 13
  3. Very specific:

    Never invent interactions.

    line 28
  4. Distinctive:

    Always end with the single goal for the call.

    line 29

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

Goal

In seconds, give the user a complete, current picture of a client/project before a call: where things stand, what was decided, what the client is waiting on, and what to push for next.

Process

  1. Identify the client/project (from the command, e.g. /context-load Brightwell, or ask).
  2. Read that client's section in context/clients.md: status, history, concerns, decision-maker, budget, last interaction.
  3. If connections are configured (connections/README.md), pull recent emails/calendar/notes for that client. Otherwise work from context/clients.md and ask for anything missing.
  4. Produce a one-screen prep brief:
    • Where we are — current status in one line.
    • Last 3 touchpoints — what happened, what was decided.
    • What they care about — their stated concerns/priorities.
    • Open / waiting on — what the user owes them, what they owe the user.
    • Goal for this call — the one outcome to push for.
  5. Offer to draft talking points or a follow-up via /proposal.

References

  • context/clients.md — primary source.
  • connections/README.md — optional email/calendar pull.

Rules

  1. One screen. This is a pre-call brief, not a dossier.
  2. Never invent interactions; if history is thin, say so and prompt the user to fill context/clients.md.
  3. Always end with the single goal for the call.

Improvement

  • Last updated: 2026-06-13
  • Next: auto-append each call's outcome back into context/clients.md after the call.

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