pod-sales
Run one tick of the sales business-pod (ADR-164 §4.1, Phase 2). Loads templates/sales.json, validates it against the pod-schema, resolves agents against ruflo's agent registry, reserves budget via the Phase-2 file-based stub ledger (atomic SQLite tracker is Phase 3 per ADR-164.1), constructs per-agent dry-run prompts, posts a summary envelope to room "sales" via the federation_bbs_publish JSONL backing store, and emits a structured {podName, tickId, agentsRan, totalUsd, envelopeId, status} line for /loop ingestion. Dry-run by default; --live is reserved for Phase 3.
Profile →npx skills add ruvnet/ruflo --skill pod-sales --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
Surfaces `pod-tick.mjs` as a single-shot skill for the sales pod. Use when Claude Code needs to demonstrate, smoke-test, or schedule one iteration of the sales autopilot without spawning real LLM workers. ## Algorithm Implementation: [`scripts/pod-tick.mjs`](../../scripts/pod-tick.mjs). 1. Parse args (`--pod-template`, `--base-path`, `--dry-run` / `--live`, `--budget-cap-usd`, `--tick-id`). `--live` is refused with exit code 3 in Phase 2. 2. Load the pod template JSON (default: `templates/sales.json`). 3. Validate via `validatePodTemplate(json)` — schema in `v3/@claude-flow/cli/src/business-pods/pod-schema.ts` and inlined in `pod-tick.mjs` so the script runs without a built CLI. Throws with a JSON-pointer path on the first violation. 4. Resolve every `agent.agentType` against `KNOWN_AGENT_TYPES`. Unknown types abort with exit code 2 and an actionable error. 5. Reserve `min(budgetUsdPerRun, --budget-cap-usd)` USD against the file-based ledger at `<base-path>/budget/<roomId>.json`. Honors `reservationExpiryMs` (default 60_000 ms, bounded to [5000, 300000] per ADR-164.1 §3.2). `TODO(adr-164.1)`: swap the file ledger for the atomic SQLite tracker in Phase 3. 6. Build per-agent prompts
- Algorithm
- Exit codes
- Phase 3 surfaces (not in this build)
What does the pod-sales skill do?
Run one tick of the sales business-pod (ADR-164 §4.1, Phase 2). Loads templates/sales.json, validates it against the pod-schema, resolves agents against ruflo's agent registry, reserves budget via the Phase-2 file-based stub ledger (atomic SQLite tracker is Phase 3 per ADR-164.1), constructs per-agent dry-run prompts, posts a summary envelope to room "sales" via the federation_bbs_publish JSONL backing store, and emits a structured {podName, tickId, agentsRan, totalUsd, envelopeId, status} line for /loop ingestion. Dry-run by default; --live is reserved for Phase 3.
How do I install it?
Run `npx skills add ruvnet/ruflo --skill pod-sales --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ruvnet/ruflo, a repository with 67,015 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.