Brief Report
Use when a sub-session has finished its delegated task and needs to write a results brief for the parent session to pick up — captures what was done, what worked, what didn't, and any new blockers the parent should know about. Triggered after completing a task that was started from a `brief-delegate` brief, or when the user says "write a report brief", "I'm done — brief back".
Install
$ agentstack add skill-useaitechdad-agent-skills-brief-report ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-useaitechdad-agent-skills-brief-report) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
brief-report — report results back to the parent session
You are a sub-session that finished its delegated task. Write a results brief the parent session will read to continue.
Where to save
~/.claude/projects//briefs/brief-.mdCompute the paths yourself — no shell needed for the slug:
- `
= current working directory with every/replaced by-(e.g. cwd/Users/you/code/myapp→ slug-Users-you-code-myapp`). You already know the cwd from your environment. - briefs dir =
/.claude/projects//briefs(absolute, your real home path).
You do need one shell call — the timestamp, since Claude has no clock:
date +%Y-%m-%d-%H%M%S # local time — keeps the filename stamp consistent with the log stampThe filename is brief-.md. Write it with the Write tool (it creates the briefs dir if missing) — don't shell out to create the file.
What to write
Aim for ~15-30 lines. Concrete outcomes, not retelling.
# Brief —
**Flavor**: report
**Created**:
**Project**:
**Responds to**: .md`). You read it to start this work, so you know its path. Never leave blank.>
## Outcome
## What changed
-
-
## What worked
-
## What didn't / blockers
-
## Loose ends
- After writing
- Append the log entry via the shared helper (owns the format + trim + file pruning — don't hand-format the line). Pass the absolute briefs dir and the file you just wrote:
``bash ~/.claude/skills/_brief-shared/append-log.sh "" report "" "" ``
- Print the file path.
- One-line hint: "In the parent session, run
/brief-resumeand pick this entry."
What NOT to include
- Don't try to solve loose ends here — flag them; let the parent decide.
- Don't include speculative plans for what to do next — only what actually happened.
- Don't include reasoning chains or rejected alternatives.
- Don't gloss over partial completion as "done" — be honest.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: useaitechdad
- Source: useaitechdad/agent-skills
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.