New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Handoff Report

by happier-dev in happier-dev/happier

Output contract for substantive deliverables — outcome first, evidence-pointed reasoning, observed/derived/assumed labels, residual risk last, failures never buried, and an optional evidence-backed…

MITAuto-check passedProduct & Project Management

Install Handoff Report

skills CLI
$ npx skills add happier-dev/happier --skill handoff-report -a claude-code

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

GitHub CLI
$ gh skill install happier-dev/happier handoff-report --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/happier-dev/happier.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/handoff-report .claude/skills/handoff-report && 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
handoff-report
GitHub stars
1.9k
Token cost
~944 tokens
SKILL.md length
505 words
Files
1
Skills in repo
28
Repo updated
First seen
Licence
MIT

At a glance

Output contract for substantive deliverables — outcome first, evidence-pointed reasoning, observed/derived/assumed labels, residual risk last, failures never buried, and an optional evidence-backed…

  • Works in 4 steps: Outcome first. The first sentence… → Failures and scope changes in the first… → Reasoning, auditable. Evidence pointers… → …
  • Reporting completed work
  • SKILL.md covers Order, Labeling, Style and Optional retrospective for…, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Handoff Report is an agent skill from happier-dev/happier. Output contract for substantive deliverables — outcome first, evidence-pointed reasoning, observed/derived/assumed labels, residual risk last, failures never buried, and an optional evidence-backed retrospective for explicit requests or major program closeout. Use when reporting completed work, findings, diagnoses, reviews, lane results, or a requested retrospective.

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

It sits in Product & Project Management, covering Retrospectives. The repository describes itself as: Web, Desktop & Mobile client and orchestrator for Codex, Claude Code, OpenCode, Pi, Cursor, Grok, Antigravity, Kimi, Augment Code, Qwen, fully end-to-end encrypted. The licence is MIT.

When your agent uses it

  • Reporting completed work
  • A requested retrospective

Example prompts

  • “/handoff-report”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Outcome first. The first sentence answers what the reader would ask for if they said "just the TLDR": what happened, what was found, or…
  2. Failures and scope changes in the first block. A failed check, a skipped step, a scope change, an error worked around — these go up front…
  3. Reasoning, auditable. Evidence pointers with every load-bearing statement: file.ts:line, the log excerpt, the measurement, the command…
  4. Residual risk last, explicitly. What remains unverified, what to check next, what would invalidate the conclusion. If there is genuinely…

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

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

  • Network

    No URLs in SKILL.md.

    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

Handoff Report loads about 944 tokens when it runs. Until then it costs about 96 tokens; SKILL.md has 505 words of instructions outside code blocks.

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

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 passed

The automated check found no risky patterns in SKILL.md.

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 happier-dev/happier at commit 1f03ccd, republished under its MIT licence (© happier-dev). 505 words, ~944 tokens.

