Agent skill

Brief

by davepoon in davepoon/buildwithclaude

Session-start briefing from Origin. An agent skill from davepoon/buildwithclaude.

MITAuto-check: notes

Install Brief

skills CLI
$ npx skills add davepoon/buildwithclaude --skill brief -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install davepoon/buildwithclaude brief --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/davepoon/buildwithclaude.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/origin/skills/brief .claude/skills/brief && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
brief
GitHub stars
3.6k
Token cost
~1.3k tokens
SKILL.md length
594 words
Files
1
Skills in repo
245
Repo updated
First seen
Licence
MIT

At a glance

Session-start briefing from Origin. An agent skill from davepoon/buildwithclaude.

  • Works in 3 steps: Read project status file first → Call context → Pending revisions check
  • SKILL.md covers 1. Read project status file…, 2. Call context, When to use and When NOT to use, plus 2 more sections
  • Calls git

What it does

Brief is an agent skill from davepoon/buildwithclaude. Session-start briefing from Origin. Reads the project status file (the /handoff-maintained ledger of Active/Backlog work), then loads identity, preferences, and topic-relevant memories so the agent walks in with context. Surfaces any memories the daemon has flagged for human revision before the session uses them. Invoked as /brief [topic]. Call FIRST at session start, before any other Origin verb.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: A single hub to find Claude Skills, Agents, Commands, Hooks, Plugins, and Marketplace collections to extend Claude Code, Claude Desktop, Agent SDK and OpenClaw. The licence is MIT.

Example prompts

  • “/brief”

Requirements

  • Pre-approved tools (allowed-tools): Bash, mcp__plugin_origin_origin__context, mcp__plugin_origin_origin__recall, mcp__plugin_origin_origin__list_pending_revisions, mcp__plugin_origin_origin__accept_revision, mcp__plugin_origin_origin__dismiss_revision

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Read project status file first
  2. Call context
  3. Pending revisions check

What it can do on your machine

Read from SKILL.md and the folder at commit 10bfc43. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash
    • mcp__plugin_origin_origin__context
    • mcp__plugin_origin_origin__recall
    • mcp__plugin_origin_origin__list_pending_revisions
    • mcp__plugin_origin_origin__accept_revision
    • mcp__plugin_origin_origin__dismiss_revision

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Brief loads about 1.3k tokens when it runs. Until then it costs about 102 tokens; SKILL.md has 594 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~102
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash, mcp__plugin_origin_origin__context, mcp__plugin_origin_origin__recall, mcp__plugin_origin_orig

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from davepoon/buildwithclaude at commit 10bfc43, republished under its MIT licence (© davepoon). 594 words, ~1,343 tokens.

