SKILLEMALL.ai
GitHub ↗ RU Sign in

DF 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.

ruvnet/claude-flow Claude Code author: ruvnet MIT 1 file body ≈ 586 tokens Open the sourcegithub.com↗ analyzed 30 h ago

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…

As a process F 33/100 · No process to follow — References files that are not bundled: ../../scripts/pod-tick.mjs, scripts/pod-tick.mjs, templates/sales.json

AnalyzerAI and agentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
D
77/100
safety, quality, tests
Safety 60%
95
Quality 40%
51
Run on models
none yet
Process rating
F
33/100
No process to follow
References files that are not bundled: ../../scripts/pod-tick.mjs, scripts/pod-tick.mjs, templates/sales.json
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 1

✓ No critical or high findings

Medium and low: 1
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Bash

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: ../../scripts/pod-tick.mjs
  • warning missing-ref reference to a missing file: scripts/pod-tick.mjs
  • warning missing-ref reference to a missing file: templates/sales.json

Process rating: all ten parameters 33/100

Will not run. References files that are not bundled: ../../scripts/pod-tick.mjs, scripts/pod-tick.mjs, templates/sales.json
  • 0Tools and files. 3 referenced file(s) missing: ../../scripts/pod-tick.mjs, scripts/pod-tick.mjs, templates/sales.json
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 2 mutating operations with no state check
  • 100Steps. 15 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 586 tokens

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • -5TODO / placeholder text left in the skill
  • +1No license
  • +2Single-language instructions
  • +3Description length 572: enough signal without eating the budget
  • +4Structure: 3 headings
  • +3Step-by-step instructions: 15 items

Quality base 70; lint remarks subtract, signals add up to 100. Result: 51.