Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

report-back

Étoiles3

Forks0

Mis à jour31 mai 2026 à 21:39

The mandatory completion-report skill. When an agent finishes (or is blocked on) a handoff bundle or delegated task, it MUST write the outcome to files — never only into chat. Triggers on "I'm done", "this is shipped", "wrap up", "close out this task", "I'm blocked", or automatically at the end of any `handoff-receiver` / `execute` run. Writes a `<bundle>-shipped/handoff.md` report with a fixed schema (commit SHA, what shipped, files touched, test/smoke results, deferred items, new open questions) and sets the source bundle's `manifest.json` status to `shipped · <SHA>` or `blocked · <reason>`. This is the file-based feedback loop that lets a control plane track every agent across tools.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

AQaddora

AQaddora/pure-skill-suite

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	report-back
description	The mandatory completion-report skill. When an agent finishes (or is blocked on) a handoff bundle or delegated task, it MUST write the outcome to files — never only into chat. Triggers on "I'm done", "this is shipped", "wrap up", "close out this task", "I'm blocked", or automatically at the end of any `handoff-receiver` / `execute` run. Writes a `<bundle>-shipped/handoff.md` report with a fixed schema (commit SHA, what shipped, files touched, test/smoke results, deferred items, new open questions) and sets the source bundle's `manifest.json` status to `shipped · <SHA>` or `blocked · <reason>`. This is the file-based feedback loop that lets a control plane track every agent across tools.
license	MIT

Report-back

Files in, files out. A delegated agent that reports only in chat is invisible the moment the chat closes. This skill makes the report a durable artifact the orchestrator can read.

When to Use This Skill

Trigger when the agent:

Finishes a handoff bundle or delegated task ("done", "shipped", "wrap up", "close out")
Hits a hard block it can't resolve ("I'm blocked", "stopping here")
Reaches the end of a handoff-receiver or execute run (automatic)

How It Works (3-Step Protocol)

Step 1 — Write the completion report

Create <original-bundle>-shipped/handoff.md next to the source bundle (e.g. ~/Work/AgentHandoffs/2026-05-30-foo-shipped/handoff.md). Fixed schema:

# Shipped — <bundle name>
- Date / agent / tool:
- Commit SHA(s):
- What shipped: (bullet list of concrete changes)
- Files touched: (paths)
- Smoke / test results: (what you ran, what passed)
- Deferred / not done: (with reason)
- New open questions: (for the orchestrator/Ahmed)
- Deploy status: (prepared commands handed to Ahmed / deployed / N/A)

Step 2 — Update the source manifest

Set the source bundle's manifest.json status to shipped · <SHA> or blocked · <reason>. This is the single field an orchestrator polls to know state.

Step 3 — One-line chat summary + pointer

In chat, write one line: what shipped + the report path. Nothing more — the file is the record.

Operational Rules

Report is mandatory, not optional. No "done" without a written report.
Status field is the contract. Always update manifest.json status — orchestrators read it, not prose.
Honest blocked > fake shipped. If tests fail or work is partial, write blocked with the reason. Never mark shipped on partial work.
No secrets in reports. SHAs, paths, results — never tokens, keys, or other-client data.
Don't deploy to report. If deploy is the user's step, record "commands handed to Ahmed", don't push.

Position in the PURE Loop

The terminal step after execute / handoff-receiver. Pairs with organize-agents: report-back writes the per-task record; organize-agents indexes runs across tools.

Part of the Vibe Coding Mastery skill suite. MIT licensed.

Plus depuis ce dépôt

même dépôt

3d-modeler

AQaddora/pure-skill-suite

Generates 3D interior models from photos and injects them into Mapbox GL JS map instances.

2026-06-233

montage-creator

AQaddora/pure-skill-suite

Generates dynamic video montages and edits video content for social distribution.

2026-06-233

handoff-receiver

AQaddora/pure-skill-suite

The cold-start protocol for an AI agent PICKING UP a handoff bundle (the receiving half of `handoff`). Triggers when a fresh session is pointed at a handoff directory or pasted a handoff block — e.g. "read this handoff", "take over from this bundle", "you're picking up <path>", "continue this work", or when the first message is a handoff block. Boots the agent loaded: reads the bundle README + manifest, runs Prime from it, confirms understanding and locked decisions BEFORE writing code, and refuses to start on a bundle with no manifest/mission. Works in any tool (Claude, Cursor, Copilot, Codex, Gemini, Aider, Windsurf).

