Pod Sales logo

Pod Sales

CommunityPopular
ruvnet
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.

Overview

Publisherruvnet
Repositoryruflo
Skill namepod-sales
Stars
72.7K
Forks
8.6K
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by ruvnet on GitHub. Read the source before you install it.

Installation

Install the Pod Sales AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/ruvnet/ruflo.git /tmp/ruflo
mkdir -p .claude/skills
cp -r /tmp/ruflo/plugins/ruflo-business-pods/skills/pod-sales .claude/skills/pod-sales
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Pod Sales in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Pod Sales on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Pod Sales is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.

  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.

Frequently asked questions

What does the Pod Sales AI 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.

Why use Pod Sales on TypingMind?

Because you install it once and use it with any model. Pod Sales is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Pod Sales in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/ruvnet/ruflo/tree/main/plugins/ruflo-business-pods/skills/pod-sales. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Pod Sales?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Pod Sales?

As many as you like. As long as a model supports skills, you can use Pod Sales with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Pod Sales AI skill free?

Yes. It is published on GitHub by ruvnet under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