sales

Sales pipeline operations via snappy-knowledge.

Ported from kernel snappy-sales in Phase 0.5. See state/lib/sales.ts for the full API surface.

Steps

• getLeads() - see state/lib/sales.ts
• getSalesClients() - see state/lib/sales.ts
• logActivity() - see state/lib/sales.ts

Eval

Actor: the exported functions in state/lib/sales.ts. Auditor: none wired yet - eval is manual (Robert review). File a state/log/pending-eval.ndjson row on each run.

Score convention:

Gotchas

via the Phase 0.5 driver. Only these rewrites were applied: already in state/lib/)

1. realpathSync(process.argv[1]) CLI guard wrapped in try/catch

• See the kernel SKILL.md for the original long-form guidance if you need it

(read-only reference at the kernel path above).

Graduation

This skill is prose. Graduate by defining a deterministic auditor and flipping eval: auto.

Rubric

criteria:
  - name: get_leads_functionality
    kind: deterministic
    check: "The `getLeads()` function in `state/lib/sales.ts` executes without error and returns a valid data structure."
  - name: get_sales_clients_functionality
    kind: deterministic
    check: "The `getSalesClients()` function in `state/lib/sales.ts` executes without error and returns a valid data structure."
  - name: log_activity_functionality
    kind: deterministic
    check: "The `logActivity()` function in `state/lib/sales.ts` executes without error and correctly logs activity based on its input."
  - name: output_conforms_to_spec
    kind: judge
    check: "The output for each function call (getLeads, getSalesClients, logActivity) within the skill's execution aligns with the expected data types and content outlined in the `snappy-sales` kernel specification."

sales - loader

Per-turn rules for the sales skill. Full reference: state/skills/sales/SKILL.md.

Critical Rules

_(no failures recorded yet - this skill has not produced hard-won rules. It is a Phase 0.5 port from kernel snappy-sales. Read state/lib/sales.ts for the actual API surface before invoking.)_

• NEVER frame sales drafts with scarcity hooks ("idle hours", "leftover budget"). Banned per memory: no scarcity offers; Robert is system owner, value-first only.
• ALWAYS log activity via logActivity() after touching a lead/client - the pipeline cares about the audit trail, not just the outcome.

Commands

| ui dashboard | state/skills/sales/resources/ui.openui | |invoke (TS): import { getLeads, getSalesClients, logActivity } from "../lib/sales.ts" |eval log: state/log/pending-eval.ndjson (skill: "sales") - manual until auditor wired

OpenUI Resource

• Skill-owned OpenUI Lang resource: state/skills/sales/resources/ui.openui. Read it before rendering or editing this skill's generated component surface.
• Treat this resource as a first-class artifact of the skill, not a generic chat response. Improve it when the skill's user-facing output needs to become richer.
• System resources compose OpenUI primitives and inherit SnappyChat tokens. Use ui_contract: branded in SKILL.md only for deliberate platform or client visuals.

Known Pitfalls

• Phase 0.5 port stub. Real behavior in state/lib/sales.ts.
• This skill reads the pipeline; it does not send outbound. For outbound use state/lib/outbound.ts or the dormant-ping / testimonial-ask skills.

Self-Test

An agent reading this should correctly:

1. [ ] Refuse to draft a sales touch with scarcity framing
2. [ ] Log activity after every lead/client mutation
3. [ ] Distinguish sales (read pipeline) from outbound (send messages)

Self-report

If this loader fell short, append a line:

echo "[$(date -u +%FT%TZ)] sales: <what was missing>" >> state/log/loader-feedback.log

<!-- kernel-ok: historical attribution for the PID-loader pattern. -->

Self-correcting loader (PID feedback)

This is the rule that makes loaders learn. Ported from snappy-kernel, where it demonstrably worked: the snappy-dom-cartographer skill mapped Skool admin UI once, every later ship-agent inherited the full map for free.

Before you finish, do two things:

1. Fix gaps (P - proportional). MANDATORY. If this loader didn't cover your case - if you had to read another file, run an undocumented command, work around a wrong selector, or discover a quirk - you MUST attempt an Edit to this AGENTS.md before you log.

• Default action: edit this file. Surgical. Add the missing line, table

row, or code example where it belongs. No restructuring.

• Only LOGGED is allowed when: the fix needs >10 lines, spans multiple

files, or requires a structural rewrite. In that case the state/regen/drain.sh queue picks it up asynchronously.

• "I didn't have time" / "it's minor" / "the next agent will figure it out"

are NOT valid reasons. Minor gaps compound - that's the whole point of this loop.

• Concrete example of a valid P-fix: discover agent-browser screenshot

takes path positionally not as --output <path>. One line in a table. Edit it in. Do not just log it.

• The goal: the next agent never has to leave the loader.

2. Log the result.

echo "[$(date -u +%FT%TZ)] sales: <what was missing or fixed> [FIXED|LOGGED]" >> state/log/loader-feedback.log

• FIXED = you patched this loader inline (P-fix).
• LOGGED = too large for inline; the PostToolUse enqueue + Stop-hook drain

will rewrite the loader from scratch on next session-end.

Do not skip this. Every agent run must leave the system better than it found it. The loader is the setpoint; you are the sensor; the gap is the error signal; closing the gap is the correction.