2026-05-313

status-beacon

AQaddora/pure-skill-suite

Lightweight mid-flight progress logging for long agent runs. Where `report-back` writes the final outcome, status-beacon drops short, timestamped progress notes to a file DURING the work so a human or orchestrator can check in without interrupting. Triggers on long/multi-phase tasks, or when the user says "keep a log", "leave progress notes", "beacon this", "let me track this". Appends to a `progress.md` inside the active bundle/work dir. Honest about uncertainty — notes are signals, not guarantees. Works across Claude, Cursor, Copilot, Codex, Gemini, Aider, Windsurf.

2026-05-313

doctrine-keeper

AQaddora/pure-skill-suite

Captures insights, rules, and learnings from any AI coding conversation into the user's personal ai-doctrine.md file — a single source of truth that is then auto-synced into Claude Code, Cursor, Copilot, Codex, Gemini CLI, and Windsurf so every tool the user opens reads the same hard-won rules. Use this skill whenever the user says "add to doctrine", "save this rule", "capture this learning", "this should be a rule", "doctrine this", "remember this", or asks to record an insight from a prompt/response. Also triggers when the user shares a hard-won learning, a prompt pattern that worked unusually well, a failure mode to avoid, or any rule they want to remember across tools.

2026-05-263

execute

AQaddora/pure-skill-suite

Delegates real work to a coding agent (Claude Code, Cursor agent mode, Codex, Aider) and tracks the run end-to-end. Triggers on "execute", "run agent", "ship this", "delegate this", "hand off to Claude Code". Creates a run reference, watches for completion signals, links output back into the conversation, and offers to save successful execution patterns to ~/ai-doctrine.md so the same delegation playbook works across every agentic tool the user has installed.

2026-05-263

name	report-back
description	The mandatory completion-report skill. When an agent finishes (or is blocked on) a handoff bundle or delegated task, it MUST write the outcome to files — never only into chat. Triggers on "I'm done", "this is shipped", "wrap up", "close out this task", "I'm blocked", or automatically at the end of any `handoff-receiver` / `execute` run. Writes a `<bundle>-shipped/handoff.md` report with a fixed schema (commit SHA, what shipped, files touched, test/smoke results, deferred items, new open questions) and sets the source bundle's `manifest.json` status to `shipped · <SHA>` or `blocked · <reason>`. This is the file-based feedback loop that lets a control plane track every agent across tools.
license	MIT

Report-back

Files in, files out. A delegated agent that reports only in chat is invisible the moment the chat closes. This skill makes the report a durable artifact the orchestrator can read.

When to Use This Skill

Trigger when the agent:

Finishes a handoff bundle or delegated task ("done", "shipped", "wrap up", "close out")
Hits a hard block it can't resolve ("I'm blocked", "stopping here")
Reaches the end of a handoff-receiver or execute run (automatic)

How It Works (3-Step Protocol)

Step 1 — Write the completion report

Create <original-bundle>-shipped/handoff.md next to the source bundle (e.g. ~/Work/AgentHandoffs/2026-05-30-foo-shipped/handoff.md). Fixed schema:

# Shipped — <bundle name>
- Date / agent / tool:
- Commit SHA(s):
- What shipped: (bullet list of concrete changes)
- Files touched: (paths)
- Smoke / test results: (what you ran, what passed)
- Deferred / not done: (with reason)
- New open questions: (for the orchestrator/Ahmed)
- Deploy status: (prepared commands handed to Ahmed / deployed / N/A)

Step 2 — Update the source manifest

Set the source bundle's manifest.json status to shipped · <SHA> or blocked · <reason>. This is the single field an orchestrator polls to know state.

Step 3 — One-line chat summary + pointer

In chat, write one line: what shipped + the report path. Nothing more — the file is the record.

Operational Rules

Report is mandatory, not optional. No "done" without a written report.
Status field is the contract. Always update manifest.json status — orchestrators read it, not prose.
Honest blocked > fake shipped. If tests fail or work is partial, write blocked with the reason. Never mark shipped on partial work.
No secrets in reports. SHAs, paths, results — never tokens, keys, or other-client data.
Don't deploy to report. If deploy is the user's step, record "commands handed to Ahmed", don't push.

Position in the PURE Loop

The terminal step after execute / handoff-receiver. Pairs with organize-agents: report-back writes the per-task record; organize-agents indexes runs across tools.

Part of the Vibe Coding Mastery skill suite. MIT licensed.