Run any Skill in Manus with one click

pod-sales

Stars62,255

Forks7,299

UpdatedJune 29, 2026 at 22:28

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

ruvnet

ruvnet/ruflo

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

SKILL.md

readonly

name	pod-sales
description	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.
argument-hint	[--pod-template <path>] [--base-path <dir>] [--dry-run\|--live] [--budget-cap-usd <amt>] [--tick-id <id>]
allowed-tools	Bash

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.

More from this repository

same repository

security-scan

ruvnet/ruflo

Run full security scans on the codebase using Ruflo security tools. Use when reviewing PRs for security regressions, auditing auth/input-handling code, before production deploys, or when the user asks for a security check at quick/standard/deep depth.

2026-06-2762.3k

swarm-init

ruvnet/ruflo

Initialize a multi-agent swarm with anti-drift configuration. Use when starting a complex multi-file task that needs 3+ coordinated agents (feature implementation, refactor across modules, security audit). Skip for single-file edits or quick questions.

2026-06-2762.3k

sparc-implement

ruvnet/ruflo

Run the SPARC Pseudocode and Architecture phases (2 and 3) — write algorithm pseudocode, design module boundaries and API contracts, then implement

2026-06-2762.3k

create-plugin

ruvnet/ruflo

Scaffold a new Claude Code plugin with proper directory structure, plugin.json, skills, commands, and agents

2026-06-2762.3k

dependency-check

ruvnet/ruflo

Scan project dependencies for known vulnerabilities and CVEs. Use when auditing third-party packages, before releases, after `npm install`/lockfile changes, or when investigating reported CVE advisories.

2026-06-2762.3k

chat-format

ruvnet/ruflo

Format prompts for different LLM providers with chat templates and HNSW-powered context retrieval

2026-06-2762.3k

name	pod-sales
description	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.
argument-hint	[--pod-template <path>] [--base-path <dir>] [--dry-run\|--live] [--budget-cap-usd <amt>] [--tick-id <id>]
allowed-tools	Bash

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.