agentleFS
Sign inStart free
ethanaubuchonethanaubuchon/dossier-tradecraft/skills/load-context/SKILL.md

load-context

Skill3 starsChanged 49 days agoMITView on GitHub

Use at the start of /research and other workflow recipes to establish vault grounding. Loads vault bootstrap (profile.md), checks inbox, and pre-warms project context if a topic anchor is implied. Repo/git detection lands with /plan and /implement.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Call this once at the start of a workflow recipe to establish working context.

    line 8
  2. Very specific:

    Call mcp__dossier-mcp__get_vault_context.

    line 12
  3. Very specific:

    Call mcp__dossier-mcp__list_notes(path: "inbox").

    line 14
  4. Very specific:

    If the user has supplied a research topic with a clear project anchor (e.g.

    line 16
  5. Distinctive:

    No structured return value.

    line 20

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

Load Context

Call this once at the start of a workflow recipe to establish working context. In /research, this is the vault grounding pre-step — it loads the context that informs downstream web queries.

Steps

  1. Call mcp__dossier-mcp__get_vault_context. This loads profile.md silently — do not summarize or recite it.
  2. Call mcp__dossier-mcp__list_notes(path: "inbox"). If the inbox is non-empty, surface a one-line nudge to the user: Inbox has N notes — worth processing before we start?
  3. If the user has supplied a research topic with a clear project anchor (e.g. "relocation healthcare costs" → projects/relocation), call mcp__dossier-mcp__list_notes(path: "projects/<slug>") to pre-warm topic context. Skip if no anchor is obvious — vault-researcher will find what it needs.

Output

No structured return value. Context loads into the conversation. The recipe continues to its next step.

Future scope (not in Phase 1)

  • Repo / vault / mixed environment detection
  • git status snapshot for the working dir

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