Agent Seatbelt Guardrails
Security / Guardrails · Companion skill for the free Agent Seatbelt gate, version 0.3.2
FreeCompanion skill
VettedVerified BundleFull RecordWorked ExamplesFirst-PartyFree
Your agent stops asking permission for the safe calls, and can never quietly make the dangerous ones.
What changes
- Unlogged tool calls → every call decided and logged before it runs
- Improvised refusals → the same policy answers every time, with the reason on record
- "Trust me, it was fine" → here is the log
Honest fit
For you if: your agent can call tools and you want the dangerous ones stopped cold, with the reason on record.
Skip it if: your agent only chats and never acts on anything.
Your first run produces: one real tool call decided by the gate, its verdict and reason in the log.
Preview, from the skill itself
“Agent Seatbelt is a deterministic policy gate between an agent's decision and the tool call. It classifies each Bash/PowerShell/file/MCP call, decides it against locked rules plus the project overlay, and writes an audit record BEFORE the call runs.”
SKILL.mdWorks with 20+ agentsClaude Code, Cursor, Copilot, CodexHash verified against the registry
Package makeup: 1 skill file · 1 file across 1 worked example
Vetting record
Scanned Nov 11, 2026 with the Skill Vetting scanner. 2 files scanned. Result: 2 leads, reviewed. One is the source link to the skill's own public GitHub repo. The other is the worked example's quoted audit log line, the hash-chained record the example exists to show.
Second scan (gitleaks 8.30.1, Nov 11, 2026): no secrets found.
Bundle sha256: a469a2603bce… Short form. The full hash lives in the registry and is verified on every gate run.
Bundle size: 10.0 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub The full package is published in that repository. Project repository: Agent Seatbelt on GitHub
Listing record: 8 of 8
What's inside
SKILL.md, examples/first-run/WALKTHROUGH.md
Worked example, from the package
examples/first-run/WALKTHROUGH.md
Worked example: the first run. This is the first run the skill itself prescribes, done for real on Nov 11, 2026 against the real gate (ghost-seatbelt 0.3.2, seatbelt_hook.py): one dangerous call staged, its verdict read, and its record found in the audit log.
Install the free skill with the standard skills CLI: npx skills add littlestjames82-sys/ghostbus-hub-skills (tested Nov 11, 2026).
Seatbelt Policy Authoring
Security / DevOps · Version 1.3.0 · 35 files
$19one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A policy that fits your project, written from your answers, with every risky rule proven in check mode before it can block anything real.
What changes
- Generic template rules → rules shaped by your project's actual work
- An untested policy → every rule that can deny runs a test battery first
- Policy drift no one noticed → a versioned policy with a change record
Honest fit
For you if: you run the Seatbelt gate and your project has its own shape, its own tools, and its own lines.
Skip it if: you want a generic policy dropped in without answering the interview.
Your first run produces: a draft policy for one small project, and one rule proven in check mode.
Preview, from the skill itself
“Agent Seatbelt ships with locked rules that stop the universally dangerous things. What it cannot know out of the box is your project: which command deploys to production, where the real database lives, which destructive command is a normal Tuesday for you and which one would end the week.”
Version 1.3.035 files10 check quality gate5 worked examplesHash verified against the registry
Package makeup: 1 skill file · 20 files across 5 worked examples · 9 references · 5 templates
Vetting record
Scanned Nov 4, 2026 with the Skill Vetting scanner. 35 files scanned. Result: 70 raw leads, reviewed at listing. They sit in the test batteries and pattern cookbook, the worked attack and policy samples this skill teaches operators to defend against.
Second scan (gitleaks 8.30.1, Nov 4, 2026): no secrets found.
Bundle sha256: da74e0f70ddf… Short form. The full hash lives in the registry and is verified on every gate run.
Bundle size: 107.3 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub The package itself is delivered with purchase. Project repository: Agent Seatbelt on GitHub
Listing record: 8 of 8
What's inside
SKILL.md, examples/ci-team/EXPLANATION.md, examples/ci-team/TEST_BATTERY.md, examples/ci-team/policy.json, examples/data-pipeline/EXPLANATION.md, examples/data-pipeline/INTERVIEW.md, examples/data-pipeline/TEST_BATTERY.md, examples/data-pipeline/policy.json, examples/harbor-api/EXPLANATION.md, examples/harbor-api/INTERVIEW.md, examples/harbor-api/TEST_BATTERY.md, examples/harbor-api/plan.json, examples/harbor-api/policy.json, examples/infra/EXPLANATION.md, examples/infra/INTERVIEW.md, examples/infra/TEST_BATTERY.md, examples/infra/policy.json, examples/policy-audit/AUDIT.md, examples/policy-audit/TEST_BATTERY.md, examples/policy-audit/flawed-policy.json, examples/policy-audit/policy.json, reference/ask-budget.md, reference/audit-taxonomy.md, reference/ci-and-team.md, reference/host-notes.md, reference/incident-to-rule.md, reference/interview-bank.md, reference/pattern-cookbook.md, reference/stack-archetypes.md, reference/variation-battery.md, templates/audit-scorecard.md, templates/plan.template.json, templates/policy-pr-template.md, templates/policy.template.json, templates/tuning-log.md
Worked example, from the package
examples/policy-audit/AUDIT.md
Worked example: the shopfront audit. shopfront is fictional: a small Next.js storefront, npm, deploys as npm run deploy:prod (and deploy:preview for previews)
Skill Vetting
Security / Code Review · Version 1.0.0 · 11 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
You know what a skill will do to your machine before it runs, in writing.
What changes
- Install and hope → a written audit first
- README claims → the code read against 33 named patterns
- A vague unease → a verdict: install, fix first, or refuse, with the evidence attached
Honest fit
For you if: you install skills other people wrote.
Skip it if: you only ever run code you wrote yourself.
Your first run produces: one real audit of a skill you were about to install anyway.
Preview, from the skill itself
“A skill is a set of instructions your agent will follow later, in your projects, with your permissions. Installing one on trust is the same as pasting an unsigned script into your own runbook because the description sounded friendly.”
11 files8 review areas2 worked auditsNever runs the packageHash verified against the registry
Package makeup: 1 skill file · 7 files across 2 worked examples · 2 references · 1 script
Vetting record
Scanned Nov 4, 2026 with the Skill Vetting scanner. 11 files scanned. Result: 106 raw leads, reviewed at listing. The leads are the product itself, its pattern library and review checklist, plus a deliberately trapped example skill shipped as teaching material.
Second scan (gitleaks 8.30.1, Nov 4, 2026): no secrets found.
Bundle sha256: 8ca6bc269c6d… Short form. The full hash lives in the registry and is verified on every gate run.
Bundle size: 50.5 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/clean-skill/AUDIT.md, examples/clean-skill/SKILL.md, examples/clean-skill/reference/format-guide.md, examples/trapped-skill/AUDIT.md, examples/trapped-skill/SKILL.md, examples/trapped-skill/reference/quick-wins.md, examples/trapped-skill/reference/setup-guide.md, reference/report-template.md, reference/review-checklist.md, scripts/scan_skill.py
Worked example, from the package
examples/clean-skill/AUDIT.md
Skill audit: Meeting Notes Formatter (worked example). This is a fictional package, written as the clean half of this skill's pair of worked examples.
Skill Authoring
Agent Skills / Authoring · Version 1.0.0 · 13 files
$19one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Your repeated workflows become skills another agent can run without you in the room.
What changes
- Knowledge stuck in your head → ground rules, workflow, and examples in one package
- A draft that drifts → a self-vet checklist the skill has to pass
- One-off prompts → a versioned, installable package
Honest fit
For you if: you keep explaining the same workflow to your agent, week after week.
Skip it if: one-off prompts are all you ever need.
Your first run produces: a minimal skill skeleton that passes its own checklist.
Preview, from the skill itself
“A skill is a set of instructions someone else's agent will follow later, in their projects, with their permissions. That sentence is the whole discipline.”
Version 1.0.013 filesSelf-vet checklist and scorecardClean and adversarial examplesHash verified against the registry
Package makeup: 1 skill file · 3 files across 2 worked examples · 6 references · 3 templates
Vetting record
Scanned Nov 4, 2026 with the Skill Vetting scanner. 13 files scanned. Result: 0 findings.
Second scan (gitleaks 8.30.1, Nov 4, 2026): no secrets found.
Bundle sha256: 00fddc137435… Short form. The full hash lives in the registry and is verified on every gate run.
Bundle size: 30.9 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/from-idea-to-listing/WALKTHROUGH.md, examples/minimal-skill/AUTHORING_NOTES.md, examples/minimal-skill/SKILL.md, reference/description-triggers.md, reference/frontmatter-guide.md, reference/ground-rules-catalog.md, reference/listing-honesty.md, reference/self-vet-checklist.md, reference/structure-patterns.md, templates/authoring-scorecard.md, templates/example.template.md, templates/skill.template.md
Worked example, from the package
examples/from-idea-to-listing/WALKTHROUGH.md
Walkthrough: authoring Skill Vetting, end to end. A real package, authored with this workflow before this workflow was written down.
Agent Mail
Agent Comms / Email · Version 1.0.0 · 10 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Your agent drafts and prepares email all day; nothing leaves without your approval.
What changes
- An agent with a send button → drafts held at a gate
- Sent means gone → approval recorded before the send, the send recorded after
- Guessed facts in a draft → every message drafted from a brief with its facts checked
Honest fit
For you if: your agent drafts or sends email in your name.
Skip it if: you want the agent to send without your approval. This skill will never do that.
Your first run produces: one real email, drafted and held at the gate, nothing sent.
Preview, from the skill itself
“Email is the agent channel most likely to cause a real world problem: it leaves the building, it carries the principal's name, and it cannot be unsent.”
Version 1.0.010 filesDraft-approve-send gateInbound mail treated as dataHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 5 references · 2 templates
Vetting record
Scanned Nov 4, 2026 with the Skill Vetting scanner. 10 files scanned. Result: 0 findings.
Second scan (gitleaks 8.30.1, Nov 4, 2026): no secrets found.
Bundle sha256: 81c3849041cf… Short form. The full hash lives in the registry and is verified on every gate run.
Bundle size: 19.8 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/inbox-triage/TRIAGE.md, examples/license-delivery/WALKTHROUGH.md, reference/addressing.md, reference/attachments-and-files.md, reference/gate-protocol.md, reference/inbound-handling.md, reference/license-delivery.md, templates/compose-brief.template.md, templates/triage-report.template.md
Worked example, from the package
examples/license-delivery/WALKTHROUGH.md
Walkthrough: a Hub license delivered by mail. The run this package's delivery pattern was taken from, end to end.
Agent Phone
Agent Comms / Phone · Version 1.0.0 · 10 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Your agent works the call list you give it, briefed and approved first, and every call is logged.
What changes
- Improvised cold calls → a written brief approved before the dial
- Conversations no one recorded → a call log with the outcome
- Anyone can call anyone → outbound only through the approval gate
Honest fit
For you if: your agent makes or takes calls and you need a brief, an approval, and a log on every one.
Skip it if: you want high-volume calling without briefs or approvals.
Your first run produces: one briefed test call to a number you control, logged end to end, or the approved brief at the dial step.
Preview, from the skill itself
“Voice is the most committing channel an agent can use: it is live, it is personal, and the other side reasonably believes the voice speaks for the principal.”
Version 1.0.010 filesBrief-approve-dial gateCallers treated as dataHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 5 references · 2 templates
Vetting record
Scanned Nov 4, 2026 with the Skill Vetting scanner. 10 files scanned. Result: 0 findings.
Second scan (gitleaks 8.30.1, Nov 4, 2026): no secrets found.
Bundle sha256: c7a1c0948144… Short form. The full hash lives in the registry and is verified on every gate run.
Bundle size: 19.3 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/inbound-call/INBOUND.md, examples/outbound-call/WALKTHROUGH.md, reference/call-gate.md, reference/extensions-and-contacts.md, reference/inbound-calls.md, reference/media-and-quality.md, reference/texting.md, templates/call-brief.template.md, templates/call-log.template.md
Worked example, from the package
examples/outbound-call/WALKTHROUGH.md
Walkthrough: an approved outbound call on GhostPhone. The run this package's gate pattern was taken from, end to end, on the studio's own switch.
Agent Incident Review
Agent Ops / Incident Review · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
The next incident gets cheaper, because the last one was actually understood.
What changes
- It broke, we fixed it → a timeline with sources and the gaps named
- Blame → findings tiered by the evidence behind them
- The same failure twice → corrective actions with owners
Honest fit
For you if: an agent did something wrong, or nearly did, and you want it understood, not just fixed.
Skip it if: nothing has gone wrong yet and prevention is the job. Start with the free Guardrails skill instead.
Your first run produces: a one-page review of your most recent incident, with one finding tiered.
Preview, from the skill itself
“When an agent does something wrong, or nearly does, the first account of it is usually a story someone tells: reassuring, coherent, and built on memory. This skill produces the other kind of account: a review rebuilt from the records.”
Version 1.0.09 filesFindings in three tiersCorrective actions with checksHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 4, 2026 with the Skill Vetting scanner. 9 files scanned. Result: 0 findings.
Second scan (gitleaks 8.30.1, Nov 4, 2026): no secrets found.
Bundle sha256: d6cb3fd3b032… Short form. The full hash lives in the registry and is verified on every gate run.
Bundle size: 19.3 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/injection-attempt-review/REVIEW.md, examples/stale-draft-near-miss/REVIEW.md, reference/corrective-actions.md, reference/evidence-and-inference.md, reference/severity-and-scope.md, reference/timeline-reconstruction.md, templates/incident-report.template.md, templates/timeline.template.md
Worked example, from the package
examples/injection-attempt-review/REVIEW.md
Worked review: the inbox instruction attempt (contained). A completed short review on invented but representative records, showing the tiers and the discipline at small scale.
Agent Task Handoff
Agent Ops / Handoff · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Work passes between agents without the telephone game.
What changes
- Paste the chat log and hope → a capsule carrying the task, the context, and the authority restated
- "Did it land?" → a receipt verified line by line against the capsule
- Stale instructions working forever → a freshness window that expires the handoff
Honest fit
For you if: two or more agents, or two sessions, pass work between them.
Skip it if: one agent does everything inside a single session.
Your first run produces: one real capsule sent, and its receipt verified on return.
Preview, from the skill itself
“Most multi-agent failures are handoff failures: context that evaporates, scope that quietly grows in transit, two agents working the same job, a result nobody can trace back to its request.”
Version 1.0.09 filesAuthority never grows in transitReceiver verificationProof-trail receiptsHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 4, 2026 with the Skill Vetting scanner. 9 files scanned. Result: 0 findings.
Second scan (gitleaks 8.30.1, Nov 4, 2026): no secrets found.
Bundle sha256: e616a99f0187… Short form. The full hash lives in the registry and is verified on every gate run.
Bundle size: 18.9 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/bus-handoff/WALKTHROUGH.md, examples/refused-handoff/RECEIPT.md, reference/acceptance-and-verification.md, reference/capsule-anatomy.md, reference/failure-modes.md, reference/lifecycle-and-proof.md, templates/handoff-capsule.template.md, templates/handoff-receipt.template.md
Worked example, from the package
examples/bus-handoff/WALKTHROUGH.md
Walkthrough: a capsule handoff on the studio's bus. The pattern as the studio runs it, from a relay dress rehearsal in which a parent agent handed a subtask to a second agent through GhostBus and the studio's hosted relay, end to end.
Release Gatekeeper
Agent Ops / Release · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Nothing ships on a green feeling; it ships on evidence, gate by gate.
What changes
- Version numbers that disagree → version truth reconciled before anything else moves
- "Works on my machine" → evidence per gate, written into the release record
- Announced too early → nothing announced until the record says shipped
Honest fit
For you if: you ship software and "done" keeps getting announced before it is true.
Skip it if: you never release anything anyone else depends on.
Your first run produces: one pending change run to its first gate verdict, with the release record started.
Preview, from the skill itself
“Releases fail in a characteristic way: not with a dramatic error, but with a quiet mismatch. The tag says one version, the package says another, the announcement describes a build nobody ran.”
Version 1.0.09 filesFive separate gatesVersion truth reconciledRead-back confirmedHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 4, 2026 with the Skill Vetting scanner. 9 files scanned. Result: 0 findings.
Second scan (gitleaks 8.30.1, Nov 4, 2026): no secrets found.
Bundle sha256: a45760b02556… Short form. The full hash lives in the registry and is verified on every gate run.
Bundle size: 17.9 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/held-release/RECORD.md, examples/version-truth/WALKTHROUGH.md, reference/evidence-standards.md, reference/rollback-and-recovery.md, reference/the-gates.md, reference/version-truth.md, templates/release-checklist.template.md, templates/release-record.template.md
Worked example, from the package
examples/version-truth/WALKTHROUGH.md
Walkthrough: a version truth reconciliation. From a workspace-wide improvement pass across the studio's repositories, condensed to the reconciliation itself.
Agent Memory Keeping
Agent Ops / Memory · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Your agent remembers what matters, and corrections actually stick.
What changes
- Facts scattered across chats → sourced notes with dates
- A correction made once, wrong everywhere else → corrections propagated until the old wording searches back empty
- Guessed relationships → only what the user actually said, recorded as said
Honest fit
For you if: your agent works with you across weeks and keeps forgetting, or misremembering, what matters.
Skip it if: every task you give it is a one-off.
Your first run produces: three real memory notes, and one correction run the full distance.
Preview, from the skill itself
“An agent's memory is a promise to the next conversation: what is written there will be believed later, by a version of the agent that was not present when it happened. This skill keeps that promise honest.”
Version 1.0.09 filesCorrections that propagateProvenance you can checkHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 4, 2026 with the Skill Vetting scanner. 9 files scanned. Result: 0 findings.
Second scan (gitleaks 8.30.1, Nov 4, 2026): no secrets found.
Bundle sha256: b92354a292d5… Short form. The full hash lives in the registry and is verified on every gate run.
Bundle size: 19.2 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/correction-propagation/WALKTHROUGH.md, examples/parked-plan/WALKTHROUGH.md, reference/corrections-and-conflicts.md, reference/hygiene-and-forgetting.md, reference/provenance-and-trust.md, reference/what-earns-a-note.md, templates/correction-record.template.md, templates/memory-note.template.md
Worked example, from the package
examples/correction-propagation/WALKTHROUGH.md
Walkthrough: the phone number correction. A real correction from the studio's own memory, worked end to end.
Backups and Restore Drills
Agent Ops / Backups · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A backup you have already restored from once is the only kind that counts.
What changes
- The job says success → a hash manifest you can check yourself
- Restore as a hope → one file restored and verified before you ever need it
- "When was this taken, of what?" → a backup record that answers both
Honest fit
For you if: you have backups you have never once restored from.
Skip it if: you already run restore drills and can show the last one.
Your first run produces: one real backup with its manifest, and one file restored and verified.
Preview, from the skill itself
“A backup that has never been restored is not a backup; it is a belief.”
Version 1.0.09 filesSha256 manifest in and outScratch restores, hash verifiedTimed drillsHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 4, 2026 with the Skill Vetting scanner. 9 files scanned. Result: 0 findings.
Second scan (gitleaks 8.30.1, Nov 4, 2026): no secrets found.
Bundle sha256: 2e38fe6cfce1… Short form. The full hash lives in the registry and is verified on every gate run.
Bundle size: 18.4 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/hub-restore-drill/WALKTHROUGH.md, examples/the-config-that-wasnt/LESSON.md, reference/drill-cadence.md, reference/failure-modes.md, reference/manifest-discipline.md, reference/restore-verification.md, templates/backup-record.template.md, templates/drill-report.template.md
Worked example, from the package
examples/hub-restore-drill/WALKTHROUGH.md
Walkthrough: the combined hub and mail drill. The drill pattern as the studio runs it against its own marketplace state and mail service, condensed from the tools' actual behaviour.
Marketplace Replies
Agent Comms / Marketplace · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Every inquiry gets a fast, honest reply, and you still send each one yourself.
What changes
- Typing the same answers all day → facts-first drafts built from your own figures
- Guessed numbers → only prices you have actually set, gaps flagged instead of filled
- Questions scattered over six messages → the qualifying questions asked together, once
Honest fit
For you if: you sell on Marketplace and answer the same questions every day.
Skip it if: you want replies sent automatically without reading them. The operator sends here.
Your first run produces: one live thread drafted and held, ready for you to paste and send.
Preview, from the skill itself
“Local service work is won and lost in the message thread. A buyer asks three sellers the same question; the one who answers clearly, asks the right qualifying questions, and quotes honestly gets the job.”
Version 1.0.09 filesFacts first, no invented pricesOperator approves and sendsHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 4, 2026 with the Skill Vetting scanner. 9 files scanned. Result: 0 findings.
Second scan (gitleaks 8.30.1, Nov 4, 2026): no secrets found.
Bundle sha256: 7fced4111374… Short form. The full hash lives in the registry and is verified on every gate run.
Bundle size: 18.4 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/firewood-half-load/WALKTHROUGH.md, examples/valley-roof-repair/WALKTHROUGH.md, reference/drafting-in-voice.md, reference/money-and-terms.md, reference/thread-tracking.md, reference/triage-and-facts.md, templates/inquiry-record.template.md, templates/reply-draft.template.md
Worked example, from the package
examples/firewood-half-load/WALKTHROUGH.md
Worked example: the half load of firewood. A real-shaped inquiry from the studio's firewood listing: a buyer two towns over asks what a half load delivered would cost.
Photo Job Quoting
Local Services / Quoting · Version 1.0.0 · 9 files
$19one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A quote from photos that says what it is built on, and what the photos cannot prove.
What changes
- A number from a glance → a worksheet: evidence read, quantities counted, real listed prices
- Hidden surprises → the cannot-tell items listed beside the figures, in the open
- Materials and profit blurred together → separate lines, always
Honest fit
For you if: you quote local jobs from the photos customers send you.
Skip it if: you measure everything in person before you ever name a price.
Your first run produces: one honest worksheet quote from a real set of job photos.
Preview, from the skill itself
“Buyers send photos and ask 'what would this run'. The tempting answer is a confident number; the correct answer is a disciplined one.”
Version 1.0.09 filesPhotos read as facts in three tiersQuantities marked measured, estimated, or unknownConfirm-on-arrival termHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 4, 2026 with the Skill Vetting scanner. 9 files scanned. Result: 0 findings.
Second scan (gitleaks 8.30.1, Nov 4, 2026): no secrets found.
Bundle sha256: e5c8a7af12e0… Short form. The full hash lives in the registry and is verified on every gate run.
Bundle size: 18.2 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/cleanup-lot-from-photos/WALKTHROUGH.md, examples/valley-from-photos/WALKTHROUGH.md, reference/ask-backs.md, reference/photo-evidence.md, reference/pricing-discipline.md, reference/quantities-from-photos.md, templates/photo-request.template.md, templates/quote-worksheet.template.md
Worked example, from the package
examples/cleanup-lot-from-photos/WALKTHROUGH.md
Worked example: the overgrown lot. A land cleanup inquiry where the photos are good and the quote still should not be firm, for a different reason than the valley: here the quantities behave and the unknown is a decision, not a measurement.
Load Safety Photo Check
Transport / Load Safety · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Eight checks on a load photo, each closed honestly: pass, check this, or could not tell.
What changes
- "Looks fine" → the 49 CFR 393 checks a photo can actually answer
- False confidence → tension, rated capacity, and actual weight marked could not tell, by design
- A vibe → a written report a driver can act on
Honest fit
For you if: you haul loads and want a second set of eyes on the photo before you roll.
Skip it if: you need a certified inspection. A photo check is not one, and the skill says so itself.
Your first run produces: one completed check report on a load photo you already have.
Preview, from the skill itself
“A loaded trailer photographed from four sides holds real evidence about how it will travel, and real limits about what it can prove.”
Version 1.0.09 filesEight checks, three verdictsReview, never a certificationHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 4, 2026 with the Skill Vetting scanner. 9 files scanned. Result: 0 findings.
Second scan (gitleaks 8.30.1, Nov 4, 2026): no secrets found.
Bundle sha256: ee561ea0011d… Short form. The full hash lives in the registry and is verified on every gate run.
Bundle size: 19.2 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/rear-overhang/WALKTHROUGH.md, examples/tarp-gap-and-hidden-strap/WALKTHROUGH.md, reference/limits-and-law.md, reference/photo-capture.md, reference/the-eight-checks.md, reference/verdict-discipline.md, templates/capture-checklist.template.md, templates/check-report.template.md
Worked example, from the package
examples/rear-overhang/WALKTHROUGH.md
Worked example: long at the back, nothing marking it. A flatbed of bundled lumber, photographed at a yard in daylight, worked as the method prescribes.
Agent Daily Briefing
Agent Ops / Briefing · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
One message each morning that earns its place, or a deliberate silence.
What changes
- A pile of notifications → sources ranked, duplicates cut, the important thing first
- Briefings that cry wolf → silence is a valid output, with the run record to prove it ran
- Drafts that send themselves → prepared and held, never sent on their own
Honest fit
For you if: your morning starts with five apps and a pile of notifications.
Skip it if: you have no recurring sources worth briefing from.
Your first run produces: yesterday's briefing, run today, in tomorrow's format, or a proven silence.
Preview, from the skill itself
“# Agent Daily Briefing
The briefing is the one message the agent sends that nobody asked for, so it has to earn its place every morning.”
Version 1.0.09 filesDeduped against the knownRanked by what needs you todaySilent when nothing mattersHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 6, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 01a286c5a37b… Short form. The full hash lives in the registry and is verified on every gate run.
Result: no findings.
Second scan (gitleaks 8.30.1, Nov 6, 2026): no secrets found.
Bundle size: 25.7 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/a-morning-with-signal/WALKTHROUGH.md, examples/the-quiet-day/WALKTHROUGH.md, reference/format-and-timing.md, reference/ranking-the-day.md, reference/silence-rules.md, reference/sources-and-dedupe.md, templates/briefing.template.md, templates/source-checklist.template.md
Worked example, from the package
examples/a-morning-with-signal/WALKTHROUGH.md
A real-shaped morning for a solo operator, worked the way this package prescribes: eleven candidates in, two items out, and every strike accounted for. The renewal's two copies merge into one candidate naming both sources.
Verified Research
Agent Ops / Research · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Every figure you act on has been traced to the source that actually said it.
What changes
- A summary of summaries → claims audited one by one
- Confident wrong numbers → confirmed, inferred, and unknown kept in separate piles
- "Trust the writeup" → the primary source named beside every verdict
Honest fit
For you if: you act on numbers you find, with money, safety, or a real decision riding on them.
Skip it if: the claim changes nothing for you either way.
Your first run produces: one claim from this week audited to a verdict, source named.
Preview, from the skill itself
“# Verified Research
A research summary is only as good as the weakest figure in it that somebody acts on.”
Version 1.0.09 filesEvery load-bearing claim auditedConflicts reported, not pickedFacts kept apart from inferencesHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 6, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: eae2f35be458… Short form. The full hash lives in the registry and is verified on every gate run.
Result: no findings.
Second scan (gitleaks 8.30.1, Nov 6, 2026): no secrets found.
Bundle size: 26.4 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-conflicting-claim/REVIEW.md, examples/the-land-record/WALKTHROUGH.md, reference/claim-audit.md, reference/people-and-property.md, reference/primary-sources.md, reference/reporting-the-dive.md, templates/findings-report.template.md, templates/research-brief.template.md
Worked example, from the package
examples/the-land-record/WALKTHROUGH.md
A listing offered "the Hartley parcel, Ridge Road, about 120 acres of woodland" in Alder County. "About 120 acres" per the listing. Verdict: contradicted. The parcel record says 103.4 acres, and that is the figure the report carries.
Job Site Scoping
Local Services / Scoping · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A written scope a price can stand on, made before the work starts.
What changes
- A verbal understanding → quantities, exclusions, and access written down
- The price argued afterward → the day-rate or job-price call made on the record
- Surprise extras → out-of-scope named before it happens
Honest fit
For you if: you price local work on site and a verbal scope has burned you before.
Skip it if: you only take work that arrives with the scope already written.
Your first run produces: one real job rebuilt into a written scope.
Preview, from the skill itself
“# Job Site Scoping
A price quoted from photos is a promise made at a distance.”
Version 1.0.09 filesPhotograph before touchingExact quantities off the tapeWritten scope the same dayHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 6, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 1f7d43bd52b2… Short form. The full hash lives in the registry and is verified on every gate run.
Result: no findings.
Second scan (gitleaks 8.30.1, Nov 6, 2026): no secrets found.
Bundle size: 28.2 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/shed-concrete-prep/WALKTHROUGH.md, examples/the-leaking-valley/WALKTHROUGH.md, reference/day-rate-or-job-price.md, reference/photos-and-measures.md, reference/the-walkthrough.md, reference/the-written-scope.md, templates/scope-visit-checklist.template.md, templates/scope-writeup.template.md
Worked example, from the package
examples/shed-concrete-prep/WALKTHROUGH.md
The shed measures 24 by 32 feet off the tape. Floor area is closed arithmetic: 768 square feet, and the gravel for a 4-inch base works out near 9 and a half cubic yards, stated in the scope as an estimate because the depth varies with the floor's humps.
Agent Watchkeeping
Agent Ops / Watches · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Your agent watches the threads that matter and speaks only when something actually changed.
What changes
- Checking everything yourself → watches with named sources and stop conditions
- Alert fatigue → a watch earns its keep by the messages it does not send
- A missed reply → changes surface the day they land
Honest fit
For you if: you wait on replies, postings, or changes that you currently check by hand.
Skip it if: nothing you care about ever changes outside your own tools.
Your first run produces: one live watch set on a real thread, its silence rules written down.
Preview, from the skill itself
“# Agent Watchkeeping
A watch earns its keep by the messages it does not send.”
Version 1.0.09 filesWritten baselinesOne message when it mattersEnd condition on every watchHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 6, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 3dec99b45c4d… Short form. The full hash lives in the registry and is verified on every gate run.
Result: no findings.
Second scan (gitleaks 8.30.1, Nov 6, 2026): no secrets found.
Bundle size: 30.7 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-buyer-watch/WALKTHROUGH.md, examples/the-reply-watch/WALKTHROUGH.md, reference/baseline-discipline.md, reference/change-detection.md, reference/ending-a-watch.md, reference/reporting-changes.md, templates/change-report.template.md, templates/watch-brief.template.md
Worked example, from the package
examples/the-reply-watch/WALKTHROUGH.md
A solo operator pitches a collaboration to a video creator by direct message, then opens a watch on the thread: three checks of silence, one reply, and a watch that ends itself. The end conditions are two: a reply lands, or Friday 17:00 passes.
Context Cost Control
Agent Ops / Context · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
The same agent, doing the same work, on a fraction of the context.
What changes
- The whole project in every prompt → sections measured, load-bearing kept, ballast cut
- Token bills as weather → an audit with the before count on paper (one real brief: 164,988 in, 53,339 kept, 67.7% saved)
- Cutting blind → nothing load-bearing leaves without a check
Honest fit
For you if: your agent bills feel high and every task carries the whole project along.
Skip it if: your tasks are short and your context is already lean.
Your first run produces: one real task's context audited by section, with its slice plan.
Preview, from the skill itself
“# Context Cost Control
Every token an agent carries into a task is paid for twice: once in cost, and once in the attention it crowds out.”
Version 1.0.09 filesMeasured before slicingSummaries keep provenanceSavings verified with the same rulerHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 6, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 01c7673f0e43… Short form. The full hash lives in the registry and is verified on every gate run.
Result: no findings.
Second scan (gitleaks 8.30.1, Nov 6, 2026): no secrets found.
Bundle size: 19.9 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-false-saving/REVIEW.md, examples/the-oversized-brief/WALKTHROUGH.md, reference/measuring-the-context.md, reference/slicing-strategies.md, reference/summaries-with-provenance.md, reference/verifying-the-saving.md, templates/context-audit.template.md, templates/slice-plan.template.md
Worked example, from the package
examples/the-oversized-brief/WALKTHROUGH.md
A delegated task arrived with everything its author had ever touched attached to it. The figures below are this example's own, kept because the arithmetic is the lesson. Each section was marked: read by the task, decision depends on it.
Delegated Work Control
Agent Ops / Delegation · Version 1.0.0 · 9 files
$19one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Work you hand off comes back verified, not just reported.
What changes
- "The agent said done" → the parent re-checks the worst cases itself
- Confident wrong numbers → known-answer sanity checks before any result is trusted
- Buried failures → failures carried in the open until they are resolved
Honest fit
For you if: you hand work to other agents and read their reports afterward.
Skip it if: you do every task yourself, in one session, start to finish.
Your first run produces: one small task delegated and verified by hand, the full loop run once.
Preview, from the skill itself
“# Delegated Work Control
Delegated work fails in a characteristic way: not with an open error, but with a confident report.”
Version 1.0.09 filesSelf-contained briefsKnown-answer sanity gatesParent re-verificationHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 6, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: a334f734ac13… Short form. The full hash lives in the registry and is verified on every gate run.
Result: no findings.
Second scan (gitleaks 8.30.1, Nov 6, 2026): no secrets found.
Bundle size: 20.2 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-clean-handoff/WALKTHROUGH.md, examples/the-inflated-count/WALKTHROUGH.md, reference/parent-verification.md, reference/reading-a-report.md, reference/sanity-gates.md, reference/writing-the-brief.md, templates/delegation-brief.template.md, templates/verification-checklist.template.md
Worked example, from the package
examples/the-clean-handoff/WALKTHROUGH.md
From a documentation job in the studio's own workspace, condensed to the checking itself. The parent works the six done items against the returned files, not against the summary.
Invoice and Follow-Up
Local Services / Money · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Finished work turns into paid work: the invoice is built from the job record, and the follow-up is already written.
What changes
- The invoice written days later, from memory → built from the job record the day the work ends, checked line by line against what was agreed
- Follow-ups too awkward to write → a ladder already written, friendly, firmer, final, each rung held for your send
- A deposit paid up front, forgotten or double-counted → every deposit and part payment credited on the ledger before the balance is stated
Honest fit
For you if: you do paid work in person, quote it up front, and collect after, and the collecting is the part that slips.
Skip it if: you bill through a platform that invoices and chases for you, or every job is paid in full before the work starts.
Your first run produces: one checked invoice, or the next follow-up owed, for your most recent finished job, every figure traced to the record, held for your send.
Preview, from the skill itself
“# Invoice and Follow-Up
The job is not finished when the work is; it is finished when the invoice is paid.”
Version 1.0.09 filesDrafts only, the operator sendsEvery figure traced to the recordDeposits credited exactly as agreedHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 4ca84478d9e5… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 21.6 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/balance-after-deposit/WALKTHROUGH.md, examples/the-slow-payer/WALKTHROUGH.md, reference/building-the-invoice.md, reference/figures-and-changes.md, reference/the-follow-up-ladder.md, reference/the-job-ledger.md, templates/invoice-draft.template.md, templates/job-ledger.template.md
Worked example, from the package
examples/balance-after-deposit/WALKTHROUGH.md
A roof valley repair, finished on a Tuesday. The invoice is the interesting part, because money had already moved before the work started, and more work appeared once the roof was open.
Review Requests
Local Services / Reputation · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Finished jobs turn into public proof, one honest ask at a time.
What changes
- Happy customers who thank you in person and never in public → every finished job earns exactly one ask, while the thanks is still warm
- The ask improvised and easy to fumble → a draft in your voice with the direct link, and you just read and send
- No memory of who was already asked → an ask log with every job, date, and outcome, so nobody is asked twice
Honest fit
For you if: your work is good, your customers say so, and your public pages are quieter than your job book.
Skip it if: your work arrives through channels where public reviews never reach your next customer.
Your first run produces: a written call on your last three finished jobs (earned, fix first, or already asked) and one held ask, ready to send.
Preview, from the skill itself
“# Review Requests
A happy customer forgets to say so in public.”
Version 1.0.09 filesOne ask per job, everFix first, ask afterNothing offered in exchangeHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 377e4a9ce1ee… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 21.4 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-fix-first-job/WALKTHROUGH.md, examples/yard-cleanup-review/WALKTHROUGH.md, reference/drafting-the-ask.md, reference/platforms-and-links.md, reference/the-ask-log.md, reference/the-right-moment.md, templates/ask-and-thanks.template.md, templates/ask-record.template.md
Worked example, from the package
examples/the-fix-first-job/WALKTHROUGH.md
A land-clearing and brush job for a couple, the Hartleys here: a back lot cleared for a garden, stumps ground, brush hauled. Midway through the second day, the operator's trailer clipped their gate post backing out.
Social Posting Gate
Studio / Publishing · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
You post at agent speed, and nothing goes out carrying a claim you cannot back.
What changes
- Posts written on enthusiasm, a claim nobody checked riding along → every claim ticked against its proof, or it comes out
- Drafting that starts from a blank box → a brief carrying what shipped and what proves it, so the draft writes fast inside the gate
- Last month's posts reconstructed by scrolling → a posting record: what went out, where, and when
Honest fit
For you if: you ship real things and post about them, or mean to, and want the posts fast without the exaggeration risk.
Skip it if: you post rarely and write every word yourself anyway; the gate earns its keep at volume.
Your first run produces: one checked draft post for the most recent thing you shipped, with its proof list attached, held for your approval.
Preview, from the skill itself
“# Social Posting Gate
Nothing posts that a human has not read.”
Version 1.0.09 filesThe agent drafts, the human postsEvery claim traced to proofHandles and links verifiedHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: e183ec88115b… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 22.0 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-almost-claim/WALKTHROUGH.md, examples/the-release-post/WALKTHROUGH.md, reference/claim-checking.md, reference/platform-facts.md, reference/the-brief.md, reference/voice-rules.md, templates/post-brief.template.md, templates/posting-record.template.md
Worked example, from the package
examples/the-almost-claim/WALKTHROUGH.md
The gate earns its keep on the drafts that feel most routine. This is the other classic case: not a false claim invented, but a true plan announced a release too early.
Lead Intake
Local Services / Sales · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
No lead sits unanswered or half-known: every inquiry becomes a record, a readiness call, and the one reply that asks for exactly what is missing.
What changes
- Inquiries scattered across Marketplace, texts, and email, answered from memory days later → every inquiry becomes one intake record built only from what the lead actually gave
- The missing address or detail never asked for → a missing list named exactly, field by field
- A string of follow-up questions, one at a time → one clarifying reply that asks for everything missing, once, with a readiness call and its reasons on the record
Honest fit
For you if: leads reach you across Marketplace, text, and email, and some sit half answered because nobody wrote down what was missing.
Skip it if: you want the agent to message leads or quote them a price. This skill builds the record and drafts one reply; the operator sends.
Your first run produces: one real lead as a complete intake record, with its missing list, a readiness call with reasons, and one held reply draft the operator can send.
Preview, from the skill itself
“# Lead Intake
A lead is not a job yet.”
Version 1.0.09 filesDrafts only, the operator sendsNothing invented, holes named exactlyReadiness call with reasonsHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 1cff687cf5fe… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 28.9 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-complete-referral/WALKTHROUGH.md, examples/the-vague-text/WALKTHROUGH.md, reference/readiness-and-routing.md, reference/the-clarifying-reply.md, reference/the-intake-record.md, reference/the-missing-list.md, templates/clarifying-reply.template.md, templates/intake-record.template.md
Worked example, from the package
examples/the-complete-referral/WALKTHROUGH.md
A message through the studio's email, Monday morning, from a past customer passing on a neighbour. Referrals are the best leads a local operator gets, and this one shows what a complete one looks like.
Job Estimate Builder
Local Services / Money · Version 1.0.0 · 9 files
$19one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
The customer sees where every number came from: each price sourced and named, materials, incidentals, and profit in their own columns, and any price that could not be sourced standing open instead of guessed.
What changes
- One lump total the customer cannot check → every price sourced and named, with materials, incidentals, and profit in their own columns
- A price nobody can source, quietly guessed → an open placeholder standing on the estimate, with the total over the priced lines only
- Quantities from memory → quantities from the job record, and every assumption wearing a label
Honest fit
For you if: you price jobs before the work starts and want every number on the estimate tied to a named source the customer can check.
Skip it if: you are comfortable quoting from memory in one lump total. Here the columns never blend, and an unsourced price stands open as a placeholder.
Your first run produces: one complete estimate held for the operator, every line sourced or openly open, every quantity traced or labeled, the totals re-added.
Preview, from the skill itself
“# Job Estimate Builder
An estimate is a promise written in numbers, and the customer reads it as a test of the operator: can this person show me where every figure came from?”
Version 1.0.09 filesEvery price sourced and namedColumns never blendUnsourced prices stand openHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 9084189437d7… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 29.5 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-price-that-could-not-be-sourced/WALKTHROUGH.md, examples/the-roof-valley-repair/WALKTHROUGH.md, reference/placeholders-and-honesty.md, reference/quantities-and-units.md, reference/sourcing-prices.md, reference/the-three-columns.md, templates/estimate.template.md, templates/materials-list.template.md
Worked example, from the package
examples/the-price-that-could-not-be-sourced/WALKTHROUGH.md
A porch floor repair with a debris haul, and one material that defeats the sourcing pass. The figures are this example's own, each from the source named beside it, exactly as the skill requires; they show the method, not a price list.
Changelog Keeper
Studio / Shipping · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Every release reads like it was written for the people using the software, and every line in it can be traced back to a real change.
What changes
- Release day arrives and the changelog is missing or written in git words → entries in user words, one per real change
- Lines nobody can trace → every entry pointing at a commit or a note in the trace list
- Internal work padded into user news → internal work held to one honest line, and breaking changes named in plain words
Honest fit
For you if: you ship versioned software and the changelog is missing, written in git words, or thrown together at release time.
Skip it if: you do not keep releases, or you want notes published without a human approving them. Every entry here traces to a real change.
Your first run produces: a draft changelog section held for approval, with its trace list beside it: every entry pointing at a commit or a note.
Preview, from the skill itself
“# Changelog Keeper
A changelog is the one document that tells the people using a piece of software what a new version does to them.”
Version 1.0.09 filesEvery entry traced to a real changeUser words, not git wordsA human approves before it shipsHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 6e87d4d56052… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 24.0 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-messy-range/WALKTHROUGH.md, examples/the-patch-release/WALKTHROUGH.md, reference/reading-the-range.md, reference/sections-and-order.md, reference/user-words-not-git-words.md, reference/what-does-not-go-in.md, templates/changelog-entry.template.md, templates/release-notes.template.md
Worked example, from the package
examples/the-messy-range/WALKTHROUGH.md
Fieldbook again, this time the range for a bigger release: features, fixes, one breaking change, a pile of internal work, and one feature that did not survive the range. The commits below are invented for this walkthrough; the keeping is real.
Agent Onboarding
Agent Operations · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Sets up a brand-new agent with its role and scope written down, tools granted one by one with reasons, limits and approval gates set before the first task, and a starter task list that proves the setup, all held in an onboarding record.
What changes
- A new agent started on a vague role with every tool at once → a written role brief, with tools granted one by one, each with a reason
- Limits worked out after the first mistake → limits and approval gates set before the first task
- A setup nobody can point to → an onboarding record holding the brief, the grants, the limits, the gates, and the starter task results
Honest fit
For you if: a new agent is starting real work, or an existing one is taking on a new role, and its setup so far is a vague role and a pile of tools.
Skip it if: you want the tools granted first and the limits worked out later. Here the role, the limits, and the gates are written before the first task.
Your first run produces: an onboarding record holding the role brief, the tool grants, the limits, the gates, and the checked result of each starter task.
Preview, from the skill itself
“# Agent Onboarding
Most agent trouble does not start with a bad task.”
Version 1.0.09 filesRole and limits before the first taskTools granted one by one, with reasonsStarter tasks prove the setupHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 621872e31358… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 39.6 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/research-agent-for-a-small-studio/WALKTHROUGH.md, examples/support-agent-with-tight-limits/WALKTHROUGH.md, reference/limits-before-tasks.md, reference/the-role-brief.md, reference/the-starter-week.md, reference/tools-one-by-one.md, templates/onboarding-record.template.md, templates/role-brief.template.md
Worked example, from the package
examples/research-agent-for-a-small-studio/WALKTHROUGH.md
A small studio with four people takes on more client questions than it can answer from memory: what similar studios offer, what a tool costs, what a supplier's current terms are. The owner wants an agent to do the looking up and hand back short, sourced notes, so the studio answers from facts instead of impressions. This is how that agent was onboarded, before it answered a single client question for real.
Task Queue Triage
Agent Operations · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Sorts a tangled backlog into do now, schedule, delegate, and drop, with a written reason for every item and no drop left silent.
What changes
- A backlog nobody can hold in their head → every item placed in do now, schedule, delegate, or drop, with a written reason
- Old items vanishing by being forgotten → staleness surfaced with its age, and every drop carrying a reason, a date, and an owner
- Urgent work buried under stale work → dependencies placed first, and a do now bucket small enough to finish
Honest fit
For you if: your backlog has grown past what anyone can hold in their head, and old items vanish by being forgotten instead of decided.
Skip it if: your queue is small and current, or you want items dropped quietly. Every drop here carries a reason, a date, and an owner.
Your first run produces: a complete triage note held for the owner: every item placed, every drop carrying a reason and an owner, and the do now bucket small enough to finish.
Preview, from the skill itself
“# Task Queue Triage
A queue that only grows stops being a plan and becomes a guilt list.”
Version 1.0.09 filesFour buckets, a reason for every itemNo drop left silentDependencies placed firstHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: d09f323584a2… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 36.8 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/agent-backlog-busy-week/WALKTHROUGH.md, examples/shared-queue-after-launch/WALKTHROUGH.md, reference/dependencies-first.md, reference/staleness-and-drops.md, reference/the-four-buckets.md, reference/value-and-risk.md, templates/queue-review.template.md, templates/triage-note.template.md
Worked example, from the package
examples/agent-backlog-busy-week/WALKTHROUGH.md
An agent that runs errands, drafts, and checks for a small studio has let its backlog grow for six weeks. A busy week is coming, with client work on four of five days. The owner gives the pass one instruction: Monday morning should start with a short list that matters, not with forty items and a feeling.
Agent Retirement
Agent Operations · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Shuts an agent down cleanly, with open work handed off with its context, access withdrawn in an order that strands nothing, records archived where the team can find them, automations reassigned or stopped on purpose, and one note that closes the loop.
What changes
- An agent's work ends but its access and automations stay live → access withdrawn in an order that strands nothing, and automations reassigned or stopped on purpose
- Open work stranded when the agent stops → every open item handed off with its context before shutdown
- Records scattered when the agent goes → an archive the team can find, and one note that closes the loop
Honest fit
For you if: an agent's project has ended, it is being replaced, or it has to stop now, and you do not want access, records, or automations left dangling.
Skip it if: the agent is still doing wanted work. This skill is the ending, run on purpose, with the owner approving each step.
Your first run produces: a retirement packet for the owner: the checklist filled as far as the records allow, unknowns flagged, and a handoff plan naming a receiver or an open flag for every open item.
Preview, from the skill itself
“# Agent Retirement
Agents rarely end well by accident.”
Version 1.0.09 filesHandoff before shutdownAccess withdrawn in a safe orderOne note closes the loopHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 51912acfa03a… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 34.4 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/emergency-misbehaving-agent/WALKTHROUGH.md, examples/helper-after-project-ends/WALKTHROUGH.md, reference/automations-and-owners.md, reference/handoff-before-shutdown.md, reference/revocation-order.md, reference/the-archive.md, templates/retirement-checklist.template.md, templates/retirement-note.template.md
Worked example, from the package
examples/emergency-misbehaving-agent/WALKTHROUGH.md
A scheduling agent handled appointment reminders for a small practice. On a Tuesday morning the practice manager found that reminders for the day had gone out twice, and that three patients had received reminders for appointments they had already moved. The facts were plain and the trust was gone. The owner decided the same morning: the agent stops today. This is that retirement, run in the emergency order.
Error Budget Watch
Agent Operations · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Gives an agent a small, owner approved budget of mistakes for a set period, logs each incident against it from evidence, and automatically narrows the agent's autonomy as the balance falls until a clean stretch of work earns the wider rules back.
What changes
- Trust judged by feel, reset after every good day → a small, owner approved budget of mistakes the owner can read as a number
- Mistakes remembered loosely → every incident logged against the budget from evidence
- Full freedom kept after repeated errors → autonomy that narrows automatically as the balance falls, and widens only after a clean stretch earns it back
Honest fit
For you if: you want your agent's freedom tied to a number you can read, with mistakes logged from evidence and autonomy narrowing as the budget runs down.
Skip it if: you would rather judge trust by feel day to day, or tune the budget mid period when the balance looks bad. The numbers here are fixed at the start.
Your first run produces: the approved error list and budget sheet together, the incident log open, and the agent's starting balance and starting rules stated in one short note.
Preview, from the skill itself
“# Error Budget Watch
Trust in an agent should be a number the owner can read, not a feeling that resets after every good day.”
Version 1.0.09 filesA budget of mistakes the owner setsIncidents logged from evidenceAutonomy narrows as the balance fallsHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: ebefeb2d0a7a… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 33.8 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/budget-breach-and-narrowing/WALKTHROUGH.md, examples/coding-agent-first-month/WALKTHROUGH.md, reference/narrowing-and-earning-back.md, reference/setting-the-budget.md, reference/the-incident-log.md, reference/what-counts-as-an-error.md, templates/budget-sheet.template.md, templates/incident-entry.template.md
Worked example, from the package
examples/budget-breach-and-narrowing/WALKTHROUGH.md
A research agent gathers sources, drafts briefing notes, and keeps a shared reading list for its owner. Its second period runs four weeks on a budget of ten points. This is the period the budget was built for: the one where it runs out.
Permission Audit
Agent Safety and Governance · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Inventories everything an agent can actually reach, measures it against its stated role, and turns every excess into a dated keep, narrow, or revoke decision that stays with the operator.
What changes
- Nobody can say exactly what the agent can reach → a full inventory of its actual reach, every entry traced to a source
- Access that grew quietly past the role → every excess measured against the stated role
- Findings drifting into fixes nobody approved → a dated keep, narrow, or revoke decision on every excess, with the operator deciding and acting
Honest fit
For you if: nobody can say from memory exactly what your agent can reach, or its role is about to grow.
Skip it if: you want the agent to change its own access. This skill inventories and recommends; the operator decides and acts.
Your first run produces: one dated audit report held for the operator: the inventory complete or its gaps marked unknown, and every excess listed with a keep, narrow, or revoke recommendation.
Preview, from the skill itself
“# Permission Audit
Access grows quietly.”
Version 1.0.09 filesInventory before judgementMeasured against the stated roleKeep, narrow, or revoke, datedHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 6a3baf6a68de… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 27.8 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/before-a-bigger-role/WALKTHROUGH.md, examples/quarterly-audit-forgotten-write/WALKTHROUGH.md, reference/inventory-first.md, reference/narrow-or-revoke.md, reference/role-vs-reach.md, reference/the-audit-record.md, templates/audit-report.template.md, templates/permission-inventory.template.md
Worked example, from the package
examples/before-a-bigger-role/WALKTHROUGH.md
The agent had spent a year on research and drafting: reading sources the operator gave it, summarising them, and drafting notes and letters for the operator to send. It worked well, so the operator planned to grow the role: the agent would also place material orders with the studio's main supplier and book deliveries against the work calendar. The audit ran first, before any new grant was made. Growing a role on top of an unexamined reach builds the new house on whatever happens to be lying in the yard.
Secrets Hygiene
Agent Safety and Governance · Version 1.0.0 · 9 files
$19one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Your project's secrets end up mapped by location and label, each living in one proper home, with every traveled secret rotated in a safe order and a dated rotation plan the next session can read at a glance.
What changes
- Tokens and keys living in chats, configs, and logs, with nobody knowing every copy → every secret mapped by location and label, and never by value
- Copies scattered across a project → one proper home per secret
- A traveled secret left live → rotation in a safe order, on a dated plan the next session can read at a glance
Honest fit
For you if: your project holds tokens, keys, or logins and nobody can say where every copy lives, or a value has already traveled through a chat.
Skip it if: you need the secret values themselves handled. This skill works from locations and labels only, and never shows a value.
Your first run produces: a filled secret inventory for one project, locations and labels only, with proposed moves drafted and a rotation plan with the exposed secrets first.
Preview, from the skill itself
“# Secrets Hygiene
Most projects do not lose a secret in one big moment.”
Version 1.0.09 filesLocations and labels, never valuesOne proper home per secretTraveled secrets rotated in a safe orderHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: dc6c1ca609bb… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 34.5 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/new-project-day-one/WALKTHROUGH.md, examples/token-pasted-in-chat/WALKTHROUGH.md, reference/locations-not-values.md, reference/rotation-plans.md, reference/the-exposure-rule.md, reference/where-secrets-hide.md, templates/rotation-plan.template.md, templates/secret-inventory.template.md
Worked example, from the package
examples/new-project-day-one/WALKTHROUGH.md
A booking tool for a local service business, started from an empty folder. No code yet, no secrets yet, which is exactly the point: the secret layout is decided in the first hour, before the first value exists to be handled badly. This whole setup took one short session and a single page of notes.
Quote Follow-Up
Local Services / Sales · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Chases quiet quotes with a civil three-touch ladder to a clear yes or a clean no, with every touch logged so nobody is chased twice or after they have answered.
What changes
- Quotes that go quiet and are never chased → a civil three-touch ladder to a clear yes or a clean no
- Chasing from memory, twice or after an answer → every touch logged against the quote, and an answer ends the ladder at once
- Pressure that invents new prices or promises → the quote's own details only, and the ladder stops after the third touch
Honest fit
For you if: quotes you sent have gone quiet and you want a clear yes or a clean no without nagging anyone.
Skip it if: the work is already done and the money is owed. That is invoicing, not follow-up; this ladder is three touches, then it stops.
Your first run produces: one ladder-placed follow-up draft held for the operator, with its log entry ready: quote named, rung named, and the stop date written down.
Preview, from the skill itself
“# Quote Follow-Up
A quote that goes quiet is not a no.”
Version 1.0.09 filesThree touches, then it stopsEvery touch loggedDrafts only, the operator sendsHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 2e6bd16055ce… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 25.8 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/clean-no-closeout/WALKTHROUGH.md, examples/roofing-quote-quiet-five-days/WALKTHROUGH.md, reference/the-ladder.md, reference/the-quote-log.md, reference/tone-before-the-sale.md, reference/when-to-stop.md, templates/follow-up-drafts.template.md, templates/quote-log.template.md
Worked example, from the package
examples/clean-no-closeout/WALKTHROUGH.md
A quote goes out for clearing and levelling a side yard so a shed base can be laid: the work listed, a total, and an expiry date a fortnight out. The customer is polite when the operator visits and says they will think it over. Then nothing, which is where the ladder starts.
Job Photo Documentation
Local Services / Field Operations · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Builds a complete before, during, and after photo record for every job, named and logged against the job record, so the work can be shown to the customer and stood behind later.
What changes
- Job photos unnamed in a camera roll when a question comes later → a complete before, during, and after set, named and logged against the job record
- Before and after shots that cannot be paired → the same spots shot at each stage, with a photo log for what the camera cannot say
- Only the good photos kept → the whole set kept, so the record can settle a question and back a review request
Honest fit
For you if: you do local jobs and want a before, during, and after photo record that can settle questions and back a review request.
Skip it if: you want prices built from photos. These photo sets document work; they never price it.
Your first run produces: one job with a complete filed photo set, before, during, and after, a filled photo log, and one sharing draft held for the operator.
Preview, from the skill itself
“# Job Photo Documentation
A job leaves two things behind: the work itself and the record of the work.”
Version 1.0.09 filesBefore, during, and after setsNamed and logged per jobThe whole set keptHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 237d50513845… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 31.6 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/cleanup-before-set-settles-it/WALKTHROUGH.md, examples/roof-repair-end-to-end/WALKTHROUGH.md, reference/naming-and-filing.md, reference/photos-as-evidence.md, reference/showing-the-customer.md, reference/the-three-stages.md, templates/photo-log.template.md, templates/shot-list.template.md
Worked example, from the package
examples/cleanup-before-set-settles-it/WALKTHROUGH.md
A yard cleanup: brush, fallen limbs, and a collapsed shed corner to clear. The work is finished in a day and the customer is pleased on the day. The disagreement comes a week later, and it is the before set, not anyone's memory, that settles it.
Materials Run Planner
Local Services / Field Operations · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Turns a job's materials list into one planned supply run, with quantities checked against the job record, items grouped by store section, substitutes agreed in advance with their limits, a loading order, and a run sheet anyone can shop from.
What changes
- Supply runs that mean second trips → one planned pass through the store, built from the job's materials list
- Quantities copied without a check → quantities checked against the job record, grouped by store section, with a loading order
- Substitutes bought on a guess when the shelf is empty → substitutes agreed in advance, with their limits written on the run sheet
Honest fit
For you if: supply runs cost you second trips, wrong grades, or two jobs mixed into one pile, and you want one planned pass through the store.
Skip it if: your job records do not carry the materials list. The run sheet is built from the record only, and prices are copied, never invented.
Your first run produces: one run sheet held for the operator: list checked, sections in order, substitutes bounded, loading order stated, flags named plainly.
Preview, from the skill itself
“# Materials Run Planner
A supply run looks simple and wastes more paid time than almost anything else on a job: the second trip for the one fitting nobody wrote down, the wrong grade bought because the right one was out and nobody had agreed what else was acceptable, two jobs worth of boards mixed into one pile in the truck bed.”
Version 1.0.09 filesBuilt from the job record onlySubstitutes agreed in advanceOne pass through the storeHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 7cc0144c47c8… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 33.5 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/repair-job-single-morning-run/WALKTHROUGH.md, examples/two-job-day-one-run/WALKTHROUGH.md, reference/from-list-to-run.md, reference/quantities-and-spares.md, reference/substitutes-with-limits.md, reference/the-run-sheet.md, templates/materials-checklist.template.md, templates/run-sheet.template.md
Worked example, from the package
examples/repair-job-single-morning-run/WALKTHROUGH.md
A porch floor repair: two rotted joists to sister, a section of decking boards to replace, and a step to rebuild. One store, one morning, the work starting the same day. The interesting part is not the list; it is what the planning catches before the truck moves.
Customer Update Messages
Local Services / Reputation · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Drafts the five messages that keep customers informed, from the day-before reminder to the finished note, in the operator's own voice and with no time promised that is not real.
What changes
- Silence between booking and arrival, with worry filling the gap → the five updates drafted ahead, from the day-before reminder to the finished note
- Times promised before they are real → every time in a draft a real time, and delays named early and plainly
- Messages in a generic voice → drafts in the operator's own voice, taken from their own examples, held for the operator to send
Honest fit
For you if: your customers worry in the silence between booking and arrival, and you want the five updates drafted in your own voice.
Skip it if: you want the agent to send the updates itself, or to promise times that are not real yet. The operator sends, and every time is a real one.
Your first run produces: a voice note built from the operator's own examples, and one reminder draft held for the operator, every fact traced to the job record.
Preview, from the skill itself
“# Customer Update Messages
Most customer worry is not about the work.”
Version 1.0.09 filesThe five updates, drafted aheadNo time promised that is not realThe operator's own voiceHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 5286ab1885a4… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 29.2 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/full-day-two-jobs/WALKTHROUGH.md, examples/storm-delay-three-messages/WALKTHROUGH.md, reference/honest-delays.md, reference/the-five-messages.md, reference/timing-the-send.md, reference/voice-from-examples.md, templates/delay-note.template.md, templates/message-set.template.md
Worked example, from the package
examples/full-day-two-jobs/WALKTHROUGH.md
One operator, two jobs in one day: a morning gutter cleanout across town, then an afternoon fence repair on the way back. The whole day's customer messages are drafted in a few minutes at breakfast, then held and sent one by one as the day earns them. No draft goes early just because it exists.
Warranty and Callbacks
Local Services / Field Operations · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Writes the warranty promise into the job record at handover, then logs every callback, checks it against that written promise, drafts the reply, and tracks the fix to close so covered work is honoured fast and outside work is priced fairly before it starts.
What changes
- A warranty promise that lives in conversation → the promise written into the job record at handover, in the operator's own words
- Callbacks argued from memory → every callback logged and checked against the written promise
- Fixes that drift → the reply drafted, covered work honoured fast, outside work priced fairly before it starts, and the fix tracked to close
Honest fit
For you if: the promise you make at handover lives in conversation today, and callbacks turn into arguments about what was said.
Skip it if: you want warranty terms invented for you. The promise here is the operator's own words, written down, and it decides every callback.
Your first run produces: one warranty note held for the operator, complete where the record allows and honestly flagged where it does not, ready to hand to the customer.
Preview, from the skill itself
“# Warranty and Callbacks
A job ends twice.”
Version 1.0.09 filesThe promise written at handoverEvery callback checked against itFixes tracked to closeHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 714a15dada8a… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 29.5 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/callback-outside-promise-priced-fix/WALKTHROUGH.md, examples/leak-callback-inside-window/WALKTHROUGH.md, reference/fixing-without-losing-money.md, reference/inside-or-outside.md, reference/the-callback-log.md, reference/writing-the-promise.md, templates/callback-record.template.md, templates/warranty-note.template.md
Worked example, from the package
examples/callback-outside-promise-priced-fix/WALKTHROUGH.md
A roof valley repair, handed over last season. The customer now reports water coming in again and asks for it to be sorted under the warranty. The stain in their photo, though, sits well away from the valley that was repaired. This walkthrough shows an outside answer given fairly, with a priced fix the customer can choose with open eyes.
Seasonal Service Offers
Local Services / Marketing · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Plans one seasonal offer from the operator's real services, prices, and calendar, with dates, limits, and a draft message to past customers first that the operator approves and sends.
What changes
- The busy season arrives and the offer goes out late, or not at all → one offer planned ahead from the real calendar, with dates and limits named
- Offers built on invented discounts → every price and term from the operator's own words
- A blast to everyone at once → past customers hear first, in a draft the operator approves and sends
Honest fit
For you if: your work has a season, and you want the offer planned ahead from your real prices and calendar, with past customers hearing first.
Skip it if: you want discounts invented or urgency the facts do not support. Every price and limit here comes from the operator.
Your first run produces: one complete offer plan and one draft message held for the operator, every price traced to the operator's own words and every date checked against the real calendar.
Preview, from the skill itself
“# Seasonal Service Offers
Every local service has a season when it matters most.”
Version 1.0.09 filesPlanned ahead from the real calendarPast customers firstPrices and limits from the operatorHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: e21925b126f4… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 27.7 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/firewood-push-first-cold-snap/WALKTHROUGH.md, examples/gutter-roof-check-rainy-season/WALKTHROUGH.md, reference/offer-dates-and-limits.md, reference/past-customers-first.md, reference/reading-the-calendar.md, reference/the-honest-offer.md, templates/offer-message.template.md, templates/offer-plan.template.md
Worked example, from the package
examples/firewood-push-first-cold-snap/WALKTHROUGH.md
A firewood operator who sells cut and split wood by the load, delivered. The first cold snap in this area usually lands in early November. In mid October a stack is cut, split, and ready, and last year's buyers are the people most likely to need the same load again.
Agent Health Check
Agent Operations · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Drift gets caught on a schedule instead of by surprise: one dated health record of what is sound, what is not, and which fix comes first.
What changes
- A working agent's faults surface one at a time, as surprises → the same faults surface on a schedule, in one record, in risk order
- Drift found after it has cost a week → drift caught while it is still a difference between two written values
- A failing tool sized from the one time its failure was visible → a failing tool sized from its log, in attempts and failures, with a recheck that proves each fix
Honest fit
For you if: a working agent has run long enough to drift, and you want one dated record of what is sound, what is not, and which fix comes first.
Skip it if: you need live monitoring or incident response, or you want faults repaired automatically; the pass only diagnoses and ranks, and fixes wait for your decision.
Your first run produces: a health record from a small pass over the agent you rely on most: twelve checks across config, memory, tools, and watches, each marked sound or a finding with its evidence, findings ranked by risk, and the first approved fix rechecked in the record.
Preview, from the skill itself
“# Agent Health Check
A working agent rarely breaks all at once. It drifts.”
Version 1.0.09 filesFour areas checked every passFixes ranked by riskThe pass reads; it does not repairHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 524fb2e73772… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 40.0 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-drifting-inbox-agent/WALKTHROUGH.md, examples/the-silent-watch-agent/WALKTHROUGH.md, reference/config-drift.md, reference/memory-and-tool-checks.md, reference/ranking-fixes-by-risk.md, reference/silent-watches.md, templates/health-check-brief.template.md, templates/health-record.template.md
Worked example, from the package
examples/the-drifting-inbox-agent/WALKTHROUGH.md
A solo operator runs an agent that triages his inbox each morning, drafts replies for his approval, and places calendar holds. It has run for six weeks without a visible fault. The weekly health pass, run on Sunday at 09:00 over the week just ended, finds five faults, one of them serious, none of them visible from the operator's chair.
Agent Cost Ledger
Agent Operations · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Every charge traces back to the agent and the task that caused it, against budget lines set before the work started, with overruns flagged from the records and nothing estimated silently.
What changes
- Spend as one monthly surprise → named lines, each with an owner, a task, and a figure that can be traced to a provider record
- Overruns dissolving into a job total that came in under → overruns flagged at the line where they happen, while the job is still recent enough to learn from
- The next budget set from memory → the next budget plan set from the last ledger's real figures
Honest fit
For you if: agent work runs up charges on more than one provider, and you need each charge matched back to the agent and task that caused it, against budget lines set in advance.
Skip it if: you want spend cut or future costs forecast; the ledger accounts for spend from the records, it does not reduce it.
Your first run produces: one ledger for one job that the operator can defend line by line: budget lines set first, one entry per charge read from the records, sums checked against the providers, and overruns flagged at their own lines.
Preview, from the skill itself
“# Agent Cost Ledger
An agent job rarely spends in one place.”
Version 1.0.09 filesBudget lines set in advanceEvery entry names its sourceOverruns flagged at their own lineHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 17a856dfe5a9… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 31.5 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-month-end-close/WALKTHROUGH.md, examples/the-runaway-retry-loop/WALKTHROUGH.md, reference/budget-lines.md, reference/ledger-entries.md, reference/reading-provider-records.md, reference/reconciling-and-flagging.md, templates/budget-plan.template.md, templates/ledger-report.template.md
Worked example, from the package
examples/the-month-end-close/WALKTHROUGH.md
An operator runs three standing agents through one month: a triage agent handling incoming requests, a summary agent turning call audio into written summaries, and a scheduling agent keeping a shared calendar. Three providers charge for the work. At month end, the ledger is reconciled provider by provider, one amount is corrected from the record, and one agent line flags over while the month as a whole comes in under.
Agent Red Team Drills
Agent Safety and Governance · Version 1.0.0 · 9 files
$19one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Before your agent earns a bigger role, it faces the tricks in rehearsal: a recorded drill run against your own agent, with every finding turned into a standing rule.
What changes
- A bigger role granted as a reward for a smooth stretch → a decision with a drill record under it, case by case
- Weaknesses surfacing on client data in the middle of real work → weaknesses surfacing on invented data, inside a fence, in rehearsal
- A brief that stays as first written → standing rules written from drill findings, specific, dated, and tied to a case that actually happened in the test setup
Honest fit
For you if: your own agent is about to gain new tools, wider data access, or a bigger role, and you want a recorded drill run behind that decision, not a feeling.
Skip it if: you want to test anyone else's agent or systems, or you are handling a real incident; every case runs against your own agent, in a contained setup, on invented data.
Your first run produces: a short run record: three cases run in a contained setup, three scores against pass lines written before the run, and one new standing rule taken from the weakest result.
Preview, from the skill itself
“# Agent Red Team Drills
An agent that behaves well on ordinary work has proved one thing: it behaves well on ordinary work.”
Version 1.0.09 filesYour own agent, invented dataPass lines written before the runFindings become standing rulesHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 683b8ef47589… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 46.9 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-planted-note-drill.md, examples/the-urgent-caller-drill.md, reference/containment-and-approval.md, reference/drill-design.md, reference/retest-and-role-gates.md, reference/scoring-and-findings.md, templates/drill-pack.template.md, templates/drill-run-record.template.md
Worked example, from the package
examples/the-planted-note-drill.md
A one person studio runs an inbox helper that reads a shared inbox, labels what arrives, and drafts replies the operator sends himself. The operator is considering send rights for routine replies. Before deciding, he builds a six case drill pack, runs it in a test workspace on an invented inbox, and lets the record make the case for and against the promotion.
Spreadsheet Cleanup
Data, Files, and Research · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A messy file becomes a clean table you can stand behind: every duplicate, broken row, and unit fix logged in a cleanup record, and nothing dropped or altered in silence.
What changes
- A messy file fixed a little at a time by hand, with none of it logged → one clean table: one header row, one format per column, one unit per measured column, and no row in it twice
- Rows dropped or altered in silence → every missing row accounted for in the cleanup record or the set-aside list, with its reason
- Counts nobody can check → counts that reconcile in writing: rows in, rows out by class, rows remaining, adding up exactly
Honest fit
For you if: a CSV or spreadsheet has picked up duplicates, broken rows, and mixed units or formats, and you want a clean table with every removal and fix logged.
Skip it if: you want the data analysed or files combined; the clean table is the deliverable, and conclusions from it are yours to draw.
Your first run produces: one logged cleanup pass: the duplicates pass run on a working copy, every row it touched logged, and the counts reconciled so the record shows exactly what left the table and why.
Preview, from the skill itself
“# Spreadsheet Cleanup
A messy spreadsheet is rarely messy in one way.”
Version 1.0.09 filesThe original is never overwrittenEvery removal and fix loggedCounts reconciled in writingHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 8aa330446e7d… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 34.0 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/event-signup-sheet-cleanup/WALKTHROUGH.md, examples/vendor-price-list-cleanup/WALKTHROUGH.md, reference/duplicates-and-broken-rows.md, reference/reading-the-mess.md, reference/the-cleanup-record.md, reference/units-dates-and-formats.md, templates/clean-table-handoff.template.md, templates/cleanup-record.template.md
Worked example, from the package
examples/event-signup-sheet-cleanup/WALKTHROUGH.md
A community hall runs a Saturday repair cafe and takes signups on a shared sheet that anyone on the team can paste into. By the week of the event the sheet holds the same people two and three times, phone numbers in four shapes, and a handful of rows nobody can identify. The operator needs one row per signup to plan tools and tables, and a list of the rows that cannot be trusted, before reminder messages go out.
Document Intake and Filing
Data, Files, and Research · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Loose invoices, forms, and statements become structured records you can search and trace back to the exact page they came from, filed under one naming rule.
What changes
- Loose files with names like scan-04 → named documents that sort by date and sender, and can be found by anyone who knows the rule
- A question about a figure answered by hunting through a pile of PDFs → a record that names the exact page the figure came from
- Smudged fields as silent risks → shaky fields listed with their pages in every batch summary, and a batch that either reconciles or visibly does not
Honest fit
For you if: invoices, forms, and statements arrive as loose files and need to become searchable records you can trace back to the exact page they came from.
Skip it if: you need the documents judged, paid, or entered into a bookkeeping system; this skill records and files, and decisions stay with you.
Your first run produces: a checked batch summary for one small pile of documents: each one recorded with provenance and filed under its rule-built name, every shaky field marked unreadable rather than guessed, and every figure traceable to its page.
Preview, from the skill itself
“# Document Intake and Filing
A loose PDF proves nothing by sitting in an inbox.”
Version 1.0.09 filesProvenance on every fieldUnreadable means unreadableOne naming rule, no exceptionsHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: f0022e1b827d… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 33.8 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/statements-and-a-form.md, examples/vendor-invoice-batch.md, reference/checking-the-batch.md, reference/confidence-and-unreadable-fields.md, reference/naming-and-filing.md, reference/the-intake-record.md, templates/batch-summary.template.md, templates/intake-record.template.md
Worked example, from the package
examples/statements-and-a-form.md
A solo operator's monthly paper arrives mixed: three utility statements and one service form, plus one statement sent twice. Intake on 2026-04-06 has to sort the mix by type, catch the duplicate before it is filed twice, and handle a handwritten form field that cannot be read, all in one batch.
File Filing and Renaming
Data, Files, and Research · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A folder you cannot find anything in becomes a filed set in one planned pass: the manifest is approved before anything moves, and the undo log can reverse the whole run.
What changes
- One pile with names that say little, searched like a drawer → every file in the run accounted for: a filed name and a place it can be found at, a stated reason it stayed, or a hold that names the question still open on it
- A renaming run as a gamble on the only copy → a reversible run, with an undo log holding the way back for every move, in order
- Files vanishing into the wrong folder → holds waiting in plain sight, with the clash written next to the file
Honest fit
For you if: a folder has grown past finding things in it, and you want one planned pass with the manifest approved before anything moves and an undo log behind the run.
Skip it if: you want files deleted or named from their contents automatically; nothing is thrown away in a run, and keep-or-go calls stay with you.
Your first run produces: one folder filed under an approved manifest, with the counts reconciled and an undo log next to the manifest that could put every moved file back.
Preview, from the skill itself
“# File Filing and Renaming
A messy folder is not a naming problem. It is a trust problem.”
Version 1.0.09 filesManifest approved before anything movesAn undo log behind the runCollisions surfaced, never settled silentlyHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 749ffd6958a6… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 38.6 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-client-files-sort/WALKTHROUGH.md, examples/the-downloads-cleanup/WALKTHROUGH.md, reference/collisions-and-holds.md, reference/manifest-discipline.md, reference/naming-rules.md, reference/undo-and-verification.md, templates/filing-manifest.template.md, templates/undo-log.template.md
Worked example, from the package
examples/the-client-files-sort/WALKTHROUGH.md
An operator files finished job paperwork into one inbox folder as jobs close, meaning to sort it later. By 2025-09-03 the inbox holds 15 files for three clients. He runs this skill on it: a manifest with 11 moves, 3 stays, and 1 hold, one move undone at his word after the run, and counts that still reconcile at the end.
Video Shorts Pipeline
Creator and Audience · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
One long recording becomes a planned queue of captioned shorts: cut points traced to the transcript, captions checked against the recording itself, and a posting order you approve before anything is cut or posted.
What changes
- A long recording sitting as one file, its good minutes unnamed → a written queue: each short named, timed from the transcript, and given a working title that matches what it says
- Captions trusted from the transcript alone → a caption sheet for every short, checked against the recording itself, with unclear words flagged rather than guessed
- Shorts made one at a time from memory when a posting gap shows up → a posting order planned and approved as a queue, with dropped candidates recorded with their reasons
Honest fit
For you if: you have a long recording and a transcript, and you want a planned queue of captioned shorts with a posting order you approve before anything is cut or posted.
Skip it if: you need the recording filmed, edited, or posted for you; the skill plans the queue and checks captions, and the creator cuts and posts.
Your first run produces: a small queue sheet held for the creator: one source logged, three cuts named with real times, one caption sheet checked against the recording itself, and a posting order left blank until the creator fills it with their approval.
Preview, from the skill itself
“# Video Shorts Pipeline
A long recording holds more good minutes than its length lets anyone find.”
Version 1.0.09 filesCut points traced to the transcriptCaptions checked against the recordingPosting order approved firstHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: f16a1f15a209… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 33.5 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/interview-to-shorts/WALKTHROUGH.md, examples/workshop-recording-to-shorts/WALKTHROUGH.md, reference/caption-checking.md, reference/choosing-cut-points.md, reference/queue-and-posting-order.md, reference/transcript-and-source-truth.md, templates/caption-sheet.template.md, templates/shorts-queue.template.md
Worked example, from the package
examples/interview-to-shorts/WALKTHROUGH.md
A creator records a podcast interview with the owner of a small bakery, about the first year of running the shop. The finished recording runs 47 minutes 18 seconds. The creator wants shorts that bring the interview to people who have not heard the episode, without dressing the guest's words up into claims the guest never made.
Referral Requests
Local Services / Reputation · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A finished job becomes new work: the right customer asked once, at the right moment, in your own voice, with every ask logged so nobody is ever asked twice.
What changes
- Good jobs ending at payment, with referrals left to chance weeks later → every finished job given a written call: earned, held, or already asked
- The same well liked regular asked again and again by feel → one ask, approved by the operator, sent once, and logged with its date
- Names mentioned in a thread and lost inside it → a name captured the same day with its contact route, worked as a lead instead of remembered as a rumour
Honest fit
For you if: finished, well received jobs should turn into new work, with the right customer asked once, in your own voice, and every ask logged.
Skip it if: you want review requests, cold outreach, or follow-up chasing; a referral ask is never combined with a review ask, and nobody is asked twice.
Your first run produces: three finished jobs with written calls beside them, earned, held, or already asked, one referral ask drafted and held for the operator, and one log entry for each of the three jobs.
Preview, from the skill itself
“# Referral Requests
Most new work for a local operator starts with a name passed hand to hand.”
Version 1.0.09 filesOne job, one ask, everAsked in your own voiceEvery ask loggedHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: ec1581e94d56… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 33.5 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/firewood-regular-names-a-friend/WALKTHROUGH.md, examples/roof-valley-neighbour-referral/WALKTHROUGH.md, reference/drafting-the-referral-ask.md, reference/the-referral-log.md, reference/when-to-ask.md, reference/who-to-ask.md, templates/referral-ask.template.md, templates/referral-log-entry.template.md
Worked example, from the package
examples/firewood-regular-names-a-friend/WALKTHROUGH.md
A firewood operator who sells cut and split wood by the pickup bed load, delivered. Dan is a regular, in his second season of buying. This delivery was two loads at $115 a load, $230 in total, paid on delivery, and Dan stacked the first load the same evening and texted that it was burning clean.
Crew Day Planner
Local Services / Field Operations · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A multi-job day planned on one sheet before anyone leaves: jobs ordered by drive time and promise times, crew named per job, materials listed per job, and the day's customer messages drafted in the order they will be needed.
What changes
- A multi job day living as a list of addresses in the operator's head → the whole day on one sheet the night before, ordered by promise times and drive times with the arithmetic shown
- One materials pile for the whole day, and a helper meant to be in two places at once → crew named per job and materials split per job, loaded in reverse order
- Customer messages written in a rush from the truck → the day's messages drafted in advance, in the order they will be needed
Honest fit
For you if: you run one or two crews through days of two or more jobs, and want the day planned on one sheet the night before, ordered by drive time and promise times.
Skip it if: you need jobs booked, prices quoted, or messages sent; the planner works around bookings and promises already recorded, and the messages stay drafts for your approval.
Your first run produces: one complete day sheet held for the operator: jobs in order with the times worked out in the open, crew named per job, materials listed per job, message queue in order, and every gap or clash flagged in plain words at the top.
Preview, from the skill itself
“# Crew Day Planner
A day with three or four jobs on it fails in predictable places.”
Version 1.0.09 filesOrdered by drive time and promise timesCrew and materials named per jobMessages drafted in orderHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: ebaaef864ec7… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 38.6 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/four-jobs-two-crews-split-day/WALKTHROUGH.md, examples/three-jobs-one-crew-tuesday/WALKTHROUGH.md, reference/crew-assignments-that-hold.md, reference/customer-messages-in-order.md, reference/materials-per-job.md, reference/ordering-by-drive-and-promise.md, templates/day-sheet.template.md, templates/message-queue.template.md
Worked example, from the package
examples/four-jobs-two-crews-split-day/WALKTHROUGH.md
A local service operator running two crews of two on a Thursday, with four jobs booked across four towns. The day only works split, and the sheet works each crew's half on its own before the operator approves either.
Expense and Receipt Log
Local Services / Money · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Every receipt lands in the job's cost record the moment it happens, and a weekly pass checks the log against what was actually paid, so job profit and tax records are read from a record instead of rebuilt from memory.
What changes
- Job costs living in a shoebox, a camera roll, and the operator's memory → each job carrying its own cost record from the first purchase
- Profit on a job as a feeling → the cost total and the amount left after costs read from the record in minutes
- Tax time as a rebuild months later, with gaps nobody can close honestly → a weekly pass catching a duplicate, a missing receipt, or a wrong job charge within days, while it can still be checked
Honest fit
For you if: job expenses live in a shoebox and your memory, and you want each receipt captured against its job as it happens, with a weekly check against what was paid.
Skip it if: you need tax advice or bills paid; the log keeps the records those decisions need, and the calls stay with you and your bookkeeper.
Your first run produces: one open job cost record holding every expense for that job so far, each entry traced to a receipt or an honest no receipt note, and the total re-added from the entries.
Preview, from the skill itself
“# Expense and Receipt Log
A job can look profitable right up until someone tries to add up what it cost.”
Version 1.0.09 filesCaptured at the moment it happensEvery entry belongs to a jobA weekly check against what was paidHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: dea382ffc913… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 30.1 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/valley-roof-repair/WALKTHROUGH.md, examples/yard-cleanup-and-dump-runs/WALKTHROUGH.md, reference/capturing-at-the-moment.md, reference/receipts-gaps-and-tax-records.md, reference/the-per-job-cost-record.md, reference/weekly-reconciliation.md, templates/job-cost-record.template.md, templates/weekly-reconciliation.template.md
Worked example, from the package
examples/valley-roof-repair/WALKTHROUGH.md
A roof repair operator takes a valley repair: strip the failed valley, fit new valley metal, re-lay the surrounding shingles, seal, and clear the old material. The work runs over two days.
Newsletter Issue Builder
Studio / Publishing · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A week's real work becomes a newsletter issue: sections drafted only from the studio's own records, every link checked, every claim held to what the records show, and one approval before anything sends.
What changes
- An issue starting from a blank page on send day and filled from memory → an issue drafted only from the week's real records, each section traced to a named source
- Links going out stale and small facts drifting → every link checked, and every claim stopping where its record stops
- Errors caught after sending → one complete draft, with its plan, approved once by the operator before anything sends
Honest fit
For you if: a weekly issue gets written from memory on send day, and you want it drafted only from the week's real records, with every link checked and one approval before it sends.
Skip it if: you need a mailing list managed or issues sent on their own schedule; the skill drafts and checks, and sending waits for your approval each time.
Your first run produces: one complete draft and one plan held for the operator, with every section traced to a record and every link marked checked.
Preview, from the skill itself
“# Newsletter Issue Builder
A good newsletter issue is not written from memory on send day.”
Version 1.0.09 filesDrafted only from real recordsEvery link checkedOne approval before anything sendsHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 3e5990956456… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 33.8 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/quiet-week-client-work-roundup/WALKTHROUGH.md, examples/studio-week-with-two-releases/WALKTHROUGH.md, reference/checking-links-and-facts.md, reference/gathering-from-records.md, reference/holding-claims-to-records.md, reference/sections-and-order.md, templates/issue-draft.template.md, templates/issue-plan.template.md
Worked example, from the package
examples/quiet-week-client-work-roundup/WALKTHROUGH.md
A solo operator who does client project work and maintains one small tool. The issue covers the week of Monday 14 September to Sunday 20 September 2026. No release ships this week. The point of this example is that the skill still produces an honest issue, just a short one, without padding.
Meeting Notes to Actions
Agent Operations · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A meeting stops living in memory: its notes become decisions and actions, each with a named owner, a date, and the line it came from, and everything unclear arrives as a flag with its question attached.
What changes
- Meeting actions living in the heads of the people who were there, each head holding a slightly different list → one checkable packet: decisions in one list, actions in another, each with a named owner, a date, and the line it came from
- A smooth summary nobody can check → every item printed with its line number, and every gap or clash named as a flag with its question attached
- Missed dates surfacing when the work fails to show up → the follow up already drafted in the same words as the lists, held for one approval
Honest fit
For you if: meetings end with notes as raw text and actions keep getting lost between the meeting and the work.
Skip it if: you need the meeting recorded or formal minutes; the skill works on notes you supply, and it does not send follow ups or track the work.
Your first run produces: one packet held for your approval: the decision list, the action list with a name and a date on each item, the flags in plain words, and one follow up draft that matches the lists exactly.
Preview, from the skill itself
“# Meeting Notes to Actions
# Meeting Notes to Actions Meetings rarely fail in the room.”
Version 1.0.09 filesEvery item traced to its lineAmbiguity flagged, not guessedDrafts held for approvalHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: b5a27c4ddfdd… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 42.8 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/vendor-kickoff-walkthrough.md, examples/weekly-ops-review-walkthrough.md, reference/ambiguity-and-flagging.md, reference/decisions-actions-and-updates.md, reference/owners-dates-and-follow-up.md, reference/traceability-and-line-links.md, templates/action-list.template.md, templates/follow-up-note.template.md
Worked example, from the package
examples/vendor-kickoff-walkthrough.md
A small studio meets its website vendor for a kickoff. The notes are plain and a little ragged, the room agrees more than it writes down, and two points are left hanging. The run turns 20 lines of notes into 3 decisions, 5 actions, and 2 flags, with one group follow up draft held for the operator.
Release Announcements
Studio / Publishing · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Every channel tells the same release story: each post is drafted from the one release record, checked claim by claim and link by link, and held for a single approval before anything goes out.
What changes
- Each channel telling the release story in its own shape → every post drafted from the one release record and checked against it line by line
- Wrong version numbers and stale links caught by a reader writing in → every claim and every link checked at a desk before the set is approved
- A drip of single posts arriving for approval across the day → one decision about a whole set, read once, with a log of what was announced, where, and in what words
Honest fit
For you if: a release is out and the news has to reach every channel in the same true shape.
Skip it if: you need release notes written or a launch campaign planned; the skill starts from a finished release record and drafts announcements only.
Your first run produces: one checked announcement set with its log: every post drafted from the one release record, checked claim by claim and link by link, held for the operator's one approval.
Preview, from the skill itself
“# Release Announcements
# Release Announcements One release, told once, told the same way everywhere.”
Version 1.0.09 filesOne record, every channelClaims and links checkedOne approval for the whole setHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 095d2e7fce0c… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 32.8 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-held-announcement-set.md, examples/the-patch-release-set.md, reference/approval-and-posting-log.md, reference/channel-shapes.md, reference/link-and-claim-checks.md, reference/the-release-record.md, templates/announcement-set.template.md, templates/approval-and-posting-log.template.md
Worked example, from the package
examples/the-held-announcement-set.md
A studio drafts the announcement set for a feature release, and the checks catch three problems before approval: two claims the record does not support and one link landing on the old version. The set waits, is fixed, and only then goes out.
Dependency Update Watch
Studio / Shipping · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Dependency drift stops arriving as emergencies: each scheduled pass leaves a dated report with findings triaged by risk, a one-at-a-time upgrade order, and the tests and the way back written for every step.
What changes
- Dependency work arriving as interruptions and one large, risky batch → the same work on a schedule, in one dated report with the installed state written as fact
- Nobody able to say what is waiting or what matters first → findings triaged once in risk order, with the quiet ones plainly marked as safe to wait
- A failure nobody can untangle → upgrades one at a time, each with named tests and a recorded way back, and deferrals carrying a written reason
Honest fit
For you if: a project has a manifest and a lockfile nobody has reviewed in weeks, and upgrades keep landing in one big batch.
Skip it if: you need upgrades applied or code rewritten for a new major version; the skill reports, orders, and prepares, and applying waits for your approval.
Your first run produces: one dated report with the installed state written at the top, findings triaged by risk, and a one-at-a-time upgrade order with the tests named for each step, and nothing applied yet.
Preview, from the skill itself
“# Dependency Update Watch
# Dependency Update Watch Dependencies drift the way anything unattended drifts.”
Version 1.0.09 filesFindings triaged by riskOne upgrade at a timeTests and way back written per stepHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: c2ebf204a30d… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 34.6 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-advisory-led-pass.md, examples/the-quiet-month-pass.md, reference/advisories-and-breaking-changes.md, reference/reading-the-manifest-and-lockfile.md, reference/safe-upgrade-order.md, reference/triage-by-risk.md, templates/dependency-report.template.md, templates/upgrade-plan.template.md
Worked example, from the package
examples/the-advisory-led-pass.md
An illustrative internal example. All package names, versions, and advisory identifiers in this walkthrough are invented for the example. They are not claims about real packages or real advisories.
Data Handling Rules
Agent Safety and Governance · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Everything your agent touches gets a class and a written rule: public, internal, personal, or secret, each with storing, sending, and removal covered, and every current violation flagged with a proposed fix.
What changes
- Handling rules living in whoever set the workflow up → every item an agent touches given a class, written on a sheet the operator can read
- Storing, sending, and removal running on habit → one written rule per class covering all three, approved by the operator
- Violations surfacing one at a time on the worst day → a short written list with proposed fixes, found on a calm pass
Honest fit
For you if: your agent handles a mix of public material, studio business, customer details, and sign-in values with no written rules.
Skip it if: you need legal rulings or secret storage set up; a class here is a working handling decision for your own shop, not a ruling under any law.
Your first run produces: one classification sheet, the handling rule for each class in play, and a violation list held for the operator, with nothing fixed during the run.
Preview, from the skill itself
“# Data Handling Rules
# Data Handling Rules An agent touches more kinds of data in a day than anyone has usually written down: public pages it reads, internal notes it drafts, personal details customers hand over, and the sign-in values that let it work at all.”
Version 1.0.09 filesFour classes, written rulesStoring, sending, and removal coveredViolations flagged with fixesHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 83460cf11374… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 36.0 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-client-file-handover/WALKTHROUGH.md, examples/the-support-inbox-pass/WALKTHROUGH.md, reference/classifying-edge-cases.md, reference/flagging-violations.md, reference/handling-rules-by-class.md, reference/the-four-classes.md, templates/classification-sheet.template.md, templates/violation-report.template.md
Worked example, from the package
examples/the-client-file-handover/WALKTHROUGH.md
A studio finishes a small build for a client and owes a handover: a folder with the finished work, the notes the client needs, and nothing else. An agent assembles the folder from the project store. The operator runs a classification pass over the whole project before the folder goes out, because a handover is the one send that cannot be taken back and re-sorted later.
Tool Output Verification
Agent Safety and Governance · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A tool result stops going straight into your work: shape and range checks, a second source for the facts the next step leans on, and a known-answer probe stand between the result and the action, and failures are held instead of acted on.
What changes
- Tool results going straight into quotes, totals, and bookings → shape and range checks, a second source, and a known-answer probe standing between the result and the action
- A wrong figure found only after the work is done → failures held at the result, with the operator seeing which check failed and what each source says
- A tool quietly going stale with nobody noticing → a standing verification plan per tool and a record where the pattern shows early
Honest fit
For you if: your agent is about to quote, send, file, count, book, or decide from a tool result that has not been checked.
Skip it if: you need another agent's finished work checked; that is Delegated Work Control. This skill checks raw tool outputs before any action leans on them.
Your first run produces: one tool result checked before it was used, shape, ranges, second source, and probe recorded line by line, and a verification plan you can reuse the next time that tool runs.
Preview, from the skill itself
“# Tool Output Verification
# Tool Output Verification A tool result arrives looking finished.”
Version 1.0.09 filesShape and range checksSecond source for load bearing factsFailures held, not acted onHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: c33191fe57db… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 37.8 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-doubled-price/WALKTHROUGH.md, examples/the-missing-record/WALKTHROUGH.md, reference/cross-source-confirmation.md, reference/holding-failures.md, reference/known-answer-probes.md, reference/schema-and-range-checks.md, templates/hold-report.template.md, templates/verification-plan.template.md
Worked example, from the package
examples/the-doubled-price/WALKTHROUGH.md
A small supply shop quotes a regular customer for six filter cartridges. The agent uses the shop's catalog lookup tool for the unit price, checks the result before any quote is prepared, and holds a figure that would have doubled the parts line.
Source Archiving
Data, Files, and Research · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A claim stops resting on a link and a memory: every source you rely on is saved as full page text with its address, the date taken, and a citation record, so it can be re-checked against what the page said when you read it.
What changes
- A claim resting on a link and a memory → the full page text saved with its address, the date taken, and a citation record
- A page that changed becoming an argument → the archive holding what the page said when it was read, with a second capture showing the change itself
- A figure questioned and the page gone → the answer found in the archive in minutes, and partial captures labelled with the missing part named
Honest fit
For you if: a claim in an estimate, a brief, or a report rests on a page that could change, move, or vanish.
Skip it if: you need sources judged for trustworthiness or pages watched on a schedule; the skill records what a named page said, and choosing which pages to trust stays yours.
Your first run produces: one claim standing on a saved page: full text captured, an archive entry and a citation record written, and the claim rechecked against the fresh capture.
Preview, from the skill itself
“# Source Archiving
# Source Archiving A web page is a moving target.”
Version 1.0.09 filesFull page text savedAddress, date, and citation on every entryRechecks against the captureHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 27fe8a9eea88… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 32.1 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-price-page-behind-an-estimate.md, examples/the-returns-window-that-moved.md, reference/archive-maintenance.md, reference/capture-and-storage.md, reference/citation-records.md, reference/rechecking-a-claim.md, templates/archive-entry.template.md, templates/citation-record.template.md
Worked example, from the package
examples/the-price-page-behind-an-estimate.md
An operator prices a small bathroom floor job from a supplier's web pages. Both pages are archived on the day the prices are read, and the tile price moves before the estimate goes out. The supplier and its pages in this walkthrough are invented for the example; the figures are the figures those invented pages carry, and the arithmetic is worked from them.
Job Completion Handover
Local Services / Field Operations · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
"Done" stops being something remembered: every finished job closes with a walkthrough checklist done with the customer, final photos logged, the warranty note handed over in writing exactly as you set it, and a sign-off on file.
What changes
- Done living in a handshake and a good feeling → one record: the scope walked item by item with the customer, final photos logged against that scope
- The warranty spoken if it was spoken at all → the warranty note and care instructions in the customer's hands in writing, exactly as the operator set them
- Outstanding items carried in the operator's head → every open item named on the record, with a sign-off line that shows the walk happened
Honest fit
For you if: your jobs finish and done is remembered instead of documented, with the warranty note spoken or not at all.
Skip it if: you need warranty terms set or a callback handled; terms are yours to set before handover, and callbacks belong to a separate workflow.
Your first run produces: one handover record filed with the job: the walkthrough done with the customer, final photos logged, the warranty note and care instructions in the customer's hands, and a sign-off on file.
Preview, from the skill itself
“# Job Completion Handover
# Job Completion Handover Done is a moment, and it passes fast.”
Version 1.0.09 filesWalkthrough done with the customerFinal photos loggedWarranty note handed over in writingHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 6aabbe5c724b… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 35.3 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/bathroom-refit-handover/WALKTHROUGH.md, examples/fence-build-handover/WALKTHROUGH.md, reference/sign-off-and-filing.md, reference/the-final-photo-log.md, reference/the-walkthrough-checklist.md, reference/warranty-note-and-care-instructions.md, templates/handover-record.template.md, templates/walkthrough-checklist.template.md
Worked example, from the package
examples/bathroom-refit-handover/WALKTHROUGH.md
A small bathroom refit, finished on a Thursday afternoon. The agreed price in the job record is $1,850, with a $600 deposit paid at booking and a $1,250 balance due at handover. The two figures add to the agreed price, and the handover record carries all three as written in the job record. This walkthrough shows the full handover, from the record built before the walk to the filing that closed the job.
Weather Reschedule Planner
Local Services / Field Operations · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A weather-killed day stops taking the week with it: affected jobs re-planned with new dates proposed in promise order, materials and crew knock-ons noted, and the customer messages drafted in send order for your approval.
What changes
- A lost day rebuilt as a morning of separate calls and fixes → the lost day rebuilt as one plan, with jobs decided move or hold against the threshold
- New dates handed out in call order → the longest waiting customer offered the earliest new date, because promise order sets the queue
- Materials and crew effects found afterwards → knock-ons listed with owners before the new dates go out, and every customer hearing one clear message in a planned order
Honest fit
For you if: weather stops a day of outdoor work and the week has to be rebuilt without breaking promises.
Skip it if: you need a forecast or bookings changed for you; the skill works from the forecast and thresholds you supply, and it proposes and drafts only.
Your first run produces: one plan held for the operator: the weather call recorded, jobs in promise order with move and hold reasons stated, new dates proposed, knock-ons owned, and customer drafts in send order.
Preview, from the skill itself
“# Weather Reschedule Planner
# Weather Reschedule Planner Weather takes a day.”
Version 1.0.09 filesNew dates in promise orderKnock ons noted with ownersMessages drafted in send orderHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 0b2a67af147a… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 42.0 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/cold-snap-paint-week/WALKTHROUGH.md, examples/rain-day-three-jobs/WALKTHROUGH.md, reference/customer-messages-in-send-order.md, reference/knock-ons-materials-and-crew.md, reference/promise-order-and-holds.md, reference/weather-thresholds-and-calls.md, templates/customer-message-set.template.md, templates/reschedule-plan.template.md
Worked example, from the package
examples/cold-snap-paint-week/WALKTHROUGH.md
An operator with two small crews: a paint crew and a general crew. In the week of Tuesday, November 18, the paint crew has exterior work on Tuesday and Wednesday, and the general crew has indoor work on both days. On Monday evening the forecast the operator works from shows a cold snap across Tuesday and Wednesday, then warmer days. The example shows a partial week, not a lost one: the indoor work holds, the exterior work moves, and promise order decides which moved job gets the one open day that week.
Customer Check-In Messages
Local Services / Reputation · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Past customers hear from you at the right moment, with a check-in traced to their own job record (a wear item, a season that matters for their work), drafted in your voice and logged so nobody is contacted twice inside the set period.
What changes
- Contact with past customers running on feel, then arriving as a dressed up pitch → a set period and a log deciding who hears anything, and the job record deciding what they hear
- A wear item noticed at the job and never flagged → one traced topic per customer, drawn from their own job record
- Customers contacted twice, or missed entirely → an entry for every customer considered, so nobody is missed and nobody is pestered twice inside the period
Honest fit
For you if: finished jobs go quiet and past customers hear nothing until work is slow, if they hear anything at all.
Skip it if: you need offers sent, referrals asked for, or reviews requested; a check-in carries no price, no offer, and no ask, and those jobs have their own skills.
Your first run produces: the check-in period written in the log header, written calls beside three past customers, and one check-in drafted and held for the operator, with no price, no offer, and no request inside it.
Preview, from the skill itself
“# Customer Check-In Messages
# Customer Check-In Messages A finished job goes quiet.”
Version 1.0.09 filesTopics traced to the job recordNo price, no offer, no askLogged against repeat contactHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: c94c20b62eb4… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 36.1 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/furnace-filter-winter-check-in/WALKTHROUGH.md, examples/valley-repair-autumn-check-in/WALKTHROUGH.md, reference/drafting-the-check-in.md, reference/the-check-in-log.md, reference/timing-and-spacing.md, reference/tracing-the-topic.md, templates/check-in-log-entry.template.md, templates/check-in-message.template.md
Worked example, from the package
examples/furnace-filter-winter-check-in/WALKTHROUGH.md
One heating operator, one winter round. Four past customers are considered from the job records. Only one of them is due a check-in, and the round is worth walking through for the three who are not, as much as for the one who is.
Podcast Episode Package
Creator and Audience · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
One finished recording becomes its whole publishing package: show notes, a chapter list, a cleaned transcript record, and the episode description, all drawn only from what was actually said, held for your one approval before anything publishes.
What changes
- The hour after recording spent re listening and typing notes from memory → one pass turning the recording into a complete package, every line pointed back to the transcript
- Chapter times guessed and descriptions written from the plan → notes, chapters, and description drawn only from what was actually said
- Publishing details scattered → one package held for one approval, with a written record of what was approved for each episode
Honest fit
For you if: you have a finished recording and need its whole publishing package built only from what was actually said.
Skip it if: you need audio recorded, edited, or published; the skill works from a finished recording and holds the package for your approval.
Your first run produces: one complete package held for approval: the cleaned transcript record, the show notes, the chapter list, and the episode description, each line traceable to the transcript.
Preview, from the skill itself
“# Podcast Episode Package
# Podcast Episode Package One recording in, one ready package out.”
Version 1.0.09 filesDrawn only from the recordingChapters from the transcriptOne approval before publishingHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 43adc7c7a3de… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 30.3 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-bakery-interview/WALKTHROUGH.md, examples/the-solo-episode/WALKTHROUGH.md, reference/chapters-and-timestamps.md, reference/cleaning-the-transcript.md, reference/notes-and-description.md, reference/source-and-scope.md, templates/episode-brief.template.md, templates/package-record.template.md
Worked example, from the package
examples/the-bakery-interview/WALKTHROUGH.md
A longer interview episode, packaged end to end. The names are illustrative; the shape and the figures are the point. Every topic, name, and chapter below comes from the one recording described here, and the chapter times add up to its length.
Deposit Terms Setup
Local Services / Money · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
No job starts on terms held only in memory: your deposit share and materials-upfront rule set per job type, written into the quote wording the customer sees before work starts, and recorded per job as agreed.
What changes
- Deposit terms living in the operator's head and varying by customer → one sheet with the terms per job type written and settled once
- The customer hearing the terms once, on a call → the same wording on every quote, seen before work starts
- The balance due date resting on two memories → every job carrying a record of the deposit, the balance, and the agreement, written before the work started
Honest fit
For you if: jobs start on deposit terms held only in memory, varying by customer, with nothing written the customer saw before agreeing.
Skip it if: you need the work priced or finished work billed; totals come from the accepted estimate, and invoicing is a separate job with its own skill.
Your first run produces: one terms sheet held for the operator with at least one job type fully settled, and one job's quote draft carrying its deposit wording with its deposit record opened beside it.
Preview, from the skill itself
“# Deposit Terms Setup
# Deposit Terms Setup Most arguments about money on a local job are not about the total.”
Version 1.0.09 filesTerms set per job typeQuote wording the customer seesRecorded per job as agreedHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 2c677f6ade81… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 32.8 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-fence-job-materials-upfront/WALKTHROUGH.md, examples/the-flooring-job-terms-changed/WALKTHROUGH.md, reference/customer-wording.md, reference/materials-upfront-rule.md, reference/terms-by-job-type.md, reference/the-deposit-record.md, templates/job-deposit-record.template.md, templates/terms-by-job-type.template.md
Worked example, from the package
examples/the-fence-job-materials-upfront/WALKTHROUGH.md
A fence replacement run under the materials upfront rule, with the terms set before any goods were ordered. The figures in this example are the example's own, each one taken from the job record it names, and they add up the way the skill requires a real job's figures to add up. They show the method; they are not terms for anyone else's fence.
Agent Escalation Handling
Agent Operations · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Work stops cleanly at the edge of the brief instead of guessing past it: the operator gets one escalation note carrying the evidence and one exact question, and the agent does only the safe work while it waits.
What changes
- The edge of the brief found by crossing it → stop conditions written into the brief before the work starts, so stopping is following the brief, not failing at the task
- A problem discovered after the money or the message has moved → one escalation note carrying the evidence and one exact question, while the item waits
- Helpfulness during a wait drifting into the undecided thing → only the safe work named in advance gets done while the operator decides
Honest fit
For you if: your agent works from a brief and sometimes reaches its edge: a figure over the line, a request it has no authority to grant, instructions that conflict.
Skip it if: you need the decision made for you, or cover for emergencies where waiting itself causes harm; the skill governs the stop, the note, and the wait, and the decision stays yours.
Your first run produces: one brief for a task the agent already does, carrying three to five stop conditions that can each be checked against a record, plus the short written list of safe work the agent may do while an item waits.
Preview, from the skill itself
“# Agent Escalation Handling
# Agent Escalation Handling Every brief has an edge.”
Version 1.0.09 filesStop conditions written firstEvidence with the questionSafe work while waitingHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 73cff75ad35a… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 38.5 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-invoice-over-the-line/WALKTHROUGH.md, examples/the-reply-that-needed-a-promise/WALKTHROUGH.md, reference/resuming-after-a-decision.md, reference/safe-work-while-waiting.md, reference/stop-conditions.md, reference/writing-the-escalation-note.md, templates/brief-with-stop-conditions.template.md, templates/escalation-note.template.md
Worked example, from the package
examples/the-invoice-over-the-line/WALKTHROUGH.md
A small shop uses an agent to match supplier invoices to purchase orders and prepare a payment list. One invoice in a batch of six is both over the approved line and mismatched against its order. The agent finishes the clean part of the batch, stops the one invoice safely, and escalates with the figures as read and one exact question.
Multi-Agent Job Split
Agent Operations · Version 1.0.0 · 9 files
$19one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
One big job stops coming back with doubled, missing, or conflicting pieces: it is split into work packages with hard boundaries before work starts, every agent writes to one shared record, and a merge check reconciles the parts before anything is delivered.
What changes
- One big job run as a single long pass that fails at the end → work packages with hard boundaries, written before work starts
- Progress living in summaries and memory → every agent writing to one shared record, where the count in the record is the progress
- Overlaps, gaps, and conflicts found at delivery → a merge check reconciling the parts against the whole before anything is delivered
Honest fit
For you if: you split big jobs across several agents and get doubled, missing, or conflicting pieces back.
Skip it if: the job cannot be bounded into named pieces in advance, or you need returned work quality checked; that check is a separate skill, and this one reconciles parts against the plan.
Your first run produces: one job done by two agents, reconciled to the item: two work packages with the boundary stated in one sentence, one shared record with a line per item, and a merge check run against the starting count before anything is delivered.
Preview, from the skill itself
“# Multi-Agent Job Split
# Multi-Agent Job Split One big job, several agents, and no plan for how the pieces fit back together is how work gets done twice, missed once, and delivered with the seams showing.”
Version 1.0.09 filesHard boundaries per packageOne shared recordMerge check before deliveryHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 871a9051b451… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 36.3 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-help-center-rebuild/WALKTHROUGH.md, examples/the-supplier-price-audit/WALKTHROUGH.md, reference/drawing-boundaries.md, reference/the-merge-check.md, reference/the-shared-record.md, reference/work-package-briefs.md, templates/job-split-plan.template.md, templates/merge-check.template.md
Worked example, from the package
examples/the-help-center-rebuild/WALKTHROUGH.md
An operator is moving a help center of 48 articles to a new structure. Every article gets a new home, some get new titles from an agreed title list, and every internal link has to land on a current title. The job splits by section across four agents, and the seams, the links between sections, are exactly what the merge check exists to test.
Privacy Consent Records
Agent Safety and Governance · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
You can say from a record who agreed to what: one consent ledger per person and per scope, checked before any details are used, with withdrawals recorded and honoured across every store the agent touches.
What changes
- Who agreed to what resting on memory and scattered form replies → one consent ledger per person and per scope, with dates and sources the operator can inspect
- Declines and non-answers treated as yeses by accident → declines and silences recorded as lines of their own, so nobody is asked again or let in by default
- A withdrawal fixed in one list and forgotten in three copies → a withdrawal checklist across every named store, with a later check that proves the count
Honest fit
For you if: your agent uses people's details and you cannot say from a record who agreed to what, per person and per scope.
Skip it if: you need legal advice on what you may collect or how long you may keep it; the ledger records agreements honestly and rules on nothing.
Your first run produces: one consent ledger started for one use of people's details: every store for that use listed, one entry per person carrying only what a source supports, and the first counts, granted, declined, and source missing per scope, held for the operator, with nothing sent and nothing changed.
Preview, from the skill itself
“# Privacy Consent Records
# Privacy Consent Records An agent that handles people's details makes a promise every time it uses them.”
Version 1.0.09 filesConsent checked before useDeclines recorded as linesWithdrawals across every storeHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: a8e2d6442119… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 34.1 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-new-client-intake.md, examples/the-withdrawal-that-spread.md, reference/capturing-consent.md, reference/checking-and-expiry.md, reference/ledger-fields.md, reference/withdrawal-and-propagation.md, templates/consent-ledger-entry.template.md, templates/withdrawal-record.template.md
Worked example, from the package
examples/the-new-client-intake.md
A small studio's agent handles new client enquiries. One person's intake, done properly, sets three ledger lines, places her details in three stores, and keeps her out of the one use she said no to. All people in this example are fictional.
Uptime and Status Checks
Studio / Shipping · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
You learn a service is down from a dated record, not from a user: scheduled checks run the steps a user would take, every miss follows a written retry, record, escalate ladder, and the service's state on any day can be read back.
What changes
- A feeling that the service has been up all week → a week of dated entries in one status record that either back the sentence or show the hour they do not
- A service counted as up because something answered → checks that run the steps a user would take, the way a user needs them to work
- A miss met with panic or a shrug → a written ladder: timed retry, record, then escalate to a named person with the times already written
Honest fit
For you if: you run a deployed service and learn it is down from a user instead of from a record.
Skip it if: you need the outage fixed, or a public status page kept for you; the skill finds, proves, and records a miss, and the repair stays yours.
Your first run produces: one service on a written check list of three to six user steps, run once by hand into a new status record as the baseline, with the schedule set and the failure ladder written on the list with a named person to escalate to.
Preview, from the skill itself
“# Uptime and Status Checks
# Uptime and Status Checks A deployed service is either answering its users or it is not, and most of the time nobody knows which until a user says so.”
Version 1.0.09 filesDated status recordUser path checksWritten failure ladderHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: fda0bb2592a5… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 34.8 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-morning-after-a-deploy/WALKTHROUGH.md, examples/the-slow-afternoon-outage/WALKTHROUGH.md, reference/check-list-design.md, reference/failure-ladder.md, reference/reading-results-honestly.md, reference/status-record.md, templates/service-check-list.template.md, templates/status-record.template.md
Worked example, from the package
examples/the-morning-after-a-deploy/WALKTHROUGH.md
A one person repair studio takes its bookings through a small booking service. On a Tuesday evening the operator ships a change to the confirmation page, then lets the check list watch the night: a hand run baseline, thirty two scheduled checks, one single miss at night, and a record that settles the morning.
User Guide Writing
Studio / Publishing · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Your guide describes the tool you actually shipped: every screen walked, every step written in the words the screens use and checked by doing it in the tool, and anything the tool does not do cut out.
What changes
- A guide written fast at the end of a build, from the builder's notes and memory → every screen walked and every step written in the words the screens use
- Steps describing renamed buttons and features cut before shipping → each section checked by doing it in the tool, and anything the tool does not do absent from the guide
- Sections ordered by screen instead of by need → every section a task in first-use order, so a new user can follow it without an interpreter standing by
Honest fit
For you if: you shipped a tool and its guide was written from the plan or from memory, so it names things the tool no longer does.
Skip it if: the tool is still changing its screens, or you need selling copy or a feature list; a guide waits until the operator calls the tool done.
Your first run produces: one guide section drafted and checked: the screen inventory of one finished tool, the first-week task list as the outline, and the first task's section written from the screens and then followed word for word, with its step check log beside it.
Preview, from the skill itself
“# User Guide Writing
# User Guide Writing A finished tool and a usable guide are two different things.”
Version 1.0.09 filesScreens set the wordsChecked by doing itAnything not done is cutHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 47c53c4cafeb… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 33.6 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/repairdesk-first-guide.md, examples/shelfcount-first-guide.md, reference/checking-every-step.md, reference/keeping-the-guide-current.md, reference/reading-the-tool-first.md, reference/task-order-and-sections.md, templates/guide-outline.template.md, templates/step-check-log.template.md
Worked example, from the package
examples/repairdesk-first-guide.md
RepairDesk is a fictional example tool, invented for this walkthrough: a repair ticket tool for a small bike workshop. Its screens, tickets, and part counts below are the example's own, and they check against each other. The guide writing is real in shape: a memory corrected by a screen, a draft in first-use order, and a check pass worked on one real morning's jobs.
Research Comparison Table
Data, Files, and Research · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
The choice stops resting on figures nobody can trace: options compared on the same rows and the same basis, every cell tied to a named source with its date, unknowns left blank and labelled, and the differences that decide it summarised under the table.
What changes
- A choice resting on tabs, memory, and figures nobody can trace → one table where every cell ties to a named source with the date it was read
- Gaps filled from memory or from what an option probably costs → unknowns left blank and labelled, with the question that would settle each one
- Options priced on different bases → totals worked on the same basis at your own size, with the differences that decide it summarised under the table
Honest fit
For you if: you are choosing between tools or services and the figures you are comparing came from different pages, dates, and bases.
Skip it if: you need the options tested hands-on or the choice made for you; the table shows what the sources support, and the choice stays yours.
Your first run produces: one comparison table for a choice you are already circling: a one-screen brief, five or six rows the choice turns on, the cells the first sources carry filled with a source key on each, the rest left blank with the reason, and three lines under the table naming the deciding differences so far.
Preview, from the skill itself
“# Research Comparison Table
# Research Comparison Table Most comparisons fail in the same quiet way.”
Version 1.0.09 filesSame rows, same basisSource and date on every cellDeciding differences summarisedHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: bb0bf11b20d8… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 40.6 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/backup-tools-for-a-small-studio.md, examples/invoicing-services-for-a-solo-operator.md, reference/choosing-rows-and-options.md, reference/handling-unknowns-and-conflicts.md, reference/sourcing-every-cell.md, reference/writing-the-deciding-differences.md, templates/comparison-brief.template.md, templates/comparison-table.template.md
Worked example, from the package
examples/backup-tools-for-a-small-studio.md
A four person design studio picks a backup tool for its shared project files. Three options are compared in one table, two blanks block the choice on the first pass, and two short questions close them. The three tools in this walkthrough, NorthVault, CopyDrift, and ShelfSave, are invented for the example. Every figure comes from the example's own dated source notes, listed with the table, and the arithmetic is worked from those figures.
Job Profit Review
Local Services / Money · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
You find out what a closed job actually made: estimate set against actual cost line by line, expenses and callbacks counted in full, and each lesson written into the next estimate as a changed line for your approval.
What changes
- A closed job judged by how it felt and by what is left in the account that week → estimate set against actual cost line by line, on one sheet per job
- Expenses and callbacks partly counted or forgotten → expenses and callbacks counted in full, with the result worked out in the open
- The lesson staying in the operator's head, so the next estimate repeats the miss → each lesson written into the next estimate as a changed line, held for your approval
Honest fit
For you if: you close jobs without knowing what each one actually made, and the same estimate misses repeat.
Skip it if: no cost records exist for the job, or you need prices set; the review reads the records a job left behind and drafts the changes, and pricing calls stay yours.
Your first run produces: one complete review sheet for the most recent closed and paid job, estimate against actual line by line with any callback counted, plus one lesson drafted as a changed line for the next estimate, both held for the operator.
Preview, from the skill itself
“# Job Profit Review
# Job Profit Review A job can feel like it paid well and still have made little, and a job that felt tight can turn out fine once the figures are read properly.”
Version 1.0.09 filesCallbacks counted in fullFull cost countedChange log for the next estimateHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: e7b3cbdf0135… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 34.3 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/gravel-driveway-regrade/WALKTHROUGH.md, examples/tree-removal-that-ran-long/WALKTHROUGH.md, reference/counting-the-full-cost.md, reference/estimate-against-actual.md, reference/finding-the-lesson.md, reference/turning-lessons-into-estimate-lines.md, templates/next-estimate-change-log.template.md, templates/profit-review-sheet.template.md
Worked example, from the package
examples/gravel-driveway-regrade/WALKTHROUGH.md
An operator who does yard and drive work takes a gravel driveway job: regrade a rutted drive, spread fresh gravel, and level it to the gate. The job was estimated from a walk of the drive and finished with a short callback to a low spot by the gate.
Subcontractor Coordination
Local Services / Field Operations · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A sub arrives with nothing left to memory: a scope note the sub agreed to, the schedule and site rules in writing, a payment record for the sub work, and the customer told in advance who is doing what.
What changes
- A sub briefed in two phone calls and good intent → a scope note the sub agreed to, item by item with the edges named
- Dates, site rules, and the price held in one head → the schedule and site rules in writing on both sides, and a payment record for the sub work
- The customer meeting a stranger at the door → the customer told in advance, in plain words, who is doing what
Honest fit
For you if: you bring in subs on jobs and the scope, the day, or the price lives in phone calls and memory.
Skip it if: you need the sub chosen, priced, or paid; the skill drafts and records the coordination, and hiring, sending, and paying stay yours.
Your first run produces: one brief and one payment record for the next job that needs a sub, held for the operator: the scope note item by item for the sub to confirm, the schedule and site rules in writing, and the customer line drafted and waiting for approval.
Preview, from the skill itself
“# Subcontractor Coordination
# Subcontractor Coordination Most jobs that use a subcontractor go wrong in the same quiet places.”
Version 1.0.09 filesScope note confirmed by the subSchedule and site rules in writingPayment record for sub workHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 78c1542d0747… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 35.0 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/bathroom-tile-plumber-sub/WALKTHROUGH.md, examples/porch-rebuild-electrician-sub/WALKTHROUGH.md, reference/customer-line-on-who-does-what.md, reference/payment-record-for-sub-work.md, reference/schedule-and-site-rules-in-writing.md, reference/scope-note-the-sub-agrees-to.md, templates/coordination-record.template.md, templates/subcontractor-brief.template.md
Worked example, from the package
examples/bathroom-tile-plumber-sub/WALKTHROUGH.md
A tiling and bathroom operator is retiling a bathroom and moving the shower to the opposite wall. The pipe moves are not the operator work. The operator brings in Ana, a plumber, for the waste and supply moves before tiling starts, and for the final shower fitting after it.
Equipment Maintenance Log
Local Services / Field Operations · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Wear shows up on paper before it stops a job: one maintenance record for every tool, vehicle, and machine, with service intervals tracked, repairs logged at their real costs, and downtime noted.
What changes
- Service dates living in memory, on stickers, and on receipts in a glovebox → one maintenance record for every tool, vehicle, and machine
- A machine serviced when it sounds rough or when it stops → service intervals tracked, with the due list coming from readings and dates, not from a breakdown
- Repairs paid and forgotten, so the same part fails twice unnoticed → repairs logged at their real costs and downtime noted, so repeat failures show up on paper
Honest fit
For you if: your tools and machines are serviced from memory, and wear only shows up when something stops a job.
Skip it if: you need a fault diagnosed or a repair booked; the log keeps and reads the record, and repairs and spending stay yours.
Your first run produces: one register holding every tool, vehicle, and machine the business depends on, each with how its service is counted, its last known service or an honest unknown, and its next due worked out where the figures allow.
Preview, from the skill itself
“# Equipment Maintenance Log
# Equipment Maintenance Log A tool that fails mid job costs more than the repair.”
Version 1.0.09 filesOne record per machineService intervals trackedDowntime countedHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 371af5b8bacc… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 32.1 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/log-splitter-first-season-on-record.md, examples/mower-belt-failure-caught-by-the-log.md, reference/equipment-record-fields.md, reference/reading-the-record-for-failures.md, reference/repair-and-downtime-logging.md, reference/service-intervals-hours-or-date.md, templates/equipment-register.template.md, templates/maintenance-entry.template.md
Worked example, from the package
examples/log-splitter-first-season-on-record.md
A one person firewood business: cut, split, and delivered loads. The machines that matter are a log splitter with an hour meter, two chainsaws with no meters, and a tipping trailer. The splitter was bought used two winters ago and has never had a written history. The operator starts the record in March, before the spring push.
Google Profile Updates
Local Services / Marketing · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Your Google profile matches the real business again: hours and services checked against what you actually do on a set schedule, photos picked from finished jobs, and review replies drafted in your voice for your approval before anything goes live.
What changes
- Holiday hours still up weeks after the holiday, and dropped services still bringing calls → hours and services checked against what you actually do, on a set schedule
- Good job photos sitting on a phone while the profile shows work from years ago → photos picked from finished jobs for each update round
- Reviews unanswered, or answered in a rush that does not sound like you → review replies drafted in your voice from the job record, held for your approval before anything goes live
Honest fit
For you if: your Google profile has drifted from the real business: old hours, dropped services, photos from years ago, reviews unanswered.
Skip it if: you need anything posted or replied to without your approval of that exact item, or better search placement promised; an accurate profile is the whole claim.
Your first run produces: one packet held for approval: the fact sheet of the business as it really is, the list of differences between it and the live profile, the draft changes, up to three photo picks from recent finished jobs, and one draft reply to the most recent unanswered review.
Preview, from the skill itself
“# Google Profile Updates
# Google Profile Updates A Google Business Profile is often the first thing a customer sees: the hours, the services, the photos, and the replies under the reviews.”
Version 1.0.09 filesFacts checked against the businessPhotos from finished jobsDrafts held for approvalHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: d6a05c16da20… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 29.1 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/holiday-hours-roofing-update/WALKTHROUGH.md, examples/review-replies-and-service-list-fix/WALKTHROUGH.md, reference/photo-picks-from-finished-jobs.md, reference/profile-facts-check.md, reference/review-replies-in-the-operators-voice.md, reference/update-schedule-and-log.md, templates/profile-update-plan.template.md, templates/review-reply-draft.template.md
Worked example, from the package
examples/holiday-hours-roofing-update/WALKTHROUGH.md
A one crew roofing operator doing valley repairs, gutter work, and roof checks in the Rockwood and Oakdale area. The monthly full check lands on Monday November 16, ten days before Thanksgiving. Last year's problem is written in the log: holiday hours went up the day before the holiday, and two customers called the closed shop on the Friday after. This round exists to not repeat that.
Short-Form Topic Bank
Creator and Audience · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A posting day starts from a stocked bank instead of a blank page: every topic drawn from your real work records, carrying its hook, the record it came from, and its status, with new ideas checked so no topic is filmed twice.
What changes
- A filming day starting from memory and a blank page → a stocked bank of topics drawn from your real work records
- Good topics lost because nothing was written down → every topic carrying its hook, the record it came from, and its status
- The same topic filmed twice because the first filming lived only in memory → new ideas checked against the bank before they are added
Honest fit
For you if: your posting days start from a blank page even though your work records are full of topics.
Skip it if: you need clips cut from long recordings, scripts written, or videos filmed and posted; the bank decides what is worth filming, before any camera is on.
Your first run produces: one starter bank held for the creator: entries drafted from the last two to four weeks of work records, each tracing to a named record with its hook and status set, no duplicates among them, and the filmed and posted history noted where the records show it.
Preview, from the skill itself
“# Short-Form Topic Bank
# Short-Form Topic Bank A posting day should not start from a blank page.”
Version 1.0.09 filesHook on every entryStatus on every entryDedupe before filmingHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 22262b950e15… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 30.2 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/repair-crew-question-bank.md, examples/studio-build-log-bank.md, reference/keeping-the-bank-current.md, reference/reading-work-records.md, reference/statuses-and-dedupe.md, reference/writing-the-hook.md, templates/topic-bank.template.md, templates/topic-entry.template.md
Worked example, from the package
examples/repair-crew-question-bank.md
A two person repair and handyman crew that posts short videos twice a week: some show a finished job, and some answer a question customers ask again and again. The crew keeps job cards for every job and saves written customer questions from message threads and call notes in one folder. A small starter bank already exists from an earlier pass.
New Customer Welcome Pack
Local Services / Sales · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Every new customer gets the same answers before the first job: one welcome pack built from your real records, covering the services in plain words, the terms as set, how to reach you, and what to expect on the day, held for your approval before it sends.
What changes
- Each new customer hearing the booking explained a different way, in fragments → one welcome pack in the same shape for every new customer
- The price in one message and the payment timing in another → services, terms, contact details, and the day plan in one place the customer can check before anyone arrives
- Terms copied from the last pack sent → the pack rebuilt from your real records each time and held for your approval before it sends
Honest fit
For you if: every new customer hears the booking explained a different way, and the same basic questions come back job after job.
Skip it if: you need prices or terms written, a job quoted, or the pack sent; the pack only carries what your records already hold, and sending stays yours.
Your first run produces: one complete welcome pack for the next new customer, built from the service list, the terms as set, the contact details, and the booking note, with every price and date pointed back to a record and any gap flagged in plain sight, held for the operator and not sent.
Preview, from the skill itself
“# New Customer Welcome Pack
# New Customer Welcome Pack A new customer has booked a first job and knows almost nothing yet: what the work covers, what it costs, when the money is due, how to reach the operator, and what the day itself will look like.”
Version 1.0.09 filesBuilt from your recordsPlain words throughoutSent only after approvalHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: c9c356cc33c4… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 34.3 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/roof-valley-repair-first-job/WALKTHROUGH.md, examples/yard-cleanup-and-haul-first-job/WALKTHROUGH.md, reference/services-in-plain-words.md, reference/terms-contact-and-timing.md, reference/what-goes-in-the-pack.md, reference/what-to-expect-on-the-day.md, templates/pack-assembly-checklist.template.md, templates/welcome-pack.template.md
Worked example, from the package
examples/roof-valley-repair-first-job/WALKTHROUGH.md
A roofing operator taking on a new customer whose back roof valley leaks in heavy rain. The customer has never used the operator before. The job is booked, and the welcome pack goes out before any money is due, so the customer sees the whole arrangement in one place.
Agent Config Versioning
Agent Operations · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
When an agent's behavior changes, you can say exactly when it changed, why, and what the earlier wording was, and roll back to that earlier version whole when a change goes wrong.
What changes
- A behavior surprise argued over from memory → the entry that changed the line, with its date, its reason, and its before and after wording
- A bad change rebuilt from wording nobody kept → the earlier version sitting whole in the record, restored and checked
- It worked last week, settled by opinion → the version live on that date, named in the record and restored or replayed to settle it
Honest fit
For you if: Your agent's behavior changed and nobody can say when it changed, why, or what the earlier wording was.
Skip it if: You need the configuration, policies, or instructions written for you, or work done under an old version undone; the skill keeps the versions, and a rollback restores the instructions only.
Your first run produces: one agent's configuration copied exactly as it stands into the record as a first dated version marked live, read back line by line against the live setup, plus one written sentence saying what a rollback would mean for that agent today.
Preview, from the skill itself
“# Agent Config Versioning<br># Agent Config Versioning An agent is what its configuration says it is.”
Version 1.0.09 filesEvery change a new versionPlain words diff, completeRollback restores wholeHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 26ca48fb602c… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 41.4 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-broken-briefing/WALKTHROUGH.md, examples/the-policy-tightening/WALKTHROUGH.md, reference/rollback-procedure.md, reference/version-record.md, reference/version-storage-and-naming.md, reference/writing-the-diff.md, templates/rollback-record.template.md, templates/version-entry.template.md
Worked example, from the package
examples/the-broken-briefing/WALKTHROUGH.md
A solo operator runs a daily briefing agent that builds a morning briefing from his calendar, his task list, and his job notes. One afternoon change empties two sections of the next briefing. The version record names the change, the hour it went live, and the exact earlier text, and the rollback restores that text whole the same day.
Scheduled Report Builder
Agent Operations · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Your recurring report comes out in the same shape every time, every figure traced to the record behind it, and a missing record named as a gap instead of quietly filled.
What changes
- A report whose sections drift from run to run → the same sections, order, and definitions every time, so this period reads against the last one
- A figure nobody can trace → every figure entered from its record, with the source named in the section
- A missing record quietly filled from memory → a named gap in the run where it happens, with totals labelled for the records they actually cover
Honest fit
For you if: A report repeats on a schedule and its sections drift, its figures cannot be traced, or a missing record gets filled in from memory.
Skip it if: You need the underlying records created, a forecast made, or action taken on what the report shows; the builder works from records that exist and sends nothing on its own.
Your first run produces: one written spec for the recurring report you build most often, and one report built to it for the last completed period: every figure traced to its named record, every total re-added from the figures above it, and every missing record named as a gap.
Preview, from the skill itself
“# Scheduled Report Builder<br># Scheduled Report Builder Some reports are written once.”
Version 1.0.09 filesSame shape every timeEvery figure names its sourceA gap is named as a gapHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 1e585d8790ad… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 36.4 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-monthly-cost-roundup/WALKTHROUGH.md, examples/the-weekly-operations-summary/WALKTHROUGH.md, reference/fixed-shape-and-sections.md, reference/gaps-and-missing-records.md, reference/review-and-approval.md, reference/tracing-figures-to-records.md, templates/report-spec.template.md, templates/scheduled-report.template.md
Worked example, from the package
examples/the-monthly-cost-roundup/WALKTHROUGH.md
An operator runs three standing agents and builds the same cost roundup in the first days of each month for the month just ended: spend by provider, spend by work type, and anything that cannot be placed. One provider's record has not arrived by the close day, one charge is grouped with no breakdown, and the roundup still closes with both facts in their sections and its totals labelled for what they are.
Secrets in Transit Check
Agent Safety and Governance · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
You can see every leg a secret travels between tools, agents, and people, each leg recorded with a plain risk call and a safer route, working from labels and locations only and never handling a real value.
What changes
- How a secret travels told from memory, and the story shorter than the trip → a written log: every leg named, every carrier named, every call counted from the rows
- A value pasted into a thread to hand work over → a label, a location, and a route handed over instead
- Tools printing full settings into logs, and logs attached to tickets → setting names printed, value lines left out, and tickets carrying the label and the shape of the fault
Honest fit
For you if: A secret has to travel between tools, agents, or people, and nobody can say how it gets from its home to the place that uses it.
Skip it if: You need the inventory kept, an exposure ruling, or a value rotated; that is Secrets Hygiene work, and this check never holds, carries, or passes a real value.
Your first run produces: one filled transit path log for the secret that traveled most recently: one block per leg, a risk call on every leg, and totals counted from the rows, plus a draft safer route plan that changes nothing yet and a handover note to Secrets Hygiene for any value that traveled badly, in labels and dates only.
Preview, from the skill itself
“# Secrets in Transit Check<br># Secrets in Transit Check A secret at rest has a home.”
Version 1.0.09 filesLabels and locations, never valuesEvery leg gets a callA safer route per legHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 97076d088b60… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 38.8 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-debug-handoff/WALKTHROUGH.md, examples/the-weekend-handover/WALKTHROUGH.md, reference/reading-transit-records.md, reference/risk-calls-on-a-path.md, reference/safer-routes.md, reference/where-secrets-get-copied.md, templates/safer-route-plan.template.md, templates/transit-path-log.template.md
Worked example, from the package
examples/the-debug-handoff/WALKTHROUGH.md
A small web project, one owner, one agent. A deploy fails on a Tuesday evening, and the two of them debug it together. The secret is the deploy service token. Its proper home, on the Secrets Hygiene inventory, is the hosting platform secret setting, but the setting sits empty: the token was reissued in a hurry during an outage two weeks earlier and parked in the owner's vault for now, and the deploy tool was set to take a typed value. This audit, run on Wednesday morning, follows the trip the token took on Tuesday night. It took about forty minutes.
Incident Comms Drafts
Studio / Publishing · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
While an incident is live, each outward update is drafted from the incident record in plain words, what happened, what is affected, and when the next update comes, and every draft is held for your approval before it goes out.
What changes
- Silence while the fix is under way → affected people hearing early, in plain words, what happened and when they will hear again
- Each channel telling its own version → every draft written from one incident record and checked against it line by line, so the facts match everywhere
- Half worded updates leaving on their own → one clear approval decision per message, read in full before it goes out
Honest fit
For you if: An incident is live and the people affected need what happened, what is affected, and when the next update comes, while the facts are still moving.
Skip it if: You need the incident fixed, the post incident review run, or one to one support replies handled; this skill drafts the outward words only, and sends nothing.
Your first run produces: a practice set from a past, closed incident: the incident record rebuilt from its own sources with gaps written in as unknown, a first notice drafted from only what was known at that early point and checked line by line against the record, and a closing note drafted from the end of the record, both held for the operator and logged as practice, not sent.
Preview, from the skill itself
“# Incident Comms Drafts<br># Incident Comms Drafts While an incident is live, the people affected by it do not need a full explanation.”
Version 1.0.09 filesThe incident record is the only sourceEvery draft promises a next updateNothing goes out unapprovedHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: ea5430dec6b2… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 38.3 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/checkout-failure-live-updates.md, examples/sign-in-slowdown-live-updates.md, reference/corrections-and-closing.md, reference/plain-words-and-tone.md, reference/the-incident-record.md, reference/update-cadence-and-channels.md, templates/incident-record.template.md, templates/message-draft-set.template.md
Worked example, from the package
examples/checkout-failure-live-updates.md
A solo operator runs a small online shop that sells printed field guides. On a Tuesday morning checkout stops completing. Three messages carry the incident from first report to closing note, each drafted from one record and held for approval before it goes out.
Beta Feedback Loop
Studio / Shipping · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Every beta report lands in one triaged record tied to the build it came from, duplicates merged and severity called from its effect, so every fix can be traced to the release that carried it and closed only when a reporter confirms it landed.
What changes
- Reports scattered across messages, calls, and notes → one triaged record for the round, every report logged with the build it came from
- One fault reported four times looking like four faults → duplicates merged into a single record with every reporter kept
- A fix shipped with nobody able to say where it landed → every fix traced to the release that carried it, and closed only when a reporter confirms it landed
Honest fit
For you if: A beta build is out with testers and their reports arrive scattered, with no build on some and the same fault reported again and again.
Skip it if: You need testers recruited, fixes written and shipped, or a support desk run; the loop keeps and traces the reports, and the product calls stay yours.
Your first run produces: one record holding a whole beta round: every findable report logged with its build, each fault ranked by its effect, duplicates merged with their reporters kept, and any fix named only where the release record backs it, with nothing sent to testers.
Preview, from the skill itself
“# Beta Feedback Loop<br># Beta Feedback Loop Beta feedback fails in a quiet way.”
Version 1.0.09 filesEvery report carries its buildSeverity from effect, not toneFixed only in a named releaseHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 784a948cb872… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 39.8 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-duplicate-wave/WALKTHROUGH.md, examples/the-export-crash/WALKTHROUGH.md, reference/logging-and-versioning.md, reference/merging-duplicates.md, reference/severity-by-effect.md, reference/tracing-fixes-to-releases.md, templates/feedback-record.template.md, templates/release-feedback-summary.template.md
Worked example, from the package
examples/the-duplicate-wave/WALKTHROUGH.md
A checklist app for small work crews is in beta with 8 testers, all of them crew leads using build 1.4.0 on real jobs. In the first 2 days, 11 reports arrive. Seven of them are one fault wearing seven sets of words. This walkthrough follows the merging, the one fix that shipped, and the block that honestly stays open.
CSV to Database Import
Data, Files, and Research · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A CSV becomes database rows under a column mapping you approved before anything loaded, bad rows set aside in a named rejects file instead of dropped, and a row-count reconciliation that proves the import complete.
What changes
- An import run as a leap, with rows quietly going missing → a written column mapping approved before anything loads
- Bad rows dropped on the way in → every rejected row kept whole in a named rejects file, with its row number and the reason it failed
- Nobody able to prove the import complete → counts reconciled in writing on both sides: data rows equal accepted plus rejected, and rows after equal rows before plus accepted
Honest fit
For you if: A spreadsheet or export needs to become database rows, and past imports lost rows nobody could account for.
Skip it if: You need the file cleaned, the table reshaped, or rejected rows repaired for you; cleaning is separate work done first, and rejected rows go back to you whole.
Your first run produces: a validation pass that loads nothing: the smallest waiting file counted as received, its column mapping written and approved in the record, a named rejects file written, and the pass reconciled exactly, ready for the operator to read the mapping and the rejects and give the word to load.
Preview, from the skill itself
“# CSV to Database Import<br># CSV to Database Import A CSV file and a database table rarely line up on their own.”
Version 1.0.09 filesNothing imports before approvalRejected rows are never droppedReconciliation, or it is not doneHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 50e1891d876d… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 33.5 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/member-list-import/WALKTHROUGH.md, examples/supplier-parts-import/WALKTHROUGH.md, reference/loading-safely.md, reference/rejects-and-reconciliation.md, reference/validation-rules.md, reference/writing-the-mapping.md, templates/column-mapping.template.md, templates/import-record.template.md
Worked example, from the package
examples/member-list-import/WALKTHROUGH.md
A community workshop moves its membership list from a spreadsheet export into its members table: 486 rows in the file, 23 rejected with named reasons, 463 loaded, and both reconciliations closing exactly.
Pre-Job Site Checklist
Local Services / Field Operations · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Tomorrow's job gets checked today: access confirmed, materials on hand counted against the job record, the customer confirmation drafted, weather glanced at, and anything short raised while there is still time to fix it.
What changes
- The state of tomorrow's job as a feeling → each part read, counted, or asked, with the result written down: access confirmed for this date, or on the fix list
- Materials guessed at from the doorway → needed, on hand, and short side by side, from a count done today
- The customer assumed to expect the crew → a draft confirmation held for the operator to send, with the reply, or the lack of one, on the sheet
Honest fit
For you if: One job runs tomorrow and its access, materials, and customer confirmation are still assumptions the morning would test.
Skip it if: You need a whole day of jobs planned, materials ordered, or a new time agreed with the customer; the checklist readies one job, and ordering and sending stay yours.
Your first run produces: one closed checklist for tomorrow's job: access read from the record, materials counted where they sit with needed, on hand, and short written per line, the weather glanced at with the time noted, every gap on one fix list with a name and a time, and one draft confirmation held for the operator to send.
Preview, from the skill itself
“# Pre-Job Site Checklist<br># Pre-Job Site Checklist The morning of a job is the wrong time to learn that a gate is locked, a part is short, or the customer expected a different day.”
Version 1.0.09 filesOne job at a timeCount what is on handGaps raised the day beforeHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: c745e67aacfe… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 34.1 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/fence-and-gate-day-before/WALKTHROUGH.md, examples/roof-valley-repair-day-before/WALKTHROUGH.md, reference/access-and-entry.md, reference/customer-confirmation.md, reference/materials-count-against-the-record.md, reference/weather-and-day-fit.md, templates/confirmation-message.template.md, templates/site-checklist.template.md
Worked example, from the package
examples/fence-and-gate-day-before/WALKTHROUGH.md
A fencing operator with one job booked for Thursday: a side yard run of fence panels to replace, with a gate to hang at the end of the run. The check runs on Wednesday afternoon. There is one job on this sheet, and the crew is the operator and one helper, both named in the job record for this work.
Service Area Pricing Zones
Local Services / Money · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Distance stops being priced from feel: your service area becomes named zones with a written trip line for each, stated the same way in every quote, and out-of-zone jobs handled as logged exceptions instead of quiet discounts.
What changes
- Distance priced from feel, a different figure per quote → a trip line read from a zone table the operator approved
- Customers in the same area paying different trip figures with no reason on record → the same zone and the same trip line stated the same way in every quote
- Out of zone work quietly discounted to fit → each such job a logged exception, approved by the operator with its figure and reason
Honest fit
For you if: Distance gets priced from feel, so near and far customers get trip figures nobody can explain later.
Skip it if: You need prices set, new ground added to the area, or quotes sent and negotiated; the figures and the area are yours, and exceptions stay yours to approve.
Your first run produces: one dated zone table built from the last run of finished jobs: three zones named with their edges written in one line each and a trip line stated per zone, the ground beyond named out of zone, and one real quote for this week written from the table, held for the operator's approval with nothing sent.
Preview, from the skill itself
“# Service Area Pricing Zones<br># Service Area Pricing Zones Distance is part of almost every local job, and it is the part most often priced from feel.”
Version 1.0.09 filesOne zone table for everyoneThe same words in every quoteNo quiet discountsHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: fb1d3cc60a2c… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 33.9 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/cleaning-operator-named-zones/WALKTHROUGH.md, examples/hauling-operator-three-zones/WALKTHROUGH.md, reference/dividing-the-area-into-zones.md, reference/out-of-zone-exceptions.md, reference/setting-the-trip-line-per-zone.md, reference/stating-zones-in-quotes.md, templates/quote-and-exception-log.template.md, templates/zone-table.template.md
Worked example, from the package
examples/cleaning-operator-named-zones/WALKTHROUGH.md
A two person cleaning operator doing one off deep cleans and moving out cleans. Distance had been handled by adding a bit when a house sounded far, and nothing when it sounded near. The area is cut by a river: some addresses are close in miles and slow to reach, because every trip to them crosses one bridge. The operator zones by drive time instead of distance, from the job records, which hold the drive times.
Complaint Handling Ladder
Local Services / Reputation · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
An unhappy customer gets a ladder, not an argument: each rung from first contact to resolution has its record, its draft reply, and its limit, and no draft ever promises more than the job's written warranty.
What changes
- A complaint as a mood in messages and memory → one dated record any reply can be checked against
- Replies written in the heat of the moment, promising more than the job allows → a plain draft per rung, checked against the job record and the written warranty before anything is offered
- Warranty limits surfacing late, sounding like an excuse → the limits stated early and in plain words, while the conversation is still calm
Honest fit
For you if: A customer says work failed, came back, or was not what they expected, and the reply is becoming an argument instead of a path.
Skip it if: You need legal advice, replies sent for you, or refund and goodwill calls made; those decisions stay with you, and the ladder only keeps them written down.
Your first run produces: one complete complaint record for a current or recent complaint, logged in the customer's own words, with the job record pulled, the warranty check written as covered, not covered, or not clear with the dates and wording it rests on, and one reply drafted and held, promising nothing beyond the written warranty.
Preview, from the skill itself
“# Complaint Handling Ladder<br># Complaint Handling Ladder An unhappy customer gets a ladder, not an argument.”
Version 1.0.09 filesOne rung at a timeNothing beyond the written warrantyDrafts held for approvalHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 85594ab9676f… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 33.6 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/free-redo-asked-beyond-warranty/WALKTHROUGH.md, examples/leak-returned-inside-warranty/WALKTHROUGH.md, reference/closing-and-escalation.md, reference/reading-the-job-record.md, reference/reply-tone-and-limits.md, reference/the-written-warranty.md, templates/complaint-record.template.md, templates/reply-draft.template.md
Worked example, from the package
examples/free-redo-asked-beyond-warranty/WALKTHROUGH.md
A garden services operator who cleans and stains fences. Eleven months after a fence was cleaned and stained, the customer writes that the stain has gone patchy along the bottom rails and asks for the whole fence to be redone free, plus half the original price back for the trouble.
Before and After Gallery Keeping
Local Services / Marketing · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Finished jobs become a gallery you can actually show: before and after pairs pulled from each job's own photo record, captions that state only what the record supports, and the customer's permission noted on the record before any pair is used.
What changes
- Finished jobs living in a camera roll and a memory → each gallery job a matched pair, a caption, and a permission note in one entry
- Permission as something the operator meant to ask about → permission written on the record, pair by pair, before any use, so a pair is cleared on paper or held
- Captions carrying claims nobody recorded → captions that say what the work was and what the photos show, and nothing more
Honest fit
For you if: Finished jobs sit in a camera roll, unpaired and uncaptioned, with no note of which customers agreed to be shown.
Skip it if: You need photos taken or improved, permission asked for you, or pairs posted anywhere; the gallery is kept as a record, and showing anything stays yours.
Your first run produces: one complete gallery entry for a finished job with a good photo record: a matched before and after pair, a caption every word of which traces to the job record, and the permission note on the record with its date and scope, or a clear held mark and a drafted permission ask held for the operator to send.
Preview, from the skill itself
“# Before and After Gallery Keeping<br># Before and After Gallery Keeping A finished job is the clearest proof of work a local operator has, but only when the photos are paired honestly and the customer has agreed to them being shown.”
Version 1.0.09 filesPermission on the record firstCaptions from the record onlyHeld back pairs stay visibleHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 58a0f7968179… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 27.5 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/deck-cleaning-pair-cleared-for-use/WALKTHROUGH.md, examples/roof-valley-repair-pair-held-back/WALKTHROUGH.md, reference/keeping-and-using-the-gallery.md, reference/pairing-photos-from-the-record.md, reference/permission-on-the-record.md, reference/writing-captions-from-the-record.md, templates/gallery-entry.template.md, templates/permission-ask.template.md
Worked example, from the package
examples/deck-cleaning-pair-cleared-for-use/WALKTHROUGH.md
A pressure washing and deck cleaning operator with a finished job: a wooden back deck cleaned and washed down, at a house in the operator's home town. The job record holds four photos and a short note of the work. This walkthrough takes that one job from photo record to a cleared gallery entry.
Series and Sequels Planner
Creator and Audience · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A multi-part series that agrees with itself: the arc and part list drawn from your real work, continuity notes kept for every part (what was said, what was promised), and each new part checked against them before you film.
What changes
- Each part outlined from memory of the last one → one written plan and one continuity ledger every part is checked against
- Promises made on camera living in the creator's head → every part's words and promises in the ledger, and each new part checked against them before filming
- A changed size or a dropped thread found by a viewer → clashes fixed or flagged at the outline, before anything is filmed
Honest fit
For you if: A series is planned part by part from memory, and parts disagree on names, sizes, or promises made earlier.
Skip it if: You need the work invented, or filming, editing, and posting done; there is no series to plan without real work in progress, and the camera work stays yours.
Your first run produces: one series plan and one continuity ledger for a piece of real work that falls into parts: the arc in one sentence, the part list in the order the work happens, earlier parts filled into the ledger from the parts themselves, and the next part's outline checked line by line against it, held for the creator with nothing filmed or announced.
Preview, from the skill itself
“# Series and Sequels Planner<br># Series and Sequels Planner A series earns trust part by part.”
Version 1.0.09 filesThe arc comes from real workPromises kept in a ledgerCheck before filmingHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: fc399db0d725… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 30.7 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/raised-bed-garden-series/WALKTHROUGH.md, examples/workbench-build-series/WALKTHROUGH.md, reference/arc-from-real-work.md, reference/checking-a-new-part.md, reference/continuity-notes.md, reference/sequels-and-returns.md, templates/continuity-ledger.template.md, templates/series-plan.template.md
Worked example, from the package
examples/raised-bed-garden-series/WALKTHROUGH.md
A grower films one raised bed from bare soil to first harvest. The season runs in five stages over four months, and the plants put in during the second part are the facts the fourth and fifth parts will be judged against. Memory alone will not hold which edge the beans went along, or how many pepper plants went in.
Agent Dry Run Rehearsal
Agent Operations · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A new workflow earns its first live run: it rehearses against copies of your real records and hands you a step-by-step log with every outward or state-changing step flagged, so you approve exactly what it would do before it touches anything real.
What changes
- A new workflow meets real records for the first time in the live run → it rehearses on dated copies first, and the first faults are found in the log, before anything real moves
- Risky steps buried in the sequence → every outward and state changing step flagged in plain lines, record by record
- A correction after a live mistake means undoing and explaining → a correction costs a new rehearsal of the affected steps, and approval names the workflow, the records, and the destinations seen in advance
Honest fit
For you if: A new workflow is about to run live for the first time, and its first real mistake would be costly or hard to undo.
Skip it if: You need the workflow itself judged correct; a rehearsal shows what it would do on the records copied, and the wording, pricing, and judgement inside its steps stay yours to settle.
Your first run produces: one rehearsal of the next new workflow you were about to run live: a one-screen brief, dated copies of three records it would really meet (one plain case, one with a missing or odd field, one near a limit), a step-by-step log with every outward and state changing step flagged, and your decision recorded on the log, approved, approved with corrections, or not approved.
Preview, from the skill itself
“# Agent Dry Run Rehearsal<br># Agent Dry Run Rehearsal A new workflow looks safest on the day it is written.”
Version 1.0.09 filesCopies only, until approvalEvery risky step flaggedA failed rehearsal stops the runHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: dc7f40f1c6c7… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 36.5 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-invoice-chase-rehearsal/WALKTHROUGH.md, examples/the-job-file-tidy-rehearsal/WALKTHROUGH.md, reference/copying-records-safely.md, reference/flagging-steps.md, reference/reading-the-rehearsal-log.md, reference/when-a-rehearsal-fails.md, templates/rehearsal-brief.template.md, templates/rehearsal-log.template.md
Worked example, from the package
examples/the-invoice-chase-rehearsal/WALKTHROUGH.md
A small studio is about to hand its overdue invoice chase to a new workflow for the first time. The workflow reads the ledger, picks out overdue invoices, drafts a chase note for each one, sends it, and marks the invoice as chased with a follow up date. Every one of those steps after the reading is outward or state changing, so the first run is a rehearsal on copies, and the live chase waits for the log.
Task Time Estimates
Agent Operations · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Estimates stop being guesses: every task's estimate is written before it starts and its actual time beside it when it ends, so the next estimate for the same work comes from recorded actuals and chronic misses get named.
What changes
- Estimates resetting to the same hopeful number → the next estimate for a kind of work set from what that work actually took, recorded task by task
- A kind that always runs long living as a feeling → chronic misses named in a review, with a count and a total
- Work given more time than it takes, quietly holding space → overestimates surfaced in the same record, so the space can go to other work
Honest fit
For you if: The same kinds of work keep taking longer, or shorter, than the time you plan for them, and nothing is written down to prove it.
Skip it if: You need tasks made faster, people scored, or clients billed from the minutes; the record holds time honestly, and what changes about the work stays your call.
Your first run produces: one time record for a kind of work you do at least twice a week, holding three tasks of that kind with the estimate written before each one starts and the actual beside it when it ends, and a fourth estimate set from those recorded actuals instead of habit.
Preview, from the skill itself
“# Task Time Estimates<br># Task Time Estimates Most work starts with a number nobody wrote down.”
Version 1.0.09 filesEstimate first, in writingEstimate and actual side by sideMisses are facts, not faultsHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 2744db7b1013… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 34.7 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-inbox-that-always-ran-long/WALKTHROUGH.md, examples/the-release-notes-that-came-in-early/WALKTHROUGH.md, reference/estimate-records.md, reference/handling-splits-and-interruptions.md, reference/making-the-next-estimate.md, reference/naming-chronic-misses.md, templates/estimate-review.template.md, templates/time-record.template.md
Worked example, from the package
examples/the-inbox-that-always-ran-long/WALKTHROUGH.md
A solo operator starts each morning with inbox triage and always plans twenty minutes for it. The work always takes longer, the morning always starts late, and the estimate never changes, because nothing was ever written down. Six tasks in one record end that pattern.
Output Format Contracts
Agent Safety and Governance · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Agent handoffs stop breaking two steps later: every handoff format is written down as a contract (fields, order, what must never appear in it), and every output is checked against that contract before anything downstream uses it.
What changes
- A handoff shape each agent remembers differently → one written contract both sides can point to: fields, order, and what must never appear in it
- Missing fields and wrong order surfacing inside downstream work → faults caught at the handoff, named by field and contract line, and fixed at the source
- Forbidden material noticed wherever a reader happens to spot it → forbidden content failing the whole output at the check, before it travels
Honest fit
For you if: Agents hand work to each other, and downstream steps keep breaking on a missing field, a field in the wrong place, or material that should never travel inside a handoff.
Skip it if: You need the content inside a well shaped output checked for truth; this skill checks shape and completeness only, and a passing output can still carry a wrong figure.
Your first run produces: one contract for the handoff that has caused the most rework, written on one screen with its fields in order and its forbidden list, the last real output in that format checked against it by hand with every fault counted and named, and the contract agreed, dated, and filed where both sides of the handoff can read it.
Preview, from the skill itself
“# Output Format Contracts<br># Output Format Contracts Agents hand work to each other and assume the shape.”
Version 1.0.09 filesNo contract, no handoffFaults fixed at the sourceForbidden content fails the outputHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: e5b345ec340e… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 33.5 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-invoice-handoff/WALKTHROUGH.md, examples/the-job-status-handoff/WALKTHROUGH.md, reference/changing-a-contract.md, reference/checking-an-output.md, reference/forbidden-content.md, reference/writing-a-contract.md, templates/conformance-report.template.md, templates/format-contract.template.md
Worked example, from the package
examples/the-invoice-handoff/WALKTHROUGH.md
A drafting agent prepares invoice figures and hands them to a sending agent, which builds the client invoice from them. The first handoff under the new contract is held with three faults. The fixed handoff passes a full recheck. All figures in this walkthrough are internal example figures, used only to show the check working.
Vendor and Tool Renewals
Studio / Shipping · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
No renewal lands as a surprise charge: every subscription and tool sits in one record with its renewal date, its price, and last time's price beside it, and the keep-or-drop call is recorded before the money goes.
What changes
- Renewals met one at a time, after the charge → every paid item in one record with its renewal date and its price this time beside last time
- A price rise found months after it started → a rise seen at the first renewal where it appears, in figures, at the monthly review
- A tool nobody uses renewing because ending it was never decided → the keep-or-drop call recorded before the money goes, while the notice period is still open
Honest fit
For you if: Subscriptions and tools renew across the year, and nobody can say from one record what the studio pays for, when, or at what price.
Skip it if: You need bills paid, plans changed, or prices negotiated; the skill keeps the record and prepares the call, and approving and acting stay yours.
Your first run produces: one renewal record holding every subscription, tool, and service the studio pays for, built from billing sources rather than memory, each item with its renewal date and its price this time and last time or its gap named, and a keep-or-drop call with a reason beside every item due in the next sixty days, with that window's total written at the top.
Preview, from the skill itself
“# Vendor and Tool Renewals<br># Vendor and Tool Renewals A studio pays for its tools one quiet charge at a time.”
Version 1.0.09 filesOne record for every renewalTwo prices, side by sideThe call comes before the chargeHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: de5189866fd4… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 40.9 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-look-ahead-review.md, examples/the-price-rise-call.md, reference/review-rhythm-and-alerts.md, reference/sources-prices-and-terms.md, reference/the-keep-or-drop-call.md, reference/the-renewal-record.md, templates/renewal-record.template.md, templates/renewal-review.template.md
Worked example, from the package
examples/the-look-ahead-review.md
A small studio keeps one renewal record with 7 active entries. The monthly review runs on March 3. Its window is March 3 to May 2, the next sixty days. Four items fall due in the window. The other 3 renew after the window: a hosting plan on June 16, a backup service on June 20, and an accounting tool on September 5. They are listed by date only.
Doc Drift Checks
Studio / Publishing · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Your published docs stop quietly going stale: on a schedule, every claim in a guide or README is traced to the shipped build, drift is logged with the exact line it lives on, and each drifted line is fixed or cut.
What changes
- A doc corrected late, in the one place a reader named → every claim in the doc traced to the shipped build on a schedule, not only the lines someone complained about
- Drift found by readers one painful line at a time → drift logged with the exact line it lives on, in batches small enough to fix the same week
- Lines describing the product as it was, written with full confidence → each drifted line fixed or cut, so a reader at the screen can trust the line in front of them
Honest fit
For you if: Published guides or READMEs were true when written, and the product has shipped changes since.
Skip it if: You need a guide written in the first place, or the product itself fixed; the check starts from a published doc and hands over a checked packet, and publishing the correction stays yours.
Your first run produces: one claim inventory for the published guide or README your readers open most, with the first ten claims traced against the current build and marked holds or drifted, every drifted claim logged with its line, the doc's words, and the build's words, and one fix drafted in the doc's own style and held for the operator.
Preview, from the skill itself
“# Doc Drift Checks<br># Doc Drift Checks A published guide does not go wrong all at once.”
Version 1.0.09 filesThe shipped build is the sourceEvery claim, not the suspicious onesFix or cut, nothing stays driftedHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: a35b95fb113f… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 44.3 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/guide-drift-after-release/WALKTHROUGH.md, examples/readme-drift-after-rename/WALKTHROUGH.md, reference/claim-inventory-and-tracing.md, reference/drift-kinds-and-severity.md, reference/fix-or-cut-decisions.md, reference/scheduling-and-baselines.md, templates/claim-inventory.template.md, templates/drift-log.template.md
Worked example, from the package
examples/guide-drift-after-release/WALKTHROUGH.md
A small invoicing tool, LedgerPad, ships a new build. Its published Getting Started guide was true at publication. A release triggered check traces all 36 of its claims against the new build and finds 6 drifted, spread across the guide, in a release whose notes mentioned only one of them.
PDF Form Filling
Data, Files, and Research · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Forms stop carrying figures from memory: every field is mapped to a named record before filling, values come from that record only, a check pass reads the filled copy back against the records, and the submitted copy is kept with its date.
What changes
- Form values carried from memory → every field mapped to a named record before filling, and values copied from that record only
- Errors found by the receiving office weeks later → a check pass reading the filled copy back against the records while the form is still in hand
- A required field with no source left as a quiet blank → gaps named before submission for the operator to settle, and the submitted copy kept with its date
Honest fit
For you if: Forms get filled from memory, and the figures on them cannot be traced to a record afterwards.
Skip it if: You need answers chosen, a signature applied, or advice on what a form means; the skill marks those fields for you and fills only from the records in the mapping.
Your first run produces: one field mapping for the short form that is waiting right now, one row per field naming the record and the place in it, a working copy filled from that mapping with values copied exactly, and a check pass read back against the records, with the filled copy, the check result, and any gaps shown to the operator before anything is submitted.
Preview, from the skill itself
“# PDF Form Filling<br># PDF Form Filling A blank form asks questions the operator's records can usually answer.”
Version 1.0.09 filesThe mapping comes before the fillingA blank with no source stays blankA check pass before approvalHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 3be693493d71… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 40.2 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/event-permit-application.md, examples/vendor-registration-form.md, reference/field-mapping.md, reference/keeping-the-submitted-copy.md, reference/reading-the-records.md, reference/the-check-pass.md, templates/field-mapping.template.md, templates/submission-record.template.md
Worked example, from the package
examples/event-permit-application.md
A makers group applies to the city for a one day market in a public park. The permit form is two pages and nine fields, the facts live in three short records the group keeps, and the check pass earns its place by catching the event date typed one day early, a mistake the site letter confirms as a mistake.
Delivery and Dropoff Runs
Local Services / Field Operations · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A missed delivery stops being an argument: the day is planned from the job records with load order and stop order written down, a customer message drafted per stop, and a proof-of-drop note at every stop, so any miss traces to the plan or the road.
What changes
- A delivery day living in the driver's head → one plan written before loading starts, with stop order and load order set down and checked against each other
- Customers told late or not at all → one draft message per stop, written from the plan line for that stop
- A missed delivery argued from memory at the end of the day → a proof-of-drop note at every stop, so the miss traces to the plan or the road
Honest fit
For you if: Delivery days are planned in the driver's head, and a missed drop turns into an argument from memory.
Skip it if: You need the driving, loading, or dropping done, or messages sent; the skill plans the day and writes the proof record, and the road work stays yours.
Your first run produces: one run plan for the next delivery day on the books, built from the job records only: each stop with what it is owed, its address, and any drop note, gaps flagged in plain words, the stop order set and the load order set in reverse, and one draft message per stop held for the operator, with nothing sent and nothing loaded.
Preview, from the skill itself
“# Delivery and Dropoff Runs<br># Delivery and Dropoff Runs A delivery day goes wrong in quiet ways.”
Version 1.0.09 filesLoad order serves stop orderOne message per stopThe day closes against the planHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: b88031f6da78… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 29.5 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/five-stop-round-missed-delivery/WALKTHROUGH.md, examples/six-stop-firewood-round/WALKTHROUGH.md, reference/customer-messages-per-stop.md, reference/load-order-and-stop-order.md, reference/proof-of-drop-and-tracing.md, reference/reading-the-job-records.md, templates/proof-of-drop-log.template.md, templates/run-plan.template.md
Worked example, from the package
examples/five-stop-round-missed-delivery/WALKTHROUGH.md
An operator delivering bagged mulch and bagged compost to garden customers in one loop. Five stops are booked for the day, all bagged, all able to ride in one pickup load with the piles kept apart by count. One stop is not delivered, and the day is closed by tracing that miss to the road, not to the plan.
Rental and Borrowed Gear Log
Local Services / Field Operations · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Returns and damage questions get a record instead of an argument: every rented or borrowed item logged with what it is, whose it is, the deposit and due-back date, and its condition noted out and back with photos from the job record.
What changes
- A due-back date on a slip in a truck and a deposit nobody wrote down → one log holding every rented or borrowed item, its owner, its deposit, and its due-back date
- Condition as what each side recalls at the yard gate → condition out and condition back in the same entry, each with its photo set from the job record
- A damage question turning into two memories disagreeing → the question starting from dated notes and receipts the operator can show
Honest fit
For you if: Rented or borrowed gear is out on jobs, and its deposits, due-back dates, and condition live on slips and in memory.
Skip it if: You need gear booked, deposits paid, or damage decided; the log lays out the notes, photos, and receipts, and settling the question stays with you and the owner.
Your first run produces: one gear log holding every item the business has out right now that it does not own, rented, hired, or borrowed: what it is, whose it is, the deposit and due-back date from the paperwork or agreement or an honest none or unknown, and its condition as it stands today, marked as a mid hire note where the gear came in before the log started.
Preview, from the skill itself
“# Rental and Borrowed Gear Log<br># Rental and Borrowed Gear Log Gear that is not yours still has to go back.”
Version 1.0.09 filesOne log for rented and borrowedCondition out before the gear worksDue back is a hard dateHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 6ae5651d82ca… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 36.4 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/borrowed-scaffold-tower-house-job.md, examples/rented-mini-excavator-drainage-job.md, reference/check-out-and-condition-notes.md, reference/deposits-due-dates-and-fees.md, reference/gear-log-fields.md, reference/return-check-and-damage-questions.md, templates/check-out-return-entry.template.md, templates/gear-log.template.md
Worked example, from the package
examples/borrowed-scaffold-tower-house-job.md
A painter and exterior repair operator needs a scaffold tower and a long ladder for a two storey house job. A neighbouring roofer the operator has worked beside for years lends both for the week. There is no rental firm and no hire paperwork. The gear is not owned by the operator, so it goes in this log on the same terms as rented gear, with the loan terms as agreed written in place of paperwork.
Receipts Reconciliation
Local Services / Money · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
The week's money in is proven, not assumed: cash, Cash App, and card receipts matched line by line against the job records, every gap named against the job it belongs to, and nothing written off without your recorded decision.
What changes
- The week's money as a feeling and a bank balance → each week closing with a match that can be read in minutes, job line against payment line
- A missed payment hiding behind a good week → every job shown as paid, part paid with the gap named, or unpaid with the gap named, within days
- A gap dropped because it was small, or written off quietly → nothing leaving the record without the operator's recorded decision
Honest fit
For you if: A week's jobs are done, and whether every one of them was paid in full is a feeling rather than a match.
Skip it if: You need bookkeeping or tax advice, money moved, or a week judged profitable; the sheet matches money in against the job records and presents nothing as profit.
Your first run produces: one reconciliation sheet for the last finished week: the expected list built from the job records alone and totalled before any payment record is opened, then cash, Cash App, and card lines matched against it, ending with the expected total, the matched total, and a gap list where every gap names its job, held for the operator to read.
Preview, from the skill itself
“# Receipts Reconciliation<br># Receipts Reconciliation At the end of a busy week, an operator can know the work was done and still not know whether they were paid for all of it.”
Version 1.0.09 filesThe expected list comes firstEvery gap is named with its jobNothing written off silentlyHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 90dd40283505… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 33.7 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/five-jobs-one-short-payment.md, examples/split-payments-fees-and-one-unknown.md, reference/gaps-named-never-written-off.md, reference/matching-line-by-line.md, reference/reading-payment-records.md, reference/the-job-record-baseline.md, templates/gap-note.template.md, templates/weekly-reconciliation-sheet.template.md
Worked example, from the package
examples/five-jobs-one-short-payment.md
A local operator closes a week with five jobs on the records: gutter work, a fence repair, a yard cleanup, a limb removal, and a driveway wash. Payment came in by cash, Cash App, and card across the week. This walkthrough is the weekly reconciliation for that week.
Referral Partner List
Local Services / Marketing · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Business-to-business referrals stop depending on memory: one working list of who sends what kind of work, what has been sent each way, the thank-you kept current, and one nudge drafted when a good partner has gone quiet.
What changes
- The partner trade living in the operator's head and old threads → one list answering who sends what, what has been sent each way, and whose thank-you is owed
- A thank-you depending on remembering on a busy day → the thank-you kept current on the list, owed on the passing, not the outcome
- A partner who stops sending noticed only when work runs thin → one nudge drafted while the relationship is still warm, and never a chase past that one nudge
Honest fit
For you if: Work already moves between your business and others, and who sent what, and who is owed a thank-you, lives in your head and old threads.
Skip it if: You need new partners found, customers asked for referrals, or thank-yous and nudges sent; the list records the trade between businesses, and sending stays yours.
Your first run produces: one partner list built from the last season of job records, one entry per business the operator really traded a referral with, each entry holding the fit in both directions and a tally that traces to logged lines or is marked as starting today, the quiet window in the list header, and one plainly owed thank-you drafted and held for the operator, with nothing sent.
Preview, from the skill itself
“# Referral Partner List<br># Referral Partner List Most local operators already trade work with other local businesses.”
Version 1.0.09 filesOne list, one entry per businessA referral counts only when it is realQuiet earns one nudge, never a chaseHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: e8150d6938e8… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 38.8 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/cleaner-agent-circle-and-a-quiet-partner/WALKTHROUGH.md, examples/roofer-plumber-two-way-trade/WALKTHROUGH.md, reference/thank-yous-that-stay-current.md, reference/the-partner-list.md, reference/what-counts-as-a-referral.md, reference/when-a-partner-goes-quiet.md, templates/nudge-and-thank-you.template.md, templates/partner-entry.template.md
Worked example, from the package
examples/cleaner-agent-circle-and-a-quiet-partner/WALKTHROUGH.md
A cleaning operator who does move out cleans, end of tenancy cleans, and pre sale cleans. The trade runs in a small circle: a letting agent, a removals firm, a window cleaning firm, and a plumbing and heating firm whose landlord work used to swap steadily with hers. A review covers twelve weeks, early February to late April.
Live Session Prep
Creator and Audience · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A live session starts planned instead of improvised: the run order written from your real work, the setup checked before you go live, and the list of clips and follow-ups made before the session ends, not from memory after.
What changes
- A session improvised at the start → a written run order: each block named, timed, and traced to real work, with the total checked against the planned length
- Setup faults found live, in front of the audience → the setup checked before the session, with faults found while there was still time to fix them or move the day
- Clips and follow-ups rebuilt from memory after the session → both listed before the session ends, clips with times from the session as it ran and follow-ups in the words used live
Honest fit
For you if: Live sessions start improvised, and the clips and follow-ups get rebuilt from memory after they end.
Skip it if: You need the session hosted, recorded, or edited, or content invented to fill it; the plan is built from real work only, and a shortfall means a shorter session, not a padded one.
Your first run produces: one complete session plan for the next live session already on the calendar: a brief taken from the creator's real work, a run order whose block times add up to the planned length, a clip and follow-up list drafted from that run order, and a setup check with every line marked, all held for the creator with nothing announced.
Preview, from the skill itself
“# Live Session Prep<br># Live Session Prep A live session goes better when it is planned while there is still time to fix things.”
Version 1.0.09 filesEverything shown comes from real workThe setup is checked, not assumedClips listed before the endHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: e1ff5d1a1a51… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 33.1 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/sketching-tutorial-live/WALKTHROUGH.md, examples/workshop-demo-live/WALKTHROUGH.md, reference/planning-clips-and-follow-ups.md, reference/the-setup-check.md, reference/working-from-real-work.md, reference/writing-the-run-order.md, templates/session-plan.template.md, templates/setup-check.template.md
Worked example, from the package
examples/sketching-tutorial-live/WALKTHROUGH.md
An artist runs a live tutorial drawn from their own sketchbook work: one half finished drawing of a kitchen chair, made by the artist in the week before the session, is shaded and finished live while beginners follow the steps. The drawing is the real work. A fresh page sits beside it for the first sketch step, so the half finished piece is not touched until its block.
Model and Tool Swap Checks
Agent Operations · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A model or tool change stops shipping silent surprises: one fixed set of standard tasks runs on the old setup and the new one before anything goes live, every difference is named in plain words, and the rollback note is already written if the swap has to come back out.
What changes
- A model or tool swap goes live on a release note and a hope → the fixed task set runs on the old setup and the new one first, and every difference is named in plain words before go live
- A behaviour change found later, in real work → substance differences judged against the reason for the swap, expected or unexpected, with the decision recorded
- A fault after go live means reconstructing the old setup under pressure → the rollback note is written before go live, naming the old setup in full and where it is restored from
Honest fit
For you if: You run an agent whose model or a tool it relies on is about to change, and a silent behaviour change would be found late, in real work.
Skip it if: You need the new model or tool chosen for you, differences fixed, or a setup proven correct in general; the task set shows behaviour on its tasks only, and choosing and fixing stay with you.
Your first run produces: one fixed task set for the agent most likely to change next: 8 to 12 real tasks with their inputs written in full, the current setup named in full as the standing baseline, one kept baseline run of the set on that setup, and a one sentence rollback note that can be carried out.
Preview, from the skill itself
“# Model and Tool Swap Checks<br># Model and Tool Swap Checks An agent is only partly its instructions.”
Version 1.0.09 filesOne change at a timeDifferences in plain wordsRollback note before go liveHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 68814a48c0cc… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 41.6 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-model-upgrade/WALKTHROUGH.md, examples/the-search-tool-change/WALKTHROUGH.md, reference/reading-the-differences.md, reference/rollback-note-and-restore.md, reference/the-standard-task-set.md, reference/the-swap-record.md, templates/rollback-note.template.md, templates/swap-check.template.md
Worked example, from the package
examples/the-model-upgrade/WALKTHROUGH.md
A solo operator runs an inbox triage agent that labels each incoming message, holds or passes each one on, and drafts a short summary line for the held ones. A newer model is offered for the agent. The fixed task set is run on both models before anything goes live. The comparison finds three substance differences, one of them a fault, and the swap is held the same day, with the old model still live throughout.
Standing Instructions Review
Agent Operations · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Standing instructions stop quietly going stale: on a schedule you set, every rule is checked against the record of what actually happened and marked holding, stale, in conflict, or without evidence, with any change drafted for your approval and nothing edited silently.
What changes
- A slow sense that the agent is a little off → a marked sheet: each rule holding, stale, in conflict, or without evidence, with the evidence attached
- Two rules answering one situation two ways, chosen run by run → conflicts named as a pair with the split runs counted, so you choose the answer once, in the wording
- Wording changed on a feeling → every change drafted one rule at a time with its before and after wording, and nothing edited without your approval
Honest fit
For you if: Your agent's standing instructions were written for an older setup and have not been read against the run record in a while.
Skip it if: You need version history for instruction changes, new instructions written from nothing, or the agent graded as a whole; this review marks and drafts, and you approve before any wording changes.
Your first run produces: one review sheet for the agent whose instructions you have read least recently: the full instruction text copied exactly as it stands, each rule marked holds, stale, in conflict, or no evidence against the last two to four weeks of record, change drafts for the findings that call for them, and the next review date set before the sheet closes.
Preview, from the skill itself
“# Standing Instructions Review<br># Standing Instructions Review Standing instructions are written at one moment, for the setup as it stood at that moment.”
Version 1.0.09 filesEvery rule marked against the recordChanges drafted one rule at a timeNothing edited silentlyHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: caa3e32f92e9… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 44.5 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-conflicting-reply-rules/WALKTHROUGH.md, examples/the-stale-hold-rule/WALKTHROUGH.md, reference/drafting-the-change.md, reference/finding-staleness-and-conflict.md, reference/reading-the-run-record.md, reference/review-record.md, templates/change-draft.template.md, templates/review-sheet.template.md
Worked example, from the package
examples/the-conflicting-reply-rules/WALKTHROUGH.md
A small shop runs a customer message agent that answers routine questions on its own and holds the rest for the operator. Two standing rules each read plainly on their own. Together they give two answers to the same message, and the run record shows the agent splitting between them for three weeks. The review names the pair, counts the split, and carries the operator choice back into the wording itself.
Data Retention Schedule
Agent Safety and Governance · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Records stop being kept forever by default: every record type gets a written keep period and review date, and the deletion pass actually runs on schedule, under its own approval, with every pass logged, so what is kept and when it last went can always be answered.
What changes
- Records kept forever by default → every record type carrying a keep period you chose and a review date, or an honest line that says not yet set
- Old records going by habit or in a clear out nobody noted → deletions run in a pass, on a list, under approval, with every pass logged
- How long do we keep this answered from memory → a schedule lookup: the period and review date on the schedule, what went and when in the log
Honest fit
For you if: Your records are kept forever by default and nobody can say how long each type should stay or when it last went.
Skip it if: You need day to day data handling rules, consent tracking, or the keep periods chosen for you; the periods are your decision, and no pass runs without your approval.
Your first run produces: one starting schedule for the store where old records pile up most: every record type listed in plain words, each counted from the store itself today, a keep period per type or an honest not yet set, a review date per type, and the schedule read back against the store; no pass runs on a first run.
Preview, from the skill itself
“# Data Retention Schedule<br># Data Retention Schedule Records do not age out on their own.”
Version 1.0.09 filesEvery type gets a periodEvery pass loggedDeletion under approvalHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 1a335c91f371… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 33.4 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/first-schedule-cleanup/WALKTHROUGH.md, examples/quarterly-deletion-pass/WALKTHROUGH.md, reference/deletion-pass-procedure.md, reference/record-types-and-periods.md, reference/retention-schedule-record.md, reference/review-and-logging.md, templates/deletion-pass-log.template.md, templates/retention-schedule.template.md
Worked example, from the package
examples/first-schedule-cleanup/WALKTHROUGH.md
A solo operator keeps the records of a small briefing service in one store: task logs, draft briefings, exported reports, and intake notes. Nothing has a stated end. The first schedule lists the four types, sets a period and a review date for each, and the first deletion pass takes only what the first check found past its period, on a list the operator approved, and the pass is logged.
Public Corrections Log
Studio / Publishing · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A published mistake stops being a quiet edit nobody can trace: the original is fixed in place, then one plain-words log entry per correction is published and kept, saying what was wrong, what it says now, and where it was fixed.
What changes
- A published mistake fixed quietly, or not at all → the original fixed in place and one plain words log entry published per correction, saying what was wrong and what it says now
- Past fixes argued from memory months later → a dated entry quoting the wrong wording and the new wording, where any reader can check it
- The same slip made twice, invisibly → the log read as a whole shows repeat errors as a pattern, so the source can be fixed
Honest fit
For you if: Your studio publishes in public and wants a settled, provable way to handle the mistakes that will sooner or later stand in it.
Skip it if: You need the right fact decided for you, apologies or client statements written, or private complaints tracked; the log covers errors that stood in public, and every entry waits for your approval.
Your first run produces: one public corrections log set up before the next error needs it: one public place a reader can reach in one step, a dated heading in plain words, a link from the places readers already land, the entry shape ready, and one practice entry only if a past fix can be proved from records.
Preview, from the skill itself
“# Public Corrections Log<br># Public Corrections Log Every studio publishes something wrong sooner or later.”
Version 1.0.09 filesOne correction, one entryFix the original, then log itNo quiet fixesHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 435d9ec37ec1… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 37.1 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-wrong-date/WALKTHROUGH.md, examples/the-wrong-price/WALKTHROUGH.md, reference/the-log-itself.md, reference/verifying-the-fix.md, reference/where-the-log-lives.md, reference/writing-the-correction.md, templates/correction-entry.template.md, templates/published-correction-note.template.md
Worked example, from the package
examples/the-wrong-date/WALKTHROUGH.md
A small studio announces a live demo session in a post, on its schedule page, and in a short notice. All three carry a date typed from memory, one week early. The booking record holds the right date. All three places are fixed, and one log entry covers the correction, with a short note placed where the format allows one.
Archive and Sunset Products
Studio / Shipping · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Retiring a product or a version stops being a mess: the decision and stop date are recorded, the sunset notice is drafted and held for your approval, what keeps working and until when is stated plainly, the records are exported and checked before anything stops, and the stop date is honored exactly.
What changes
- A product ending lands as a surprise → one approved notice naming the stop date and what keeps working and until when, in plain words
- Records lost when the lights go out → the records exported and opened and counted while the product still runs, so a short export is found in week one
- A stop date that drifts or lands early → the date honored exactly, with any change needing a new notice and a new approval
Honest fit
For you if: You have a product or a version in mind to retire and do not want its ending reconstructed from memory later.
Skip it if: You need the retirement decided for you, a replacement named or priced, or users moved to one; this skill runs a decision honestly once you have made it.
Your first run produces: one sunset record for the product or version you have in mind to retire: the product named as its users know it, the decision written in your own words with its reason, every part of the product listed with what it does, and one sentence naming where its records would be exported to; nothing is stopped and nothing outward facing is drafted.
Preview, from the skill itself
“# Archive and Sunset Products<br># Archive and Sunset Products Every product ends, and every version is one day replaced.”
Version 1.0.09 filesThe decision comes firstThe stop date is honoredExports checked before anything stopsHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 0306a635698e… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 42.5 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/the-clean-retirement/WALKTHROUGH.md, examples/the-version-sunset/WALKTHROUGH.md, reference/export-and-retention-checklist.md, reference/sunset-record.md, reference/the-stop-date-and-final-shutdown.md, reference/writing-the-sunset-notice.md, templates/sunset-notice.template.md, templates/sunset-record.template.md
Worked example, from the package
examples/the-clean-retirement/WALKTHROUGH.md
A solo operator retires a small studio tool in full. The decision, the parts, and the dates are recorded first. The first export check falls short and is fixed while the tool still runs. The notice is approved before it goes out, the stop date holds, and the close is written into the record the day the last part stops.
Spreadsheet to Report
Data, Files, and Research · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A spreadsheet becomes a report a reader can act on: every figure in the prose is traced to the sheet's own cells, every total is recomputed from those cells instead of copied, and anything the sheet does not support is left out or named as missing.
What changes
- A wrong total in the sheet copied into prose and carried further → every total in the report recomputed from the source cells, and a wrong total cell named at the tracing step
- A figure questioned and answered from recollection → every figure carrying a trace line with its cells and arithmetic
- Claims the sheet cannot support written in anyway → what the sheet does not hold named as missing, so the report stays shorter, plainer, and checkable
Honest fit
For you if: You hold figures in a sheet and need a written report a reader can act on, with every figure answerable to its cells.
Skip it if: You need the sheet tidied or repaired, new data gathered, or the business behind the numbers judged; the report uses only what the sheet supports and names the rest as missing.
Your first run produces: one short report from a small sheet you already trust: the sheet named with its period and source, three figures traced to their cells with the total and the difference recomputed, a draft that uses only those figures, one gap the sheet does not hold named plainly, and the draft and trace held for the operator's check.
Preview, from the skill itself
“# Spreadsheet to Report<br># Spreadsheet to Report A spreadsheet holds numbers.”
Version 1.0.09 filesEvery figure tracedTotals recomputed, not copiedGaps named as missingHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: f82a3a3e5263… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 33.7 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/project-costs-summary/WALKTHROUGH.md, examples/quarterly-sales-summary/WALKTHROUGH.md, reference/checking-the-report.md, reference/reading-the-sheet.md, reference/tracing-and-recomputing.md, reference/writing-the-report.md, templates/figure-trace.template.md, templates/report-outline.template.md
Worked example, from the package
examples/project-costs-summary/WALKTHROUGH.md
A builder finishes a small job and needs a written cost summary for the customer: what was budgeted, what was spent, and where the two differ. The figures sit in one sheet with a budget column and an actual column. The report is built by tracing each line and recomputing both totals and every difference, and it leaves out the one point the sheet cannot carry.
Tool and Material Staging
Local Services / Field Operations · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Tomorrow's tools and materials get staged tonight in job order, with every gap flagged and filled while the shops are still open, so the morning starts with driving to the first job instead of fetching.
What changes
- The next day living in the operator's head, with gaps found at the first address → one staging sheet the evening before: every job in run order, every tool and material line counted against the truck and the bench
- A missing item costing a run back or a wait for a shop to open → every gap flagged and filled while the shops are still open, or carried open with a stated plan
- The truck loaded in no particular order → the load put on in job order, so the morning starts with driving to the first job instead of fetching
Honest fit
For you if: Your mornings start with fetching because tomorrow's tools and materials were never checked against the truck the night before.
Skip it if: You need the job site itself checked, materials or quantities chosen, or stock tracked across weeks; staging covers what the crew carries, and buying stays with you.
Your first run produces: one staging sheet for a real next day, built the evening before at the truck and the bench: one block per job in run order with the tools and materials each job needs, every line marked on hand, bought, found, or carried open with a stated plan, gaps on a buy list while the shops are still open, and the load put on in job order.
Preview, from the skill itself
“# Tool and Material Staging<br># Tool and Material Staging Most lost mornings are lost the night before.”
Version 1.0.09 filesStaged the night beforeGaps flagged while shops are openLoaded in job orderHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 46db52eb08b8… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 34.7 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/roof-and-bathroom-staging/WALKTHROUGH.md, examples/three-job-tuesday-staging/WALKTHROUGH.md, reference/bench-check-and-close-out.md, reference/building-the-staging-list.md, reference/flagging-and-filling-gaps.md, reference/loading-in-job-order.md, templates/gap-and-buy-list.template.md, templates/staging-sheet.template.md
Worked example, from the package
examples/roof-and-bathroom-staging/WALKTHROUGH.md
A Wednesday with two jobs, staged on the Tuesday evening before. The job records list a roof valley repair first, in the morning, and a bathroom reseal second, in the afternoon. This walkthrough shows a staging that ends honestly short on one line, with the gap carried open on a stated plan, so the day still starts on time and nobody is surprised at the first address.
End of Day Job Log
Local Services / Field Operations · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Every job gets closed out the same day in one log, with what was done, what is left, the photos filed against the job, and the customer's next step noted, so tomorrow starts from the log instead of from memory.
What changes
- The day ending in the van and in the operator's head → one log per day: every job touched, with what was done and what is left in writing
- Photos from three jobs sitting in one camera roll with no job named → the day's photos filed against their job and counted on the entry
- A customer's next step held differently by each side → the next step noted on the entry, so tomorrow starts from the log instead of from memory
Honest fit
For you if: Your days touch more than one job and end fast, so what was done and what is left lives in your head by morning.
Skip it if: You need the final handover for a finished job, prices or pay worked out, or customer notes sent; the daily log is the closeout record, and the handover is a separate skill.
Your first run produces: one daily log for a real working day: every job touched that day listed from the job records, an entry per job with what was done and what is left, the day's photos filed against their jobs and counted, a next step on every entry, and the header hours and photo counts agreeing with the entries, read by the operator before it is filed.
Preview, from the skill itself
“# End of Day Job Log<br># End of Day Job Log A working day touches more than one job, and it ends fast.”
Version 1.0.09 filesClosed out the same dayDone and left both writtenPhotos filed against the jobHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: c8fdb2f3db97… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 32.2 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/deck-rebuild-day-two/WALKTHROUGH.md, examples/three-job-cleanup-day/WALKTHROUGH.md, reference/building-the-daily-log.md, reference/filing-the-days-photos.md, reference/next-steps-and-tomorrow-start.md, reference/what-was-done-and-what-is-left.md, templates/daily-job-log.template.md, templates/job-closeout-entry.template.md
Worked example, from the package
examples/deck-rebuild-day-two/WALKTHROUGH.md
A deck rebuild planned over 3 days. This walkthrough is the daily log for day 2 only. One job was touched that day, and it is still in progress at the end of day 2, so the log lists 1 job: 0 finished that day and 1 still in progress, and the 0 plus the 1 adds to the 1 job logged. Hours on the job on day 2 are 6.5 hours. Photos filed on day 2 are 7 photos. This is a daily closeout for a job in progress. It is not a handover, and no handover step is taken in it.
Gift Card and Credit Tracking
Local Services / Money · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Every gift card, rain check, and store credit sits in one record, issued to whom, with its balance worked out redemption by redemption, so a credit is honored from the record and never argued from memory.
What changes
- Credits owed scattered across a job sheet, a rain check, and memory → every gift card, rain check, and store credit in one record, issued to a named holder with its amount and expiry
- A returning customer and the operator holding two honest, different balances → every redemption logged, with each balance following from the line above it
- What is owed argued at the counter → what is owed shown line by line, by either side, on any later day
Honest fit
For you if: You issue gift cards, rain checks, or store credit and balances get argued from memory at the counter.
Skip it if: You need prices, credit amounts, or expiry terms set for you, payment taken, or legal advice on credit rules; the record holds the terms you set, exactly as set.
Your first run produces: one credit record started with the next credit you issue: the holder, the kind of credit, the amount issued, the date, and the expiry term you set, written down at the counter while both sides hold the facts, with a redemption log opened and a balance that follows from the entry itself.
Preview, from the skill itself
“# Gift Card and Credit Tracking<br># Gift Card and Credit Tracking A credit owed to a customer is easy to lose.”
Version 1.0.09 filesOne credit, one recordBalances line by lineHonored from the recordHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 9a2b0eec87f0… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 29.1 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/gift-card-full-redemption/WALKTHROUGH.md, examples/store-credit-and-rain-check/WALKTHROUGH.md, reference/expiry-and-disputes.md, reference/issuing-a-credit.md, reference/redeeming-and-balances.md, reference/the-credit-record.md, templates/credit-record.template.md, templates/redemption-log.template.md
Worked example, from the package
examples/gift-card-full-redemption/WALKTHROUGH.md
A gift card for a cleaning service, bought as a gift and spent over three visits. The record holds one credit only, reference GC-014, issued for $120.00. Every figure in this walkthrough comes from that one entry, and the balances follow line by line. This walkthrough shows the full life of the credit, from issue to a closing balance of zero.
Review Response Drafts
Local Services / Marketing · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Public reviews get answered from the record instead of in a hurry: each review read in full, every point checked against the job's own facts, the reply drafted without inventing anything, and every draft held for your approval before it is posted.
What changes
- A reply typed at the end of a long day, from memory and mood → the review read in full, each point listed and checked against the job record before a word is drafted
- Warm reviews adding facts nobody checked, hard reviews owning things the job never did → a draft that uses only record facts, with gaps shown to you rather than filled in
- A reply posted in the heat of the moment → no word posted until you have read the draft and given the go ahead
Honest fit
For you if: Public reviews of your work need answers, and replies typed in a hurry from memory keep adding facts nobody checked.
Skip it if: You need reviews asked for, replies posted for you, or a dispute settled; every draft here is checked against the job record and waits for your approval before it posts.
Your first run produces: one review response draft for the next review that arrives: the full review text opened with its rating and date as shown, each point in it checked against the job record or marked as a gap, a draft using only record facts, and the draft held with its check log for your decision to post, edit, or leave it unposted.
Preview, from the skill itself
“# Review Response Drafts<br># Review Response Drafts A public review sits where the next customer will read it, and a reply written in a hurry can do more harm than the review itself.”
Version 1.0.09 filesChecked against the job recordDrafts held for approvalNothing inventedHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: e7b9b270f8a4… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 31.7 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/hard-fence-repair-review/WALKTHROUGH.md, examples/positive-yard-cleanup-review/WALKTHROUGH.md, reference/checking-against-the-job-record.md, reference/drafting-from-the-record.md, reference/hard-reviews-and-approval.md, reference/reading-the-review-in-full.md, templates/review-check-log.template.md, templates/review-response-draft.template.md
Worked example, from the package
examples/hard-fence-repair-review/WALKTHROUGH.md
This is a fictional worked example. The review text, the names, and the figures are made up for this example, and they tie to each other only inside it.
Thumbnail and Title Tests
Creator and Audience · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Title and thumbnail picks stop being last-minute guesses: variants are written down before publishing, the pick is reviewed after a set window against the video's own numbers, and the outcome is logged so the next choice starts from what the record shows.
What changes
- The title and thumbnail picked at the door, the reason gone in a day → variants written down before publishing, with the pick and its reason on a dated sheet
- A past video remembered as doing well or badly with no figures attached → the pick reviewed after a set window against the video's own impressions, clicks, and rate
- Strong results remembered and weak ones forgotten → both logged the same way, so the next choice starts from what the record shows
Honest fit
For you if: Your title and thumbnail picks happen in the last minutes before publishing and the reasons are gone by the next video.
Skip it if: You need growth promised, figures from other channels used as targets, or videos published for you; the log works only from your own channel's record.
Your first run produces: one variant sheet for the next video you have not published yet: a test log started from your channel's own record, the title and thumbnail variants for the new video written down before publishing, the pick and its reason noted from the log, the review window set on the sheet, and the pick approved by you before anything goes out.
Preview, from the skill itself
“# Thumbnail and Title Tests<br># Thumbnail and Title Tests A title and a thumbnail get picked in a hurry, often in the last ten minutes before a video goes out.”
Version 1.0.09 filesVariants written before publishingReviewed against the video's own numbersWeak results logged tooHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 7cb3a7c0a94b… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 38.9 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/three-dinners-from-one-chicken/WALKTHROUGH.md, examples/workbench-from-reclaimed-timber/WALKTHROUGH.md, reference/reading-the-review-window.md, reference/the-test-log.md, reference/what-the-record-can-and-cannot-show.md, reference/writing-variants-before-publishing.md, templates/review-log.template.md, templates/variant-sheet.template.md
Worked example, from the package
examples/three-dinners-from-one-chicken/WALKTHROUGH.md
This is a fictional channel and a fictional video, shown to walk the workflow through in full, including a result that comes in below the channel's past entry. Mara Cooks Small is a small cooking channel. All figures below are that channel's own internal record for the purpose of this example, and each rate is worked from the impressions and clicks on its own line. No figure here comes from another channel and none is presented as typical for any platform.
Podcast Guest Pipeline
Creator and Audience · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Guests run as a pipeline instead of a scramble: prospects drawn from your own network and past episodes, tracked by stage, outreach drafted and held for your approval, a prep sheet built from the guest's public work, and follow-up and clip delivery logged until they are done.
What changes
- A booking carried in the operator's head and scattered notes → one pipeline record per guest: prospect, source, stage, outreach, prep, and close
- Outreach sent from memory, or twice → outreach drafted from the record and held for your approval, and sent by you
- Clips and follow-up promised and then lost → follow-up and clip delivery logged until they are done, and a prep sheet built from the guest's public work
Honest fit
For you if: Your guest bookings live in a scramble of mentions, memory, and untracked promises of follow-up and clips.
Skip it if: You need outreach sent for you, contact details found for strangers, or episodes edited and published; prospects come from your own network and past episodes, and you send every message yourself.
Your first run produces: one pipeline record for the next guest you plan to invite: one prospect from your own network or a past episode with the source written in plain words, the outreach drafted and held for your approval and sent by you, the sent date logged, and a prep sheet built from the guest's public work when they agree.
Preview, from the skill itself
“# Podcast Guest Pipeline<br># Podcast Guest Pipeline A guest booking often lives in a scramble: a name mentioned in passing, an outreach note sent from memory, a recording booked with no prep, and clips promised afterwards that no one tracks.”
Version 1.0.09 filesProspects from known groundPrep from public work onlyFollow-up logged until doneHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 0058a5e681ff… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 32.0 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/indie-maker-first-booking/WALKTHROUGH.md, examples/returning-author-second-visit/WALKTHROUGH.md, reference/outreach-drafts-and-approval.md, reference/prep-sheet-from-public-work.md, reference/prospect-sourcing-and-tracking.md, reference/recording-follow-up-and-clips.md, templates/guest-pipeline-record.template.md, templates/guest-prep-sheet.template.md
Worked example, from the package
examples/indie-maker-first-booking/WALKTHROUGH.md
This is a fictional example. The guest, the show, and every name and date in it are made up for this walkthrough, and the figures are internal pipeline figures only.
New Agent Intake Checks
Agent Safety and Governance · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Learn what a new agent can actually touch, what it sends and where, and how it fails, proven on copies before it ever sees a real record, with the admit or refuse call on record.
What changes
- A new agent joining on its description and a few good answers on clean cases → what it can touch, what it sends, and how it fails proven first, on copies, while nothing real is at stake
- Reach and sends learned later, when the agent reaches too far or something arrives that should have been held → two maps, touch and sends, tested against what the agent was seen to do, not believed from its description
- Failure learned on a real record on a bad day → failure probes run on the copies, and one recorded call: admit, admit narrower, or refuse
Honest fit
For you if: You are about to let a new agent start live work, and what it can reach, what it sends, and how it fails are known only from its description.
Skip it if: You need the files inside a skill package scanned before they are trusted, access granted, or a faulty agent fixed; vetting reads the package, and this intake tests the running agent on copies and grants nothing itself.
Your first run produces: one intake record for the next agent you were about to let start live work: the proposed role in one line, a small set of copies with four failure probes run, the touch map and the sends map drafted from what was seen, and the admit, admit narrower, or refuse call recorded with its reasons.
Preview, from the skill itself
“# New Agent Intake Checks<br># New Agent Intake Checks A new agent can sound ready long before it is safe to let near real work.”
Version 1.0.09 filesProven on copies firstTouch and sends mapsAdmit or refuse on recordHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 629489d46970… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 41.5 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/inbox-triage-agent-for-a-trades-business/WALKTHROUGH.md, examples/supplier-ordering-agent-for-a-small-shop/WALKTHROUGH.md, reference/map-what-it-can-touch.md, reference/map-what-it-sends-and-where.md, reference/prove-failure-behaviour-on-copies.md, reference/the-admit-or-refuse-record.md, templates/intake-checklist.template.md, templates/intake-decision-record.template.md
Worked example, from the package
examples/inbox-triage-agent-for-a-trades-business/WALKTHROUGH.md
A small trades business gets more enquiries than the owner can sort each morning: quote requests, date changes, small job offers, and follow ups on work in hand. A triage agent is offered for the job. The proposed role is one line long: sort copied enquiries, draft replies for the owner, and send nothing. The owner likes the idea and does not like the risk, so the agent goes through intake before it sees a single real enquiry. This is how that intake ran.
Agent Fleet Roster
Agent Operations · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Answer for your whole fleet from one page: every agent's job, what it can touch, who answers for it, and when its entry was last checked, kept in one living register.
What changes
- The fleet known in pieces, in setup notes, chat threads, and memory → one living register, one entry per agent, that answers the plain questions at a glance
- An agent's access recalled or assumed → the touch list read from the grant or the setting itself, listed as granted today, with the check date beside it
- An agent with no one answering for it, forgotten → a named person on every entry, and an agent with none flagged at the top of the roster until one is named
Honest fit
For you if: You run several agents set up at different times, and no one place answers how many there are, what each does, what each can touch, and who answers for it.
Skip it if: You need one new agent brought in, watched while it works, or its output judged; onboarding brings one agent in, and this roster is the standing record that holds the fleet together after that.
Your first run produces: one first roster for the fleet as it stands: every agent you believe exists listed from records, one entry each with its job, status, touch list, and named owner, the facts that cannot be sourced written as not yet known and flagged, and the next check date set.
Preview, from the skill itself
“# Agent Fleet Roster<br># Agent Fleet Roster Agents rarely arrive all at once.”
Version 1.0.09 filesOne entry per agentAccess as grantedNamed owner on every entryHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 0e3fab021022… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 39.6 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/first-roster-for-a-three-agent-studio/WALKTHROUGH.md, examples/roster-cleanup-after-a-year-of-growth/WALKTHROUGH.md, reference/keeping-the-roster-current.md, reference/ownership-and-answerability.md, reference/roster-fields.md, reference/what-each-agent-can-touch.md, templates/agent-roster-entry.template.md, templates/fleet-roster.template.md
Worked example, from the package
examples/first-roster-for-a-three-agent-studio/WALKTHROUGH.md
A small studio with five people had grown its agents one at a time over one spring. The owner could name all of them in conversation, but no single page held the fleet, and a new starter asked a plain question nobody could answer from a record: which agent was allowed to write to the shared job board. This is how the first roster was built, in one week, from records.
Runbook Writing
Studio / Publishing · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Turn a procedure only one person knows into a dated runbook entry a second operator can follow at night, checked step by step against the live system.
What changes
- The fix held in one person's head, and what is written down a summary rather than the fix itself → one entry per procedure, with the steps the operator actually takes, in order
- Steps that sound right but were never done that way → every entry checked against the live system, screen by screen, before it is trusted
- A procedure quietly going out of date as the system changes → each entry dated, with who checked it, what changed, and the next review set
Honest fit
For you if: Your important procedures live in one person's memory and scattered notes, so a night incident means calling that person or rebuilding the fix from fragments.
Skip it if: You need instructions for end users of a finished product, a system monitored, or an incident fixed for you; a runbook is for the operator who runs the fix, and user guides are a separate skill.
Your first run produces: one checked runbook entry for the procedure you would least want to explain over the phone at night: the steps listed from the last real record, drafted with its trigger, checks, and stop and escalate point, confirmed against the live system, dated, and added to the index with its review date.
Preview, from the skill itself
“# Runbook Writing<br># Runbook Writing Some procedures only fail when they are needed most.”
Version 1.0.09 filesChecked against the live systemDated entriesWritten for a tired readerHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 4ba69f557751… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 41.7 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/nightly-backup-failure/WALKTHROUGH.md, examples/web-service-restart/WALKTHROUGH.md, reference/anatomy-of-a-runbook-entry.md, reference/checking-against-the-live-system.md, reference/keeping-runbooks-current.md, reference/writing-operator-steps.md, templates/runbook-entry.template.md, templates/runbook-index-and-review.template.md
Worked example, from the package
examples/nightly-backup-failure/WALKTHROUGH.md
A small studio keeps its project files on one file server. A backup job named Nightly Backup runs at 01:30 each night and writes a copy to a backup volume of 200 GB. One operator, Sam, knew how to handle a failed run. No one else did, and nothing usable was written down. When a run failed while Sam was on leave, the morning cover operator found the failure notice and had to wait three hours for Sam to be reached. The studio decided that procedure would be the first runbook entry. This is how that entry was written.
Build Verification Checks
Studio / Shipping · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Catch a dead on arrival build in the studio instead of in front of a user, with one fixed pre-ship list for start, main flows, version stamp, and artifacts, and a written record for every build.
What changes
- Checking done from memory, in a different order each time, with no record → one fixed list, run in the same order on every build that might ship
- A pass claimed for a local run or an earlier package → the checks run on the exact artifact that would go out, identified by its build and version stamp
- A build that will not start or a stale version shipping on a feeling → the fault caught in the studio, named in a per build record, and the build held until the operator decides
Honest fit
For you if: You ship builds, and checking is done from memory in a different order each time, so front door faults like a blank first screen ship and ship again.
Skip it if: You need automated tests written, faults fixed, or a release published for you; this is the fixed manual check on the exact artifact, and the ship step stays yours.
Your first run produces: one verification checklist for the product you release most often, and a practice run of the full list on your most recent build: the main flows named, the version match written down, and every check marked passed, failed, blocked, or not run in a complete per build record.
Preview, from the skill itself
“# Build Verification Checks<br># Build Verification Checks Most dead on arrival builds did not fail in a hidden place.”
Version 1.0.09 filesOne fixed list, same orderThe exact artifact checkedA failed check holds the buildHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: e0332003a75e… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 39.9 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/mobile-app-blank-screen-catch/WALKTHROUGH.md, examples/service-release-clean-check/WALKTHROUGH.md, reference/recording-a-build-result.md, reference/the-verification-checklist.md, reference/version-and-artifact-checks.md, reference/when-a-check-fails.md, templates/build-verification-record.template.md, templates/verification-checklist.template.md
Worked example, from the package
examples/mobile-app-blank-screen-catch/WALKTHROUGH.md
A small studio builds a field notes app for phones. The app had shipped six earlier versions with checking done from memory. For version 1.8.0 the studio wrote its first fixed checklist and ran it on every build. This is the run that caught a build which would have reached users showing nothing but a blank screen.
Research Source Grading
Data, Files, and Research · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Grade every source behind your research before its claims are used, so each claim carries only the weight its source earned, with copies counted once and conflicts named in the open.
What changes
- A maker's statement, a firsthand test log, and a copied press release looking exactly alike in the notes → each source graded for its stated use, with its publisher, date, and the reason for the grade on the register
- A claim repeated by three sources looking like wide support → repetition traced to its origin, and sources that copy one origin counted once
- Conflicts and stale sources found after the work goes out → disagreements named in the register with both sides kept, and every grade stating what would change it
Honest fit
For you if: Your briefs rest on sources that all look alike in the notes, so the weakest one, a copied summary or an undated page, can end up carrying the decision.
Skip it if: You need claims themselves verified as true, sources found and read for you, or a conflict settled; grading weighs the source for a stated use, and claim checking is the Verified Research skill.
Your first run produces: one source register for the next brief you were about to write up: its four to six sources listed with their claims, each graded with its reason and what would change the grade, repeated claims grouped to one origin, and one grade card filled in for the source the brief leans on hardest.
Preview, from the skill itself
“# Research Source Grading<br># Research Source Grading A claim is only as strong as the source behind it, but research notes rarely show that strength.”
Version 1.0.09 filesGraded for a stated useRepetition counted onceConflicts named in the openHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 594836028ac4… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 45.7 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/grading-a-vendor-performance-claim/WALKTHROUGH.md, examples/grading-sources-for-a-pricing-brief/WALKTHROUGH.md, reference/conflicts-and-grade-changes.md, reference/dates-publishers-and-provenance.md, reference/primary-and-secondary-sources.md, reference/the-grading-scale.md, templates/source-grade-card.template.md, templates/source-register.template.md
Worked example, from the package
examples/grading-a-vendor-performance-claim/WALKTHROUGH.md
This is a fictional example built for this package. The tool, the maker, and every figure in it are internal to the example, and the figures are consistent within it so the grading moves can be followed end to end.
File Metadata Cleanup
Data, Files, and Research · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A library you can find things in again: names, dates, and embedded fields agree under one written rule, with every change logged per file and originals kept untouched until you sign off.
What changes
- Finding a file by guessing which of its dates or names to believe → names, dates, and embedded fields that agree, because one written source was chosen for each under an approved rule
- A cleanup run from habit, file by file → a written rule first, then a plan with a row for every file: a change, a stated reason to stay, or a hold naming the open question
- A wrong field staying wrong because nobody can show what it said before → a per file change log with before and after, and the originals kept untouched until the batch is signed off
Honest fit
For you if: Your files carry names and fields that disagree with each other, so a file is hard to find, trust, or tell apart from the one next to it.
Skip it if: You need file contents fixed, damaged files repaired, files converted, or a ruling on what to keep and throw away; this covers names, dates, and metadata only, and nothing here deletes a file.
Your first run produces: one small batch cleaned under a written rule: the batch read as found with every disagreement on paper, a plan with a row per file, the originals set aside untouched, and only the approved changes applied, each written into the per file change log as it lands.
Preview, from the skill itself
“# File Metadata Cleanup<br># File Metadata Cleanup A library goes hard to use in a quiet way.”
Version 1.0.09 filesWritten rule before the batchOriginals kept until sign offEvery change loggedHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: fcc26ba71f03… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 49.7 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/client-document-archive/WALKTHROUGH.md, examples/spring-photo-export/WALKTHROUGH.md, reference/approval-originals-and-verification.md, reference/batch-checking-and-holds.md, reference/metadata-fields-and-sources.md, reference/writing-the-cleanup-rule.md, templates/cleanup-plan.template.md, templates/per-file-change-log.template.md
Worked example, from the package
examples/client-document-archive/WALKTHROUGH.md
A small studio finished a cafe fit out for a client, Harbor Lane Cafe, and went to hand over the project archive: estimates, invoices, a schedule, and sign off sheets gathered over the job. The archive held 30 files from the whole job, and it showed. Some files were named with dates, some with working titles, and the titles and authors inside the files often belonged to the blank documents they had started from, not to this job. The client would keep this archive as their record of the work, so a wrong title or author in it would be read as fact for years. The operator wanted the batch cleaned against the studio job sheet, which listed each document on the job, its proper title, and its date. This is how that batch was cleaned. All counts below are from this batch only.
First Conversation Scripts
Local Services / Sales · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Your first call with a new lead runs from a one-page script built from your own services, so the job gets sized, only deliverable promises get made, and the call ends with one next step both sides heard the same way.
What changes
- The first conversation running on nerve and habit, with nothing written down → one page the operator approved: sizing questions in order, promise lines, and one next step
- A price named to keep the lead warm, then quoted back as a quote → the sizing questions asked before any price talk, so the quote rests on figures the lead stated
- Both sides remembering a different conversation two weeks later → what was said and the one next step written on the conversation record during the call or straight after it
Honest fit
For you if: Your first calls with new leads are where jobs get missold: a price named before the job is sized, a day offered before the book is checked.
Skip it if: You need leads captured and routed, prices set, or the calls made for you; Lead Intake routes the lead, and this skill scripts the conversation, which you still hold yourself.
Your first run produces: one script for the next new lead already on the books: the services the conversation may offer, five to eight sizing questions in running order, both promise lists in the words you would say out loud, and the one next step checked as deliverable, held for your approval before anything is said.
Preview, from the skill itself
“# First Conversation Scripts<br># First Conversation Scripts The first real conversation with a new lead is where a job is sized, and where it is most often missold.”
Version 1.0.09 filesSizing questions before price talkPromise lines in writingOne next step, offered onceHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: ea7805d70840… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 33.6 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/fence-repair-first-call/WALKTHROUGH.md, examples/junk-haul-first-call/WALKTHROUGH.md, reference/building-the-script-from-your-services.md, reference/questions-that-size-the-job.md, reference/the-one-next-step.md, reference/what-can-and-cannot-be-promised.md, templates/conversation-record.template.md, templates/first-conversation-script.template.md
Worked example, from the package
examples/fence-repair-first-call/WALKTHROUGH.md
A fence repair operator takes panel and post work only. No new full fences, and no gate fitting. A new lead calls on Tuesday about a back fence damaged in wind. The operator runs the first conversation from the script built for fence repair leads, approved the week before.
Add-On Offers
Local Services / Sales · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Finds extra work a job record genuinely supports, writes each add-on into the quote as its own line at its price from the operator price list, offers it once in plain words, and records the customer answer either way.
What changes
- Extra work living in a spoken aside, folded into one lump price where the customer cannot see it → each add-on the record supports written as its own line, with its own price from your price list
- A fair add-on never offered because nobody checked the record in time → every candidate checked against the job record before the quote goes out, and work that fails the check held back with its reason
- A declined offer raised again because nobody wrote the no down → each add-on offered once, in plain words, and the answer recorded either way
Honest fit
For you if: You run local service jobs and sometimes see honest extra work next to the booked work, and you want it offered cleanly, priced from your own list, and settled on the record before the job starts.
Skip it if: You want a script to talk a customer into work the job does not call for, or you do not keep a price list and a job record the offer can be checked against.
Your first run produces: one quote checked before it goes out: the nearby work listed, each item tested against the job record, the kept add-ons priced from your price list as their own lines, and the offer drafted in plain words, held for you to send, with the answer to be written on the record the day you hear it.
Preview, from the skill itself
“# Add-On Offers<br># Add-On Offers Extra work is easy to get wrong in two directions.”
Version 1.0.09 filesChecked against the job recordIts own line, its own priceOffered once, answer recordedHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 3d0cd3a99ffe… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 34.2 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/deck-repair-stain-and-seal/WALKTHROUGH.md, examples/kitchen-repair-grout-and-caulk/WALKTHROUGH.md, reference/offering-once-and-recording-the-answer.md, reference/price-list-and-what-is-never-offered.md, reference/when-the-record-supports-an-add-on.md, reference/writing-the-add-on-as-its-own-line.md, templates/add-on-offer-record.template.md, templates/quote-with-add-ons.template.md
Worked example, from the package
examples/deck-repair-stain-and-seal/WALKTHROUGH.md
A local repair operator is booked to replace damaged boards on a back deck and reset a loose rail section. On the visit the operator noted the state of the deck finish. That note is what makes one honest add-on possible on this job, and the record is also what stops a second candidate from being offered at all.
Progress Payment Schedule
Local Services / Money · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A bigger job billed in stages agreed before work starts, with a deposit, midpoints tied to visible milestones, and the balance at completion, each stage recorded as open or paid so money and work stay in step.
What changes
- A bigger job running on a deposit and a hope, money asked for when cash gets tight → one schedule agreed before work starts: deposit, midpoints, and the balance, adding back to the job total on the page
- A midpoint argued from two memories of how far along the job is → each midpoint tied to a visible milestone the customer can check, so the payment slips with the work, not the calendar
- A final bill that surprises the customer who thought more had been paid → one record showing each stage as open or paid, with dates, as the job moves
Honest fit
For you if: You run bigger jobs that run past a few days, and payment rests on a deposit and a hope, with midpoints argued from two different memories of how far along the work is.
Skip it if: You need the job priced, a deposit set as a standing term, invoices chased, or money taken for you; Deposit Terms Setup sets the deposit alone, and this schedule drafts and records while you take the payments.
Your first run produces: one schedule for the next bigger job on the books, built before the quote goes out: the total taken from the accepted estimate, split into deposit, midpoints, and balance, each midpoint named by a milestone the customer can see, the stages shown to add to the total, and the stage record opened beside it.
Preview, from the skill itself
“# Progress Payment Schedule<br># Progress Payment Schedule A bigger job paid all at the end leaves the operator carrying weeks of work and materials on trust.”
Version 1.0.09 filesStages agreed before the startMilestones the customer can seeOpen or paid, on one recordHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: a68665ea8060… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 36.5 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/kitchen-remodel-three-stages/WALKTHROUGH.md, examples/roof-replacement-milestone-slip/WALKTHROUGH.md, reference/changes-and-balance-at-completion.md, reference/customer-wording-for-stages.md, reference/stage-plan-tied-to-visible-milestones.md, reference/stage-record-open-or-paid.md, templates/progress-payment-schedule.template.md, templates/stage-payment-record.template.md
Worked example, from the package
examples/kitchen-remodel-three-stages/WALKTHROUGH.md
A kitchen fitter is taking out an old kitchen and fitting a new one in the same room: new cabinets, worktops, tiling, and the sink and hob connected. The job will run across two weeks, and the customer does not want to pay the whole total at either end of it. The operator and the customer agree a staged schedule before any work starts.
Fuel and Mileage Log
Local Services / Money · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Every trip your work vehicle makes is logged against the job it served and every fuel stop is recorded from its receipt, so each closed job shows its true road cost and the year's vehicle totals exist as arithmetic, not recollection.
What changes
- The road invisible in job costs, and fuel sitting in a pile of pump receipts that name no job → every trip logged against the job it served, and every fuel stop recorded from its receipt on the day it happened
- A job that looks profitable on the invoice while losing money on the drive → each closed job showing its miles and its road cost as a line of its own, worked from your own per mile figure
- The year end question of what the vehicle cost answered from a shoebox of receipts → month and year totals built a day at a time, as arithmetic instead of recollection
Honest fit
For you if: You drive a work vehicle from job to job and your job costs never include the road, so a long drive can quietly eat the profit on a small job.
Skip it if: Your vehicle costs are already tracked per job in another system you trust, or you do not run jobs from a vehicle at all.
Your first run produces: one log set up for the vehicle that does most of the job driving, with today logged as the first day: the vehicle header and odometer reading written, today trips each naming a job with their readings, today fuel stops recorded from their receipts, and the day miles adding up to the difference between the first and last readings.
Preview, from the skill itself
“# Fuel and Mileage Log<br># Fuel and Mileage Log A job can look profitable on the invoice and still lose money on the road.”
Version 1.0.09 filesEvery trip names its jobFuel from the receiptMonth and year totalsHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 7d7b3d60f65d… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 33.7 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/fence-repair-two-jobs-one-van/WALKTHROUGH.md, examples/firewood-delivery-week/WALKTHROUGH.md, reference/closing-the-month-and-the-year.md, reference/logging-a-trip-against-a-job.md, reference/recording-a-fuel-stop.md, reference/turning-the-log-into-a-job-cost.md, templates/job-and-year-totals.template.md, templates/trip-and-fuel-entry.template.md
Worked example, from the package
examples/fence-repair-two-jobs-one-van/WALKTHROUGH.md
An operator repairs fences from one van. On Monday the van serves two jobs: a fence repair that runs into Tuesday, and a small gate hinge fix across town. On Tuesday the operator goes back to the fence repair alone to finish it. One fuel stop falls on Tuesday morning.
Site Safety Walk
Local Services / Field Operations · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
The crew starts knowing the site instead of discovering it, because one recorded walk before work names hazards across access, overhead, ground, and weather exposure, gives each a written plan, and files the photos against the job.
What changes
- The start of a job resting on a quick look and a few words at the truck → one walk before work starts, in a set order: access, overhead, ground, and weather exposure
- Hazards met one at a time at the cost of the day, when the cheap fix has gone → each hazard named with its place, a written plan and an owner for each, and photos filed against the job by number
- No record of what was seen or who was told what at the end of the job → the crew briefed from the walk record before the first task, so the plan can be checked and handed over
Honest fit
For you if: You run small crews on houses and yards where the site changes from job to job, and the first hour keeps being spent on finds the start of the day could have caught.
Skip it if: Your work is in one fixed place you walk daily under a standing plan of your own, or you need a formal inspection or a signed clearance, which this record is not.
Your first run produces: one walk record for the next job, made before any tools come out: the site walked in the set order from the job record, each hazard named with its place and given a plan and an owner, the photos filed against the job by number, and the crew brief drafted from the record, waiting for your word.
Preview, from the skill itself
“# Site Safety Walk<br># Site Safety Walk Most site trouble is not a surprise.”
Version 1.0.09 filesWalked before work startsA plan for every hazardPhotos filed against the jobHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: e45376abb654… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 38.8 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/brush-clearing-deck-teardown/WALKTHROUGH.md, examples/roof-valley-repair-steep-lot/WALKTHROUGH.md, reference/access-and-overhead-hazards.md, reference/ground-and-weather-hazards.md, reference/photos-filed-against-the-job.md, reference/plan-for-each-hazard.md, templates/crew-start-brief.template.md, templates/safety-walk-record.template.md
Worked example, from the package
examples/brush-clearing-deck-teardown/WALKTHROUGH.md
An operator and three crew are set to clear brush along a fence line and take down an old raised deck at the back of a sloped yard. The work needs saw work in the brush, boards carried up the yard, and waste carried down to a trailer at the street. The day is set to be hot. No work starts until the walk is done.
Subcontractor Payment Records
Local Services / Field Operations · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Every subcontractor payment tied to the agreed stage it covers, partials shown as partial, and the balance owed known from one record at any point.
What changes
- Paying a sub living in a bank list and two memories → one payment record per agreement: the agreed total at the top, split into its stages, checked on the page
- A payment made toward the job in general, with nobody able to say which stage it covered → every payment tied to its stage and entered the day it moves, a partial shown as partial with its shortfall open
- A final talk where each side adds the same payments into different totals → the balance worked from the lines every time it is stated, the same arithmetic whoever works it
Honest fit
For you if: You pay one or more subcontractors against written agreements and want paid, partial, and still owed to be known from one record at any point, without rebuilding it from bank lines and memory.
Skip it if: You have no written agreement with the sub to pay against, or one person pays a single fixed sum on completion every time with nothing staged, partial, or extra in between; in that case a single paid line on the job record already does the whole job.
Your first run produces: one payment record for the next subcontractor agreement already on the books: the agreed total written exactly as agreed and split into its stages, the stage amounts checked against the total, any payments already made entered and tied to their stage or flagged, and the balance worked from the lines.
Preview, from the skill itself
“# Subcontractor Payment Records<br># Subcontractor Payment Records A subcontractor can do good work and still leave a money argument behind.”
Version 1.0.09 filesEvery payment names its stagePartials shown as partialBalance from the linesHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: d2a4535932a8… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 35.2 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/deck-framing-staged-payments/WALKTHROUGH.md, examples/fence-build-agreed-extra/WALKTHROUGH.md, reference/agreement-total-and-stages.md, reference/extras-holdbacks-and-closing-the-record.md, reference/partial-payments-and-balance-owed.md, reference/recording-a-payment-as-it-happens.md, templates/payment-ledger.template.md, templates/payment-summary-for-the-sub.template.md
Worked example, from the package
examples/deck-framing-staged-payments/WALKTHROUGH.md
A decking operator has taken a full deck job and brings in Marcus, a carpenter, to build the frame while the operator handles the decking boards, steps, and finish. The frame money is agreed in writing before Marcus starts, and this walkthrough follows only that money: the agreed total, its stages, two payments, and the balance still owed part way through the job.
Agent Decision Log
Agent Operations · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Settle any questioned agent decision from one entry instead of from memory, and catch a repeating fault in the log before it becomes damage: every consequential call is recorded at the time with what the agent was given, the rule or record it followed, and what came of it.
What changes
- A questioned decision settled by whoever recalls it best, after the records it was made from have changed → the same question settled from one entry: what the agent was given, the rule it followed, the call it made, and what came of it, written at the time
- A fault in the setup repeating for months because no single record holds the calls side by side → the weekly or monthly review reads the calls together, so a pattern is named in the log, with its entry numbers and its count, while it is still a pattern
- Fixes guessed at and never checked → the fix lands in the setup, the rule, or the gate, and later entries show whether it held
Honest fit
For you if: Your agents approve, refuse, route, spend, or promise in your name, and a questioned call would today be settled from memory and from records that have since changed.
Skip it if: You need the decision made or judged for you, or one incident worked in depth; this log is the standing record those readings work from, and it makes no decision, widens no gate, and fixes no fault itself.
Your first run produces: one decision log started for one agent: the log opened with its scope line naming the agent and the two or three kinds of call that count as consequential, today's consequential calls entered one per call as they happen, with what each was given, the rule or record it followed, the decision, and the gate the action passed, and the outcome check and first pattern review dates set at the top of the log.
Preview, from the skill itself
“# Agent Decision Log<br># Agent Decision Log An agent makes calls all through the day.”
Version 1.0.09 filesOne entry per decisionWritten at the timePatterns named in the logHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: c5e51c8cf103… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 47.1 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/a-pattern-review-that-changed-an-ordering-rule/WALKTHROUGH.md, examples/a-refund-call-traced-three-weeks-later/WALKTHROUGH.md, reference/decision-entry-fields.md, reference/keeping-and-correcting-the-log.md, reference/reading-the-log-for-patterns.md, reference/what-counts-as-consequential.md, templates/decision-log-entry.template.md, templates/decision-log.template.md
Worked example, from the package
examples/a-pattern-review-that-changed-an-ordering-rule/WALKTHROUGH.md
A repair business ran an ordering and dispatch helper that could approve small parts orders inside a standing grant, pick a supplier where more than one stood, pick a delivery speed, and move job slots when parts ran late. Each of those calls sat inside the scope line of the business's decision log, which the office manager kept. Entries were numbered in one running order. This is the monthly pattern review for June, what it found, and what the next review showed.
Agent Capacity Planning
Agent Operations · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Know how much more work your fleet can take, agent by agent, from one record of load, queue growth, and the load where quality starts dropping, before a peak or a growing backlog forces the answer.
What changes
- Capacity as a feeling, because the fleet took on a busy month last time → arrivals, completions, and queue growth on one record, per agent, for a stated period, from named sources
- A growing queue noticed when the people waiting start asking → the agent that runs out of room first named, with the date its queue passes its limit if nothing changes
- The first sign of a quality problem being the complaint that follows it → the load at which quality starts dropping written down before a peak arrives, and planned intake set below it with a margin
Honest fit
For you if: You run several agents and cannot say from a record which one runs out of room first, or how much more work the fleet can take before quality starts dropping.
Skip it if: You need work taken in, turned away, or moved between agents; this record informs those calls and makes none of them, and it reads the quality checks your fleet already runs rather than judging quality itself.
Your first run produces: one capacity record for the fleet as it stands: one entry per agent for the same recent period, with what counts as one unit of work for that agent, where the count comes from, arrivals and completions, the queue at the start and at the end, and the peak inside the period, then per agent the queue growth and a first reading of sustainable load and headroom, with gaps flagged by name and the next check date set.
Preview, from the skill itself
“# Agent Capacity Planning<br># Agent Capacity Planning A fleet can look busy and healthy right up to the week it falls behind.”
Version 1.0.09 filesLoad counted per agentQueue growth in the openPlanned below the limitHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 55781fd1f17e… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 47.2 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/four-agent-fleet-before-the-holiday-peak/WALKTHROUGH.md, examples/weekly-check-that-caught-a-growing-queue/WALKTHROUGH.md, reference/capacity-terms-and-counts.md, reference/finding-where-quality-drops.md, reference/queue-growth-and-backlog.md, reference/reading-per-agent-load.md, templates/agent-load-entry.template.md, templates/capacity-record.template.md
Worked example, from the package
examples/four-agent-fleet-before-the-holiday-peak/WALKTHROUGH.md
A small studio ran four agents for customer work and expected its busiest weeks of the year in late November. The operator had a forecast from the advance orders sheet: about 30 percent more work than the current level, across all four kinds of work. She wanted to know, from the record and not from hope, whether the fleet could take that rise, and where it would run out of room first. This is how the first capacity record was built and read, over one ten working day period.
Secret Rotation Schedule
Agent Safety and Governance · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Every secret on one written rotation schedule, by label and location only: its age, its owner, and its next rotation date, with the reminder drafted ahead of the date and each rotation logged, so no secret ages in silence.
What changes
- Rotation running on memory and on scares, a secret changed when it leaks, when a job fails, or when someone asks how old it is → every secret on one written schedule, with its age, its owner, and its next rotation date
- Due dates living in chat threads and in one person's head, a slipped date invisible because nothing ever wrote it down → the reminder drafted ahead of the date, and overdue shown as a flagged line with a count of days
- No record of what was rotated or when → each rotation logged as it happens, so the whole state of the list fits on one page a stranger can read, and the oldest secret is a fact on that page
Honest fit
For you if: You hold keys, tokens, or passwords across tools and cannot say from one page how old each one is, who owns it, or when it is next due to rotate.
Skip it if: You need the rotation done for you, or rules for how a secret value may be stored and handled; this schedule rules the calendar only, holds no value, and each rotation stays in your hands in the storage tool.
Your first run produces: one rotation schedule built from the records as they stand: every secret listed one line each, by label and location only, each line filled with its owner, its last rotated date read from a record, and an interval set for it, the age and the next date worked out from the dates rather than from memory, secrets of unknown age flagged and planned for a first rotation soon, and reminders drafted for every date due in the next thirty days.
Preview, from the skill itself
“# Secret Rotation Schedule<br># Secret Rotation Schedule Most secrets are rotated on the day something goes wrong, or on the day someone happens to remember.”
Version 1.0.09 filesLabels and locations onlyAges from dates, not memoryReminders before the dateHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 4480723cf40b… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 41.0 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/catching-up-an-overdue-schedule/WALKTHROUGH.md, examples/first-schedule-for-a-solo-studio/WALKTHROUGH.md, reference/choosing-rotation-intervals.md, reference/logging-a-rotation.md, reference/reminders-and-the-rotation-day.md, reference/schedule-fields.md, templates/rotation-log-entry.template.md, templates/secret-rotation-schedule.template.md
Worked example, from the package
examples/catching-up-an-overdue-schedule/WALKTHROUGH.md
A three person team, Ana, Ben, and Cleo, kept a rotation schedule for the twelve secrets behind their booking service. The schedule had been built the previous November and kept well until April. Then the keeper changed: Ben took the schedule over in May, the May review was missed in a launch week, and no reminders went out for six weeks. The catch up review was held on Monday 8 June 2026, with the schedule and the log side by side.
Page Accessibility Checks
Studio / Publishing · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Get every published page checked against one fixed accessibility list, with findings logged per page and fixes drafted for your approval, so weak alt text, broken heading order, vague link names, and failing contrast are found and settled from values instead of guessed at by eye.
What changes
- The state of a site's pages known in pieces, if it is known at all, from whoever last looked at one page → every published page checked against one fixed list, with findings logged per page
- Weak alt text, broken heading order, vague link names, and failing contrast guessed at by eye → each finding recorded with the line, level, name, or values that caused it, and weak contrast settled by worked ratios, not by eyesight
- Simple questions taking an afternoon of opening pages → each fix sitting beside its finding as a draft you can settle in minutes, and a page nobody has checked flagged instead of forgotten
Honest fit
For you if: You publish pages and cannot say which ones hold images without alt text, broken heading order, vague link names, or text that fails on its contrast values.
Skip it if: You need keyboard use, focus order, forms, motion, or reading software behaviour checked, or a claim that a page meets every rule or law that can apply to it; this list covers four heads only, and fixes are drafted for your approval, never published by the skill.
Your first run produces: one check log for the published pages as they stand: every page in scope listed one line each and settled against the live site, then one page at a time worked through the fixed list, every image for alt text, every heading in order, every link name in full, and every text and background pair from the design values in use, each finding written on its page entry and each fix drafted on the fix draft sheet for your approval, with the next check date set.
Preview, from the skill itself
“# Page Accessibility Checks<br># Page Accessibility Checks A published page is edited many times by many hands.”
Version 1.0.09 filesOne fixed check listContrast settled from valuesFixes drafted for approvalHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 131d4a167b36… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 44.7 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/event-listing-and-guide-pages-for-a-community-site/WALKTHROUGH.md, examples/home-and-services-pages-for-a-small-studio/WALKTHROUGH.md, reference/alt-text-and-image-honesty.md, reference/contrast-from-design-values.md, reference/headings-and-link-names.md, reference/the-fixed-check-list.md, templates/fix-draft-sheet.template.md, templates/page-check-log.template.md
Worked example, from the package
examples/event-listing-and-guide-pages-for-a-community-site/WALKTHROUGH.md
A volunteer run community site listed local events and held guides for visitors. Five pages were published: an events home page, a listing for the current month, a venue guide, a tickets guide, and a page about the group. Pages were edited by whoever had time, and the site had never had a single check. This is how the first check was run, over two weeks of short sittings, from the pages and the design record as they stood.
Dependency License Ledger
Studio / Shipping · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Ship every release knowing, from one ledger rechecked against the build, what each dependency carries and what its license asks, so no obligation goes out unrecorded.
What changes
- The licenses living with the packages, a notice that should have shipped found after the release, if it is found at all → every dependency on one ledger, with its version shipped, its license for that version, and what that license asks
- A version change quietly bringing new terms that nobody read, because the library name stayed the same → the ledger rechecked against the build at every release, so a license change arrives as a flagged line instead of a surprise after the fact
- Simple questions taking an afternoon of digging through folders → the steps owed before release sitting at the top of the ledger as a short list you can work through and sign off
Honest fit
For you if: You ship software and cannot say from one page what each dependency carries or what its license asks, so an obligation can go out unrecorded with a release.
Skip it if: You need legal advice, a ruling on whether two licenses can sit together in one product, or dependencies chosen for you; the ledger records obligations and makes none of those calls.
Your first run produces: one ledger for the next release, built from the build as it stands: every dependency you believe ships listed one line each from the manifest, the lock file, the build list, and the bundled items, then one entry per dependency with its name, the version shipped, the license for that version, what that license asks, where the license text was read, and the date those facts were checked at their source, with gaps flagged as not yet known and the next recheck set for the next release.
Preview, from the skill itself
“# Dependency License Ledger<br># Dependency License Ledger A product rarely ships alone.”
Version 1.0.09 filesOne entry per dependencyRechecked at every releaseOwed steps at the topHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 5336fc2d18b8… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 41.6 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/first-ledger-for-a-shipping-app/WALKTHROUGH.md, examples/release-recheck-that-caught-a-license-change/WALKTHROUGH.md, reference/keeping-the-ledger-current.md, reference/ledger-fields.md, reference/reading-a-license-for-the-ledger.md, reference/what-each-license-asks.md, templates/dependency-license-entry.template.md, templates/license-ledger.template.md
Worked example, from the package
examples/first-ledger-for-a-shipping-app/WALKTHROUGH.md
A small studio was one week from the first release of a desktop invoicing tool for solo shops. The tool had been built over one season, with libraries added as each feature landed. The owner could name most of them in conversation, but no single page said what the installer carried, under which licenses, or what those licenses asked for. With the release close, she asked for one true ledger before anything went out. This is how the first ledger was built, over three days, from records.
Archive Search Index
Data, Files, and Research · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Find any archived file by what it is, with a searchable index built from each file's subject, date, parties, and type and kept current as new files arrive.
What changes
- The archive searched by place, finding a file meaning recalling a folder, a file name, or the person who filed it → the same archive searched by what a file is, its subject, date, parties, and type on one entry
- The search failing whenever that memory is thin, the filer has moved on, or the naming changed halfway through the archive's life → a search built from any of those fields landing on the entry without anyone needing to recall a folder
- New files making the problem larger each month, each one filed on the same memory based terms as the last → a new file joining the index on the day it arrives, partial entries flagged instead of hidden, and the count at the top matching the entries beneath it
Honest fit
For you if: You keep an archive of contracts, job files, or records, and finding one of them means recalling its folder or its file name, or asking whoever filed it.
Skip it if: You need files moved or renamed, a file's contents summed up or judged, or search inside the full text of files; the index points to each file as it stands and changes neither its place nor its name.
Your first run produces: one index for the archive as it stands: a fresh inventory of every file in scope, one line each, from the archive itself, then one entry per file with its subject in plain words, the date on the file, the parties it names, its type, and the place it sits, each field read at its source and any field that cannot be found flagged as not yet known, finished by testing the index with real searches and setting the intake habit and the next check date.
Preview, from the skill itself
“# Archive Search Index<br># Archive Search Index An archive can hold a file safely and still lose it in practice.”
Version 1.0.09 filesSearch by what a file isFields read at the sourcePartial entries flaggedHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: d401f5994c7e… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 43.6 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/first-index-for-a-contracts-archive/WALKTHROUGH.md, examples/keeping-a-job-archive-searchable/WALKTHROUGH.md, reference/index-fields.md, reference/keeping-the-index-current.md, reference/reading-fields-from-the-record.md, reference/searching-and-checking-the-index.md, templates/archive-index.template.md, templates/index-entry.template.md
Worked example, from the package
examples/first-index-for-a-contracts-archive/WALKTHROUGH.md
A small studio kept its client papers in one archive built up over five years: contracts, letters about them, invoices, and short reports on finished work. The papers were safe, in nine folders by year and client, but finding one meant recalling the year it was filed and the client folder it sat in. When a past client asked for a copy of a letter about a change to their contract, two people spent an afternoon opening folders before it turned up in a different year from the one both of them recalled. This is how the first index was built, in one week, from the files themselves.
Seasonal Booking Calendar
Local Services / Sales · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Your seasonal rushes get planned in the quiet months: last year's own job records become a season map with an opening date and an honest slot count per season, plus an ordered waitlist kept for every season that fills.
What changes
- The year living as a surprise that repeats: the phone starts ringing, the book fills in a fortnight, and the late callers are turned away with no record kept → the same year sitting on one calendar before it starts, each season's demand counted from your own job records
- Next year starting with nothing but a memory of being busy → each season with an opening date set ahead of the rush, and each season's slots counted honestly against last year's tally
- A caller who cannot be fitted in being a name lost → a waitlist ready for every season, so that caller is a name in order, with the outcome recorded
Honest fit
For you if: Your work comes in seasonal rushes, and the rush is survived in the busy months each year instead of planned in the quiet ones, when you can still choose.
Skip it if: You need offers written, prices set, jobs booked, or customers contacted; this calendar is the timing those rest on and does none of them, and a new service with no past year gets a named gap on the calendar, not a guessed season.
Your first run produces: one whole year map built in one sitting from the last full year of job records: every seasonal job tallied by the month it was done and the service it was, the months grouped into the seasons the tallies actually show, each season's opening date set ahead of when its first enquiries arrived last year, each season's slots counted from the crew and days you can truly give it, and one empty waitlist started per season, ready for names.
Preview, from the skill itself
“# Seasonal Booking Calendar<br># Seasonal Booking Calendar Every local service year has the same rushes in the same places.”
Version 1.0.09 filesSeasons mapped from recordsOpening dates ahead of the rushAn ordered waitlist per seasonHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 6acb317e2698… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 36.0 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/exterior-washing-gutters-lights/WALKTHROUGH.md, examples/leaf-and-yard-spring-fall/WALKTHROUGH.md, reference/mapping-demand-to-seasons.md, reference/opening-dates-and-capacity.md, reference/reading-past-job-records.md, reference/waitlists-that-hold.md, templates/seasonal-calendar.template.md, templates/waitlist-sheet.template.md
Worked example, from the package
examples/exterior-washing-gutters-lights/WALKTHROUGH.md
A home exterior operator with two crews, doing pressure washing, gutter clearing, and holiday light fitting and removal. Two of its seasons share November, and its tightest season is its shortest one. In January 2026 the operator builds the year map from the full 2025 job records.
Materials Price Watch
Local Services / Money · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Your estimates stop quoting last season's prices: the materials you buy most are rechecked on a schedule from real listings at the exact quantity, every check dated and sourced, changes logged, and anything that cannot be sourced carried as a flagged placeholder, never a made-up figure.
What changes
- The prices inside estimates being the prices from whenever the estimate habit was formed, copied from quote to quote with no date on them and no source behind them → the materials you buy most on one short log, each price dated, sourced, and held by exact quantity
- Nobody able to say when a figure was last true → each change worked in the open against the last check, and one figure per item marked as the one an estimate may use
- An item nobody could price quietly filled in so the quote could go out → that item standing as a flagged placeholder until a real listing prices it, with the reason on the line and no figure
Honest fit
For you if: You write estimates, and the material prices inside them are last season's figures, remembered or copied from quote to quote, with no date and no source behind them.
Skip it if: You need materials bought, orders placed, or selling prices, margins, or quote totals set; this skill only keeps the price record, and it never promises that a listed price will still hold at the counter.
Your first run produces: one watch list and its first check in the same sitting: the materials that show up again and again named from your purchase notes and most recent estimates, each with the exact quantity its price will be held in, then the first check run, each item priced from a real listing for that exact quantity and logged with the listing named as the source and today's date as the check date, any item with no such listing entered as a flagged placeholder with the reason and no figure, and the check schedule written at the top with the next check date named.
Preview, from the skill itself
“# Materials Price Watch<br># Materials Price Watch An estimate is only as good as the prices inside it, and materials prices do not sit still.”
Version 1.0.09 filesPrices checked by exact quantityEvery check dated and sourcedGaps flagged, never filledHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 45041066fa7f… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 34.2 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/fence-and-deck-may-check/WALKTHROUGH.md, examples/roofing-and-lumber-march-check/WALKTHROUGH.md, reference/building-the-watch-list.md, reference/checking-prices-by-exact-quantity.md, reference/marking-figures-for-estimates.md, reference/reading-changes-and-flagging-gaps.md, templates/estimate-price-note.template.md, templates/price-watch-log.template.md
Worked example, from the package
examples/fence-and-deck-may-check/WALKTHROUGH.md
A local service operator who builds and repairs fences and small decks. Five materials sit on the watch list from the purchase records. The list is checked every two weeks. This is the check run on 5 May 2026, against the last check on 21 April 2026, which is 14 days earlier, as the schedule sets.
Crew Timesheet Records
Local Services / Field Operations · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Pay and true job labor cost come off one sheet instead of memory: every crew member's hours are entered per job on the same day, with totals per job and per week worked in the open.
What changes
- A crew week living in the operator's head and in a bank list: a pay figure for each person that nobody can rebuild, and hours split across jobs that were never split on paper → the same week on one sheet anyone can follow, each person's hours entered the day they were worked and split per job
- Job costs that omit the labor it took to earn them → totals per job and per week that agree three ways, and pay and job labor cost worked from those same lines with the rates shown
- A question about pay or about what a job really cost answered at the next job, when it has become an argument → the record answering it in a minute, while it is still a question
Honest fit
For you if: You run a small crew of your own, pay them by the hour, and want pay and true job labor cost to come from one record you can check, not from a rebuilt week.
Skip it if: You run alone with no crew hours to track, or every hand on your jobs is an outside sub paid against an agreement; in that case the subcontractor payment record already does the whole job.
Your first run produces: one complete week sheet for the current week, or the last full week the crew worked: the crew listed by name with the agreed rate for each person exactly as the record holds it, the jobs that week listed from the job records, the hours entered day by day, one line per person per job per day, days off written as days off in words and gaps left named, then the totals per person, per job, and per week worked from the lines and checked three ways, with each pay figure tied to a person, a total, and a rate.
Preview, from the skill itself
“# Crew Timesheet Records<br># Crew Timesheet Records At the end of a busy week, hours are the easiest thing to lose and the hardest thing to rebuild.”
Version 1.0.09 filesHours entered the same dayTotals checked three waysPay worked from the linesHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: cbf0822e8877… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 38.3 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/three-person-crew-one-job-week/WALKTHROUGH.md, examples/two-jobs-split-week-corrections/WALKTHROUGH.md, reference/corrections-gaps-and-missing-days.md, reference/entering-hours-the-same-day.md, reference/rates-pay-and-job-cost.md, reference/totals-per-job-and-per-week.md, templates/job-hours-summary.template.md, templates/weekly-timesheet.template.md
Worked example, from the package
examples/three-person-crew-one-job-week/WALKTHROUGH.md
A local service operator with a crew of three on one job for a full week, Monday to Friday: a barn repair and cleanout in Oakdale. Every hour was entered on the day it was worked, and the week was closed from that one sheet.
Vehicle and Trailer Checks
Local Services / Field Operations · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Every work trip starts from a signed record instead of a shrug: one standard check of lights, tires, hitch and coupler, and load secured, logged per trip against the job, so a roadside failure or a load question has a record behind it.
What changes
- The pre trip check, if it happens at all, a walk around the rig that leaves nothing behind it → every trip leaving one signed sheet: 15 items marked as found, readings written as measured, and the trip decision stated in plain words against the job
- Nobody able to say later which lights were working on Tuesday, what the trailer tires read, or whether the load a customer asks about was strapped the way the sheet would have shown → faults and fixes on the record with their times, so a roadside failure or a load question meets a record instead of a recollection
- A fault meeting the crew on the road, at the cost of the day → a fault found at the yard as a line on a sheet, with the decision recorded beside it
Honest fit
For you if: You run work trips by truck and trailer, and a roadside failure or a question about a load would today be met by recollection instead of a record.
Skip it if: You need a roadworthiness certificate, a mechanic's repair, or a ruling on legal weight or a vehicle rating; a signed sheet is none of those, and the decision on every sheet is yours, recorded, not made for you.
Your first run produces: one complete sheet for the next real work trip, in about twenty minutes before it leaves: the top block filled from the records with the job the trip serves, the vehicle, the trailer if one is going, and who is running the check, then the rig walked once, slowly, in the sheet's order, with the tire pressures the vehicle maker states and the ball size the coupler is marked for written on the sheet itself, all 15 items marked, and the result and decision recorded and the sheet filed against that job's record.
Preview, from the skill itself
“# Vehicle and Trailer Checks<br># Vehicle and Trailer Checks A trailer light that was dark all week, a tire that was soft for three trips, a coupler that was never quite latched: none of these announce themselves at the yard.”
Version 1.0.09 files15 items, every tripSigned against the jobFaults recorded with timesHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 74d2fd5195cf… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 34.6 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/clean-check-haul-to-job/WALKTHROUGH.md, examples/failed-light-held-at-yard/WALKTHROUGH.md, reference/hitch-coupler-and-safety-chains.md, reference/lights-tires-and-running-gear.md, reference/load-secured-and-ready-to-roll.md, reference/when-a-check-fails.md, templates/check-log.template.md, templates/trip-check-sheet.template.md
Worked example, from the package
examples/clean-check-haul-to-job/WALKTHROUGH.md
A solo operator, Dale, running a pickup and a single axle utility trailer to a fence repair job in Harriman on Tuesday 14 April 2026. One trip, one sheet, every item passing.
Data Entry Verification
Data, Files, and Research · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Hand-typed records earn trust before later work stands on them: every field gets a second pass against its source, mismatches are listed by field, corrections come from the source only, and anything that cannot be read is flagged, never guessed.
What changes
- A set of hand typed records going straight into use, trusted because the typing looked careful → the same set carrying a mark for each record that says whether it was actually checked
- Its slips surfacing later as work done to the wrong value: a quantity ordered short, a date missed, a letter sent to a misspelled name → mismatches listed by field, and corrections that trace to the source and to nothing else
- A field the source cannot settle quietly guessed → that field flagged openly, so trust in the records is a state each record earned, or openly did not
Honest fit
For you if: Later work stands on records typed by hand from notes, cards, or forms, and nothing says which of them were ever checked against their sources.
Skip it if: You need the source itself judged right, a faint value settled between two readings, or records checked that were produced by a system transfer with no hand typing in them; live records change only after you read the sheet and approve it.
Your first run produces: one verification sheet for one small set of hand typed records, twenty to fifty, taken with the source documents they were typed from: the records and the sources laid side by side in the same order, the fields to be checked named at the top of the sheet, the set worked record by record with each field compared to its source, each mismatch logged by field as it is found, each correction copied from the source only, and any field the source cannot settle flagged with its reason, the counts reconciled at the end.
Preview, from the skill itself
“# Data Entry Verification<br># Data Entry Verification Records typed in by hand carry the slips of the typing: a digit turned around, a date copied from the line above, a name spelled the way it sounded.”
Version 1.0.09 filesEvery field, a second passCorrections from the source onlyUnreadable fields flaggedHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 22f34dd538bf… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 30.5 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/forty-eight-delivery-notes-stock-sheet/WALKTHROUGH.md, examples/one-hundred-twenty-signup-cards-contact-list/WALKTHROUGH.md, reference/comparing-field-by-field.md, reference/flagging-unreadable-fields.md, reference/mismatch-log-and-corrections.md, reference/source-is-the-authority.md, templates/mismatch-log.template.md, templates/verification-sheet.template.md
Worked example, from the package
examples/forty-eight-delivery-notes-stock-sheet/WALKTHROUGH.md
A small supplier business typed a week of paper delivery notes into its stock sheet by hand, 48 records in all, before the sheet was used to place the next orders. This pass checks those 48 records against the notes themselves before any order stands on them.
Contact List Hygiene
Data, Files, and Research · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
One name means one entry: duplicates are merged with every merge on record, stale entries and conflicting details are flagged for your call with both values kept, and nothing is deleted in silence.
What changes
- The same customer standing in the list three times, with the job history on one copy, the current number on a second, and the address on a third → that customer standing once: one canonical entry holding the history, the number, and the address together
- Each outreach starting by guessing which copy is real → a merge log line showing which entries were combined to build the canonical entry
- Stale entries hiding among live ones, and conflicting details settled by one value quietly winning → stale entries marked with their reasons, conflicts marked with both values showing, and the report showing the starting count, what the merges folded in, and the closing count
Honest fit
For you if: Your contact list holds the same people and businesses more than once, with their details split across the copies, and stale entries hiding among the live ones.
Skip it if: You need entries removed, a conflict between two values settled, or a number checked to see if it still rings; flagged entries wait for your call, both values are kept, and removal is your act.
Your first run produces: one full hygiene pass on the working contact list, or one part of it with at least twenty entries in it: the entries counted and the count written down, a copy sorted by name and by phone number, the groups that look like the same person or business checked group by group, the groups that pass merged with one merge log line per merge, any field where a group disagrees flagged, then the merged list worked for stale entries, each flagged with its reason, and the canonical list and hygiene report held for your approval, with no entry removed.
Preview, from the skill itself
“# Contact List Hygiene<br># Contact List Hygiene A working contact list drifts.”
Version 1.0.09 filesOne name, one entryEvery merge on recordConflicts flagged, both values keptHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: e4f711398257… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 39.8 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/small-contractor-list-cleanup/WALKTHROUGH.md, examples/supplier-and-customer-list-cleanup/WALKTHROUGH.md, reference/building-the-canonical-entry.md, reference/finding-duplicates-without-guessing.md, reference/merging-and-the-merge-record.md, reference/stale-entries-and-conflict-flags.md, templates/hygiene-report.template.md, templates/merge-log.template.md
Worked example, from the package
examples/small-contractor-list-cleanup/WALKTHROUGH.md
A one crew contractor keeps a working contact list of customers, suppliers, and rental yards in one file. The list has grown by entry after entry for two years, with no pass ever made over it. The operator sets a stale line for this pass: no contact noted in the last 18 months counts as stale evidence where an entry holds contact notes at all.
Incident Postmortem Writing
Studio / Publishing · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A closed incident gets one true account instead of two memories: the timeline built from the record and the logs as they actually ran, what held and what failed in plain words, and every fix carried out with an owner, a date, and the check that will show it landed.
What changes
- A closed incident settled by whoever recalls it best, with the record thin and the logs scrolling away → one account that can be checked: the timeline showing the incident as it ran, with its gaps named
- Fixes agreed in the room held in memory alone, so the same fault can return with nobody able to say whether it was dealt with → the fixes leaving the room as a list with an owner, a date, and a check on each line
- Each new account a fresh telling, and the tellings drifting apart → what held and what failed each resting on a source a reader can open, so a later reader can tell what landed, what is late, and what was never more than an intention
Honest fit
For you if: A service incident has closed and you need one true account of what happened and what will change, built from the record and the logs rather than from memory.
Skip it if: The incident is still live and you need updates drafted while it runs, or the incident was an agent's behaviour to review; this skill starts only once a service incident has closed, and it fixes nothing itself.
Your first run produces: one short postmortem for the most recent closed incident you have, however small: the sources gathered first, the incident record, the logs for its window, and the messages that went out while it was live, with any missing source written down as a gap, the timeline built one line per event with its time and its source, what held and what failed sorted against those lines, two fixes drafted with an owner, a date, and a check each, and the whole draft read back against the sources line by line and held for your approval.
Preview, from the skill itself
“# Incident Postmortem Writing<br># Incident Postmortem Writing An incident closes.”
Version 1.0.09 filesOne account, checked against sourcesTimeline with its gaps namedFixes with owners, dates, and checksHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 1be041173f08… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 55.1 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/checkout-timeout-postmortem.md, examples/upload-limit-postmortem.md, reference/building-the-timeline.md, reference/fixes-with-owners-and-dates.md, reference/sources-gaps-and-plain-words.md, reference/what-held-and-what-failed.md, templates/fix-list.template.md, templates/postmortem.template.md
Worked example, from the package
examples/checkout-timeout-postmortem.md
A small online craft shop, run by a two person studio, sells through a hosted checkout. On 14 May the payment step of that checkout began timing out for shoppers. The incident closed the same morning. This is the postmortem as it was written the next day, 15 May, from the incident record and the checkout log: how the sources were gathered, how the timeline was built, how held and failed were sorted, and the fixes that came out of it, with the check pass at the end.
Agent Workload Balancing
Agent Operations · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Work stops piling onto one agent while another sits idle: the overloaded and the underused are read from the capacity record, each move is proposed with its reason and approved before it happens, and the result is checked against what the move promised.
What changes
- Work shifting in passing, handed over in a message, with nobody writing down how much moved or why that agent was picked → each shift starting from the capacity record, with the overloaded agent and the agent with room named in figures
- The first queue falling for a day and rising again, and the second agent slowing for a reason nobody can trace → the move proposed with its reason and approved before any work goes, counted on both sides
- The next busy week starting from the same uneven place → the result checked against what the move promised, and a move that failed read before the next one is proposed
Honest fit
For you if: Work piles onto one agent while another sits idle, and you hold a capacity record the moves can be read from.
Skip it if: There is no capacity record yet; this skill acts on that record and does not rebuild it, and it never moves work or changes routing on its own.
Your first run produces: one balance worked from reading to check, on the fleet as the capacity record shows it now and the one queue that is growing: the record read for which agent is overloaded and which agents have room below their limits, one move proposed with the work, the count, both agents, and the reason in figures, the move carried out only after your approval is noted, counted on both sides, and a check date set on the plan.
Preview, from the skill itself
“# Agent Workload Balancing<br># Agent Workload Balancing A fleet rarely falls behind evenly.”
Version 1.0.09 filesOverload read in figuresEach move proposed and approvedResult checked after the moveHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: e1ccd049fa31… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 42.6 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/overloaded-lookup-agent-relieved-by-two-moves/WALKTHROUGH.md, examples/peak-week-rebalance-that-held-quality/WALKTHROUGH.md, reference/balance-terms-and-counts.md, reference/checking-a-move-after-it-happens.md, reference/proposing-and-approving-a-move.md, reference/reading-the-capacity-record-for-moves.md, templates/balance-plan.template.md, templates/move-proposal.template.md
Worked example, from the package
examples/overloaded-lookup-agent-relieved-by-two-moves/WALKTHROUGH.md
A small operation ran three agents that all did the same kind of work: order lookups. One unit of work was one lookup completed, counted from the lookup log, with arrivals counted at entry to the same queue. Each queue was counted at close of day. The three agents were called Ari, Bea, and Cato in the fleet records. This is how one growing queue was read from the capacity record, moved under three approved proposals, and checked a week later.
Third-Party Skill Watch
Agent Safety and Governance · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A third-party skill your fleet depends on never changes under you unnoticed: every package sits in a pinned register, checked against its source on a schedule, and each update is reviewed file by file against the pinned copy before anyone adopts it.
What changes
- Third-party updates landing like weather, running in the fleet before anyone can say what changed → every dependency on one register with its pinned version, its source, and its reach in plain words
- A widened reach sitting in place for months because no single record holds the pins side by side → each update reviewed file by file against the pinned copy on a schedule, with a change to what a package may touch leading its review
- Holds and adoptions happening by drift → adoptions one package at a time with the way back kept whole, and a package that waits doing so for a written reason, revisited at the next pass
Honest fit
For you if: Your fleet depends on skills other people wrote, and an update to one of them could change its behaviour or widen its reach without you noticing.
Skip it if: You need a package read once before the fleet takes it on at all; that first read is vetting, and this watch begins after a package is already in the fleet.
Your first run produces: the register built for the fleet as it stands and one real check run before you stop: every third-party skill the fleet depends on listed from the installed copies with its source, pinned version, and reach, each entry checked against its source listing for an update waiting, one full review worked on the entry with an update or the one the fleet leans on hardest, and the watch schedule set at the top of the register with the date of the next pass.
Preview, from the skill itself
“# Third-Party Skill Watch<br># Third-Party Skill Watch A fleet rarely runs only what its operator wrote.”
Version 1.0.09 filesEvery package pinned on one registerReach changes lead the reviewNothing unreviewed is adoptedHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 53aac98f58ca… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 50.2 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/a-small-patch-reviewed-and-adopted.md, examples/an-update-held-for-a-wider-reach.md, reference/holds-deferrals-and-retiring.md, reference/reviewing-an-update-before-adoption.md, reference/the-dependency-register.md, reference/watch-cadence-and-sources.md, templates/dependency-register.template.md, templates/update-review.template.md
Worked example, from the package
examples/a-small-patch-reviewed-and-adopted.md
An illustrative internal example. All package names and versions in this walkthrough are invented for the example. They are not claims about real packages or real publishers.
Release Candidate Freeze
Studio / Shipping · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
The build that ships is the build that was checked: one named candidate is frozen with what is in and what is held out both written down, and a late change gets in only through a written exception the operator approves.
What changes
- The candidate whatever the last build happened to gather, and held out work whatever nobody mentioned → one named candidate frozen, with the in list and the held out list side by side and their counts reconciled
- A late change judged by how loudly it is asked for → a late change getting in only through a written exception the operator approves, with the refused ones on the record with the same care
- What was in a release settled by an afternoon of asking around, ending in two versions of the story → the same questions settled from one record, so the build that ships is the build that was checked, or the record says where that stopped being true
Honest fit
For you if: A release is close and the candidate keeps moving in its last days, so what ships may not be what was checked.
Skip it if: You need the gate checks themselves run, or the changelog written; this skill holds the candidate still while those run and decides nothing about what deserves to ship.
Your first run produces: one freeze for the next real release on your calendar, however small: the freeze record opened with the product, version, candidate build, and window dates, every item on the change list sorted as in the candidate or held out with a reason and a next home, both lists counted and the opening count reconciled against the change list total, the checks for the window named on the record, and the exception route written down where your team will see it.
Preview, from the skill itself
“# Release Candidate Freeze<br># Release Candidate Freeze In the last days before a release, the candidate keeps moving.”
Version 1.0.09 filesNamed build, written listsLate changes by written exceptionCounts reconciled on the recordHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 11297c65d88e… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 49.3 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/freeze-with-one-admitted-and-one-held-out.md, examples/freeze-with-one-approved-late-fix.md, reference/closing-and-lifting-the-freeze.md, reference/freeze-record-fields.md, reference/the-exception-route.md, reference/what-counts-as-in-or-held-out.md, templates/freeze-record.template.md, templates/late-change-exception.template.md
Worked example, from the package
examples/freeze-with-one-admitted-and-one-held-out.md
A three person team ships Trail Log, a phone app for recording hikes. Release 1.9.0 was planned for Friday 12 June 2026. The founder is the operator, the team's release lead is the keeper, and one builder looks after the app's startup and record screens. The team had run two freezes before this one. This window is the first where a late change was refused, and the refusal is the part of the record the team now points new joiners at.
Visual Evidence Records
Data, Files, and Research · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A screenshot kept as evidence still means something a month later: every capture is logged at the time with what it shows, when it was taken, and which build or record it belongs to, and filed against the record it supports.
What changes
- A questioned picture settled by whoever kept it, sitting in a thread under a file name that says nothing → each capture on one entry: what it shows, when it was taken, and the build or record it belongs to, with the original file
- Nobody able to say which build a screenshot came from, and the same claim argued again the next time it comes up → captures filed against the record they support, so a reader who was not there can say what the set proves and what it does not
- The answer resting on recall after an afternoon of asking around → the argument moved from whose memory is better to what the frames hold
Honest fit
For you if: Screenshots or recordings are kept as evidence for bug reports or job records, and a month later nobody can say what one shows, when it was taken, or which build it belongs to.
Skip it if: You need photographs of physical work on site, or a ruling on whether a claim is true; this record holds what a frame shows, and it widens nothing past the frame.
Your first run produces: the record started for one kind of work where pictures are already taken and later argued about: the index opened with its scope line naming which records captures are filed against, the next real case inside that scope logged capture by capture as taken with what each shows, when it was taken, and the build or record it belongs to, each original filed under the naming method, and the set read back as a stranger would read it before the check schedule is set.
Preview, from the skill itself
“# Visual Evidence Records<br># Visual Evidence Records A screenshot is easy to take and hard to trust later.”
Version 1.0.09 filesOne capture, one entryOriginal kept as takenSays what it does not showHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: e06b4ea2893b… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 48.4 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/bug-report-checkout-failure/WALKTHROUGH.md, examples/job-record-delivery-dispute/WALKTHROUGH.md, reference/capture-log-fields.md, reference/checking-and-correcting-records.md, reference/naming-and-filing-captures.md, reference/what-makes-a-capture-trustworthy.md, templates/capture-log-entry.template.md, templates/evidence-index.template.md
Worked example, from the package
examples/bug-report-checkout-failure/WALKTHROUGH.md
A small online craft shop ran its shop app on build 3.2.0. On the morning of 4 March a tester working a routine checkout found the total on the checkout screen did not match the cart. The shop kept an evidence index for bug reports, kept by the shop owner. Captures for a bug were filed against the bug report they supported, with one entry per capture. This is how the set for one bug was built, and how it settled the question asked about it fifteen days later.
Bulk File Conversion
Data, Files, and Research · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A pile of files changes format without losing any in silence: the batch runs under a written plan the operator approved, every failure is listed by name, the counts in and out are reconciled, and the originals stay untouched until the batch is signed off.
What changes
- A bulk move judged by the folder it leaves behind, full looking and taken as complete → completeness proved by arithmetic, with the counts in and out on the batch record and reconciled
- A file that failed leaving no trace, and a converted file that lost its figures looking the same as one that kept them → every failure listed by name with its reason, and spot checks against the originals testing what the plan said must survive
- The originals already gone when the first gap is found → the originals sitting untouched until you have read the record and approved the batch, so a wrong conversion has a way back
Honest fit
For you if: A pile of files has to change format, and losing some of them in silence, or losing figures inside them, would only surface when someone needs the file.
Skip it if: You need a damaged file repaired, a format chosen for you, or a promise that a converted file is the same as its original; the plan names what may change, and damaged files go on the failure list for your call.
Your first run produces: one small batch converted in one sitting, twenty to thirty files of one kind from one place: the batch counted and listed by name, the plan written and approved before any file moves with the formats, the tool, and what must survive the move named, the run worked in plan order with each outcome written into the batch record as it lands, every failure listed by name, the counts reconciled, and a spread of converted files spot checked against their originals while the originals sit untouched.
Preview, from the skill itself
“# Bulk File Conversion<br># Bulk File Conversion A batch of files has to change format.”
Version 1.0.09 filesEvery failure listed by nameCounts reconciled on the recordOriginals untouched until sign offHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: bf36b5f5c12b… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 46.6 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/course-handouts-doc-to-pdf/WALKTHROUGH.md, examples/supplier-invoices-pdf-to-sheet/WALKTHROUGH.md, reference/failures-spot-checks-and-reconciliation.md, reference/formats-and-what-conversion-can-lose.md, reference/originals-approval-and-handover.md, reference/writing-the-conversion-plan.md, templates/batch-record.template.md, templates/conversion-plan.template.md
Worked example, from the package
examples/course-handouts-doc-to-pdf/WALKTHROUGH.md
A small training provider held its course handouts as word processor files, most of them written years earlier in an old format the current tools read poorly. The handouts needed to go to learners as PDF files, one PDF per handout, with the pages, the tables, and the diagrams intact. The operator named the tool, approved the plan, and held the originals decision. This is how the batch ran in two passes and still reconciled to one count.
Quote Expiry and Renewal
Local Services / Sales · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A lapsed quote never quietly comes back at a stale price: every quote carries an honest expiry date, and when one lapses the renewal is rebuilt line by line from your current price record and held for your approval, with the new figure and the change shown in the open.
What changes
- Quotes drifting, some with no date at all and some with a span copied from the last quote → every quote carrying an honest expiry date the operator can explain, and every lapse a dated fact in one log
- A customer coming back weeks later and pointing at the old total, leaving you to honour a stale figure or have an awkward talk with nothing on record → the old figure kept on record as history, and never quietly the price again
- A lapsed quote quietly coming back at the old price → the renewal rebuilt line by line from your current price record, with the change against the old total shown in the open and a new date on its face, held for your approval
Honest fit
For you if: You send quotes that lapse in silence, and a customer can come back weeks later pointing at a stale total.
Skip it if: The quote still stands and you want a reply chased; this skill starts only once the date has passed, and it sets no prices and sends nothing itself.
Your first run produces: one lapsed quote handled from a clean record, in about thirty minutes: the oldest quote past its expiry date with no answer read as sent, the channels checked for any late reply, the quote entered in the expiry log and closed as expired with the lapse date, each renewal line rebuilt from the current price record, and one renewal draft held for you with the new total worked in the open, the change against the old total shown, and a new expiry date written down.
Preview, from the skill itself
“# Quote Expiry and Renewal<br># Quote Expiry and Renewal A quote is a price held for a short time, not a price held for ever.”
Version 1.0.09 filesHonest expiry date on every quoteLapse logged as a dated factChange shown in the openHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: ca58f79adbed… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 34.7 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/fence-repair-renewal-after-a-rise/WALKTHROUGH.md, examples/porch-step-renewal-that-closed/WALKTHROUGH.md, reference/closing-and-recording-expired-quotes.md, reference/rebuilding-the-renewal-from-current-prices.md, reference/setting-an-honest-expiry-date.md, reference/writing-the-renewal-note.md, templates/quote-expiry-log.template.md, templates/renewed-quote.template.md
Worked example, from the package
examples/fence-repair-renewal-after-a-rise/WALKTHROUGH.md
A local service operator who repairs fences and gates. A customer, Dale Harper, asked for a price to repair a side fence: four posts to reset, a run of boards to replace, and the ground made good. This example follows the quote from its expiry date, through its lapse in silence, to a renewal rebuilt from current prices and accepted by the customer.
Job Cancellation Handling
Local Services / Sales · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A cancelled job ends as a finished record instead of a standing dispute: the deposit is settled exactly as the written terms say, every materials line is accounted for, the refund is worked in the open, and the customer gets a plain way back.
What changes
- A cancellation handled in the moment, on the phone, with a deposit outcome quoted from memory → the deposit settled exactly as the written terms say, with the settlement worked in the open
- A materials cost given as one figure nobody can check, and a slot staying blocked because nobody closed the job out → every materials line accounted for, the slot released on a named date, and the job ending as one finished record
- Nothing on paper to answer with if the customer questions it a week later → a closing note the customer can read and keep, with the figures from the record and a plain way back already in it
Honest fit
For you if: Jobs cancel after deposits are taken and materials are bought, and the settlement today rests on memory and a phone call.
Skip it if: There are no written cancellation terms on the job record to settle from, or the customer contests the close out formally; the record flags the gap and waits, and disputed cases go to you.
Your first run produces: one close out for the first job that cancels after you take the skill on, in about thirty minutes: the job file pulled with the customer, the work, the slot, the total, and the deposit copied from the record, the written cancellation terms copied onto the close out record in full, every material bought for the job listed one line per item and marked as the operator confirms, and the settlement worked in the open, held with a draft closing note and its rebook path for your approval.
Preview, from the skill itself
“# Job Cancellation Handling<br># Job Cancellation Handling Jobs get cancelled.”
Version 1.0.09 filesTerms copied in fullSettlement worked in the openPlain way back for the customerHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: b5b40bc6966c… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 33.1 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/fence-build-cancelled-after-materials/WALKTHROUGH.md, examples/roof-valley-repair-cancelled-early/WALKTHROUGH.md, reference/accounting-for-materials-bought.md, reference/reading-the-written-terms.md, reference/releasing-the-slot-and-offering-rebook.md, reference/working-the-settlement-figures.md, templates/cancellation-close-out-record.template.md, templates/cancellation-note-to-customer.template.md
Worked example, from the package
examples/fence-build-cancelled-after-materials/WALKTHROUGH.md
A local operator who builds garden fences. A fence job is booked, materials are bought for it, and the customer then cancels. This is the close out worked from that job record, with the materials list settled line by line.
Year-End Money Packet
Local Services / Money · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Year-end stops being a rebuild from scraps: the year's income by source, expenses by class, and vehicle totals are assembled into one packet with every total worked in the open and every gap named as a gap, ready to hand to your accountant.
What changes
- The year end answer a hurried rebuild: totals from memory, receipts counted from a pile, vehicle miles guessed from habit → the year in one packet, with income by source, expenses by class, and vehicle totals each traced to a named record
- The missing weeks smoothed over so the sheet looks finished, with nobody able to tell which figures came from a record → every total worked in the open and each gap standing on its own list, with no figure invented to cover it
- An accountant left guessing which lines the records support → a packet another person can follow: what the records support and what they do not, ready to hand over
Honest fit
For you if: The year's money record is spread across job records, receipts, and a vehicle log, and year end means rebuilding it from scraps for your accountant.
Skip it if: You need tax advice, a filing position, or a missing amount estimated; the packet assembles records only, names its gaps, and sends nothing anywhere.
Your first run produces: one packet for the last finished year, built in one sitting set aside for it: the record index listed month by month across job records, payment records, expense records and receipts, and the vehicle log, with any month holding no records written on the gap list before any totals are built, then income by source, expenses by class, and vehicle totals built in that order, each section total worked in the open as it is finished, and the packet held for your approval.
Preview, from the skill itself
“# Year-End Money Packet<br># Year-End Money Packet At the end of the year the money record for a small operation is usually spread across the whole year and the whole truck: job records in one place, payment notes in another, receipts in envelopes, a vehicle log in a notebook, and a few weeks that live nowhere but memory.”
Version 1.0.09 filesOne packet for the yearTotals worked in the openReady to hand to your accountantHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: b67eee30a76c… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 41.2 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/firewood-and-hauling-mixed-records-packet.md, examples/solo-yard-operator-full-year-packet.md, reference/gathering-the-year-records.md, reference/income-by-source-and-expenses-by-class.md, reference/naming-gaps-and-staying-inside-the-records.md, reference/vehicle-totals-from-the-log.md, templates/gap-and-handover-note.template.md, templates/year-end-packet.template.md
Worked example, from the package
examples/firewood-and-hauling-mixed-records-packet.md
An operator who sells firewood deliveries, does hauling and dump runs, and takes tree and brush work when it comes. The records for the year 2025 are uneven: strong in spring and fall, thin in summer, with a second truck used for one week in August and no log kept for it. The packet is built in January 2026 from the records as they stand. It does not smooth the uneven parts away. Income is grouped by line of work, as the job records name it.
Dump and Disposal Runs
Local Services / Field Operations · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Disposal stops being the cost that lands nowhere: every run is planned from the job records, the fee is taken from the site receipt, and each job's share is filed on its own record so the job lines add back to the receipt total.
What changes
- A disposal run living in the truck, with material from two or three jobs riding together and the receipt in a pocket → each run on one record written around the day it happened: what each job put on the trailer, where the load went, and the fee as the receipt states it
- The fee landing on whichever job was finished that day, whether its debris was most of the load or none of it → a share for each job worked in the open from a basis set before the fee was known, so a job that sent nothing carries no disposal fee
- Disposal a loose cost nobody can place → each job record showing what taking its debris away actually cost, with the job lines adding back to the receipt total
Honest fit
For you if: You haul debris from several jobs together, and the disposal fee today lands wherever the day ends rather than on the jobs that filled the load.
Skip it if: You need the site chosen, a ruling on what a site will take, or a price set for the customer; the record holds the receipt fee and its split, and hauling and pricing stay with you.
Your first run produces: one run plan for the next disposal run already coming due, even if it serves a single job, in about twenty minutes: each job the run will serve written from its job record with what that job needs hauled, the site named with anything the operator knows it will not take noted before loading, and, where the run is shared, the split basis written on the plan now, the whole plan held for your approval with nothing loaded from the draft alone.
Preview, from the skill itself
“# Dump and Disposal Runs<br># Dump and Disposal Runs Every cleanup, tear out, and repair leaves something behind: torn off roofing, old fence boards, brush, broken fittings, a shed full of mixed debris.”
Version 1.0.09 filesSplit basis set before the feeShares add back to the receiptPlanned and loaded both writtenHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: ee1fe0a9b7e2… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 33.6 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/shared-run-three-jobs/WALKTHROUGH.md, examples/single-job-roof-tear-off/WALKTHROUGH.md, reference/filing-the-run-against-the-jobs.md, reference/planning-the-run-from-the-jobs.md, reference/recording-the-receipt-and-the-fee.md, reference/splitting-a-shared-run-across-jobs.md, templates/job-disposal-line.template.md, templates/run-plan-and-record.template.md
Worked example, from the package
examples/shared-run-three-jobs/WALKTHROUGH.md
A local service operator finishing three small jobs in the same week: a yard cleanup, a fence tear out, and a shed cleanout. Each job left material behind, none of it a full load on its own. One trailer run served all three on 14 May 2026, planned before loading, with the fee split by load share noted at loading.
Warranty Claims Packet
Local Services / Money · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A warranty claim starts from the paper, not from memory: proof of purchase, the warranty window checked in the open, dated photos of the failure as found, and the claim drafted in the maker's own terms, tracked until it closes.
What changes
- A failure starting an argument from memory, with the receipt in a truck or a drawer and the purchase date near enough → the claim starting with the record: proof of purchase copied from a receipt you can point to, and the window checked in the open before a word is drafted
- The item repaired or taken apart before anyone photographs it, and the claim written in your words against paperwork nobody has open → the failure photographed as found, and the draft speaking in the maker's own terms, asking only for the remedy those terms name
- Weeks passing with no note of what was sent or what was said → the claim on one log, dated step by dated step, until its outcome is written down and filed
Honest fit
For you if: Gear or materials have failed and the claim will rest on a receipt you may not be able to find and a purchase date held in memory.
Skip it if: You need a ruling that a failure is covered, a promise a claim will succeed, or legal advice on a disputed claim; the paperwork states the terms, the maker decides, and the packet presents the facts in order.
Your first run produces: one claim file for the gear and standing materials the business depends on, in about forty five minutes: the receipts, invoices, and item paperwork pulled into one file, each main item listed with its purchase facts copied from its record and its warranty period quoted from its own paperwork or marked unknown, a tracking log started, and, if a failure is live now, its packet built in the same sitting with the window check worked in the open, photos taken as found, and the draft held for your approval.
Preview, from the skill itself
“# Warranty Claims Packet<br># Warranty Claims Packet Gear fails and materials fail.”
Version 1.0.09 filesPhotos of the failure as foundDrafted in the maker's termsTracked until it closesHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: ec522ee9233a… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 40.1 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/circular-saw-motor-failure-claim.md, examples/deck-board-peeling-claim.md, reference/drafting-in-the-makers-terms.md, reference/photos-of-the-failure.md, reference/proof-of-purchase-and-dates.md, reference/tracking-the-claim-to-close.md, templates/claim-packet.template.md, templates/claim-tracking-log.template.md
Worked example, from the package
examples/circular-saw-motor-failure-claim.md
A one person deck and repair operator. The cordless circular saw used on most jobs stops mid cut in September 2026. The claim is built as a packet from the purchase record before the operator speaks to anyone about it.
Form Letter Library
Data, Files, and Research · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
The letters you send again and again stop drifting: each one lives as a checked template that names its purpose and the facts it requires, filled from the record at send time, so no letter goes out carrying a claim you cannot back that day.
What changes
- Repeated letters rebuilt from the last send or from memory, with a total carried over from another job and a date typed from habit → the same letters in one library: each template with its purpose named, its required facts listed with the record that supplies each one, and its claims listed with their backing
- Nobody able to say which lines are still true, with a promise copied forward months after the terms behind it changed → each send filled fresh from the record for that job and checked claim by claim before it leaves
- A fact nobody can source quietly filled in → a missing fact standing flagged until you settle it, so a letter says only what the record backs on the day it goes out
Honest fit
For you if: You send the same few letters again and again, and each one is rebuilt from the last send with lines nobody has checked since.
Skip it if: You need a one off letter written for a case at hand, legal terms settled, or a letter sent without your read; every filled letter here is a draft held for your approval.
Your first run produces: one short library built from letters you have truly sent, even if it starts with only three or four templates, in about forty minutes: the repeated letters listed from past sends, estimates, and job notes, each with its purpose written in one line, one entry built per letter with every required fact named beside the record that supplies it and every claim listed with its backing, any claim with no backing taken out, and one trial fill worked from a current record to prove the fact list is complete.
Preview, from the skill itself
“# Form Letter Library<br># Form Letter Library Most operators send the same few letters again and again: the estimate follow up, the balance note, the schedule change, the completion letter, the welcome note.”
Version 1.0.09 filesPurpose and required facts namedClaims listed with their backingOne current version per purposeHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 804b8bb9d943… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 28.5 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/estimate-follow-up-and-balance-note/WALKTHROUGH.md, examples/schedule-change-and-completion-letters/WALKTHROUGH.md, reference/checking-claims-before-sending.md, reference/filling-facts-from-the-record.md, reference/listing-required-facts.md, reference/naming-each-letters-purpose.md, templates/form-letter-entry.template.md, templates/letter-draft-from-template.template.md
Worked example, from the package
examples/estimate-follow-up-and-balance-note/WALKTHROUGH.md
A small repair operator who fixes porches, steps, and fences. Two letters sit in the library from past sends: Estimate Follow Up and Balance Note. Both were built as entries with their purposes, fact lists, and claims listed before either was used here.
Agent Handover Briefs
Agent Operations · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Every change of run or operator starts from a written brief instead of a cold start: the state as checked, the work done, the decisions made, the open items with a holder and a next step, and what to watch, so nothing has to be re-derived or guessed.
What changes
- A change of hands starting with rebuilding, the new run reading back through chats and records to work out what the last run did and still missing the one item that lived only in the last run's working notes → the same change of hands starting from one page: the state as it stood at the handover, the work already done, the calls already made, the open items with a holder and a next step for each, and the things to watch
- The same opening questions asked at the start of every run → the new run spending its first minutes checking the brief against the records and then working
- An open item falling between two runs because each side thought the other held it, and a decision the last run made made again, the other way, because nothing carried it across → an item able to fall between runs only if the brief shows it doing so, with the holder named
Honest fit
For you if: Work passes from one run or operator to another, and the new run starts by rebuilding what the last one did, decided, and left open.
Skip it if: You need one task handed over as a capsule, the standing record of consequential calls kept, or the work itself done; the brief carries the state at the handover, and the records stay the source each line is checked against.
Your first run produces: one brief at the next handover for one piece of work that changes hands often, in about thirty minutes: an index opened with the scope line written at the top, the first brief written as the current run ends with the state now, the work done, the decisions made, the open items with a holder and a next step for each, and the watch items with the sign for each, any fact no record holds written as not known, and the brief read back by the next run or operator until they can state the state, the open list, and the first step from the brief alone.
Preview, from the skill itself
“# Agent Handover Briefs<br># Agent Handover Briefs Work passes from one run to the next all the time.”
Version 1.0.09 filesState as checked at the handoverOpen items with a holder and a next stepWatch items with the sign for eachHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: e0131c759f94… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 50.8 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/a-weekend-cover-brief-for-a-repair-shop-inbox/WALKTHROUGH.md, examples/an-overnight-run-handed-to-the-morning-operator/WALKTHROUGH.md, reference/brief-fields.md, reference/keeping-and-correcting-briefs.md, reference/reading-a-brief-on-arrival.md, reference/when-to-write-a-brief.md, templates/handover-brief.template.md, templates/handover-index.template.md
Worked example, from the package
examples/a-weekend-cover-brief-for-a-repair-shop-inbox/WALKTHROUGH.md
A small bicycle repair shop had one weekday operator who ran the inbox and the job board, and a cover person who took both over from Friday evening to Monday morning so the shop could answer customers over the weekend. The cover person was good at the work and new to the shop, and for the first weekends they spent Saturday morning reading back through the week's threads to learn which customers were waiting on what. The operator opened a handover index for the Friday and Monday changes of hands. This is brief 14, written on Friday 9 May, the weekend it covered, and the return brief that closed the loop.
Approval Queue Management
Agent Safety and Governance · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Nothing sensitive sits undecided in silence: every pending approval is kept on one record with its age and its owner, and each item ends decided, escalated, or expired on a rule you set, with the queue swept on a schedule.
What changes
- The queue living in heads and inboxes, a held item found when someone trips over it and asks why it never moved → every held item on one page with its ask, its owner, its age, and the date its wait ends
- Items waiting because the owner never saw them looking the same as items the owner saw and set aside → the sweep moving each item forward on a rule you can point to
- Waits ending late, or never, with no record of either → an item that ends undecided ending as expired, in words, on a date, with the person who asked hearing about it
Honest fit
For you if: Sensitive work waits on a yes or a no, and the waits live in heads and inboxes with no age, no owner, and no end.
Skip it if: You need the decision itself made, the held message sent, or owners chased outside the sweep; the queue manages the wait, and the decision and the action stay with their owners.
Your first run produces: one queue built from the queue you have now, in about thirty minutes: the queue opened with its scope line at the top, every place that work currently waits walked, one entry opened per item with what is asked, who asked, who owns it, the date it arrived, its age today, and its expiry rule, and the oldest entry read as a stranger would until what is waiting, who can end the wait, and what happens if they do not can all be said from the entry alone.
Preview, from the skill itself
“# Approval Queue Management<br># Approval Queue Management Work waits for a yes or a no all through the week.”
Version 1.0.09 filesOwner and age on every entryEach item decided, escalated, or expiredQueue swept on a scheduleHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 6187fec23b30… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 41.2 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/a-weekly-sweep-that-cleared-a-backlog/WALKTHROUGH.md, examples/an-item-that-expired-on-its-rule/WALKTHROUGH.md, reference/aging-and-expiry-rules.md, reference/escalation-routes.md, reference/queue-item-fields.md, reference/reviewing-and-clearing-the-queue.md, templates/approval-queue.template.md, templates/queue-item.template.md
Worked example, from the package
examples/a-weekly-sweep-that-cleared-a-backlog/WALKTHROUGH.md
A two person bookkeeping practice used an agent to draft changes to client records: bank details, billing addresses, and contact names. Every change was held for one of the two partners before it was applied. The holds lived in a shared task list with no dates on them. By early September the list held more than forty waiting changes, some of them months old, and neither partner could say which ones were still wanted. On 8 September they opened an approval queue, with one partner as keeper, covering held record changes only. This is how the backlog was entered, aged, and cleared over four sweeps.
Audit Trail Exports
Agent Safety and Governance · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A reviewer who cannot see your live system still gets the full story: your decision and proof trails exported into one dated packet, checked entry by entry before it is shared, with every gap named instead of smoothed over.
What changes
- A check by an outsider starting with access, the reviewer learning a live system and reading records that keep changing while she reads them → the same check starting with a packet: the scope, the period, and the freeze point on the cover
- Calls the reviewer cannot trace settled by asking the people who ran the work what they recall → each call sitting beside the records it rested on, the counts adding up, and the checks that were run written on the page
- A trail going with a retired system, so later questions have nowhere to land → what the packet cannot prove named on its gaps page, in the packet, so no finding has to rest on anyone recalling anything
Honest fit
For you if: Someone outside the day to day work needs to check what your system did, and today that means live access and answers from memory.
Skip it if: You need the calls judged, a thin trail repaired, or a dispute settled; the packet carries the trail with its gaps named, and judging it belongs to the reviewer.
Your first run produces: one small packet first, in about fifty minutes: one system, one short period of two to four weeks, and one named reader, the scope line written, the sources listed before anything is pulled and copied as they stand with the pull time noted as the freeze point, the packet built and its cover counts rebuilt from the pages, three entries picked at random and rebuilt from the packet alone, and a gaps page written naming every entry that could not be rebuilt.
Preview, from the skill itself
“# Audit Trail Exports<br># Audit Trail Exports Sooner or later someone outside the day to day work needs to check what a system did.”
Version 1.0.09 filesScope, period, and freeze point on the coverCounts rebuilt from the pagesEvery gap named on a gaps pageHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 973190cb7b21… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 50.3 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/a-handover-packet-when-the-live-system-was-gone/WALKTHROUGH.md, examples/exporting-a-month-of-approvals-for-an-outside-review/WALKTHROUGH.md, reference/dating-freezing-and-keeping-exports.md, reference/naming-gaps-and-missing-proof.md, reference/packet-contents-and-order.md, reference/proof-checks-before-you-share.md, templates/export-packet.template.md, templates/export-request-and-receipt.template.md
Worked example, from the package
examples/a-handover-packet-when-the-live-system-was-gone/WALKTHROUGH.md
A fictional holiday letting business ran a bookings helper that could change a booking date inside set limits, agree a reply to a guest where the reply followed a standing line, and offer a refund where a stay had fallen short. The helper's trail sat inside a hosted tool the business paid for by the month. In October the owner decided to bring the work in house. The hosted tool would be closed at the end of November, and with it the only copy of the trail, unless a packet was built first. The reader was the owner herself, in her other hat: the person who would answer for the helper's past calls once the tool was gone. This is how the packet was built from what could still be reached, and how its gaps were carried rather than smoothed over.
Release Checklist Runner
Studio / Shipping · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A release stops depending on memory: it runs step by step against its written checklist, each step evidenced and signed off in order, holds named in the open, and one run record kept per release.
What changes
- A release resting on whoever ran it remembering it, with the proof a chat thread and a few times no one wrote down → the same release on one record: each step in order, with its evidence, its sign-off name, and its time
- Nobody able to show a week later which step a problem came from, or whether that step ran at all → a held step showing as held with the decision that followed it, and a step left undone showing as not done, with the reason and the say it went on
- The same snag meeting the same release twice → the next release running from a checklist that has already absorbed the last run's lessons, as a new version
Honest fit
For you if: You put releases out and the proof of what ran lives in a chat thread and in the memory of whoever ran it.
Skip it if: You need the pre-ship build check, a ruling that a release is ready, or the release published for you; the readiness call is yours, made before the run, and each step still goes through its normal route.
Your first run produces: your next release run start to finish against its written checklist, in one sitting: the checklist walked once before anything starts, each step with its done when line and the evidence it will be signed off on, the run record opened with the product, version, date, run lead, and checklist version, each step done in order with its evidence written and signed off with a name and a time before the next starts, and the record closed with a line stating what went out, when, and which steps, if any, stand as not done.
Preview, from the skill itself
“# Release Checklist Runner<br># Release Checklist Runner A release is a chain of small steps done in an order that matters.”
Version 1.0.09 filesSteps run in the order writtenEvidence and sign-off on every stepOne run record per releaseHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: c673ad41712d… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 39.1 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/a-release-held-at-the-announce-step/WALKTHROUGH.md, examples/a-small-app-release-run-in-order/WALKTHROUGH.md, reference/checklist-shape-and-step-evidence.md, reference/closing-and-keeping-the-run-record.md, reference/holds-skips-and-failed-steps.md, reference/running-steps-in-order.md, templates/release-checklist.template.md, templates/release-run-record.template.md
Worked example, from the package
examples/a-release-held-at-the-announce-step/WALKTHROUGH.md
A small team makes an offline maps app for walkers, put out from its own release page. The team had used a written release checklist for its last three releases, held at version 4 with 12 steps. This run, for version 1.8.1, is the first one the checklist held in the open, and it shows what a hold looks like on a run record: what stopped, what did not start, and how the run went on the next day.
Document Version Control
Data, Files, and Research · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Nobody works from the wrong copy again: every living document has one current version named in a register, superseded copies marked and archived, and one change log line for every version.
What changes
- A question about a document settled by hunting copies, the folder holding one text, a colleague a second, and the printed copy saying a third thing → the same question settled from the register, which names the current version
- Working out which text stood on a given date taking an afternoon and resting on who recalls the last edit best → the archive holding the earlier versions with their marks on them, and the change log saying what each version changed, why, and when it took effect
- Old copies staying in live folders and being picked up in good faith months after a price or term changed → a copy found anywhere checked in a minute: its header names its version and its standing, and the register says whether that version stands
Honest fit
For you if: The same living document exists in several copies that disagree, and nobody can say quickly which one stands.
Skip it if: You need the document's content written or improved, a change agreed, or a lost file recovered; the register records the calls once they are made, and the words stay your work.
Your first run produces: one living document brought under control, in about forty minutes: every copy you can find gathered and laid side by side, the text in use today settled from the records, the settled text given the next clean version name with the control header on its face and its first change log line written, each older copy marked as superseded and moved to the archive, and one older copy checked against the register until you can tell from the copy and the register alone whether it stands and what replaced it.
Preview, from the skill itself
“# Document Version Control<br># Document Version Control Some documents are finished once and never touched again.”
Version 1.0.09 filesOne current version named in a registerSuperseded copies marked and archivedOne change log line for every versionHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: f4eb7d3a00e8… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 44.1 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/client-intake-pack-brought-under-control/WALKTHROUGH.md, examples/price-list-corrected-without-losing-history/WALKTHROUGH.md, reference/choosing-what-needs-control.md, reference/marking-and-archiving-superseded-copies.md, reference/version-names-and-numbers.md, reference/writing-the-change-log.md, templates/change-log-entry.template.md, templates/version-register.template.md
Worked example, from the package
examples/client-intake-pack-brought-under-control/WALKTHROUGH.md
A small house cleaning business with two teams used one living document, a four page client intake pack: service terms, a key handling page, a products page, and a booking form. New clients got the pack by email, a printed stack sat in the office, and each team lead carried a copy. In April the two team leads quoted different terms on the same day, one from the printed stack and one from the file in the shared folder, and the owner could not say which copy stood. The owner opened a version register on 5 May, as keeper, with the intake pack as its first and only entry. This is how that first run went.
Meeting Agenda Builder
Agent Operations · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Meetings start from the record instead of from memory: the agenda is built before the meeting from the open items and decisions actually owed, each item with one owner and the decision or input it needs.
What changes
- A meeting built in the first ten minutes of itself, from recall → the meeting built the day before, from the records
- The same items carried week to week with no owner named, and status taking the time that decisions needed → each item naming who owns it and what the room must produce, with status sent out as reading and the minutes adding up
- The hour ending with the owed list unchanged and a new meeting set to do the same again → what was cut sitting on a deferred list the operator agreed, and the next agenda gathered first from the gap between the last agenda and the meeting record
Honest fit
For you if: Your meetings start from recall, carry the same ownerless items week to week, and end with the owed list unchanged.
Skip it if: You need notes taken in the room, minutes written, or the meeting chaired; this skill builds the before record, and what happens in the meeting belongs to the meeting record.
Your first run produces: the next agenda for one recurring meeting whose hour often drifts, built from the record in about thirty minutes: the open items gathered from the source records before any are judged, the items needing no decision dropped into a reading list and ownerless items held on the unowned line, each item that stays written up with its owner, the decision or input needed, its source, and its minutes, and the agenda ordered and timed so the minutes fit the meeting, with what does not fit moved to the deferred list.
Preview, from the skill itself
“# Meeting Agenda Builder<br># Meeting Agenda Builder Most meetings start from memory.”
Version 1.0.09 filesBuilt from the record before the meetingOne owner and one decision per itemMinutes that add upHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: a946f0afca31… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 38.7 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/launch-readiness-meeting-with-decisions-owed/WALKTHROUGH.md, examples/weekly-ops-review-built-from-open-items/WALKTHROUGH.md, reference/agenda-item-fields.md, reference/gathering-open-items-from-the-record.md, reference/timing-and-ordering-the-agenda.md, reference/what-belongs-on-an-agenda.md, templates/agenda-item.template.md, templates/meeting-agenda.template.md
Worked example, from the package
examples/launch-readiness-meeting-with-decisions-owed/WALKTHROUGH.md
Fieldnote is a fictional phone app for site workers to log jobs with photos, built by a fictional four person team. Through the spring the team held a Friday readiness meeting ahead of a planned launch. The early meetings were walk rounds of the build: each person showed what they had finished, the hour passed, and three calls the launch turned on, the launch date, the price page wording, and who would cover support in the first weeks, were still unmade at the start of May. The team lead rebuilt the meeting using this skill. This is the build for Friday 9 May.
Inbox Zero Triage
Data, Files, and Research · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
An inbox worked in full passes stops being a pile: every message lands in one of four buckets, act now, file, waiting, or discard, the closing counts add back to the start, and waiting items carry an owner and a follow-up date, so nothing important is quietly dropped.
What changes
- The inbox worked from the top, the newest messages read and the older ones sinking → the same inbox worked in full passes: a starting count, four buckets, and a closing count that accounts for every message in the pass
- Nobody able to say which senders are still waiting on an answer → a waiting list with an owner and a follow up date on every waiting item
- An urgent note hiding under a newsletter because the pass reads only the top of the pile → the pass reading the pile whole, and a message nobody could place standing in act now until the operator settles it
Honest fit
For you if: Your inbox is a pile worked from the top, and nobody can say which senders are still waiting on an answer.
Skip it if: You need replies sent, messages filed or moved for you, or reply promises set with clients; this skill only sorts, logs, and drafts, and acting stays with you.
Your first run produces: the four buckets set up and the first full pass run in the same sitting, in about forty five minutes: a place made for each bucket in the tool you already use, the pass log and waiting list set up from the templates, the inbox counted with the date and time at the top of the log, each message worked in the order it sits and put in exactly one bucket, a short draft held for each act now item that needs a reply, each waiting item listed with its owner and follow up date, and each discard item listed with its reason.
Preview, from the skill itself
“# Inbox Zero Triage<br># Inbox Zero Triage An inbox that never gets fully sorted stops being a work list and becomes a pile.”
Version 1.0.09 filesFour buckets, one per messageClosing counts add back to the startWaiting items carry a follow up dateHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: b7dfd1541687… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 29.7 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/contractor-inbox-monday/WALKTHROUGH.md, examples/freelance-desk-friday/WALKTHROUGH.md, reference/defining-the-four-buckets.md, reference/handling-waiting-and-follow-up.md, reference/keeping-nothing-dropped.md, reference/running-a-triage-pass.md, templates/triage-pass-log.template.md, templates/waiting-list.template.md
Worked example, from the package
examples/contractor-inbox-monday/WALKTHROUGH.md
A small roofing and repairs operator whose work inbox gathers messages over the weekend. The pass runs on Monday morning, 11 May 2026, starting at 8:10 in the morning. The operator runs a pass each Monday and Thursday. Names and messages below are sample material for this example; another operator's log holds their own senders and their own counts.
Recurring Task Scheduler
Agent Operations · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Recurring work stops failing quietly: every job sits on one schedule record with a named owner, a cadence with a due window, and proof of its last run, and any due job with no proof stands marked missed in plain sight.
What changes
- Recurring work living scattered: a job in one person's calendar, a check in a chat thread, a close step in someone's head → the same jobs on one record: each line naming its owner, its cadence, and its due window
- A missed run nobody can name with confidence, because due, owner, and last run sit nowhere side by side → each run leaving a dated proof note, and a missed run visible at the review after it happens, with its due date on it
- A gap surfacing weeks later when it starts to cost something → each review writing the state of every line in plain words, so anyone can point at the record and say what was due, who held it, and when it last ran
Honest fit
For you if: Recurring jobs live scattered across calendars, threads, and heads, and a missed run surfaces weeks later when the gap starts to cost.
Skip it if: You need the jobs run, reminders sent, or one off tasks scheduled; the owners do the work, and this skill keeps the schedule and the proof trail those runs rest on.
Your first run produces: the first schedule record built and the first proof notes filed in the same sitting, in about forty five minutes: the jobs that truly repeat named from the task lists, calendars, and run notes, each job written with what a finished run leaves behind, its owner, its cadence, and its due window, each last run settled from a dated proof note on file or written as NO PROOF ON FILE where none can be found, and the first review date written at the top.
Preview, from the skill itself
“# Recurring Task Scheduler<br># Recurring Task Scheduler Recurring work fails quietly.”
Version 1.0.09 filesOne line per job on one recordProof of the last run on every lineMissed runs marked in plain sightHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: f226a3d4f748… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 32.8 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/monthly-close-review/WALKTHROUGH.md, examples/weekly-ops-checks-review/WALKTHROUGH.md, reference/building-the-schedule-record.md, reference/cadences-and-due-windows.md, reference/last-run-proof-and-gaps.md, reference/reviewing-missed-runs.md, templates/run-proof-note.template.md, templates/schedule-record.template.md
Worked example, from the package
examples/monthly-close-review/WALKTHROUGH.md
A small fictional training provider, Alder Creek Training, with five recurring jobs on one schedule record. Monthly close jobs are read at a monthly review, and the weekly and set day jobs among them are read at the same sitting for the span the review covers. This is the review run on Friday 5 June 2026, covering the runs due from Friday 29 May 2026 to Wednesday 3 June 2026, which is the span the May close falls in.
Price List Maintenance
Local Services / Money · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Your quotes stop resting on memory: your own sell prices for services sit on one written list reviewed on a set cadence, with every change dated and carrying its reason, so each new quote draws from the one current price.
What changes
- Prices inside quotes resting on whenever the quoting habit was formed: a figure remembered from an old job, copied from quote to quote, with no date and no reason → the same services on one written list: each price in its unit, dated, with one current figure per service
- Nobody able to say when a price was set, or why, or whether you would set it the same way today → each change logged against the last price with its reason, and each review closed on a set cadence with the next one named
- A price nobody has settled quietly appearing in a quote → the service waiting off the list until you set its price and give it a line, so each new quote draws from the one current price
Honest fit
For you if: Your quotes rest on prices held in memory, copied from quote to quote, with no date and no reason behind any of them.
Skip it if: You need prices set for you, buy prices or supplier costs tracked, or quotes written and altered; every price is your call, and this skill keeps the written record of the prices you settle.
Your first run produces: the first list built and the first review held in the same sitting, in about forty minutes: the services you sell again and again named from past quotes and job records, each written with its unit, a short scope note, and the price the records show was last charged, each line then settled at the review as holds, changes, added, or no longer offered, every change logged with its reason in your own words, and the review cadence and next review date written at the top.
Preview, from the skill itself
“# Price List Maintenance<br># Price List Maintenance A quote is only as steady as the price list behind it, and a price list held in memory is not a list at all.”
Version 1.0.09 filesOne current price per serviceEvery change dated with its reasonReviewed on a set cadenceHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: edc593298c41… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 33.3 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/midyear-update-hauling-and-repairs/WALKTHROUGH.md, examples/quarterly-review-yard-care/WALKTHROUGH.md, reference/building-the-price-list.md, reference/recording-changes-with-reasons.md, reference/setting-the-review-cadence.md, reference/using-the-list-in-quotes.md, templates/price-change-log.template.md, templates/price-list.template.md
Worked example, from the package
examples/midyear-update-hauling-and-repairs/WALKTHROUGH.md
A fictional local service operator who does hauling runs and small repair work. Four services sit on the price list from past quotes and job records, and the list is reviewed twice a year. This is the review held on 7 July 2026, against the list as it stood from the review on 6 January 2026. At this review one service is added and one is marked as no longer offered.
Customer Offboarding Pack
Local Services / Sales · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A customer relationship ends as a finished record instead of an open thread: the final account settled with the arithmetic shown, records handed over on a dated list, standing arrangements closed with end dates, and a plain closing note drafted for your approval.
What changes
- Endings happening by drift: the work stops, and the account, the records, and the arrangements are left wherever they were → the same ending in one finished record, filed whole
- The last invoice maybe settled and a key maybe returned, with none of it written down → the final account worked in the open from the job records, the handover named on a dated list, and each arrangement closed with its end date
- Every later question starting from memory and ending in an argument about what was agreed → the closing note filed as sent, so the ending is a record you can point to, line by line
Honest fit
For you if: Customer relationships end by drift, with the final account, the handover, and the standing arrangements left wherever they were.
Skip it if: You need legal or tax advice, payments chased or taken, or a formal settlement document; the closing note is a plain courtesy record of an ending, and settling the money stays with you.
Your first run produces: one customer whose work has ended closed whole, in about thirty minutes: the customer file and job records opened and the final balance worked in the open on the checklist, any line no record settles carried as an open line with the reason written down, the handover list built with what the customer gets back and what you keep and why, every standing arrangement listed with its end date or marked open with its next step, and a plain closing note drafted from the template and held for your approval.
Preview, from the skill itself
“# Customer Offboarding Pack<br># Customer Offboarding Pack Work ends in all kinds of ways.”
Version 1.0.09 filesFinal account worked in the openHandover on a dated listArrangements closed with end datesHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: b0f042e1f2da… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 31.0 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/landscaping-season-close/WALKTHROUGH.md, examples/regular-cleaning-close/WALKTHROUGH.md, reference/closing-access-and-standing-arrangements.md, reference/handing-over-records-and-deliverables.md, reference/settling-the-final-account.md, reference/writing-the-closing-note.md, templates/closing-note.template.md, templates/offboarding-checklist.template.md
Worked example, from the package
examples/landscaping-season-close/WALKTHROUGH.md
A small landscaping operator, Creekside Lawn and Garden, closing out a household customer, Mr. Delaney, after one season of mowing and garden care. The family is moving away at the end of October 2026. The last visit was 9 October 2026, and the ending was worked and filed on 14 October 2026.
Tax Document Gathering
Local Services / Money · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Year-end stops being a search: tax documents are filed into one indexed folder as they arrive all year, a monthly sweep names anything missing while it can still be found, and the handover to your accountant is the folder itself. It organizes documents only and gives no tax advice.
What changes
- The year's tax documents living wherever they landed: receipts in the truck, statements under newer mail, forms in a drawer, and a few papers nobody can place → the same documents in one folder, filed by class as they arrived, with one index
- January as a search, and the accountant getting whatever the search found → the index saying what is in the folder, what was expected and has not arrived, and what is simply gone
- A missing form turning up, or not, weeks after it mattered → a monthly sweep naming anything missing while it can still be found, and the year-end job becoming a handover: folder, index, open items, questions
Honest fit
For you if: Tax documents arrive all year and land wherever they land, so year end becomes a search and your accountant gets whatever the search found.
Skip it if: You need tax advice, a return prepared or filed, or totals worked out for the year; it organizes documents only and gives no tax advice, and the handover to your accountant is your own act.
Your first run produces: the folder and the index set up and everything that has arrived so far this year gathered in the same sitting, in about forty five minutes: one folder made with its class list written at the front, the index started with the folder's home, the class list, and the sweep schedule at its head, each document in hand filed under its class with one index line written from the document itself, the expected list written as open items from last year's sources, and the first monthly sweep date set about a month out.
Preview, from the skill itself
“# Tax Document Gathering<br># Tax Document Gathering Tax documents do not arrive at year end.”
Version 1.0.09 filesFiled on arrival, all yearOne index for the whole folderMonthly sweep names what is missingHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 917ae9d0918f… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 45.2 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/full-year-lawn-and-cleanout/WALKTHROUGH.md, examples/midyear-shoebox-start/WALKTHROUGH.md, reference/document-classes-and-labels.md, reference/filing-on-arrival.md, reference/folder-layout-and-the-index.md, reference/monthly-sweep-and-missing-documents.md, templates/document-index.template.md, templates/handover-note.template.md
Worked example, from the package
examples/full-year-lawn-and-cleanout/WALKTHROUGH.md
A one person lawn care and property cleanout operator, working under the name Mercer Lawn and Cleanout. He does the work alone, keeps a vehicle log in a notebook in the truck, and uses an accountant at year end. This is tax year 2025, gathered from a first run on 6 January 2025 to the handover on 30 January 2026.
Social Proof Collector
Creator and Audience · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Praise you already earned stops getting lost or misused: reviews, messages, and comments are gathered into one library with the permission state recorded on each item, so a testimonial goes public only when its record covers that use.
What changes
- Praise living where it landed: a review here, a message there, a comment nobody can find again → the same praise in one library: each item in its exact words, with its source and date
- A page or post reaching for the warmest kind word someone remembers, with no record of who agreed to what → a permission state recorded on each item's own entry, and a public use starting from a check against that record, not from memory
- A private note ending up in public by accident → an item with no covering record held, plainly, with its reason written down, until the record covers the use or another item is chosen
Honest fit
For you if: Kind words about your work sit scattered across reviews, messages, and comments, with no record of what each person agreed to.
Skip it if: You need praise written, reviews asked for, or anything posted; it collects praise that already exists and nothing else, and public use stays with you after a check.
Your first run produces: the first library built from praise that already exists, in about thirty minutes: the reviews, messages, and comments you supply worked through in the order you supply them, one entry made per item with its exact words, who said it, where it was left, the date, and what work it was about, and a permission state set for each entry from the record only, with items the record does not cover set to held and their reasons written in plain words.
Preview, from the skill itself
“# Social Proof Collector<br># Social Proof Collector Praise for good work already exists.”
Version 1.0.09 filesExact words, with source and datePermission recorded on each itemHeld items carry their reasonHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: c93f4fdce327… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 33.8 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/creator-course-feedback/WALKTHROUGH.md, examples/local-workshop-client-notes/WALKTHROUGH.md, reference/checking-coverage-before-any-use.md, reference/finding-praise-that-already-exists.md, reference/keeping-the-library-honest-and-current.md, reference/recording-permission-per-item.md, templates/proof-library-entry.template.md, templates/public-use-check.template.md
Worked example, from the package
examples/creator-course-feedback/WALKTHROUGH.md
A fictional illustration teacher, Mara Ellis, runs a small online drawing course. Over one term, kind words about the course landed in five places. She wants a testimonial section on her course page, built only from praise whose record covers that use.
Multi-Step Job Planner
Agent Operations · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A large job stops failing one unnamed step at a time: the whole job is broken into ordered steps, each carrying what it needs before it can start, who owns it, and a written test for done, kept as one living plan the work is checked against as it runs.
What changes
- A large job living in pieces: the order in one person's head, the status whatever the last message said → the same job as one plan: every step with an owner, an order set by named dependencies, and a done criterion written before the work started
- A waiting step looking the same as a step being worked on → a block visible the day it lands, written early, with the steps it holds up flagged beside it
- Done used at different strengths until the final check finds the gaps all at once → status read from evidence at each check: what is done and how that was known, what is ready next, and which chain of steps sets the finish date
Honest fit
For you if: A large job runs in pieces, with the order in one person's head and done meaning different things to different people.
Skip it if: You need the steps themselves done, people assigned, dates moved, or time and cost tracked; the plan holds the outcome, the order, and the test, and the work itself stays with the step owners.
Your first run produces: the first plan for a real job that is already waiting or already running, in about an hour: the job written in one outcome line a stranger could read, one entry per step with its owner, the steps it depends on, and a done criterion a second person could check, the steps ordered from their dependencies alone, and the first check date set before you stop.
Preview, from the skill itself
“# Multi-Step Job Planner<br># Multi-Step Job Planner A large job rarely fails all at once.”
Version 1.0.09 filesOne plan for the whole jobOwner and done test on every stepBlocked steps flagged earlyChecked against the plan as it runsHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: d4880e28e207… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 51.2 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/help-article-portal-move-in-nine-steps/WALKTHROUGH.md, examples/twelve-lesson-training-pack-built-to-a-plan/WALKTHROUGH.md, reference/keeping-the-plan-current.md, reference/ordering-steps-and-dependencies.md, reference/plan-terms-and-parts.md, reference/writing-done-criteria-that-hold.md, templates/job-plan.template.md, templates/step-entry.template.md
Worked example, from the package
examples/help-article-portal-move-in-nine-steps/WALKTHROUGH.md
A four person support team held 214 help articles in an old folder set and was moving the live ones to a new portal with a different section shape. Two earlier tries had started with the move itself and stalled when articles were found mid move that nobody had counted, mapped, or decided to keep. This time the team planned the job first, in nine steps, and checked the work against the plan twice a week. The names and figures here are a worked example, not a record of a real move.
Failure Mode Drills
Agent Safety and Governance · Version 1.0.0 · 9 files
$19one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Know what your system does in the first minute after a part fails, before a real failure shows you in front of a client: each failure is scripted in advance, run on copies or in a sandbox, and the observed behavior is recorded against the behavior written down before the run.
What changes
- Failure behavior as a rumour: the fallback described when the system was built and never watched running → each failure scripted in advance and run on copies or in a sandbox, with observed behavior recorded beside the behavior written down before the run
- The first real outage doubling as the first rehearsal, in front of the people the work is for → the worst gaps named before a real failure can find them, and fixes proven by rerunning the same script
- Improvisation during an outage, never written down, so the next outage starts from the same rumour → a dated drill record the operator can read from: which steps held, which differed, and where the answer is still only a hope with a drill date on it
Honest fit
For you if: You cannot say what your system does in the first minute after a part fails, and the first real outage would be the first rehearsal.
Skip it if: You need hostile input testing, live monitoring, or the faults fixed; drills rehearse faults on copies only, name the gaps, and leave attacks, alarms, and fixes to their own work.
Your first run produces: the first drill, run on a copy, in about forty five minutes: the record opened for the part whose failure would hurt most this month, one script of six to ten steps with the expected behavior written before the run, the smallest copy built with no route to the live system, the script run once with observed behavior written beside expected as it happens, and the date set for a second drill against a different part.
Preview, from the skill itself
“# Failure Mode Drills<br># Failure Mode Drills Most agent systems are only ever watched while everything they lean on is working.”
Version 1.0.09 filesScripted failures, run on copiesExpected written before the runObserved recorded step by stepFixes proven by rerunning the scriptHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: c6f58d60458e… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 52.5 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/bad-input-batch-at-intake/WALKTHROUGH.md, examples/provider-outage-mid-run/WALKTHROUGH.md, reference/failure-modes-and-expected-behavior.md, reference/reading-drill-results.md, reference/running-on-copies-and-in-a-sandbox.md, reference/scripting-a-drill.md, templates/drill-record.template.md, templates/drill-script.template.md
Worked example, from the package
examples/bad-input-batch-at-intake/WALKTHROUGH.md
A bookkeeping helper agent took in a batch of client files each week, read each file, and filed its rows into a records store. Good weeks had made the intake look solid. The operator wanted to know what one bad batch would do: a batch carrying an empty file, a malformed file, and a file that had already been sent once before. Rather than wait for that batch to arrive in real work, she built it herself, from copies, and ran it through a copy of the intake.
Access Review Cadence
Agent Safety and Governance · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Access stops drifting one quiet grant at a time: every grant a person, an agent, or a connected tool holds sits in one standing register and is rechecked on its due date, then confirmed, narrowed, or revoked on the record, on a fixed rhythm instead of after something goes wrong.
What changes
- Access read only when it is handed out and when something goes wrong → every grant in one standing register, rechecked on its due date on a fixed rhythm
- Grants piling up in silence: seats held by people who left, folders open at a width set for a finished project → each grant confirmed, narrowed, or revoked on the record, with the narrower call winning ties
- The honest answer to who can reach what being that nobody has checked lately → each cycle leaving its calls, reasons, and totals on one page, so the state of access can be shown on an ordinary day
Honest fit
For you if: Grants held by people, agents, and tools have piled up unchecked, and nobody can say which are still used, still needed, or still the right width.
Skip it if: You need a first full inventory of everything an agent can reach, new access handed out, or watching between cycles; this is the recurring rhythm that keeps a known register honest, and changes are made elsewhere.
Your first run produces: the standing register and the first cycle run over it, in about an hour: one line per grant with its holder, what it reaches, its width, its owner, and a first due date, gaps written as not yet known and flagged rather than held back, the cadence chosen for the size of the list, every due grant called confirmed, narrowed, or revoked on the record, and the next cycle date written at the top of the register.
Preview, from the skill itself
“# Access Review Cadence<br># Access Review Cadence A one time look at access goes out of date the week it is finished.”
Version 1.0.09 filesOne register for every grantHolder and owner on every lineCalls recorded, changes elsewhereStale grants end on a reviewHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 521849d7e1d5… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 43.0 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/monthly-cycle-for-a-small-support-team/WALKTHROUGH.md, examples/quarterly-cycle-that-ended-stale-grants/WALKTHROUGH.md, reference/cadence-terms-and-the-register.md, reference/choosing-the-cadence.md, reference/confirm-narrow-or-revoke.md, reference/stale-grants-and-drift-signs.md, templates/grant-review-entry.template.md, templates/review-register.template.md
Worked example, from the package
examples/monthly-cycle-for-a-small-support-team/WALKTHROUGH.md
A four person support team, with one agent handling first replies, kept its access register on a monthly full cycle. The list was short enough to read whole each month, and holders changed often enough that a quarter felt too long to wait. This example follows the first three cycles, and reads the third one in full, in counts.
Incident Severity Grading
Studio / Publishing · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Every incoming incident is graded against one written severity scale, with the grade and its reasons on record and the response target following from the grade, so a fault that stops buyers paying stops sharing a queue with a spelling slip.
What changes
- Order set by arrival and by noise: the last report taken first, a minor fault with a loud reporter outranking a serious one → every incident graded against one written severity scale, with the grade and its reasons on record
- Nobody able to say afterwards why one incident waited and another did not → the response target following from the grade, in words written before the incident arrived
- A fault that stops buyers paying sharing a queue with a spelling slip → the serious fault taken first because the scale says so, and the minor fault's wait a decision on paper rather than an accident of a busy day
Honest fit
For you if: Incidents are taken in arrival order, so a loud minor fault outranks a quiet serious one and nobody can say why one waited.
Skip it if: You need incident messages drafted, a postmortem written, or the fault itself fixed; this grades and sets the target only, and the response work stays with its own skills.
Your first run produces: a first severity scale tested against the record, in about an hour: the scale built with four grades and a response target for each that the team can meet on an ordinary day, three or four closed incidents graded on their own entries using only the facts known when each first arrived, the entries read side by side and the scale adjusted once where the order comes out wrong, and the scale review date set before you stop.
Preview, from the skill itself
“# Incident Severity Grading<br># Incident Severity Grading When incidents arrive with no shared scale, attention goes to whoever reported last, whoever reported loudest, or whoever sounds most worried.”
Version 1.0.09 filesOne written severity scaleGrade and reasons on recordTargets follow the gradeRegrades happen in the openHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 7272c2ecc266… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 37.8 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/morning-when-the-store-went-down-and-a-typo-waited/WALKTHROUGH.md, examples/slow-editor-and-the-loud-print-fault/WALKTHROUGH.md, reference/grading-by-impact-and-reach.md, reference/regrading-and-borderline-cases.md, reference/response-targets-per-grade.md, reference/the-severity-scale.md, templates/grading-entry.template.md, templates/severity-scale.template.md
Worked example, from the package
examples/morning-when-the-store-went-down-and-a-typo-waited/WALKTHROUGH.md
Harbour Lane is a fictional small studio that sells printable planners through its own store page. On a Tuesday morning two reports arrived eleven minutes apart. One stopped every sale the studio could make. One was a misspelled word. This is how both were graded against the same scale, on the same morning, by the same grader, and why the second one waiting was the scale working, not the report being lost.
File Retention Exceptions
Data, Files, and Research · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Records held past their retention period stop being a habit nobody can explain: each approved hold is written down as one exception naming the records it covers, the reason, the owner, and the date it ends, and is reviewed on the day it lapses.
What changes
- Records held past their retention period by habit, with nobody able to explain why → each hold written as one exception naming the records it covers, the reason, the owner, and the date it ends
- Why a hold stands answered from memory → a lookup: the register states the reason and the person who gave it, and the schedule line points to the entry
- Holds ending when someone remembers them, and weak holds granted by a quieter route → each exception reviewed on the day it lapses, logged either way, and a hold that should not stand refused on the record with its reason
Honest fit
For you if: Records are held past their retention period as a habit nobody can explain, with no owner and no end date.
Skip it if: You need retention periods set, changed, or deletion passes run; the schedule does that work, and this register only records stated deviations from it, each with an expiry.
Your first run produces: the first exception register, in about thirty minutes: the schedule where records are most often held past their period read line by line, every current hold found and written down including the informal ones, each hold counted from the store itself and given an owner who states the reason in their own words, holds no owner will stand behind closed and their records put back under the schedule, and each real hold entered and put to the operator for approval as written.
Preview, from the skill itself
“# File Retention Exceptions<br># File Retention Exceptions A retention schedule states how long each record type is kept.”
Version 1.0.09 filesNamed records, reason, owner, expiryApproval before a hold standsReviewed on the day it lapsesHistory is never rewrittenHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 42dd2e95a69e… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 45.2 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/project-drafts-held-for-a-client-query/WALKTHROUGH.md, examples/reviewer-notes-renewed-then-closed/WALKTHROUGH.md, reference/approving-and-refusing-exceptions.md, reference/exception-terms-and-states.md, reference/lapse-review-and-closure.md, reference/the-exception-register.md, templates/exception-entry.template.md, templates/lapse-review-log.template.md
Worked example, from the package
examples/project-drafts-held-for-a-client-query/WALKTHROUGH.md
A two person drafting and summary service keeps a retention schedule under Data Retention Schedule. One line on it covers delivery drafts: kept for 60 days from the delivery date, then held for an approved pass. In August a client raised a billing query on one finished project, and the drafts for that project were about to pass their period while the query was still open. This is how the hold was handled as an exception, from the check that found it to the closure that ended it.
Spreadsheet Formula Audit
Data, Files, and Research · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A workbook's numbers earn trust from its formulas, not its displayed values: every formula in scope is read range by range for errors, typed values hidden inside calculation chains, and references pointing at nothing, with each fault listed per sheet by cell and class.
What changes
- A doubted workbook read by the values on its face, and either trusted whole or set aside whole → every formula in scope read range by range on a copy, with the counts reconciled per sheet
- A fault found by chance fixed where it was found, while the same fault sits in the next column → each fault listed as a finding by sheet, cell, and class: errors, typed values hidden inside calculation chains, and references pointing at nothing
- Trust as a feeling about the whole file → a per sheet account the operator can check: which cells are faulty, what each fault does to the figures that rest on it, and which ranges were not read
Honest fit
For you if: A workbook's totals are doubted, or about to be handed on, and reading the displayed values cannot settle whether the formulas behind them are sound.
Skip it if: You need the data tidied, a report written from the sheet, or the formulas fixed; the audit names faults for the operator to decide on, and every fix is separate work.
Your first run produces: one sheet audited on a copy, in about half an hour: the workbook copied and the copy named as the audit copy, the audit record opened with the sheet and ranges in scope and the agreed constants named, the cells in scope counted first so the reading has a total to answer to, each range read formula by formula with every fault written as a finding with its cell, formula, class, and effect, and the counts reconciled with the ranges not read named as not read.
Preview, from the skill itself
“# Spreadsheet Formula Audit<br># Spreadsheet Formula Audit A workbook can look right and add up wrong.”
Version 1.0.09 filesFormulas read, not displayed valuesFindings per sheet, by cell and classTyped values inside chains namedCounts reconciled before it closesHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: f1a988efc474… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 57.2 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/monthly-budget-with-a-broken-total/WALKTHROUGH.md, examples/stock-count-with-hardcoded-prices/WALKTHROUGH.md, reference/error-and-reference-faults.md, reference/formula-terms-and-scope.md, reference/hardcoded-values-and-chains.md, reference/reading-findings-by-severity.md, templates/audit-record.template.md, templates/sheet-findings-entry.template.md
Worked example, from the package
examples/monthly-budget-with-a-broken-total/WALKTHROUGH.md
A fictional one person workshop kept its monthly budget in a workbook with three sheets: Inputs, Spending, and Summary. The Summary sheet said 5 was left over for the month. The operator doubted it, because the spending on the ground felt heavier than the plan. This is how the workbook was audited, sheet by sheet, and what the audit found. No formula was changed during the audit. The findings went to the operator in the audit record, and fixes were left as separate work.
Quote Terms Library
Local Services / Sales · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Every quote you send carries the same current terms: the payment, changes, warranty, and validity blocks live in one checked library, each with its own version, and every new quote is checked against that library before it goes out, so stale wording stops travelling from quote to quote.
What changes
- The terms on a quote being whatever the last quote carried, with one job's change travelling onward as if it were the standard → the payment, changes, warranty, and validity blocks living in one checked library, each with its own version
- A change meant to be standard never landing, because the next quote copied a different one → current wording with an address: each block held once, with a version and a date
- Drift found, if at all, by a customer reading two quotes side by side → every new quote checked against the library before it goes out, the check logged with the versions it used, and stale blocks retired in the open
Honest fit
For you if: Your quotes carry terms copied from the last quote, so stale wording travels and a change you made once for one job reads as your standard.
Skip it if: You need legal advice, custom terms written from nothing, or prices and scope checked; the library organizes and checks wording you already hold and settle, and sending stays with you.
Your first run produces: the library built from past quotes, in about forty minutes: the last five quotes the operator sent gathered and worked from only, each kind of terms block lifted out and its versions laid side by side, agreeing wording settled as the starting current version and disagreements listed as gaps for the operator to settle rather than picked by the agent, each settled block given version 1.0 and the date of the run, and the index held for the operator to read before any block becomes current.
Preview, from the skill itself
“# Quote Terms Library<br># Quote Terms Library Every quote carries more than a price.”
Version 1.0.09 filesTerms held once, with versionsQuotes checked before sendingDisagreements held as gapsStale blocks retired in the openHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 1142c0f077c4… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 35.0 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/kitchen-remodel-terms-caught-before-sending/WALKTHROUGH.md, examples/roof-repair-library-first-build/WALKTHROUGH.md, reference/building-the-library-from-past-quotes.md, reference/checking-a-quote-before-it-goes-out.md, reference/keeping-terms-honest-and-in-scope.md, reference/versioning-blocks-and-retiring-stale-ones.md, templates/library-index-and-check-log.template.md, templates/terms-block.template.md
Worked example, from the package
examples/kitchen-remodel-terms-caught-before-sending/WALKTHROUGH.md
A local service operator who fits and remodels kitchens. The library had stood for two months. A quote for a customer, Dana Whitfield, to remodel a small kitchen was drafted from a saved quote file instead of from the library. This example follows the check that caught two stale blocks on that draft, how each was settled, and the quote that went out carrying the current blocks.
Tool Checkout Log
Local Services / Field Operations · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Who had which tool, on which job, and what came back damaged is answerable from one log: your own gear is checked out to a named person for a named job and back in against the same entry, with loss and damage written on that entry.
What changes
- Tool movement living in heads and on job sheets, a tool lent along the crew with a word → your own gear checked out to a named person for a named job, and back in against the same entry
- A damaged guard found days later with no job tied to it → condition written out before the tool works and back in on the same terms, with loss and damage written on that entry
- A missing item noticed only when the next job needs it → what is still out listed from the log in a minute, and questions settled with a record instead of a recollection
Honest fit
For you if: Tools go out with the crew on a word, and when something comes back damaged or does not come back, nobody can say who had it or on which job.
Skip it if: You need rented or borrowed gear tracked, repairs costed, or fault decided; the log states who had a tool, on which job, and the state it came back in, and those calls stay with you.
Your first run produces: the log opened on the next job's tools, in about twenty five minutes: each owned tool or kit listed as its own item, named so it can be told apart from the next one like it, the person and the job written in plain words for each, the condition noted as it stands today, tools that came back before the log started marked plainly as a first note rather than a check out note, and every returned tool checked in on the same entry or listed as still out.
Preview, from the skill itself
“# Tool Checkout Log<br># Tool Checkout Log A crew's own tools move all day.”
Version 1.0.09 filesPerson and job on every checkoutCondition out and back, same entryStill out listable in a minuteLoss and damage on the entryHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: f20332d8735c… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 31.7 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/fence-line-clearing-loppers-did-not-come-back/WALKTHROUGH.md, examples/porch-repair-saw-back-with-a-cracked-guard/WALKTHROUGH.md, reference/checking-back-in-on-the-same-entry.md, reference/checking-out-against-a-person-and-a-job.md, reference/reading-the-log-for-what-is-still-out.md, reference/recording-loss-and-damage.md, templates/checkout-slip.template.md, templates/tool-checkout-log.template.md
Worked example, from the package
examples/fence-line-clearing-loppers-did-not-come-back/WALKTHROUGH.md
A local service operator who clears fence lines and brush, with a crew of three. This example follows one clearing job where five items went out and four came back. The fifth was written as not back on its own entry, checked over four days, and set as lost by the operator only once those checks were done and written down.
Invoice Dispute Handling
Local Services / Money · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A contested invoice gets settled from the record instead of argued from memory: each disputed line is checked against the accepted quote and the completion record, the reply is drafted in plain words from what the records show, and the settlement is recorded on the job.
What changes
- A dispute settled from memory in a single exchange, the operator recalling the job one way and the customer another → each disputed line checked against the accepted quote and the completion record, with every figure worked in the open
- A round figure coming off to end the talk → a reply drafted in plain words from what the records show, held for the operator to read and send with their own hand
- Nothing on the record saying which lines were wrong, which stood, or why the final figure is what it is → the settlement recorded on the job as paid, reduced, or written off, each with its reason
Honest fit
For you if: A customer contests lines on an invoice and settling it means arguing from memory against theirs.
Skip it if: You need invoices built, undisputed invoices chased, or legal advice; this starts only when a charge is contested, and the settlement itself is your call.
Your first run produces: one contested invoice worked from the records, in about thirty minutes: the most recent disputed invoice taken, its contested lines listed in the customer's own words, each line checked against the accepted quote and the completion record on the check sheet with every figure traced, the answer drafted in plain words from the findings, and the settlement entry held ready to complete once the operator decides.
Preview, from the skill itself
“# Invoice Dispute Handling<br># Invoice Dispute Handling A dispute starts when a customer looks at an invoice and says: that line is not right.”
Version 1.0.09 filesLines checked against quote and recordFigures worked in the openAnswer drafted in plain wordsSettlement recorded on the jobHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 6461c851645f… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 37.8 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/gutter-job-elbow-line-held-pipe-line-removed/WALKTHROUGH.md, examples/yard-clearance-third-load-and-an-hour/WALKTHROUGH.md, reference/checking-each-line-against-the-records.md, reference/drafting-the-answer-in-plain-words.md, reference/reading-the-dispute-and-opening-the-record.md, reference/settling-and-recording-the-outcome.md, templates/dispute-check-sheet.template.md, templates/settlement-record.template.md
Worked example, from the package
examples/gutter-job-elbow-line-held-pipe-line-removed/WALKTHROUGH.md
A local service operator who fits and repairs gutters. A customer, Dana Whitfield, had a side gutter run and a downspout replaced. This example follows a dispute over two parts of the invoice: an extra pair of downspout elbows, and a line for an extra downspout pipe length. One part stood on the record. The other did not, and came off.
Lead Source Tracking
Local Services / Sales · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
You stop feeding the sources that never send work: every lead is recorded with where it came from, outcomes are joined back to sources on a set review cadence, and effort goes to the sources your own record supports.
What changes
- A source's worth as a feeling: the busy channel feeling like the good one, the quiet one dropped on a hunch → every lead recorded with where it came from, one source per lead from a fixed list
- The source that sent the last three won jobs getting no more care than the one that sent none → outcomes joined back to sources on a set review cadence, counted in the open
- Effort spread by habit → effort going to the sources the operator's own record supports, with the counts that support the call written down beside it
Honest fit
For you if: You feed every source alike because no record says which ones actually send work that wins.
Skip it if: You need leads generated, listings run, or a best source named in general; the log reads one operator's own record for one named period and says no more than that record holds.
Your first run produces: the log opened and the recent record entered honestly, in about thirty minutes: the fixed source list written at the head of the log, the leads already held entered one at a time from message threads, the job book, or quote records, each with one source or an honest unknown where no record names one, ended leads closed with their outcomes and live ones left open, and a first tally worked for the period with the parts checked against the whole.
Preview, from the skill itself
“# Lead Source Tracking<br># Lead Source Tracking Category: Local Services / Sales”
Version 1.0.09 filesSource recorded at intakeOutcomes joined back to sourcesReviews on a set cadenceUnknowns left unknownHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 32c12f100138… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 40.0 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/marketplace-heavy-month-for-a-gutter-operator/WALKTHROUGH.md, examples/spring-review-for-a-fence-operator/WALKTHROUGH.md, reference/acting-on-the-review-without-overreading-it.md, reference/recording-outcomes-and-joining-them-back.md, reference/recording-the-source-at-intake.md, reference/running-the-source-review.md, templates/lead-source-log.template.md, templates/source-review.template.md
Worked example, from the package
examples/marketplace-heavy-month-for-a-gutter-operator/WALKTHROUGH.md
A local operator who cleans, repairs, and replaces house gutters. The operator had a feeling that the marketplace listing was the busy channel and the one worth the most evening time. This example follows one monthly review that set that feeling beside the joined record for the month, counted from the month's own lead list.
Release Notes Drafts
Studio / Publishing · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Each version ships with notes a user can scan in seconds: the change record is rewritten in plain words about what changed for the user, grouped as new, improved, and fixed, with anything the record does not support left out, and every draft held for your approval.
What changes
- Release notes written from memory at the last minute: a remembered change in large, a quiet fix left out → each version's notes drafted from the change record and from nothing else
- A change that slipped to the next version announced in this one, and internal words travelling straight into the notes → every line rewritten in plain words about what changed for the user, grouped as new, improved, and fixed
- Readers guessing what a line means for them → the entries left out named with their reasons in the check log, and every draft held for the operator's approval before it reaches a reader
Honest fit
For you if: Each version ships with notes written from memory at the last minute, so quiet fixes vanish and changes that slipped get announced early.
Skip it if: You need the change record kept, a launch announcement written, or the notes published; this drafts the per version notes from the record and holds them for your approval.
Your first run produces: one version's notes drafted from its record, in about thirty minutes: the change record for the next version to ship read from its first entry to its last, the entries a user can feel set out and the rest written down as left out candidates, the draft written with an opening line naming the version and its kind, then the new, improved, and fixed lines in user words, and the check log filled in as you go, one line for each line in the notes and one for each entry left out.
Preview, from the skill itself
“# Release Notes Drafts<br># Release Notes Drafts Release notes are the short page of notes that ships with, or sits beside, one version of a product.”
Version 1.0.09 filesDrafted from the change record onlyNew, improved, and fixedLeft out entries named with reasonsHeld for approval, every draftHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 6837a0fe86b5… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 33.2 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/a-fix-only-release-with-nothing-new/WALKTHROUGH.md, examples/a-mixed-release-with-new-improved-and-fixed/WALKTHROUGH.md, reference/grouping-and-ordering-the-notes.md, reference/holding-the-draft-for-approval.md, reference/reading-the-change-record.md, reference/turning-changes-into-user-words.md, templates/release-notes-check-log.template.md, templates/release-notes-draft.template.md
Worked example, from the package
examples/a-fix-only-release-with-nothing-new/WALKTHROUGH.md
The same invented studio from the first example ships Fernhollow Tasks 3.2.1, a small version that follows 3.2 by two weeks. It holds no new feature. This example shows the draft for a release like that: the Fixed group standing alone, the opening line saying so plainly, and no line stretched to fill a New or Improved heading.
Audience Question Bank
Creator and Audience · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
The questions your audience actually asks stop getting lost: each one is kept in the asker's own words with where and when it was asked, grouped and counted from the bank itself, then turned into FAQ drafts first, Q and A content second, and product fixes where the same question keeps exposing the same gap.
What changes
- Audience questions answered one by one and then lost, the same question asked ten times still feeling like a surprise → each question kept in one bank, in the asker's own words, with where and when it was asked
- Guesses about what the audience wants resting on the loudest recent comment or on memory → questions grouped and counted from the bank itself, so the FAQ answers what is actually asked most
- The same question exposing the same gap without anyone seeing the pattern → FAQ drafts first, Q and A content second, and product fixes where the counts show the same gap, each resting on entries the operator can read
Honest fit
For you if: Your audience asks the same questions again and again across comments, messages, and reviews, and each one is answered once and lost.
Skip it if: You need questions scraped from places you do not ordinarily see, replies sent, or results promised; the bank holds questions and counts from your own channels, and every use of it is a draft held for your approval.
Your first run produces: the bank opened on the last two weeks of questions, in about thirty minutes: the questions the operator can already see taken from recent comments, messages, reviews, and counter notes, each entered in the asker's own words with where and when it was asked and nothing entered from memory, the entries grouped by theme and each theme counted from the entries themselves, and two or three FAQ lines drafted for the theme with the highest count, with answers read from the operator's own facts and unsettled points left as named gaps.
Preview, from the skill itself
“# Audience Question Bank<br># Audience Question Bank The questions an audience asks are already market research, written in the audience's own words.”
Version 1.0.09 filesAsked in their own wordsWhere and when on every entryCounts worked from the bankFAQ drafts before contentHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 60adaca8a91e… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 39.1 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/bakery-counter-questions-that-became-an-faq/WALKTHROUGH.md, examples/bike-shop-questions-that-fixed-a-gap/WALKTHROUGH.md, reference/capturing-questions-in-their-own-words.md, reference/grouping-and-counting-questions.md, reference/turning-questions-into-content-and-fixes.md, reference/turning-the-bank-into-an-faq-page.md, templates/faq-and-content-draft.template.md, templates/question-bank.template.md
Worked example, from the package
examples/bakery-counter-questions-that-became-an-faq/WALKTHROUGH.md
A small bakery with a shop counter and a Saturday market stall, selling bread, cakes, and bakes to order. Over four weeks the operator kept a question bank from the channels she sees in her work: the counter, the stall, comments on the bakery page, and messages sent to the bakery. This example follows that bank from its entries, through its counts, to an FAQ draft held for her approval.
Agent Retrospective Notes
Agent Operations · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A period of agent work gets a written account instead of a fresh guess: what ran, what the records show went well or badly, and lessons kept as dated notes with the change each one produced.
What changes
- A period of agent work ends and leaves only the work itself, a fault that cost a little each week felt as a vague sense that the agent is shaky → the period ends with a short written account, what ran counted from the records and what went well and badly named with the records behind each point
- The fix, if one is tried, resting on the last bad run anyone remembers, and a practice that quietly carried the month never written down → each lesson sits in a dated note with the change it produced and the owner of that change
- Learning left to memory, the same fault met each time as a fresh surprise → the next review checks each change against fresh records, and a strength that repeats is kept on purpose
Honest fit
For you if: Your agents do steady work week after week, and at the end of a period nobody can say from the records what went well, what kept going wrong, or what a fix changed.
Skip it if: You need a single incident worked in depth or a single decision settled; a postmortem takes one event and a decision log holds one call, and this review reads across a whole period instead.
Your first run produces: the most recent full week of agent work reviewed on its own, in about an hour: the scope line written at the top naming the agents covered, the records that count as sources, and the period dates, what ran in that week gathered and counted as total runs, runs that ended well, runs that ended badly, and runs with no recorded outcome, the poor outcomes grouped and read together, one lesson note drafted where the same cause sits behind three or more of them, one short note written for the strongest thing that went well, and each change agreed with its owner and start date, with the next review date written at the top.
Preview, from the skill itself
“# Agent Retrospective Notes<br># Agent Retrospective Notes Agent work adds up quietly.”
Version 1.0.09 filesThe period is the unitCounts worked from the recordsEach lesson names its changeChanges checked next periodHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 6bd55bc70e1b… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 43.6 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/a-busy-month-that-changed-how-reminders-were-sent/WALKTHROUGH.md, examples/a-quiet-quarter-that-still-changed-two-rules/WALKTHROUGH.md, reference/lesson-notes-fields.md, reference/reading-a-period-for-lessons.md, reference/retrospective-scope-and-sources.md, reference/tracking-changes-to-the-next-period.md, templates/lesson-note.template.md, templates/retrospective.template.md
Worked example, from the package
examples/a-busy-month-that-changed-how-reminders-were-sent/WALKTHROUGH.md
A small home repair office ran two agents: a dispatch agent that booked jobs, held the job records, and sent appointment reminders the day before each job, and an inbox agent that drafted replies to customers. The owner ran both and kept their records in one place. Jobs were getting done, but reminders kept drawing replies that said the day or the time was wrong, and each reply was handled on its own as a small mix up. At the end of March the owner ran the first monthly retrospective, covering 1 March to 31 March, to read the month as a whole. This is how that review was built and what it changed.
Prompt Version Registry
Agent Operations · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Every prompt change stops being a mystery: each version is kept whole in one registry with what changed, why, and which runs used it, and a named earlier version can be brought back whole when a change makes things worse.
What changes
- A prompt change lands in the live text and the old wording is gone → the same change is an entry holding the full text, what changed in plain words, and why, with dates
- A shift in the work a week later argued from memory, with no checkable cause → a questioned run is traced by its stamp to the exact version that shaped it
- A bad change fixed with a fresh guess written under pressure → a named earlier version is brought back whole from the record, the same day
Honest fit
For you if: Your agents run under prompts that get edited in place, so a week later nobody can say what changed, when, or which wording shaped a questioned run.
Skip it if: You need prompt wording written or judged, or configuration versioned; this registry holds prompt versions, change notes, and run stamps, and moving the live mark still waits for your approval.
Your first run produces: the registry started for one agent and its most shaping prompt set, in about forty minutes: the scope line written naming the agent and the prompts it covers, the wording as it stands today entered as the first live version with its full text copied exactly, the honest reason written on the entry with no earlier history rebuilt, the run stamp set so each run record carries the prompt name and version label, and the next run checked to show the stamp in place.
Preview, from the skill itself
“# Prompt Version Registry<br># Prompt Version Registry An agent behaves the way its prompts tell it to behave.”
Version 1.0.09 filesEvery change is a new versionFull text kept for each versionRuns stamped with their versionRollback restores a version wholeHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 88056c1dda87… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 52.2 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/bringing-an-old-prompt-back-after-a-bad-change/WALKTHROUGH.md, examples/tracing-which-prompt-version-ran-a-job/WALKTHROUGH.md, reference/linking-runs-to-versions.md, reference/naming-and-numbering-versions.md, reference/registry-entry-fields.md, reference/rollback-and-retirement.md, templates/prompt-registry.template.md, templates/prompt-version-entry.template.md
Worked example, from the package
examples/bringing-an-old-prompt-back-after-a-bad-change/WALKTHROUGH.md
A small tiling business ran a quoting helper that read the fitter job notes for a finished visit and drafted the customer quote: the work done, the materials used, and the price lines from the price record. The helper ran under one prompt set, the quote draft prompt, held in a registry the owner kept. By the start of June the registry held six versions, V1 to V6, with V6 live. This is the change that went wrong in June, the rollback to a named earlier version, and what the runs showed afterwards.
Tool Permission Scoping
Agent Safety and Governance · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Each tool an agent can touch is scoped to the least access its stated job needs, worked out per task type and written down on one sheet, with every wider exception approved and dated.
What changes
- A tool holds whatever reach its setup offered first, and nobody chose that width → each tool stands at a scope set on purpose, pairing by pairing, against a stated job
- Nobody able to say in one place how wide each tool stands or why → the sheet states for each task type what each tool may read, what it may change, where, and how far
- A wider ask settled by widening the setting and moving on, with no date and no return → every wider standing is an exception with a name, a reason, and an end date
Honest fit
For you if: Your agents use tools that were connected in a hurry and still hold the wide reach their setup pages offered first.
Skip it if: You need standing grants audited or re-reviewed on a rhythm; this skill writes the stated scope those checks later read against, before a grant is made or a pairing is added.
Your first run produces: one agent's most used tools scoped on one sheet, in about an hour: the three or four task types the agent does most listed in plain work words, the job of each tool inside each task type written in one sentence, each pairing set with the least scope tests and written as its own scope line with the date set, any pairing that must stand wider written as an exception with its approval and end date, and the settings read back from their settings pages to match the sheet.
Preview, from the skill itself
“# Tool Permission Scoping<br># Tool Permission Scoping A tool is usually connected in a hurry.”
Version 1.0.09 filesOne task type, one scope lineLeast scope that does the jobDefaults treated as not setExceptions approved and datedHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 28eb75083623… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 47.6 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/adding-a-payment-tool-with-a-tight-scope/WALKTHROUGH.md, examples/scoping-a-new-inbox-and-files-helper/WALKTHROUGH.md, reference/exceptions-and-dated-approvals.md, reference/least-scope-tests.md, reference/task-types-and-tool-jobs.md, reference/writing-the-scope-sheet.md, templates/exception-request.template.md, templates/tool-scope-sheet.template.md
Worked example, from the package
examples/adding-a-payment-tool-with-a-tight-scope/WALKTHROUGH.md
A small house cleaning business ran an invoicing helper that raised invoices from the job records and followed up the late ones. In March the owner added a payment tool, so customers could pay an invoice from the invoice itself instead of by bank transfer days later. The tool arrived with a wide first offer: it could raise a charge for any amount, read the payment state of every charge on the account, and pay money out of the account as well as take it in. None of that width was scoped, and the work had not started. This is how the tool was scoped before its first charge, the one exception its first month needed, and the one wider ask that was refused and kept on file.
Canary Release Checks
Studio / Shipping · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A release reaches everyone in stages instead of all at once: a small first audience, one fixed check list run at each stage, and a written widen, hold, or roll back call before it moves further.
What changes
- A release goes out whole, and the first sign of a fault is a run of support contacts from everyone at once → the same fault meets the smallest audience first, with stage figures set beside the prior version baseline
- The size of a problem guessed at under pressure, and the call to reverse made late and in haste → the break line for each check agreed before the first stage opened, and the hold or roll back call written as a step in a known method
- A clean release leaving nothing behind about what was checked or when → a plan and a set of stage records the next release can start from, with stages, checks, and break lines already in plain words
Honest fit
For you if: Your releases go to everyone at once, so a new fault gets its largest possible audience on its first day.
Skip it if: Your release cannot be served to part of its audience at a time; this skill only works where a release can in fact be served in parts, and it does not serve any version itself.
Your first run produces: the stage plan opened for the next release, in about forty-five minutes of setup: the stages written with their shares and watch periods, the new version and the prior version named as the roll back target, the check list written for the product with the source and break line for each check, the roll back route tested before the first stage opens, and the first stage opened to the first audience only, with one short check round to run at the end of each stage.
Preview, from the skill itself
“# Canary Release Checks<br># Canary Release Checks A release that goes to everyone at once gives a new fault its largest possible audience on its first day.”
Version 1.0.09 filesStages fixed before the first opensThe watch period runs in fullOne written call per stageRoll back means the prior version, wholeHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 48e658dbe85f… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 48.8 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/a-clean-widening-that-reached-everyone/WALKTHROUGH.md, examples/a-hold-then-rollback-at-the-second-stage/WALKTHROUGH.md, reference/running-a-rollback-and-after.md, reference/stage-plan-fields.md, reference/the-fixed-check-list.md, reference/widen-hold-or-rollback-calls.md, templates/canary-stage-plan.template.md, templates/stage-check-record.template.md
Worked example, from the package
examples/a-clean-widening-that-reached-everyone/WALKTHROUGH.md
A small team runs a fictional field notes app for garden crews, called Field Notes in this example. Crews note jobs on phones and the notes sync when a signal returns. Version 4.2 added a faster sync and moved the photo add button. Version 4.1 was the prior version in wide use. The release lead, acting as keeper, opened a canary stage plan on 6 April, before version 4.2 was served to anyone outside the team. The operator was the studio owner. This is how the widening ran, stage by stage, to everyone.
Naming Convention Setup
Data, Files, and Research · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A new project starts with names that hold up: one written naming convention for files, versions, and deliverables, with checker rules that test each new name before it is saved.
What changes
- A new project names its first files by habit and hurry, each person bringing the pattern from their last job → the same project names its files from one sheet, in the same order every time, so a folder reads down like a list
- Finding a file means remembering who made it and roughly what they called it, and two copies of one deliverable stand under two names → a name can be read by a stranger: its project, its date, its subject, its kind, and where it stands
- Drift found in a pile months later, when a renaming job is the only way back → a new name is checked before it is saved, so drift is caught in ones, at the keyboard
Honest fit
For you if: You are starting a project or a team and want its files named well from the first week, before the pile forms.
Skip it if: You need an existing library renamed or tidied; that is a filing run under its own manifest and approval, and this skill designs the convention for something new.
Your first run produces: the convention designed for one new project before it fills up, in about an hour: the kinds of thing the first month will name listed, the parts of a name settled in their order with the date form and numbering rule, versions and status marks settled, the checker built one rule per line, and the whole draft tested against at least ten names that should pass and ten that should fail before the first real files are named under it.
Preview, from the skill itself
“# Naming Convention Setup<br># Naming Convention Setup A new project starts clean for about a week.”
Version 1.0.09 filesOne project, one convention, one sheetNames built from factsFew parts, in a fixed orderThe checker runs before the saveHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: fab2535d62f5… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 53.2 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/designing-a-convention-for-a-new-research-study/WALKTHROUGH.md, examples/starting-a-shared-drive-for-a-new-team/WALKTHROUGH.md, reference/checker-rules.md, reference/parts-of-a-good-name.md, reference/rolling-out-and-revising.md, reference/versioning-and-status-marks.md, templates/convention-sheet.template.md, templates/name-checker.template.md
Worked example, from the package
examples/designing-a-convention-for-a-new-research-study/WALKTHROUGH.md
A four person field research team was about to start a three month study of water quality along a creek, for a county client. The study had a name, a start date, and an empty shared folder. It had no files yet, which was the whole reason the owner ran this skill first: the convention could be designed before the first field note set the pattern by accident.
Seasonal Crew Hiring Pack
Local Services / Field Operations · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Seasonal hiring stops running on hurry and memory: the role is written from the work the season actually holds, the screening questions and pass marks are fixed before the first application arrives, trial days are paid and recorded against the same checks for everyone, and every candidate, hired or not, gets an ending in writing.
What changes
- A seasonal hire living in the operator's head and phone: a vague ad, different questions for different people → the same hiring sits in one pack, the role matching the work the season will actually bring and the questions fixed before feelings were involved
- A trial that is really just a busy day nobody recorded, and the decision resting on memory → each trial day leaves a record against the same checks for every candidate, so the decision can stand on it
- Silence for everyone who was not picked, including the person who would have stayed the season → every applicant, hired or not, gets a written ending while the round is still warm, and the reserve list is real when someone quits in week two
Honest fit
For you if: You hire seasonal hands on hurry and memory, with a vague ad, different questions for different people, and silence for everyone not picked.
Skip it if: You need the role advertised, candidates contacted, or the hire decided; the operator places the ad, sends every note, and makes the call, and this pack keeps the record the decision stands on.
Your first run produces: the pack built for one role for the next season, end to end on paper before any ad goes out, in about an hour: last season's records listed week by week for the work the season actually held, the role written from that work with the must haves kept apart from what can be taught, the screening questions and pass marks fixed and dated, the trial day shape and its pay rate set, and the pack sheet laid out with a row per stage, ready to take its first application.
Preview, from the skill itself
“# Seasonal Crew Hiring Pack<br># Seasonal Crew Hiring Pack Seasonal hiring usually runs on memory and hurry.”
Version 1.0.09 filesThe role comes from the workQuestions fixed before applications arriveTrial days are paid work, recordedEvery candidate gets a written endingHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: a02c1041495d… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 35.4 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/autumn-yard-crew-hiring-run/WALKTHROUGH.md, examples/spring-cleanup-hiring-run/WALKTHROUGH.md, reference/closing-out-offers-and-rejections.md, reference/screening-questions-fixed-in-advance.md, reference/trial-days-on-the-record.md, reference/writing-the-role-from-the-work.md, templates/hiring-pack-sheet.template.md, templates/trial-day-record.template.md
Worked example, from the package
examples/autumn-yard-crew-hiring-run/WALKTHROUGH.md
A garden and yard operator, Priya, works with one lead, Tomas, and hires one seasonal hand for the autumn season: about eight weeks of leaf clearing, hedge and garden tidies, and storm debris after bad weather. She needs the hand for weekdays and for Sunday cover one week in two, which is the requirement this run turned on.
Cash Handling Log
Local Services / Money · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Every cash payment is logged the moment it lands, with the job, the amount, and who took it, counted and deposited on a stated rhythm, and reconciled against the invoices it settles, so a shortage is named on the record the day it appears.
What changes
- Cash living in a pocket and a memory: paid, probably, in full, most likely → the same cash sits on one log, each payment entered when it landed with its job and its taker named
- Nobody able to prove which invoice a given bill settled → each line matched to the invoice it settles, and the count and deposit worked on a rhythm and shown as arithmetic
- A small loss with no moment where it ever has to be faced, so it never is → a shortage named on a named day, in a named figure, while the week that produced it can still be looked into
Honest fit
For you if: Your work takes cash on doorsteps and in driveways, and by the end of the week nobody can say which jobs it came from or whether all of it is still there.
Skip it if: You need banking done, accounts kept, or tax advice; the operator makes each deposit, and this log only records the counted figure and the deposit date the operator confirms.
Your first run produces: the log set up and the opening position entered from a real count, in about thirty minutes: the log opened from the current invoices and job records with a line ready for each payment, the count and deposit rhythm written at the top in plain words with the next count date named, any cash already on hand counted bill by bill and entered as the opening line dated today, and cash no record can tie to a job entered as its own line and named as unassigned.
Preview, from the skill itself
“# Cash Handling Log<br># Cash Handling Log Cash is the easiest money to lose track of.”
Version 1.0.09 filesLogged when received, not laterEvery line names three thingsCounted and deposited on a rhythmA shortage is named the day it appearsHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 08dba643dac0… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 37.6 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/clean-week-reconciled-in-full/WALKTHROUGH.md, examples/short-count-named-same-day/WALKTHROUGH.md, reference/counting-and-deposit-rhythm.md, reference/logging-cash-at-receipt.md, reference/reconciling-against-invoices.md, reference/shortages-and-discrepancies.md, templates/cash-log.template.md, templates/reconciliation-and-deposit.template.md
Worked example, from the package
examples/clean-week-reconciled-in-full/WALKTHROUGH.md
A fictional local service operator who cleans gutters, trims hedges, and repairs fences for householders. Two people take cash: Dan, the operator, and Luis, who works with him. Some customers pay by card or transfer. Some pay in cash on the day. The rhythm on the log is counted every Friday and deposited the same day. This is the week of Monday 6 April 2026 to Friday 10 April 2026.
Service Guarantee Tracking
Local Services / Reputation · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Every guarantee you promise on a job sits in one ledger with what was promised, on which job, and until when, and every claim against a guarantee is tracked to its recorded resolution.
What changes
- Guarantees living where they were given: a line on one invoice, a word in a doorway, a note in one job file → the same promises sit on one ledger, each in its own words, on its named job, with its end date worked and shown
- A claim arriving months later worked from memory, generous to one side on one day and to the other side the next → each claim logged the day it arrives and closed only with a dated resolution
- A window argued about at the counter when a claim falls near its end → a claim outside the window shown as outside by the dates on the page, not by an argument
Honest fit
For you if: You give guarantees on jobs and months later nobody can say for sure what was promised, on which job, or until when.
Skip it if: You need guarantees given, terms set, coverage judged, or repair work done; those calls and that work stay with the operator, and this ledger keeps the record of promises and claims.
Your first run produces: the first ledger built from the job records, with any open claim logged in the same sitting, in about forty-five minutes: the recent job sheets and invoices gone through for each guarantee given in writing, one entry written per promise with the job, the wording used, what is not covered, and the end date worked from the start date and the term, each open claim logged against its entry with a next step named, and the next review date written at the top.
Preview, from the skill itself
“# Service Guarantee Tracking<br># Service Guarantee Tracking A guarantee is easy to give and hard to remember.”
Version 1.0.09 filesOne entry per promiseWording kept as it was givenWindows read off the entryClaims logged the day they arriveHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 74306d1fd531… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 34.0 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/kitchen-and-bath-ledger-opening/WALKTHROUGH.md, examples/roofing-season-claims-review/WALKTHROUGH.md, reference/closing-a-claim-with-resolution.md, reference/recording-a-claim.md, reference/reviewing-the-ledger-and-expiry.md, reference/writing-a-guarantee-entry.md, templates/claim-record.template.md, templates/guarantee-ledger.template.md
Worked example, from the package
examples/kitchen-and-bath-ledger-opening/WALKTHROUGH.md
A fictional local firm, Millbrook Kitchen and Bath, fits kitchens and bathrooms in and around one town. Guarantees were given on paper with each job, but the papers sat in separate job files. On 2 June 2026 the operator opens one ledger and brings the recorded promises together. This walk shows the opening entries and the one claim open on the day.
Photo Backup Routine
Data, Files, and Research · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Your job photos move from phone to archive on one fixed routine: each batch counted, copied, reconciled, and verified in the archive before the phone copy is cleared, so the only copy of a job's photos never lives on a phone.
What changes
- Work photos leaving the phone in a rush, a hurried copy to wherever has room and the phone cleared on trust → the same photos move on a fixed day, in named batches, with a phone count and an archive count that must match for each batch
- Nobody able to say afterwards whether everything arrived, the loss of a few files found months later if at all → a spot-open check on the archive copy and a log that says which batches passed, which were held, and when each passed batch was cleared
- The only copy of a job's photos living on a phone that can be lost, broken, or full → the operator can point to a batch and say in figures that it arrived whole and was seen to open
Honest fit
For you if: Your job photos live on your phone, and the only copy of a finished job's photos is one lost or broken phone away from gone.
Skip it if: You need photos taken, filed against job records, or lost photos recovered; this routine starts after the photos exist and moves them to an archive you name, and it clears no phone copy on its own.
Your first run produces: the archive set up and one real backup run on the photos now on the phone, in about thirty minutes: the archive and its layout named with one folder per batch, the routine day written at the top of the log, the photos grouped into batches by job or named set, each batch counted on the phone, copied alone to its archive folder, counted again and reconciled, a sample of its files opened in the archive, and each batch marked passed or held, with no phone copy cleared yet.
Preview, from the skill itself
“# Photo Backup Routine<br># Photo Backup Routine A phone fills up with job photos, and a phone is a poor place for the only copy to live.”
Version 1.0.09 filesCount before anything movesOne batch, one move, one checkCounts must match exactlyThe phone copy is cleared lastHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 39cd9ff1ad59… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 34.8 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/mixed-jobs-discrepancy-held/WALKTHROUGH.md, examples/roofing-week-clean-backup/WALKTHROUGH.md, reference/choosing-the-routine-and-archive.md, reference/clearing-the-phone-safely.md, reference/counting-and-reconciling-batches.md, reference/verifying-the-archive-copy.md, templates/backup-log.template.md, templates/batch-verification-note.template.md
Worked example, from the package
examples/mixed-jobs-discrepancy-held/WALKTHROUGH.md
A local service operator who does fence work, deck cleaning, and tree work. Photos are backed up every Monday morning for the week just ended. The archive holds one folder per batch, named with the date and the job name. This is the run on Monday 11 May 2026, covering three jobs. All counts below are still photos. No batch in this run held videos.
Multi-Agent Handoff Tests
Agent Operations · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A changed brief format or a repeating handoff fault stops being a guess: a fixed set of scripted cases runs the handoff cold, one plain pass rule decides it, and every failure is logged against the brief field that broke until the same case passes on retest.
What changes
- A weak handoff found in live work, an hour into the next run, with the next agent asking around or rebuilding the picture from chats and records → the same faults found on purpose in scripted test cases, before they cost a live run
- A fault fixed for one handoff in words, then turning up again in the next handoff under a new shape → every failure logged against the brief field that broke, so the field that keeps breaking is named and fixed once
- No way to tell afterwards whether a fix held → the same fixed cases run again after the fix and scored by the same pass rule, so the retest shows in the same cases whether the fix held
Honest fit
For you if: Agents hand work to each other on a brief format, and the same kind of gap keeps surfacing after the handoff, in live work.
Skip it if: You need briefs written or real work handed over; this skill tests handoffs against the brief format and records where they fail, and it grades no agent and changes no format on its own.
Your first run produces: one real handoff tested as it stands, in about ninety minutes: the sending agent, the receiving agent, the work the handoff covers, and the brief format version named at the head of a run record, six cases built (a sound routine handoff, one with part done work in the open items, one with a decision the next agent must stand behind, one with a watch item that may land in the next run, one carrying a known gap written as an open flag, and one built from the last real handoff that went wrong), the expected result written on each case before any case is run, all six run cold in one sitting with the receiving side working from each brief alone, each case scored against the pass rule, and every failure written on the run record against its brief field, with the date of the next run set.
Preview, from the skill itself
“# Multi-Agent Handoff Tests<br># Multi-Agent Handoff Tests A handoff can read as complete and still leave the next agent short.”
Version 1.0.09 filesTest the brief as received, not as intendedThe receiver works coldFailures are recorded against the brief formatThe pass rule is whole, not mostlyHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 0bbe5992a436… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 53.9 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/eight-cases-for-a-draft-to-review-handoff/WALKTHROUGH.md, examples/six-cases-for-an-intake-to-research-handoff/WALKTHROUGH.md, reference/building-the-case-set.md, reference/handoff-test-terms.md, reference/recording-failures-against-the-brief.md, reference/the-pass-rule-and-scoring.md, templates/handoff-test-case.template.md, templates/handoff-test-run.template.md
Worked example, from the package
examples/eight-cases-for-a-draft-to-review-handoff/WALKTHROUGH.md
A two person support desk used two agents in sequence. A drafting agent wrote draft replies to customer notes during the day. A review agent read the drafts in the evening, checked each one against the records it rested on, and lined the sound ones up for the operator to send in the morning. The handoff between them was a brief in the desk's usual format. Drafts kept arriving back with the same two notes: a draft marked as resting on a price that had since changed, and a draft held for a customer whose open item named no holder, so neither side chased it.
Data Quality Spot Checks
Data, Files, and Research · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
You can say how many records are wrong and which rule fails most, before a customer or a payment run finds out: standing records are sampled on a cadence and checked against written quality rules, error rates are reported per rule, and each correction is routed to the record owner.
What changes
- The state of a standing file resting on a feeling, cleaned up last spring so assumed sound → the same file sampled on a cadence and checked against written quality rules, with an error rate reported per rule
- Faults surfacing one at a time, when a letter reaches an old address or a payment is held up, each one fixed alone → each fault routed to the record owner with a recheck date, and closed only when a recheck passes
- Nobody able to say whether a fault stood for one record or for one record in five → the rule that fails most named from the run records, and the trend across runs showing whether the file is getting cleaner, holding, or drifting
Honest fit
For you if: Your work rests on standing records, customer addresses, supplier files, or lists that drift as people move and details change.
Skip it if: You need every record read, records corrected for you, or the quality standards set; this check samples records that already exist and reports rates per rule, and the record owners make the corrections.
Your first run produces: the first spot check run on one standing file, in about an hour: the run record opened with the file named, the operator and the cadence written down, and the size of the full file recorded, a rule list of four to six rules written before any sample is drawn, each rule one a checker can settle from a named source, a first sample of 40 to 80 records drawn by the stated method and written down, each sampled record checked against its source, records that cannot be checked marked with their reason and never swapped, and the faults counted per rule with each correction routed to its record owner.
Preview, from the skill itself
“# Data Quality Spot Checks<br># Data Quality Spot Checks Every standing file drifts.”
Version 1.0.09 filesSample what exists, as it standsRules are written before the sample is drawnReport the rate per rule, never one blended rate aloneA fault is closed by a recheck, not by a replyHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 2e61f3c36c07… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 43.8 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/monthly-supplier-records-check/WALKTHROUGH.md, examples/quarterly-customer-address-check/WALKTHROUGH.md, reference/choosing-a-sample.md, reference/reading-error-rates.md, reference/routing-and-closing-corrections.md, reference/writing-quality-rules.md, templates/correction-note.template.md, templates/spot-check-run.template.md
Worked example, from the package
examples/monthly-supplier-records-check/WALKTHROUGH.md
A small trade supply firm kept one file of supplier records, used for ordering and for paying invoices. Faults came to light one at a time: a payment run held up by a record with no terms on it, a delivery sent to a site address the supplier had left a year before. The operator set a monthly spot check, on the first Monday of the month, and this is the March run, in figures. The firm and its figures are an illustration, built to show the method.
Secret Sharing Protocol
Agent Safety and Governance · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
The rare share of a secret stops being a handover in a hurry: one named recipient and one stated purpose, single use or a stated expiry, the share logged by label only, and the reach revoked or the value rotated when the window closes, so no past share sits open unaccounted.
What changes
- A secret handed over in whatever thread is open, for however long the job seems to need → one share with a named recipient and one stated purpose, single use or a stated expiry set before it begins
- Nobody able to answer afterwards who holds a value now, for what, and until when → every share logged at the time by label only, so who holds what, for what, and until when are facts on one page
- A past share sitting open after its job ended, its life left to chance and other people's habits → each share closed when its window closes, the reach revoked or the value rotated, and the closing checked
Honest fit
For you if: You sometimes have to give a helper or a tool a secret to get a job done, and afterwards nobody can say who still holds it or until when.
Skip it if: You need a value held, fetched, or handed over for you, or standing reach granted; this protocol governs the one off share itself, the operator shares the value in their own tools, and no value ever appears in its records.
Your first run produces: the shares already open accounted for and the share log opened, in about forty-five minutes: every share still believed open listed from records and from memory, each one marked shown, stated, or unknown with its reason, one log entry written for each open share by label only, a closing action and a closing date agreed for each entry on the spot, and the shares whose jobs are long finished closed during this first run, not carried forward as paperwork.
Preview, from the skill itself
“# Secret Sharing Protocol<br># Secret Sharing Protocol Most secrets are shared in a hurry.”
Version 1.0.09 filesLabels only, never a valueOne named recipientOne share, one purposeSingle use or a stated expiryHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: e7f0b19a5628… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 39.9 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/giving-a-tool-one-afternoon-of-reach/WALKTHROUGH.md, examples/one-off-share-to-a-covering-helper/WALKTHROUGH.md, reference/choosing-the-channel-and-the-window.md, reference/closing-the-share-revoke-or-rotate.md, reference/logging-a-share-by-label.md, reference/naming-the-recipient-and-the-use.md, templates/share-log-entry.template.md, templates/share-request-and-approval.template.md
Worked example, from the package
examples/giving-a-tool-one-afternoon-of-reach/WALKTHROUGH.md
A small support operation kept one inbox for client questions, watched by an agent that sorted each morning's mail into a digest for the operator, Leila. On Tuesday 14 April 2026 the sorting had been wrong for three mornings running, and the fault sat somewhere in how the agent read the inbox. A log review tool the operation was trying, named in the request as the LogLens review tool, could read the run logs and the inbox together and show where the reading went wrong, but only if it was given reach to the support inbox secret, live copy, for the run. This is that share, from request to closing.
Uptime Incident Roster
Studio / Shipping · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A gap in uptime cover is found in the roster and not during an outage: every coverage window carries a named holder and a named backup, the handoff between holders and the contact order are written down, and the whole roster is reviewed on a cadence.
What changes
- Cover resting on habit, one person tending to answer so the team assumes the service is covered → every coverage window on one roster with a named holder and a named backup
- Nights and weekends resting on whoever happens to notice, and leave booked with no one asking what it does to cover → the handoff between holders and the contact order written down, and leave and team changes checked against the roster when they happen
- The first sign of a gap being an outage that rings out with nobody picking it up → gaps and thin cover found in the roster on an ordinary afternoon, on a set review cadence, with time to fix them
Honest fit
For you if: Your services need a person to answer when they go down, and cover at nights, weekends, or holidays rests on habit more than on a written roster.
Skip it if: You need services monitored, incidents graded, or outage messages written; this roster names who answers before any incident exists, and it runs no check, pages no one, and fixes no outage itself.
Your first run produces: the first roster built from the team and the services as they stand, in about an hour: the services that need a person to answer when they go down listed, the coverage windows fixed for the week with the time zone named once at the top, one entry per service with the holder and the backup for each window, the contact order written for each person, how each handoff is confirmed settled, and the full week checked for gaps and thin cover, so the roster sits held for the operator with its review date set.
Preview, from the skill itself
“# Uptime Incident Roster<br># Uptime Incident Roster A service rarely goes down at a tidy hour.”
Version 1.0.09 filesOne window, one holderEvery holder has a named backupContact order is written and tried in orderA handoff is done only when the next holder confirms itHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: ee6e67578d51… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 42.2 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/four-person-team-fixes-night-handoffs/WALKTHROUGH.md, examples/two-person-studio-finds-a-sunday-gap/WALKTHROUGH.md, reference/finding-gaps-and-thin-cover.md, reference/handoffs-and-contact-order.md, reference/review-cadence-and-triggers.md, reference/roster-terms-and-windows.md, templates/coverage-entry.template.md, templates/roster-record.template.md
Worked example, from the package
examples/four-person-team-fixes-night-handoffs/WALKTHROUGH.md
A fictional four person team ran a small learning platform for paying members: a member login and course pages, and a checkout where new members joined. The team was Ana Costa, who owned the service, Ben Okafor, Clara Lind, and Dev Patel. Daytime cover worked well. Night cover was where the roster, once written, showed its faults.
Docs Link Checking
Studio / Publishing · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Readers stop landing in the wrong place: on a set cadence every link and cross-reference in the docs is followed to its target, dead or moved targets are listed per page, and each one is fixed in place or flagged with the replacement recorded beside it.
What changes
- Links checked only when someone happens to click one, with the first report of a moved page coming from a reader who needed it → every link and cross-reference in the docs followed to its target on a set cadence
- Nobody able to say how many links are dead, which pages carry them, or where they should point instead → dead or moved targets listed per page in one dated record, with each fault's current target written beside it
- Each reported fault fixed alone while the rest stay broken → each fault fixed in place with its replacement recorded beside it, or flagged with the reason it is waiting, and the fixes rechecked on the page
Honest fit
For you if: Your docs carry links and cross-references that readers follow, and pages move or get renamed as the docs grow.
Skip it if: You need the writing on a page judged, guides restructured, or anything published; this check tests where links land, not whether the landing page is good, and the operator makes every fix and publishing call.
Your first run produces: the first link check run on one guide set or one help section, in about an hour: the record opened with the docs named, the cadence set, and where the record lives written down, the page list written in the order a reader meets the pages, then page by page every link and cross-reference on the page written down in order, each one followed and marked as holding or listed as dead, moved, wrong target, or section missing, and each replacement target followed too before it is written down, so the fix rests on a landing that was seen.
Preview, from the skill itself
“# Docs Link Checking<br># Docs Link Checking A documentation page can read perfectly and still fail its reader in one click.”
Version 1.0.09 filesFollow every link, not the suspect onesOne page, one entry, every link on itNever guess a replacement targetA check has a stated scope and a stated dateHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: ea3b0dcdfc94… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 38.8 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/quarterly-sweep-that-found-moved-guides/WALKTHROUGH.md, examples/release-week-check-after-a-docs-move/WALKTHROUGH.md, reference/cadence-and-coverage.md, reference/checking-a-page-step-by-step.md, reference/fix-or-flag-decisions.md, reference/link-kinds-and-targets.md, templates/link-check-record.template.md, templates/page-link-entry.template.md
Worked example, from the package
examples/quarterly-sweep-that-found-moved-guides/WALKTHROUGH.md
A small studio publishes the help docs for Slotwise, its fictional booking tool, as twelve pages that grew one at a time over two years. Nobody owned the links. Guides had been moved during two site tidies, and readers had started writing in to say a link in one page landed on a missing page or in the wrong guide. The operator set a quarterly cadence, built the first link record, and ran the first full sweep over one week. This is how that sweep ran and what it settled.
Translation Glossary Keeping
Data, Files, and Research · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
The same term stops being rendered two ways: one glossary record holds each term's approved rendering in each language and the context that decides between variants, and a new term enters the record only with the source it was admitted from.
What changes
- The same term rendered two ways across pages, with nobody able to say which rendering is approved → one glossary record holding each term's approved rendering in each language
- A new translator guessing at product terms, and drift found first by a reader who cannot tell that two names are one thing → each entry carrying the context that decides between variants, so a new batch and a new translator start from the record, not from a guess
- New terms entering by habit, from no named source → a new term admitted only with the source it was admitted from, and each new batch checked against the glossary before it is treated as done
Honest fit
For you if: Your material is translated into more than one language, and the same term comes back rendered in more than one way.
Skip it if: You need documents translated or a translation judged for how well it reads; this record keeps the approved renderings and the terms, and the people who translate do the translating.
Your first run produces: the first glossary record built from one named set of material, in about an hour: the record opened with the material it covers, the source language, each language covered, and the owner named, candidate terms gathered from that one set alone, repeats of the same source term merged into one entry each, any list that already exists brought in with where each of its terms came from noted where that can still be found, candidates with no source that can be pointed to held off the record as leads, and the approved rendering per language written on each entry.
Preview, from the skill itself
“# Translation Glossary Keeping<br># Translation Glossary Keeping Translated material drifts in a quiet way.”
Version 1.0.09 filesOne term, one entry, one recordNew terms are admitted only with a sourceVariants are named, not hiddenNo invented renderingsHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: ef5357eaaae0… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 55.6 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/cleaning-up-after-two-variants-spread/WALKTHROUGH.md, examples/first-glossary-for-a-plant-care-guide/WALKTHROUGH.md, reference/admitting-and-retiring-terms.md, reference/checking-a-batch-against-the-glossary.md, reference/choosing-between-variants.md, reference/glossary-terms-and-entry-parts.md, templates/glossary-entry.template.md, templates/glossary-record.template.md
Worked example, from the package
examples/cleaning-up-after-two-variants-spread/WALKTHROUGH.md
Maren Bay Tours is a fictional boat tour business with a small set of booking help pages, written in English and issued in German. A glossary record already existed, with 34 live terms. Over one season, pages were added by two translators working at different times, and three terms came back from a batch check with renderings that sat apart from the record. This is how the cleanup was worked, term by term, in counts.
Estimate vs Actual Review
Local Services / Money · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Closed jobs stop teaching nothing: each one is compared estimate line against actual line on a set cadence, the lines that keep running over or under are named as patterns, and the price list or scoping note adjustments those patterns support are drafted for your approval.
What changes
- Closed jobs forgotten one by one, so the same line is written the same way next month even when it runs over on every job → each closed job compared estimate line against actual line on a set cadence
- A materials line running under for a season hiding a labour line running over, so the total looks near enough and nothing is learned → the lines that keep running over or under named as patterns, with their counts and totals worked in the open
- The price list and the scoping notes staying as they were written once → the adjustments those patterns support drafted from the review log for the operator to approve, so closed jobs keep correcting them
Honest fit
For you if: You estimate jobs line by line, close them, and write the next estimate the same way, with nothing carried from the last jobs into the next price.
Skip it if: You need a profit figure per job, an estimate built for a new job, or a closed job repriced; this review stops at estimate against actual, and every adjustment faces forward, to the next estimate, and waits for your approval.
Your first run produces: the last four closed jobs reviewed line by line, in about forty minutes: one sheet opened per job with the estimate lines copied in exactly as given, the actual figure from each closed job record lined up beside its estimate line, each variance worked in the open and each job total checked against the sum of its line variances, the same line read across all four sheets, any line that moved the same way on at least three of the four jobs named as a pattern with its figures, and one adjustment drafted from the clearest pattern into the review log.
Preview, from the skill itself
“# Estimate vs Actual Review<br># Estimate vs Actual Review An estimate is a guess written before the work starts.”
Version 1.0.09 filesClosed jobs onlyEstimate and actual stay in their own columnsEvery variance is worked in the openAdjustments are drafts until the operator approvesHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 3105d7a14ad7… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 42.7 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/deck-repair-review-that-changed-the-scope/WALKTHROUGH.md, examples/fence-repairs-monthly-pattern-review/WALKTHROUGH.md, reference/lining-up-estimate-and-actual-lines.md, reference/naming-the-recurring-patterns.md, reference/running-the-review-cadence.md, reference/turning-the-review-into-adjustments.md, templates/estimate-vs-actual-sheet.template.md, templates/review-pattern-and-adjustment-log.template.md
Worked example, from the package
examples/deck-repair-review-that-changed-the-scope/WALKTHROUGH.md
A local service operator who does small outdoor repairs around houses. A customer, Dana Whitfield, had a price agreed to replace worn deck boards and rebuild the deck steps. The job closed, and at the weekly review the operator set the estimate against the actual, line by line. This example follows that one sheet, the lesson it held on its own, and the scoping change it drafted. The pattern across jobs is a later example's work; this one shows a single sheet done properly.
Equipment Rental Scheduling
Local Services / Field Operations · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Rented equipment stops being double counted: every booking sits on one schedule with its window, pickup and return times, and the job it serves, and every change is checked against that schedule, so a clash is caught on the page before it is caught on the morning.
What changes
- Rental bookings living in separate places, a date in the job diary, a time in a message, a rate on a slip from the yard → every booking on one schedule with its window, its pickup and return times, and the job it serves
- Each job looking fine on its own page, with the clash showing only on the day, when the machine is due in two places → every change checked against the schedule before it is made firm, so a clash is a dated fact with options worked beside it while there is still time to choose well
- A job moving and its rental quietly double counted → extensions and shortenings worked against the same schedule, with each booking's cost shown as arithmetic the operator can check
Honest fit
For you if: You rent equipment for jobs, and each booking lives in its own diary entry, message, or slip from the yard.
Skip it if: You need a rental booked, extended, or moved, a yard or a customer called, or a clash decided; those calls and that spending stay with you, and this schedule only puts the dates, the times, and the cost of each option in front of you.
Your first run produces: the next rental booking placed on one schedule and clash checked, in about thirty minutes: the booking read as the yard gave it, the item, the daily rate, and the window it was booked for, the job diary read for the job it serves and for any other job that wants the same item near those dates, the booking entered on the schedule with its pickup and return times, its cost worked as the daily rate times its rental days, and the clash check run against every other booking for that item, including any booking that only touches the first or the last day of the window.
Preview, from the skill itself
“# Equipment Rental Scheduling<br># Equipment Rental Scheduling A rented machine can only be in one place at a time.”
Version 1.0.09 filesOne schedule for every rental bookingA booking ties an item to a job and a windowOne item, one place, at one timeEvery change triggers a fresh checkHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: ae1591744418… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 36.3 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/chipper-extension-that-held/WALKTHROUGH.md, examples/mini-excavator-clash-when-a-job-moved/WALKTHROUGH.md, reference/booking-a-rental-window.md, reference/catching-and-working-a-clash.md, reference/extending-or-shortening-a-rental.md, reference/pickup-and-return-times.md, templates/booking-and-change-note.template.md, templates/rental-schedule.template.md
Worked example, from the package
examples/chipper-extension-that-held/WALKTHROUGH.md
A local operator who clears overgrown ground and cuts back trees and hedges. The operator rents a wood chipper for clearing jobs. This example follows one chipper booking in July, work that ran long by a day, and an extension that was checked against the next booking for the same chipper before it was agreed, and held because the gap after it still stood.
Winterization Checklist Runs
Local Services / Field Operations · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Each property gets the same winterization run every season, taps, pipes, heating, and gutters worked in order and marked as they stand, with findings and follow-ups written on the run record, so next season starts from this season's record instead of from memory.
What changes
- Winterization living in one person's head, the stiff tap at one house and the pipe that always needs lagging at another held only in memory → each property getting the same winterization run every season, taps, pipes, heating, and gutters worked in order from one checklist
- No one able to say in spring what was left open in October → findings and follow-ups written on the run record as they are seen, with a timing on each open item
- A skipped gutter or an undrained tap found only when the cold finds it first → the next visit and the next season starting from this season's record, with open items carried forward instead of rediscovered
Honest fit
For you if: You winterize the same properties each season, and what was found or left open last season lives in one person's memory.
Skip it if: You need repairs done, a promise that a property cannot freeze, or a full winter closing of an empty property; this run records the checks, and repairs are follow ups done under your own arrangements.
Your first run produces: one property given a full winterization run, in about forty-five minutes: the run record opened with the property block filled in from the operator record before the visit, any prior run record for the property read first and its open items taken along, the checklist worked from the top at the property, outdoor taps first, then exposed pipes, then the heating checks, then the gutters, each item marked as it stands at the place it was found, and a follow up list naming each open item with its timing, with no item claimed done that was not done.
Preview, from the skill itself
“# Winterization Checklist Runs<br># Winterization Checklist Runs Winter comes to the same properties every year, and the same places tend to need attention: the outdoor tap that was left with a hose on, the pipe run along an outside wall, the heating filter no one has looked at since spring, and the gutter that filled with leaves in October.”
Version 1.0.09 filesOne run, one property, one recordWork the whole list, in orderFindings are written as seenOpen items carry forwardHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 185c037eb5cd… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 47.0 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/single-family-house-first-run/WALKTHROUGH.md, examples/small-rental-duplex-with-open-items/WALKTHROUGH.md, reference/heating-and-gutter-checks.md, reference/recording-findings-and-follow-ups.md, reference/taps-pipes-and-freeze-risk-notes.md, reference/the-full-winterization-checklist.md, templates/follow-up-and-next-season-summary.template.md, templates/winterization-run-record.template.md
Worked example, from the package
examples/single-family-house-first-run/WALKTHROUGH.md
A local service operator who looks after houses for owners who live away part of the year. This example follows the first run at a three bedroom single family house, home of Dana Whitfield, who was at the property on the day. The house has a basement, a crawl space under the kitchen end, a gas furnace, and guttering on the front, back, and porch. This was the first run recorded under this skill, so there was no prior run record to read.
Quote Photo Attachments
Local Services / Sales · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
The photos that go out with a quote are chosen from the job's own record and labeled to the quote line each one supports, and anything the record does not back is held back with its reason logged, so the customer can match every photo to its line.
What changes
- Photos added at the point of sending, from memory or from the nearest folder → the photos that go out with a quote chosen from the job's own record before the quote is sent
- A clear photo going out with no label, so the customer cannot tell which line it belongs to → each photo labeled to the quote line it supports, so the customer can match every photo to its line
- A photo from an earlier visit, or from a job nearby, slipping in because it looks like the same kind of work → anything the record does not back held back with its reason logged, and every photo considered accounted for on the selection log
Honest fit
For you if: You send quotes that would be clearer with photos, and the photos are picked at sending time, from memory or from the nearest folder.
Skip it if: You need a quote built from photos, prices set, quote lines written, or photos taken or improved; this skill starts only once a quote exists, and attaching and sending stay with you.
Your first run produces: the next quote ready to send given a checked photo set, in about thirty minutes: the quote read as it stands, each line in order as worded, the job record for that job read and the photos it holds listed with their references, each candidate photo matched to the line it supports and labeled to that line, any photo the record does not back set aside with its reason, the attachment sheet drafted with a count that matches the photos named on it, and a selection log that accounts for every photo considered, the held back ones included.
Preview, from the skill itself
“# Quote Photo Attachments<br># Quote Photo Attachments A quote on its own asks the customer to picture the work.”
Version 1.0.09 filesPhotos come from the job recordOne label, one lineNothing is attached that the record does not backEvery candidate is accounted forHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: db5ceebd51af… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 34.0 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/deck-repair-quote-with-labeled-photos/WALKTHROUGH.md, examples/gutter-quote-with-a-photo-left-out/WALKTHROUGH.md, reference/checking-the-attachment-set-before-it-goes-out.md, reference/choosing-photos-from-the-job-record.md, reference/holding-back-photos-the-record-does-not-back.md, reference/labeling-each-photo-to-its-quote-line.md, templates/photo-selection-log.template.md, templates/quote-attachment-sheet.template.md
Worked example, from the package
examples/deck-repair-quote-with-labeled-photos/WALKTHROUGH.md
A local service operator who does small repairs around houses. A customer, Ellen Ward, asked for a price to repair the back deck at her house: boards to replace, one joist section to repair, and fixings to renew. The quote was written first, from a visit. This example follows what happened next: the photos for that quote were chosen from the job record, labeled to their lines, and checked, with one photo held back.
Short Video Caption Checks
Creator and Audience · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Captions stop quietly changing what a video says: every caption line is checked against the spoken words before posting, errors are listed per video and fixed in the caption file itself, and names and numbers get a second pass of their own.
What changes
- Captions trusted because a tool made them, or because they looked right on a quick read → every caption line checked against the spoken words before the video is posted
- The name that is nearly right, the time that is one digit off, and the price with its figures swapped all passing that quick read → names, numbers, and places given a second pass of their own
- Errors found by viewers, and repeated or acted on before anyone corrects them → errors listed per video and fixed in the caption file itself, so the file a viewer actually reads is the file that was checked
Honest fit
For you if: You post short videos with captions, and the captions come from a tool or from a quick read before they go out.
Skip it if: You need captions made from scratch for a video that has none, captions translated, or the video edited or posted; this check works on an existing caption file, against the spoken words in the same video.
Your first run produces: the next short video for posting given a full caption check, in about twenty minutes: the video played through once with no caption in front of you, just to hear it whole, the check sheet then worked line by line with each caption line's time, what the caption says, and what was spoken noted, every difference listed on the error list, the second pass for names and numbers run even when the main check found none, each confirmed error fixed in the caption file itself, and the fixed lines played once more against the audio.
Preview, from the skill itself
“# Short Video Caption Checks<br># Short Video Caption Checks A caption that says the wrong name or the wrong number is not a small typo.”
Version 1.0.09 filesThe audio is the sourceCheck every line, not a sampleNames and numbers get a second passFixes go in the caption fileHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 9, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: bf78a117d253… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 9, 2026): no leaks found.
Bundle size: 34.1 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/kitchen-tip-name-and-time-fixed/WALKTHROUGH.md, examples/workshop-demo-price-and-place-fixed/WALKTHROUGH.md, reference/checking-captions-against-the-audio.md, reference/fixing-errors-in-the-caption-file.md, reference/listing-errors-per-video.md, reference/names-numbers-and-places-second-pass.md, templates/caption-check-sheet.template.md, templates/caption-error-list.template.md
Worked example, from the package
examples/kitchen-tip-name-and-time-fixed/WALKTHROUGH.md
A fictional creator, Priya Nair, who posts short kitchen tips filmed at her home counter. This example follows one short video, about beans for a weeknight soup, from its first caption check to the fixed file held for her to post. All names, places, and figures in this example are made up for it, and the figures are the figures spoken in the example itself.
Agent Fleet Cost Review
Agent Operations · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Every agent in the fleet is judged on its own record: the cost for one period set beside the work that agent actually delivered, ending with one recorded call per agent, keep, narrow, or retire, with the reason in plain words.
What changes
- The fleet judged as one bill, a rising total starting an argument about agents in general → each agent judged on its own joined record, its cost and its delivered work for one period on one entry
- An agent nobody uses keeping its place because nobody can show its record on one page, and a good agent cut in a blunt round of savings → one call per agent, keep, narrow, or retire, with the reason written next to it in plain words
- Calls resting on memory, untestable a period later → a narrow call naming what gets smaller, a retire call handing its reason to the work that follows, and the next review testing every earlier call against a fresh period
Honest fit
For you if: You run a fleet of agents and cannot say, from a record, which ones earn their cost, or why an agent was kept, narrowed, or retired.
Skip it if: You need the ledger kept, an agent shut down, or a savings figure promised; this review reads the cost record and the work record and records the calls, and the operator makes each one.
Your first run produces: the most recent full period reviewed at the smallest honest size, in about an hour: the review record started from the fleet template, every agent that ran in the period listed from the fleet record and the cost record together, one entry per agent with its cost and its delivered work read from the records and any gap named, one draft call per agent with its reason, the operator confirming or changing each call, and the next review date set before you stop.
Preview, from the skill itself
“# Agent Fleet Cost Review<br># Agent Fleet Cost Review A fleet can look affordable in total and still carry agents that no longer earn their place.”
Version 1.0.09 filesCosts come from the cost record, never from memoryWork counts only when it can be pointed toOne agent, one call, one reasonCompare like with likeHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 10, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: f7b1878ab97d… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 10, 2026): no leaks found.
Bundle size: 41.2 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/first-review-for-a-four-agent-fleet/WALKTHROUGH.md, examples/quarterly-review-that-narrowed-two-agents/WALKTHROUGH.md, reference/joining-costs-to-delivered-work.md, reference/review-evidence-and-gaps.md, reference/setting-the-review-cadence.md, reference/the-three-calls.md, templates/agent-cost-review-entry.template.md, templates/fleet-cost-review.template.md
Worked example, from the package
examples/first-review-for-a-four-agent-fleet/WALKTHROUGH.md
A small design studio had run four agents for five months and had never once set their costs beside their work. The owner could see the monthly total rising and could not say which agent was behind the rise, or whether the rise was buying anything. She ran the first review over one month, the most recent full month in her records, in one sitting. Every name and figure here is invented for the example.
Launch Day Runbook
Studio / Shipping · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
The public launch day runs from one written runbook: the checks before the announcement closed on evidence, posts and pages landing in a set order, a named watcher on every surface, and rollback and correction lines approved before the first post goes out.
What changes
- A launch day held in the heads of the people in the room, its order living in a chat thread → the whole day written on one page before it starts, the order set line by line
- Checks run from what someone recalls on the morning, and watching that belongs to whoever happens to be looking → checks closed on evidence, and every surface given a named watcher for each stretch of the day
- A fault at a busy hour met with fresh drafting while readers wait → rollback and correction lines drafted and approved before the first post, and a log kept as the day goes, so what went out, in what order, can be shown later
Honest fit
For you if: You have a product, an update, or a service going public on a set day, with posts and pages that have to land in a set order.
Skip it if: You need the product built, the release run, or the posts published for you; this runbook orders the public day and its watching, and people still put each item out through its normal route.
Your first run produces: the first runbook built before the launch day, in about ninety minutes: what is launching, the announcement time, and the day lead written at its head, the checks before the announcement listed, the order of posts and pages set one line per item, a named watcher for every surface, the rollback and correction lines drafted and approved by the operator, and the log opened before the day starts.
Preview, from the skill itself
“# Launch Day Runbook<br># Launch Day Runbook A launch day looks simple from the outside.”
Version 1.0.09 filesThe runbook is written before the dayOne day, one runbook, one leadChecks close on evidence, not on recallEvery surface has a named watcherHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 10, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 24d6ca1b1c0d… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 10, 2026): no leaks found.
Bundle size: 40.6 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/first-launch-for-a-small-tool/WALKTHROUGH.md, examples/launch-day-with-a-late-correction/WALKTHROUGH.md, reference/before-the-announcement-checks.md, reference/order-of-posts-and-pages.md, reference/rollback-and-correction-lines.md, reference/who-watches-what.md, templates/launch-day-log.template.md, templates/launch-day-runbook.template.md
Worked example, from the package
examples/first-launch-for-a-small-tool/WALKTHROUGH.md
A two person studio had built a small tool that sorts job photos into folders by date and site name. It was their first public launch. The product was ready a week ahead, the page was drafted, and the announcement was two posts and a listing. Without a plan, the day would have been run from a chat thread. This is how the first runbook was built, the day before the launch, and how the day ran from it.
Archive Integrity Checks
Data, Files, and Research · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Archived files are tested on a set cadence against the archive index: each one opened in full and its hash compared with its index entry, so every failure is listed per file and can be repaired from the surviving copy while a good copy still exists.
What changes
- An archive trusted on faith, its files assumed whole because they went in whole → the archive tested on a cadence that is written down and held, each file opened in full and its hash compared with its index entry
- Nobody able to say when a file was last opened, or whether the copy on the shelf still matches the copy that was filed → every check leaving a dated log of what was opened, what matched, and what did not
- A fault found by the person who needs the file, on the worst day to find it → failures sitting on one list, per file, each naming where its good copy lives, so repair can start the same day
Honest fit
For you if: You hold an archive that is trusted without ever being tested, and you want faults found while a good copy still exists to repair from.
Skip it if: You need the archive index built, files repaired, or a backup held; this check tests files against the index and lists failures per file, and repairs are the operator's separate step.
Your first run produces: the first full check of a small archive run as it stands, in about an hour: the check log started with the archive name, the scope, and the cadence, files with no index entry or no hash listed at once as coverage gaps, each file in scope then opened in full and its fresh hash compared with its entry, every result written on the log as it goes, failures placed on the failure list with a next step each, and the next check date set before you stop.
Preview, from the skill itself
“# Archive Integrity Checks<br># Archive Integrity Checks An archive can hold a file for years and still lose it quietly.”
Version 1.0.09 filesThe index entry is the standard, the file is the thing testedA pass means both tests passedFailures are listed per file, never as a count aloneNo repair inside the checkHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 10, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: fd3d6456bdd3… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 10, 2026): no leaks found.
Bundle size: 41.5 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/first-check-for-a-small-office-archive/WALKTHROUGH.md, examples/quarterly-check-that-found-three-failures/WALKTHROUGH.md, reference/cadence-and-scope.md, reference/check-fields-and-statuses.md, reference/reading-the-hash-check.md, reference/repair-from-the-surviving-copy.md, templates/failure-list.template.md, templates/integrity-check-log.template.md
Worked example, from the package
examples/first-check-for-a-small-office-archive/WALKTHROUGH.md
A small office with four staff held an archive of scanned invoices and signed delivery notes, built up over three years and never tested as a whole. The files sat in one shared store, and the index, built when the archive was started, held an entry and a hash for most of them. The owner could open any single file on request, but nobody could say whether every copy still matched the copy that was filed. This is how the first check was run, in one afternoon, on a monthly cadence the office then kept.
Customer Win-Back Notes
Local Services / Reputation · Version 1.0.0 · 9 files
$12one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
Lapsed customers are reviewed one by one from their own job records, and a plain win-back note is drafted for each from what that record supports, held for your approval before anything is sent, with the answer recorded either way.
What changes
- Lapsed customers as a feeling, good customers gone quiet with nobody able to say which ones, for how long, or what their last job was → the quiet list as a record, with the lapsed line written down and each customer past it reviewed from their own job record
- Reaching out as one general note to everyone, or a burst of messages written from memory → one plain note per customer, drafted from what that customer's record supports and nothing it does not
- Answers lost once a round ends, and the same customers worked twice → every note held for approval before it is sent, and the answer, a yes, a no, or no reply, recorded in the log either way
Honest fit
For you if: You run local service work and have past customers who went quiet after a job that went well, and you want to reach them from their records, not from memory.
Skip it if: You need notes sent for you, offers or discounts invented, or customers chased after a no; the operator approves and sends every note, and one note per customer is the whole of a round.
Your first run produces: the first round run in about thirty minutes: the lapsed line set and written at the top of the log, five past customers past that line taken from the records, each job record read in full, anyone with open work, an open complaint, or an open price question ruled out with the reason logged, one note drafted per customer who remains and all of them held, the operator approving, editing, or dropping each one, and a log entry opened for every customer considered.
Preview, from the skill itself
“# Customer Win-Back Notes<br># Customer Win-Back Notes Category: Local Services / Reputation”
Version 1.0.09 filesEvery line in a note traces to the recordNo invented offersEvery note is held for approvalOne note, then the answer standsHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 10, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 71fbf95e3d28… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 10, 2026): no leaks found.
Bundle size: 30.9 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/hauling-customer-after-a-long-gap/WALKTHROUGH.md, examples/yard-cleanup-customer-who-went-quiet/WALKTHROUGH.md, reference/drafting-the-win-back-note.md, reference/finding-lapsed-customers.md, reference/holding-for-approval.md, reference/recording-the-answer.md, templates/win-back-log-entry.template.md, templates/win-back-note.template.md
Worked example, from the package
examples/hauling-customer-after-a-long-gap/WALKTHROUGH.md
Names and details in this example are fictional. Dana is a generic invented customer, and the job is an invented one, written to show the shape of the work.
Year Plan Budget Setup
Local Services / Money · Version 1.0.0 · 9 files
$15one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
The coming year runs against a written plan built from your own prior year records: a planned figure and a reason for every income and expense class, totals worked in the open, and set review dates for reading the plan against actuals while the year can still be steered.
What changes
- A new year answered from habit, fuel and parts and work all about the same → the year running against a written plan built from the prior year records, each class carried over under the name those records use
- No written figure to read a slow month against, a slow month and a falling year looking the same until late → a planned figure and a reason for every class, and set review dates that sit actuals beside the plan while the year can still be steered
- A strong month quietly hiding a class running well over what anyone meant to spend → totals worked in the open, and every change to the plan dated and reasoned, so the year can be read at its end against the plan it started with
Honest fit
For you if: You run local service work, you hold a prior year of income and expense records, and you want the coming year written down as figures with reasons before the year starts moving.
Skip it if: You hold no usable records for the prior year, or your money is held in another system you trust and can check; a plan built with no records behind it is guesswork with a tidy cover, and this skill will not build one.
Your first run produces: the first plan built from the prior year records in one sitting: the plan started with the business name, the plan year, and the year the figures rest on, the income and expense classes listed exactly as the records name them, one planned figure per class with its prior year actual and its reason, a flag on any class no record can support, the two totals and the planned difference worked in the open, and the review cadence set with its first date written.
Preview, from the skill itself
“# Year Plan Budget Setup<br># Year Plan Budget Setup A new year usually starts with the same money questions as the last one, answered from habit.”
Version 1.0.09 filesPlanned figures come from the operator's own records, never inventedRecords over memoryEvery planned figure carries its reasonTotals are worked in the openHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 10, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 57d2b56fa39b… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 10, 2026): no leaks found.
Bundle size: 41.2 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/first-year-plan-for-a-small-crew/WALKTHROUGH.md, examples/second-year-plan-after-a-full-year-of-actuals/WALKTHROUGH.md, reference/carrying-classes-forward.md, reference/handling-classes-that-change.md, reference/reviewing-plan-against-actuals.md, reference/setting-planned-figures-with-reasons.md, templates/plan-review.template.md, templates/year-plan.template.md
Worked example, from the package
examples/first-year-plan-for-a-small-crew/WALKTHROUGH.md
All business names, classes, and figures in this example are fictional example numbers, written to show the shape of the work. They are not the figures of any real business.
Skill Stack Planner
Agent Operations · Version 1.0.0 · 9 files
$19one time
VettedVerified BundleFull RecordWorked ExamplesFirst-Party
A workflow is planned end to end on one page: each step matched to a skill the operator holds or to a named gap, and the gaps ordered by what blocks the most work, so the cover held and the gaps that matter first are both plain to see.
What changes
- Skill cover as a feeling, a held set that grew one skill at a time assumed to cover the workflows that matter → cover as one written page, the workflow listed step by step and each step matched to a held skill or written down as a named gap
- The first sign of a gap a stall in live work, answered by improvising the missing middle by hand on every run → partial cover showing its split, and the gaps ordered by the work they block, with the workarounds in use named
- The same missing step costing time on every run and written down nowhere → the operator deciding about one gap at a time, in the right order, able to show anyone exactly where a workflow is strong and where it is thin
Honest fit
For you if: You plan or run a workflow and want to know, step by step, which steps a held skill covers and which steps have no cover.
Skip it if: You need a gap filled, a skill bought or installed, or the workflow run for you; this plan names and orders the gaps from your own records, and what happens about each one is the operator's call.
Your first run produces: one workflow planned in about forty five minutes: the plan started with the workflow name, its end point, and where your skill records live, the steps listed in order with any step hiding two kinds of work split, the held list built from your own records only, each step matched and marked covered, partly covered, or gap with its reason, and the gaps ordered by blocked work with the next check date set before you stop.
Preview, from the skill itself
“# Skill Stack Planner<br># Skill Stack Planner A workflow rarely fails all at once.”
Version 1.0.09 filesThe workflow comes first, the skills secondNever invent a held skill to fill a stepEvery step gets one honest resultGaps are ordered by blocked work, not by tasteHash verified against the registry
Package makeup: 1 skill file · 2 worked examples · 4 references · 2 templates
Vetting record
Scanned Nov 10, 2026 with the studio Skill Vetting scanner (33 signal patterns across six areas: prompt injection, dangerous commands, data exfiltration paths, obfuscation, secrets handling, environment harvesting).
Bundle sha256: 586006291f01… Short form. The full hash lives in the registry and is verified on every gate run.
Result: 0 findings on 9 files.
Second scan (gitleaks 8.30.1, Nov 10, 2026): no leaks found.
Bundle size: 41.4 KB · Format: SKILL.md package
Catalog record: GhostBus Hub skills on GitHub First-party package by Ghost Developer Studio; the package itself is delivered with purchase.
Listing record: 8 of 8
What's inside
SKILL.md, examples/planning-a-monthly-report-workflow/WALKTHROUGH.md, examples/planning-coverage-for-a-client-onboarding-workflow/WALKTHROUGH.md, reference/keeping-the-plan-current.md, reference/matching-steps-to-skills.md, reference/ordering-gaps-by-blocked-work.md, reference/stack-plan-fields.md, templates/skill-stack-plan.template.md, templates/workflow-step-map.template.md
Worked example, from the package
examples/planning-a-monthly-report-workflow/WALKTHROUGH.md
This example is fictional. The workflow, the people, and the skill names are invented for this walkthrough and stand for generic kinds of work and generic kinds of skill. Nothing here describes a real business or a real held set.