Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →davepoon/brief
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.
Passed 14 of 20 test cases with the skill, and 4 of 20 without it.
and 8 more in the full report
11 fixed5 passed either way7 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
A pending revision item returned by list_pending_revisions contains target_source_id mem_333 and revision_content, but does not include the original memory's body text. If the user wants to compare the proposed change against the original before deciding, what command should they be directed to run?
| Checked | Without skill | With skill |
|---|---|---|
| Directs the user to run /recall mem_333 | Missed | Passed |
The instructions your model reads when the skill loads.
Pull a curated session brief from Origin. Three sources, in order:
/handoff last wrote. Authoritative for
"what's left to do" right now.context MCP — identity, preferences, topic-relevant memories.
Background, not ledger.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.
Detect project root:
Bash: cd_repo=$(git -C "$PWD" rev-parse --show-toplevel 2>/dev/null); echo "${cd_repo:-no-git}"
<project> = basename (e.g. origin).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.
test cases passed, vs 4 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.