packet-factory
Creates, reviews, and dispatches atomic work packets. Every task with a side effect requires an APPROVED packet before execution. Scope is immutable after approval — expansion requires a new packet.
57
66%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./examples/jason-my-claw-is-the-law-deebee-4567b4/skills/packet-factory/SKILL.mdPacket Factory
The packet factory is the gatekeeper between intent and execution. Nothing with a side effect runs without an APPROVED packet.
Commands
# Create a new packet (DRAFT status)
skills/packet-factory/new-packet.sh \
--intent "Post daily update to Slack #arc-angels" \
--source "Ludo DM 2026-04-01 09:00" \
--destination "Slack #arc-angels"
# Review a packet (set APPROVED or REJECTED)
skills/packet-factory/review-packet.sh --id 2026-04-01-001
# Dispatch an APPROVED packet (executes and logs output)
skills/packet-factory/dispatch-packet.sh --id 2026-04-01-001Packet Queue
All in-flight packets live in memory/packet-queue.md.
The heartbeat pre-flight check reads this file. DRAFT packets older than 24h are escalated to Ludo.
Scope Lock Rule
Once a packet is APPROVED, scope_locked_at is set and the scope field is frozen.
If the task grows (new deliverable discovered, Ludo asks for something extra), the current packet is dispatched as-is and a new packet is created for the expansion. Never mutate an approved packet's intent or output.
This prevents the single most common failure mode: scope creep → context balloon → session death.
- Repository
- open-gitagent/opengap
- Commit
d7a8e2e
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.