Download SKILL.mdSave it as .claude/skills/handoff-report/SKILL.md (or your agent's skills folder).
name
handoff-report
description
Output contract for substantive deliverables — outcome first, evidence-pointed reasoning, observed/derived/assumed labels, residual risk last, failures never buried, and an optional evidence-backed retrospective for explicit requests or major program closeout. Use when reporting completed work, findings, diagnoses, reviews, lane results, or a requested retrospective.

Handoff Report

Structure any substantive report so the reader can act on the first paragraph and audit the rest. Full doctrine: docs/agent-craft.md §5 and §7.

Order

  1. Outcome first. The first sentence answers what the reader would ask for if they said "just the TLDR": what happened, what was found, or what is blocked. Not the journey, not the setup.
  2. Failures and scope changes in the first block. A failed check, a skipped step, a scope change, an error worked around — these go up front even when embarrassing, never mid-report. The most informative event is the one you are tempted to smooth over.
  3. Reasoning, auditable. Evidence pointers with every load-bearing statement: file.ts:line, the log excerpt, the measurement, the command that produced the number. Trust should rest on checkable references, not on tone.
  4. Residual risk last, explicitly. What remains unverified, what to check next, what would invalidate the conclusion. If there is genuinely no residual risk, say that — the reader cannot distinguish "no risk" from "risk section omitted".

Labeling

  • Every load-bearing statement is sortable by the reader into observed (ran it, read it, saw it) / derived (follows from observations by stated reasoning) / assumed (plausible, unverified) — without asking you.
  • Use cheap explicit markers: "verified:", "inferred from X:", "assumption:". Never let sentence confidence do the labeling; fluent prose reads as fact regardless of bin.
  • For derived claims, state the derivation ("X because A + B") so the reader can audit the step and see which assumptions it inherits.
  • Hedging is not labeling. "Probably" makes every sentence equally gray; a label says exactly what is known and what is guessed.
  • Distinguish "I didn't find X" (an observation about your search — say which search) from "X doesn't exist".
Show full SKILL.md (220 more words)Show less

Style

  • Brevity comes from selecting what matters, not compressing the writing. Complete sentences, terms spelled out, no codenames or shorthand invented mid-task.
  • Write for the teammate who stepped away and is catching up — they did not watch the process unfold.
  • Report faithfully: if tests failed, say so with the output; if a step was skipped, say that; if something is done and verified, state it plainly without hedging.

Optional retrospective for major programs

Add a compact retrospective only when the user requests one or an approved substantial program designates it. Do not make it a routine handoff artifact.

Capture only evidence-backed learning:

  • decisions confirmed or changed and the evidence that changed them;
  • assumptions disproved;
  • patterns that worked and the conditions where they apply;
  • process that consumed time without changing a decision;
  • surprises and future triggers;
  • a promotion recommendation: keep local, refine a skill, or propose repository doctrine.

One incident normally remains a local lesson. Promote it into a reusable skill or AGENTS.md only when it reflects a stable repository property, repeats across materially distinct work, or the user explicitly approves the rule. Do not collect model mix, turn counts, task counts, or other decorative metrics unless they change a future decision.

Failure this prevents

The reader acting on a misread, and caveats surfacing after the decision they should have informed.

© happier-dev, 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 .agents/skills/handoff-report of happier-dev/happier.

Open the folder on GitHubat commit 1f03ccd

Compare with similar skills

Handoff Report 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.

Handoff Report compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Handoff Report this skillhappier-dev/happier1.9k—~944Automated safety check: PassMIT
Weekly Engineering Retrogarrytan/gstack136k—~2.4kAutomated safety check: PassMIT
Dough Execute Planterryyin/lizard2.5k—~4.3kAutomated safety check: PassCustom licence
After Action Reportrampstackco/claude-skills9401 repos~2.5kAutomated safety check: PassMIT
Oral Paper SkillAdkid-Zephyr/oral-paper-skill340—~1.9kAutomated safety check: PassNone
Deck Retroasheshgoplani/agent-deck1k—~1.8kAutomated safety check: PassMIT

Similar skills

  • Weekly Engineering Retro

    garrytan/gstack

    Builds a weekly engineering retrospective from git history: commit counts, per-person contributions, work patterns and code quality numbers over a chosen window.

    136k GitHub stars~2.4k tokensUpdated today
    Product & Project ManagementAuto-check passed

  • Dough Execute Plan

    terryyin/lizard

    Executes one selected story or bounded retrospective correction through an executable plan, or one authorized planless slice from a selected simple story or a contextual instruction, with…

    2.5k GitHub stars~4.3k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

  • After Action Report

    rampstackco/claude-skills

    Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons.

    940 GitHub starsUsed in 1 repo~2.5k tokens
    Product & Project ManagementAuto-check passed

  • Oral Paper Skill

    Adkid-Zephyr/oral-paper-skill

    Help authors learn from exemplary ICLR, ICML, and NeurIPS papers through source-linked manuscript comparisons, concrete writing and experiment suggestions, and guided reflection.

    340 GitHub stars~1.9k tokensUpdated 20 days ago
    Product & Project ManagementAuto-check passed

  • Deck Retro

    asheshgoplani/agent-deck

    Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs.

    1k GitHub stars~1.8k tokensUpdated 2 days ago
    Product & Project ManagementAuto-check passed

  • Dough Execution Retrospective

    terryyin/lizard

    Reviews planned, completed planless quick, or quick-to-planned execution against original intent, aggregate commits, current whole-product architecture, and tests, including after cleanup.

    2.5k GitHub stars~4k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

More from happier-dev/happier

All 28 skills in this repo

  • Happier Review

    happier-dev/happier

    Conduct evidence-backed Happier code, plan-completeness, session, worktree, feature, commit, branch, PR, codebase, and release-readiness reviews with affected-corridor analysis, high-confidence…

    1.9k GitHub stars~4.5k tokensUpdated today
    Auto-check passed

  • Happier CI Stabilize

    happier-dev/happier

    Stabilize failing, flaky, slow, or repeatedly rerun Happier CI and nightlies by collecting all reachable failures from one exact attempt, correcting canonical causes in one batch, simplifying…

    1.9k GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Happier Commit Worktree

    happier-dev/happier

    Reconnoiter, classify, validate, group, and commit a large or continuously changing Happier worktree as coherent, human-understandable commits while preserving concurrent work and excluding…

    1.9k GitHub stars~3.9k tokensUpdated today
    Auto-check passed

  • Happier Release

    happier-dev/happier

    Resolve Happier's private release authority and run an exact-SHA release or nightly through cheap admission, verified CI evidence, resumable immutable candidates, and terminal publication proof.

    1.9k GitHub stars~2.4k tokensUpdated today
    Auto-check passed

  • Happier Diagnose

    happier-dev/happier

    Diagnose and explain a Happier runtime, session, daemon, provider (Claude/Codex/OpenCode), authentication, or connectivity incident from logs, structured diagnostics, runtime state, and source…

    1.9k GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Happier Implement

    happier-dev/happier

    Implement, change, build, fix, refactor, migrate, or apply accepted review findings in the Happier repositories with canonical-owner discovery, scope-preserving solution economy, TDD, efficient…

    1.9k GitHub stars~4.2k tokensUpdated today
    Auto-check passed

Categories

Questions about Handoff Report

What does Handoff Report do?

Output contract for substantive deliverables — outcome first, evidence-pointed reasoning, observed/derived/assumed labels, residual risk last, failures never buried, and an optional evidence-backed…. Handoff Report is an agent skill from happier-dev/happier. Output contract for substantive deliverables — outcome first, evidence-pointed reasoning, observed/derived/assumed labels, residual risk last, failures never buried, and an optional evidence-backed retrospective for explicit requests or major program closeout.

When should I use Handoff Report?

Handoff Report fits situations like: reporting completed work; A requested retrospective.

How do I install Handoff Report in Claude Code?

Run `npx skills add happier-dev/happier --skill handoff-report -a claude-code`. Or copy the skill folder (.agents/skills/handoff-report in happier-dev/happier) into .claude/skills/handoff-report in your project. Claude Code loads it when a task matches its description.

How do I install Handoff Report in Codex?

Run `npx skills add happier-dev/happier --skill handoff-report -a codex`. Or copy the skill folder (.agents/skills/handoff-report in happier-dev/happier) into .agents/skills/handoff-report in your project. Codex loads it when a task matches its description.

Can I use Handoff Report 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 happier-dev/happier --skill handoff-report -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/handoff-report, .gemini/skills/handoff-report, .github/skills/handoff-report and .opencode/skills/handoff-report in your project.

What does Handoff Report need to run?

SKILL.md names no scripts, command-line tools or credentials: Handoff Report is instructions for the agent only.

Does Handoff Report access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Handoff Report safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Handoff Report use?

Handoff Report 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 Handoff Report use?

About 944 tokens (SKILL.md is roughly 3.8k 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 Handoff Report?

Skills that share tags, products or a category with Handoff Report: Weekly Engineering Retro (garrytan/gstack, 136k stars), Dough Execute Plan (terryyin/lizard, 2.5k stars), After Action Report (rampstackco/claude-skills, 940 stars) and Oral Paper Skill (Adkid-Zephyr/oral-paper-skill, 340 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Handoff Report?

happier-dev (a GitHub organization) maintains it in happier-dev/happier, which has 1,883 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 8, 2026.

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