Skip to content
Agentmart
Submit a tool

regrounding-summary

Make Claude Fable 5 / 5.1's final report readable to someone who saw none of the work.

Skill by kpab

IndexedMIT★ 19
Write a review

Chalk Labs

Need help deploying regrounding-summary?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/kpab-regrounding-summary

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Make Claude Fable 5 / 5.1's final report readable to someone who saw none of the work. Use for long agentic sessions, overnight runs, and multi-tool tasks — whenever summaries come back as arrow-chain shorthand, invented abbreviations, references to reasoning the reader never saw, dense unbroken paragraphs, or source passages reproduced without quotation marks. Pair with grounded-progress for status content; this skill governs the prose.

Use cases: documents, writing

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md and code. Checked Oct 26, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/regrounding-summary

What's inside

Skill name
regrounding-summary
Description
Make Claude Fable 5 / 5.1's final report readable to someone who saw none of the work. Use for long agentic sessions, overnight runs, and multi-tool tasks — whenever summaries come back as arrow-chain shorthand, invented abbreviations, references to reasoning the reader never saw, dense unbroken paragraphs, or source passages reproduced without quotation marks. Pair with grounded-progress for status content; this skill governs the prose.
License
MIT
Instructions
27 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Re-grounding Summary

During a long run the model builds private vocabulary — abbreviations, arrow chains, names for intermediate artifacts. Efficient while working; opaque in a final report. The reader is seeing everything for the first time, so the summary must be a re-grounding, not a continuation of the working thread.

## Rules for the final message

- Open with the outcome: one sentence answering "what happened?" or "what did you find?" — the TL;DR the reader would ask for. Detail follows, never leads.
- Complete sentences. No arrow chains (A → B → fails), no hyphen-stacked compound labels, no abbreviations you coined mid-run. If a term you built up is worth keeping, reintroduce it as if new.
- Never reference your own working notes or reasoning as if the reader saw them ("as established above" pointing at tool transcripts).
- Identifiers — files, commits, flags, endpoints — each get their own plain-language clause: what it is, why it matters here.
- Selectivity over compression: shorten by dropping details that wouldn't change the reader's next action, not by squeezing grammar out of the sentences. Readable beats short.
- Short sentences, short paragraphs. When a literal phrase exists, use it; a metaphor or flourish standing in for a direct statement is noise to remove.
- When you reuse a source's wording, mark it as a quotation. Everything else in your own words.
- Close with the one or two things needed from the reader, if any.

## Shape

1. Outcome (1 sentence)
2. What was done / found, in reader-facing language
3. Failures, skips, open questions — stated plainly
4. What's needed from you: ...

## Before the final message

Open the task with one line saying what you're about to do, and keep short updates flowing while you work, so the recap isn't the reader's first contact with the task. Working shorthand between tool calls is otherwise fine — that's thinking out loud. This skill's rules apply the moment you address the human.

From kpab/claude-fable-5-skills, MIT.

More from kpab/claude-fable-5-skills

Signals

Stars
19
Forks
2
Open issues
0
Last commit (this folder)
Sep 2, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from kpab

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get regrounding-summary running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying regrounding-summary?

CallGet help
Cite this page

regrounding-summary skill. Agent Mart. https://agentmart.dev/skills/kpab-regrounding-summary (last updated 2026-10-24)