Progress And Streaming
Convention for streaming progress on long-running audit commands. Use during /audit, /audit-deep, /audit-strict, /simulate, /exploit-chain — anything taking >10 seconds.
Install
$ agentstack add skill-omermaksutii-rugproof-progress-and-streaming ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README — it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-omermaksutii-rugproof-progress-and-streaming) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Progress & streaming (meta-skill)
Long audits with no output feel broken. This skill defines the contract for live updates.
When to stream
- Any command expected to take >10 seconds.
- Any command that dispatches multiple subagents in parallel.
- Any command that reads many files (>5).
What to emit
Stream short status lines to stdout as work progresses. Each line should be self-contained — a user reading the third line shouldn't need the first two.
Stages
[1/5] Inventory scanning src/ for Solidity files
[1/5] Inventory found 12 files (3,456 LoC), Solidity 0.8.24
[2/5] Skills running reentrancy, access-control, oracle-manipulation, …
[2/5] Skills 18 skill checks complete (847ms)
[3/5] Specialists dispatching: amm-specialist, attacker, defender (parallel)
[3/5] Specialists amm-specialist: 3 findings
[3/5] Specialists attacker: 5 findings (1 chain candidate)
[3/5] Specialists defender: 2 missing-defense notes
[4/5] Consolidate dedup + severity assignment
[5/5] Report 12 findings, grade C → wrote rugproof-reports/audit-2026-05-13.mdFormat
[N/M] STAGE message— N is current stage, M is total- Stage name padded to 12 chars for alignment
- Message in lowercase, terse, no "I am now ..." prose
- Numbers preferred over adjectives ("847ms" beats "quickly")
Don't
- No spinners or animations (terminal output, not UI).
- No ANSI colors unless
process.stdout.isTTYAND user hasn't disabled. - No hidden state — every meaningful event gets a line.
Cancellation
If the user interrupts (Ctrl+C / Esc), emit:
[!] cancelled at stage [3/5]: dispatched specialists are still running, partial results saved to .rugproof/partial/Implementation note
In a Claude Code slash-command context, this means: emit short text messages between tool calls. The user sees them streamed. Don't batch all updates into a final block.
Related
- [[caching-and-incremental]] — show cache stats in stage [1/5]
- [[confidence-scoring]] — show per-skill confidence as findings come in
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: omermaksutii
- Source: omermaksutii/RugProof
- License: MIT
- Homepage: https://omermaksutii.github.io/RugProof
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.