How do I install the Brief skill?

Run npx skillmds add majiayu000/brief-4 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Brief skill do?

Catch up on parallel sessions and brief the user on project state It is listed under Coding & Dev Tools on SkillMD.

Is Brief safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Brief?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Brief free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Brief by majiayu000 — Agent Skill

Name: Brief
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

/brief - Catch Up & Brief

Two jobs: (1) catch yourself up on what happened in parallel sessions, (2) tell the user what's going on.

Usage

/brief

Instructions

Step 1: Catch Up (for the agent)

Read Dashboard/Brief.md and scan Recent Activity for entries you haven't seen yet — anything from other agents or sessions since your last read. Internalize what changed: new decisions, status updates, completed work, blockers.

Also check for handoff messages or new files:

Dashboard/Work_Space/HANDOFF_*.md — pending handoffs
Dashboard/Work_Space/KNOWLEDGE_REQUEST_*.md — unfulfilled research requests
Dashboard/Work_Space/**/MESSAGE_FROM_*.md — messages left by other agents

Step 2: Brief the User

Present a concise summary covering what's new AND overall state:

=== BRIEF ===

WHAT'S NEW (since last check)
=============================
[Bullet list of Recent Activity entries the user likely hasn't seen.
Focus on what OTHER agents did in parallel sessions.
If nothing new, say "No new activity."]

CURRENT FOCUS
=============
[Current focus from Brief.md — 1-2 lines]

ACTIVE PROJECTS
===============
[Active projects table — status + next action]

TEAM STATUS
===========
[Team status table]

PENDING
=======
[Any HANDOFF files, KNOWLEDGE_REQUEST files, or MESSAGE_FROM files.
If none, say "None"]

NEXT STEPS
==========
[Next steps list from Brief.md]

=============

Rules

"What's New" comes first — the user wants to know what they missed, not re-read what they already know
Be specific in "What's New" — "Gal reviewed Sunny and approved with conditions" not "Gal did some work"
Keep it concise — this is a quick catch-up, not a report
Don't read full agent memory files — this is project-level only
If running as a specific agent, note which Recent Activity entries are from OTHER agents (that's what you're catching up on)

---name: brief-4description: Catch up on parallel sessions and brief the user on project state--- # /brief - Catch Up & Brief Two jobs: (1) catch yourself up on what happened in parallel sessions, (2) tell the user what's going on. ## Usage ``` /brief ``` ## Instructions ### Step 1: Catch Up (for the agent) Read `Dashboard/Brief.md` and scan **Recent Activity** for entries you haven't seen yet — anything from other agents or sessions since your last read. Internalize what changed: new decisions, status updates, completed work, blockers. Also check for handoff messages or new files: - `Dashboard/Work_Space/HANDOFF_*.md` — pending handoffs - `Dashboard/Work_Space/KNOWLEDGE_REQUEST_*.md` — unfulfilled research requests - `Dashboard/Work_Space/**/MESSAGE_FROM_*.md` — messages left by other agents ### Step 2: Brief the User Present a concise summary covering what's new AND overall state: ``` === BRIEF === WHAT'S NEW (since last check) ============================= [Bullet list of Recent Activity entries the user likely hasn't seen. Focus on what OTHER agents did in parallel sessions. If nothing new, say "No new activity."] CURRENT FOCUS ============= [Current focus from Brief.md — 1-2 lines] ACTIVE PROJECTS =============== [Active projects table — status + next action] TEAM STATUS =========== [Team status table] PENDING ======= [Any HANDOFF files, KNOWLEDGE_REQUEST files, or MESSAGE_FROM files. If none, say "None"] NEXT STEPS ========== [Next steps list from Brief.md] ============= ``` ## Rules - **"What's New" comes first** — the user wants to know what they missed, not re-read what they already know - **Be specific** in "What's New" — "Gal reviewed Sunny and approved with conditions" not "Gal did some work" - **Keep it concise** — this is a quick catch-up, not a report - **Don't read full agent memory files** — this is project-level only - **If running as a specific agent**, note which Recent Activity entries are from OTHER agents (that's what you're catching up on)

Frequently asked questions