/quick-recapSAFE
Skills for agents
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
Make the agent's work state obvious at the end of every response.
/quick-recap adds a small red/yellow/green status footer convention. It answers the thing users otherwise have to infer from a long response: done, pending, or blocked.
What It Does
- Adds a single final status line.
- Defines when to use green, yellow, or red.
- Keeps the status user-facing and under 100 characters.
- Installs cleanly into
AGENTS.mdorCLAUDE.mdthrough a managed block.
When To Use It
Use it when you want every completed unit of work to end with a reliable state signal. It is especially useful in repos where multiple agents, long-running work, or partial handoffs can make status hard to scan.
Status Meanings
- Green: the requested coding or work unit is finished.
- Yellow: specific non-routine follow-up remains.
- Red: the agent cannot continue without user input.
Output Examples
Green means the work unit is done:
🟢 Updated quick recap docs with output examples
Yellow means a specific non-routine item remains:
🟡 Code updated, set PROVIDER_WEBHOOK_SECRET before testing webhooks
Red means the agent is blocked on user input:
🔴 Need the production API key to continue
Install
npx @agent-native/skills@latest add --skill quick-recap --update-instructions
Use --update-instructions; copying the skill alone does not make the footer automatic.
3e67e99960c8OBSERVED · 2026-10-21What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: quick-recap description: Use when adding or following the red/yellow/green final status block convention for agent responses, especially by installing managed AGENTS.md or CLAUDE.md instructions. --- # Quick Recap Make completion state obvious at the end of every response. ## Status Block Every response that completes a unit of work must end with: ```md 🟢 Actual concise status sentence ``` Rules: - Keep the status line under 100 characters. - Use `🟢` when the requested work is finished. - Use `🟡` when non-routine follow-up remains; name the pending item. - Use `🔴` only when blocked on user input. - Put the status line at the very end of the response. - Do not add `---`, spacer lines, or any content after the status line. ## Installer Behavior This convention is only automatic when it is present in project or user instructions. When installing this skill, prefer adding the managed `AGENTS.md` / `CLAUDE.md` block unless the user opts out. If you are following the convention manually, choose the status from the user's perspective: finished, pending a specific non-routine step, or blocked. ## Examples Finished work: ```md 🟢 Updated quick recap docs with output examples ``` Non-routine follow-up remains: ```md 🟡 Code updated, set PROVIDER_WEBHOOK_SECRET before testing webhooks ``` Blocked on user input: ```md 🔴 Need the production API key to continue ```
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | NA |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
3e67e99960c8full audit observations/trust-audit/skill/builderio__quick-recap.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-21 | 3e67e99960c8 | SAFE | B | 89 | first audit |
Questions
What does the quick-recap — builderio/skills skill do?
Skills for agents
Is quick-recap — builderio/skills safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can quick-recap — builderio/skills access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (3e67e99960c8), read on 2026-10-21. The repository is watched, and a new audit runs when it changes — this is the first audit.
Add this badge to your README
Shows this page's audit result and links back to it. It updates when the audit does.
[](https://modelsatlas.com/skills/builderio/quick-recap/)
Not your listing, or something out of date? Claim or update your listing.