Download SKILL.mdSave it as .claude/skills/brief/SKILL.md (or your agent's skills folder).
name
brief
description
Session-start briefing from Origin. Reads the project status file (the /handoff-maintained ledger of Active/Backlog work), then loads identity, preferences, and topic-relevant memories so the agent walks in with context. Surfaces any memories the daemon has flagged for human revision before the session uses them. Invoked as `/brief [topic]`. Call FIRST at session start, before any other Origin verb.
allowed-tools
Bash, mcp__plugin_origin_origin__context, mcp__plugin_origin_origin__recall, mcp__plugin_origin_origin__list_pending_revisions, mcp__plugin_origin_origin__accept_revision, mcp__plugin_origin_origin__dismiss_revision
argument-hint
[topic]

/brief

Pull a curated session brief from Origin. Three sources, in order:

  1. Project status file — what /handoff last wrote. Authoritative for "what's left to do" right now.
  2. context MCP — identity, preferences, topic-relevant memories. Background, not ledger.
  3. list_pending_revisions — daemon-flagged memories awaiting review.

Status file wins on "what's next" because memories rank by topic similarity and surface stale items alongside fresh ones; the status file is the live ledger maintained per session.

1. Read project status file first

Detect project root:

Bash: cd_repo=$(git -C "$PWD" rev-parse --show-toplevel 2>/dev/null); echo "${cd_repo:-no-git}"
  • If output is a path → <project> = basename (e.g. origin).
  • If no-git → <project> = cwd basename.

Read ~/.origin/sessions/_status/<project>.md:

Bash: cat ~/.origin/sessions/_status/<project>.md

If the file exists, render its ## Last session, ## Active, and ## Backlog sections verbatim at the top of the brief output, under a heading like Status (last session <date>). This is the authoritative "what's left" frame.

If the file is missing, say nothing about it. First-time projects haven't been handed off yet.

2. Call context

Call the origin MCP server's context tool. If the user passed a topic argument, pass it through. Otherwise infer scope from the working directory and the conversation so far — don't ask the user.

context(topic="<args or inferred>", space=<inferred from cwd or recent turns>)

Scope inference rules:

  • topic: if user omitted args, pass the most recent topic from the conversation (file or feature being discussed), or omit for a fresh general brief at session start.
  • space: from cwd. ~/Repos/origin/... → "origin". Other repos → repo name. Outside any repo → omit. Always pass when scope is known; if uncertain, run list_spaces later (post-PR-C) or omit.

When to use

  • Session start — call BEFORE any other Origin tool.
  • Major topic shift mid-session.
  • User says "catch me up", "what's the background on X", "remind me about Y".
  • Mid-session check-in to confirm assumptions.

When NOT to use

  • Specific factual lookup → use /recall (more targeted).
  • Storing a new memory → use /capture.
  • End of session → use /handoff.

How to use the result

Treat the status file as the live ledger (what's next), and the context memories as background (how the user thinks). When the status file says an item is done but a memory still says it's pending, trust the status file — memories don't auto-supersede. If you see drift, flag it inline rather than parrot the stale memory.

Model how the user thinks. Their preferences, corrections, and past decisions tell you how they want to be helped, not just what they already know. Don't just look things up: adjust your behavior.

Show full SKILL.md (201 more words)Show less

3. Pending revisions check

After loading context, call:

list_pending_revisions(limit=10)

If the result is empty, say nothing. Do not print "0 pending revisions" or any "all clear" line. The brief is already noisy enough.

If the MCP call errors, log a one-line warning and continue. Do not error out the brief.

If the result is non-empty, render a block at the end of the brief (after the context summary, before handing back to the user). The daemon returns rows already sorted by last_modified DESC; just slice the first three.

Each PendingRevisionItem carries target_source_id, revision_source_id, revision_content, source_agent, and last_modified. The original memory's content is not on this response. The block displays the proposed revision text and the target memory id; if the user wants to see the original before deciding, they can run /recall <target_source_id> first.

Pending revisions (<N> total, top 3 shown):

1. target: mem_abc123  (proposed by <source_agent or "daemon">)
   revision: "Origin uses Turso libSQL fork (libSQL-server) for vectors..."
   Action: accept (replace original) | dismiss (drop revision) | skip

2. ...

Inline accept/dismiss verbs map to:

  • accept: accept_revision(target_source_id="<id>")
  • dismiss: dismiss_revision(target_source_id="<id>")
  • skip: no call; the revision stays pending for the next /brief

If <N> > 3, end the block with one line:

Run `/review revisions` to walk the rest.

Do not auto-action anything. The user picks per item.

Note: this block surfaces all pending revisions, not just this session's, because revisions are about memories you may still be using right now, regardless of when the contradiction was flagged.

© davepoon, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/origin/skills/brief of davepoon/buildwithclaude.

Open the folder on GitHubat commit 10bfc43

Compare with similar skills

Brief next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Brief compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Brief this skilldavepoon/buildwithclaude3.6k—~1.3kAutomated safety check: NotesMIT
Briefalirezarezvani/claude-skills28k—~967Automated safety check: PassMIT
Cross Origin Securitythedaviddias/Front-End-Checklist74k—~595Automated safety check: PassMIT
Cross Origin Isolationthedaviddias/Front-End-Checklist74k—~565Automated safety check: PassMIT
Review Briefevery-app/open-seo23k—~1.2kAutomated safety check: PassMIT
Origin APIcursor/plugins10k—~694Automated safety check: PassMIT

Similar skills

  • Brief

    alirezarezvani/claude-skills

    /cs:brief <topic — Generate a one-page strategy brief from an office-hours intake.

    28k GitHub stars~967 tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed
  • Cross Origin Security

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing scripts, client components, bundles, or runtime behavior related to Handle cross-origin requests securely.

    74k GitHub stars~595 tokensUpdated 2 days ago
    Auto-check passed
  • Cross Origin Isolation

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing security-sensitive web apps, SharedArrayBuffer usage, worker-heavy apps, editors, or measurement features that require cross-origin isolation.

    74k GitHub stars~565 tokensUpdated 2 days ago
    Auto-check passed
  • Review Brief

    every-app/open-seo

    Produce a scannable review brief for a branch or PR so the maintainer can approve without reading the whole diff.

    23k GitHub stars~1.2k tokensUpdated yesterday
    Marketing & SEOAuto-check passed
  • Origin API

    cursor/plugins

    Official

    Routes questions about the Cursor Origin API to the right section of the Origin docs and names the few rules to check first.

    10k GitHub stars~694 tokensUpdated today
    Backend & APIsAuto-check passed
  • Traderspy Market Briefing

    sickn33/agentic-awesome-skills

    Crypto market briefing from live TraderSpy data: majors, funding, open interest, top-trader lean, fresh AI signals and screener movers.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed

More from davepoon/buildwithclaude

All 245 skills in this repo
  • Qwen Vision

    davepoon/buildwithclaude

    A skill your agent uses when the user asks to "analyze video", "watch this video", "what happens in this video", "describe this clip", "review this footage", "classify these videos", "compare…

    3.6k GitHub starsUsed in 1 repo~1.2k tokens
    Auto-check passed
  • Hard Predict Future

    davepoon/buildwithclaude

    Activate this agent for any future-oriented question that requires deep quantitative analysis, historical precedents, and structured scenario planning.

    3.6k GitHub starsUsed in 1 repo~4.2k tokens
    Auto-check passed
  • iOS Hig Design Guide

    davepoon/buildwithclaude

    Build, update, and apply iOS design specifications using Apple Human Interface Guidelines (HIG) source data.

    3.6k GitHub stars~735 tokensUpdated 2 days ago
    Auto-check passed
  • Video Downloader

    davepoon/buildwithclaude

    Download YouTube videos with customizable quality and format options.

    3.6k GitHub starsUsed in 1 repo~871 tokens
    Auto-check passed
  • Atlas Cloud Media

    davepoon/buildwithclaude

    Discover Atlas Cloud image and video models, inspect their live schemas, and submit one confirmed media generation request with bounded GET polling.

    3.6k GitHub stars~852 tokensUpdated 2 days ago
    Auto-check passed
  • Slack Gif Creator

    davepoon/buildwithclaude

    Toolkit for creating animated GIFs optimized for Slack, with validators for size constraints and composable animation primitives.

    3.6k GitHub starsUsed in 12 repos~4.3k tokens
    Auto-check passed

Questions about Brief

What does Brief do?

Session-start briefing from Origin. An agent skill from davepoon/buildwithclaude. Brief is an agent skill from davepoon/buildwithclaude. Session-start briefing from Origin.

How do I install Brief in Claude Code?

Run `npx skills add davepoon/buildwithclaude --skill brief -a claude-code`. Or copy the skill folder (plugins/origin/skills/brief in davepoon/buildwithclaude) into .claude/skills/brief in your project. Claude Code loads it when a task matches its description.

How do I install Brief in Codex?

Run `npx skills add davepoon/buildwithclaude --skill brief -a codex`. Or copy the skill folder (plugins/origin/skills/brief in davepoon/buildwithclaude) into .agents/skills/brief in your project. Codex loads it when a task matches its description.

Can I use Brief in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add davepoon/buildwithclaude --skill brief -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/brief, .gemini/skills/brief, .github/skills/brief and .opencode/skills/brief in your project.

What does Brief need to run?

Going by SKILL.md and its folder, Brief needs the command-line tools its instructions call (git). Its frontmatter pre-approves these tools: Bash, mcp__plugin_origin_origin__context, mcp__plugin_origin_origin__recall, mcp__plugin_origin_origin__list_pending_revisions, mcp__plugin_origin_origin__accept_revision, mcp__plugin_origin_origin__dismiss_revision.

Does Brief access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Brief safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Brief use?

Brief is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Brief use?

About 1.3k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Brief?

Skills that share tags, products or a category with Brief: Brief (alirezarezvani/claude-skills, 28k stars), Cross Origin Security (thedaviddias/Front-End-Checklist, 74k stars), Cross Origin Isolation (thedaviddias/Front-End-Checklist, 74k stars) and Review Brief (every-app/open-seo, 23k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Brief?

davepoon (a GitHub user) maintains it in davepoon/buildwithclaude, which has 3,604 GitHub stars. The repository holds 245 skills in this directory. The repository was last updated on October 6, 2026.

Source: davepoon/buildwithclaude on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.