agentleFS
Sign inStart free
parker-brown-familyparker-brown-family/agent-skills/briefing/SKILL.md

briefing

Skill1 starsChanged 8 days agoNo licenceView on GitHub

Write up finished work as a short brief a person can read in minutes and comment on passage by passage: HTML with drawings, or Markdown. Each claim links to its evidence, and the reader's comments come back pinned to the exact section and version they read. While the work runs, keep the agent on what was approved and record the decisions it makes that nobody made, for the person to concur with or overturn later. Use when work ends in something a person should understand, check or decide: \"write this up\", \"brief me\", \"explain what you changed\", \"summarize for review\", \"engineering write-up\", \"decision write-up\", \"a page I can comment on\", \"where are we\", \"/briefing\"; when a reader returns comments, a copied notes map, or an annotated brief; and mid-work, when a decision nobody made comes up, when the agent resumes after compaction, or when the person asks \"what did you decide\", \"do you concur\", \"judgement call\", \"standing orders\". Pick the purpose (summary, engineering, decision, or one you name) and the medium from the task and the user's recorded preferences; never run a format interview.

20 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use handoff and grill-me.

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

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 6 projects that use this

  • GoogleSkill

    grill-me

    A relentless interview to sharpen a plan or design.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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