Skip to content
Agentmart
Submit a tool

status-beacon

Lightweight mid-flight progress logging for long agent runs.

Skill by AQaddora

IndexedMIT★ 3
Write a review

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/aqaddora-status-beacon

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

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.

Use cases: documents, productivity, agent-building

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. Checked Oct 25, 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/status-beacon

What's inside

Skill name
status-beacon
Description
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.
License
MIT
Instructions
48 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Status-beacon

A long agent run is a black box until it ends. This skill cracks the box open with cheap, append-only progress notes so the orchestrator can watch without stopping the work.

## When to Use This Skill

Trigger when:

- A task spans many phases / long execution (a `report-back` at the end isn't enough visibility)
- The user says "keep a log", "leave progress notes", "beacon this", "let me track this"
- An `execute` run delegates to a coding agent that will run for a while

## How It Works

### Append, don't rewrite
Append one block per milestone to `progress.md` in the active bundle/work dir:

```markdown
## <ISO timestamp> — <phase>
- Did: <one line>
- Next: <one line>
- Blocked: <none | reason>
- Confidence: <high | medium | low> that this is on track
```

### Cadence
One beacon per meaningful milestone (a phase done, a decision made, a block hit) — not per file edit. Aim for signal, not noise: a reader should reconstruct the run from the beacons alone.

### Handoff to report-back
When the run ends, `report-back` reads `progress.md` to seed the final report, then writes the `-shipped/handoff.md`. Beacons are the rough log; the report is the clean record.

## Operational Rules

1. **Append-only.** Never rewrite history — the timeline is the value.
2. **Milestones, not keystrokes.** Beacon on phase/decision/block boundaries.
3. **Be honest about confidence.** "low confidence, exploring" beats false certainty.
4. **No secrets in the log.** Same rule as everywhere.
5. **Beacons feed `report-back`.** Don't duplicate the final report inline.

## Position in the PURE Loop

Runs alongside `execute` for long delegations; its `progress.md` is the raw material `report-back` distills. Together with `organize-agents`, it gives the orchestrator both live (beacon) and final (report) views of every run.

---

*Part of the [Vibe Coding Mastery](https://github.com/AQaddora/vibe-coding-mastery) skill suite. MIT licensed.*

From AQaddora/pure-skill-suite, MIT.

More from AQaddora/pure-skill-suite

Signals

Stars
3
Forks
0
Open issues
0
Last commit (this folder)
May 31, 2026 (5 months ago)
Last release
May 31, 2026 (5 months ago)

From GitHub (fetched Oct 24, 2026).

Details

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

More from AQaddora

Cite this page

status-beacon skill. Agent Mart. https://agentmart.dev/skills/aqaddora-status-beacon (last updated 2026-10-24)