pod-sales

Runs one dry-run tick of the sales business-pod with budget reservation and status envelope emission.

70.1k|8.4k|Updated Jun 2, 2025
One-click install
npx skills add https://github.com/ruvnet/claude-flow --skill pod-sales
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pod-sales
Source: https://github.com/ruvnet/claude-flow/tree/main/plugins/ruflo-business-pods/skills/pod-sales
Command: npx skills add https://github.com/ruvnet/claude-flow --skill pod-sales

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It lets you smoke-test or schedule a single iteration of the sales autopilot business-pod without spawning real LLM workers, validating templates, agent types, and budget reservations safely in dry-run mode.

Core Features & Use Cases

  • Pod Template Validation: Loads templates/sales.json and validates it against the pod-schema, reporting JSON-pointer paths on violations.
  • Budget Reservation: Reserves budget via a file-based ledger with configurable caps and reservation expiry, honoring ADR-164.1 constraints.
  • Status Envelope Emission: Appends a pod-status envelope to the federation BBS JSONL backing store and emits a structured JSON summary line for /loop ingestion.
  • Use Case: Run a scheduled dry-run tick of the sales pod to verify agent resolution and budget accounting before Phase 3 enables live LLM dispatch.

Quick Start

Run the pod-sales skill in dry-run mode with the default sales template to execute one validated tick and view the JSON status summary.

Frequently Asked Questions about pod-sales

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a dry-run tick of the sales business-pod?

Invoke the pod-sales skill with default arguments to load templates/sales.json, validate it, reserve budget, and emit a JSON status line. Dry-run is the default mode, so no real LLM workers are spawned and actual spend is $0.

What does the pod-sales skill validate before running a tick?

It validates the pod template JSON against the pod-schema, reporting a JSON-pointer path on the first violation, and resolves every agentType against the known agent registry. Unknown agent types abort with exit code 2 and an actionable error.

Can I run the sales pod in live mode with real LLM workers?

No, live mode is refused with exit code 3 in Phase 2. The --live flag is reserved for Phase 3, which will dispatch prompts through claude -p headless and wire an atomic SQLite budget tracker.

How does budget reservation work in the sales pod tick?

The skill reserves the minimum of budgetUsdPerRun and the --budget-cap-usd argument against a file-based ledger at <base-path>/budget/<roomId>.json. Reservation expiry defaults to 60000 ms, bounded between 5000 and 300000 ms per ADR-164.1.

Why does the pod tick fail with exit code 2?

Exit code 2 indicates an invalid template, an unknown agent type, exhausted budget, or an argument error. Check the error output for the JSON-pointer path or agent type that caused the failure.