How do I install the Pod Sales skill?

Run npx skillmds add thedixitjain/pod-sales in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pod Sales safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pod Sales?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pod Sales free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pod Sales?

thedixitjain (@thedixitjain) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pod Sales by thedixitjain — Agent Skill

Name: Pod Sales
Rating: 4.2 (5 reviews)
Author: thedixitjain

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.

thedixitjain 35cfadc 3.1 KB Updated Sep 9, 2026 2 repo stars

File contents

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.

Parse args (--pod-template, --base-path, --dry-run / --live, --budget-cap-usd, --tick-id). --live is refused with exit code 3 in Phase 2.
Load the pod template JSON (default: templates/sales.json).
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.
Resolve every agent.agentType against KNOWN_AGENT_TYPES. Unknown types abort with exit code 2 and an actionable error.
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.
Build per-agent prompts (kickoff scoped to the bench description + pod's PII policy). In --dry-run they are logged to stderr and the model is never invoked.
Commit the reservation. Dry-run actual = $0; live actual = the reserved amount (Phase 3 wires real claude -p --max-budget-usd reporting).
Append a pod-status envelope to the Phase-1 backing store at <base-path>/.agentbbs/room-<derivedRoomId>.jsonl so subsequent federation_bbs_watch calls see the tick.
Emit a single JSON line on stdout: {podName, tickId, agentsRan, totalUsd, envelopeId, status}.

Exit codes

0 — tick succeeded (status === 'success')
2 — invalid template / unknown agent type / budget exhausted / arg error
3 — --live requested (refused in Phase 2)

Phase 3 surfaces (not in this build)

--live mode: dispatch each prompt through claude -p headless or a Managed Agent and capture the actual --max-budget-usd reported spend.
Atomic SQLite budget tracker (ADR-164.1 §3.2).
Multi-pod variants (pod-marketing, pod-finance, ...) — each gets its own skill once Phase 3 ships.

Source: ruvnet/ruflo → plugins/ruflo-business-pods/skills/pod-sales/SKILL.md

---name: pod-salesdescription: 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.--- 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 (kickoff scoped to the bench description + pod's PII policy). In `--dry-run` they are logged to stderr and the model is never invoked. 7. Commit the reservation. Dry-run actual = $0; live actual = the reserved amount (Phase 3 wires real `claude -p` `--max-budget-usd` reporting). 8. Append a `pod-status` envelope to the Phase-1 backing store at `<base-path>/.agentbbs/room-<derivedRoomId>.jsonl` so subsequent `federation_bbs_watch` calls see the tick. 9. Emit a single JSON line on stdout: `{podName, tickId, agentsRan, totalUsd, envelopeId, status}`. ## Exit codes - `0` — tick succeeded (`status === 'success'`) - `2` — invalid template / unknown agent type / budget exhausted / arg error - `3` — `--live` requested (refused in Phase 2) ## Phase 3 surfaces (not in this build) - `--live` mode: dispatch each prompt through `claude -p` headless or a Managed Agent and capture the actual `--max-budget-usd` reported spend. - Atomic SQLite budget tracker (ADR-164.1 §3.2). - Multi-pod variants (`pod-marketing`, `pod-finance`, ...) — each gets its own skill once Phase 3 ships. --- **Source:** [`ruvnet/ruflo`](https://github.com/ruvnet/ruflo) → `plugins/ruflo-business-pods/skills/pod-sales/SKILL.md`

Frequently asked questions