Skip to content

reply-team/jason-ai / skills/business/sdr-operations

sdr-operations

Verified

FileKindSize
SKILL.mdskill md31.7 KB
lexicon/neutral.yamlconfig20.8 KB
operations/01-discovery.yamlconfig6.5 KB
operations/02-contacts.yamlconfig9.9 KB
operations/03-audiences.yamlconfig6.9 KB
operations/04-import.yamlconfig2.2 KB
operations/05-campaigns.yamlconfig15.5 KB
operations/06-steps.yamlconfig10.2 KB
operations/07-messages.yamlconfig3.9 KB
operations/08-enrollment.yamlconfig5.3 KB
operations/09-conversations.yamlconfig4.5 KB
operations/10-tasks.yamlconfig5.0 KB
operations/11-meetings.yamlconfig9.6 KB
operations/12-signals.yamlconfig4.8 KB
operations/13-inbound.yamlconfig5.7 KB
operations/14-privacy.yamlconfig12.0 KB
operations/15-sending.yamlconfig18.0 KB
operations/16-social.yamlconfig6.6 KB
operations/17-oversight.yamlconfig16.1 KB
operations/18-team.yamlconfig6.7 KB
operations/19-accounts.yamlconfig6.2 KB
operations/20-measurement.yamlconfig5.1 KB
operations/21-introspection.yamlconfig8.1 KB
operations/families.yamlconfig15.5 KB
references/catalog-01-discovery.mdmarkdown5.6 KB
references/catalog-02-contacts.mdmarkdown7.1 KB
references/catalog-03-audiences.mdmarkdown5.2 KB
references/catalog-04-import.mdmarkdown2.5 KB
references/catalog-05-campaigns.mdmarkdown11.4 KB
references/catalog-06-steps.mdmarkdown7.6 KB
references/catalog-07-messages.mdmarkdown3.8 KB
references/catalog-08-enrollment.mdmarkdown5.0 KB
references/catalog-09-conversations.mdmarkdown4.1 KB
references/catalog-10-tasks.mdmarkdown4.2 KB
references/catalog-11-meetings.mdmarkdown7.5 KB
references/catalog-12-signals.mdmarkdown4.2 KB
references/catalog-13-inbound.mdmarkdown4.9 KB
references/catalog-14-privacy.mdmarkdown9.2 KB
references/catalog-15-sending.mdmarkdown13.0 KB
references/catalog-16-social.mdmarkdown5.3 KB
references/catalog-17-oversight.mdmarkdown11.2 KB
references/catalog-18-team.mdmarkdown5.4 KB
references/catalog-19-accounts.mdmarkdown5.2 KB
references/catalog-20-measurement.mdmarkdown4.7 KB
references/catalog-21-introspection.mdmarkdown6.6 KB
references/chains.mdmarkdown63.3 KB
references/invariants.mdmarkdown39.7 KB
references/non-operations.mdmarkdown14.2 KB
references/open-questions.mdmarkdown40.9 KB
references/operation-index.mdmarkdown41.4 KB

references/catalog-15-sending.md

View on GitHub
<!-- Generated. Do not edit by hand. -->

# Family 15 — Sending capability and deliverability

Generated from the contract fragments in `operations/`. Edit a fragment, not this file.

*Permission and capability* · 34 operations · contract 2.0.0

**Reading the table.** † marks a core operation. The five properties are *reach*
(`read` changes nothing · `control` changes state we own · `act` reaches the outside world),
*reversibility* (`reversible` · `compensatable` · `irreversible`), *approval*
(`auto` · `confirm_once` · `confirm_each`, derived from reversibility × reach), *before repeating*
(the observable state to read before running it again) and *cost* (`none` · `metered`, with its
basis and the meter it consumes). *Key* and *per-item* are the two standing obligations: an
idempotency key on every act, every metered call, every write accepting a collection and every
write creating a durable object. A write that takes no key says why in *exempt* — `absolute_valued`
(the same value written again), `terminal_state` (the same state arrived at again), or `unstated`,
which is the contract admitting it has no reason and not a claim that one exists. And one outcome
per item whenever a collection is carried. Where a property is conditional the cell holds the
dangerous reading, with the condition beneath it.

| Operation | Intent | Reach | Reversibility | Approval | Before repeating | Cost | Key | Per-item | Invariants |
|---|---|---|---|---|---|---|---|---|---|
| `sender.list` | "What can we send from?" — mailboxes, social accounts, numbers and business messaging identities in one list. | `read` | `reversible` | `auto` | nothing at stake | `none` | `none` | `not_applicable` | — |
| `sender.get` | "Show me this sending capability in full" — identity, channel, configured pacing, message defaults, pool membership, registration. | `read` | `reversible` | `auto` | nothing at stake | `none` | `none` | `not_applicable` | — |
| `sender.health` † | "Can this sender send today, and if not why?" — connection, restrictions, warm-up position, capacity budgets, and the channel's automation sanction. | `read` | `reversible` | `auto` | nothing at stake | `none` | `none` | `required` | `A6`, `E15`, `F3`, `F4`, `F5`, `F10`, `F11` |
| `sender.connect` | "Attach a mailbox, social account, number or business messaging identity". | `control` | `compensatable` | `confirm_once` | the sender's existence and state — a half-finished connection must read as `pending_setup`, not as absent. | `none` | `required` | `not_applicable` | — |
| `sender.disconnect`<br>*questions:* 15 | "Detach it" — refused while live enrolments or open conversations depend on it, unless a rebind target is supplied. | `control` | `compensatable` | `confirm_once` | the sender's state and what is still bound to it. | `none` | `required` | `not_applicable` | `F8` |
| `sender.reauthorize` | "Restore a lapsed authorisation without losing the history behind it". | `control` | `reversible` | `auto` | the sender's authorisation state and its last-checked time. | `none` | `required` | `not_applicable` | — |
| `sender.pause` | "Stop this capability sending, now" — the first move in every incident on every channel. | `control` | `reversible` | `auto` | the sender's send state. | `none` | `required` | `required` | `L6` |
| `sender.resume` | "Let it send again" — refuses unless the warm-up position is valid or an override is recorded. | `control` | `reversible` | `confirm_once`<br>*departs:* raised from auto: sender.pause is protective, and the restart direction of a protective pair is never auto. Platforms escalate on the frequency of restrictions, not their type, so resuming at pre-restriction volume the moment a block lifts is the standard way to turn a temporary restriction into a permanent one; a recorded restriction invalidates the current warm-up position and this operation refuses while it is invalid unless a ramp restart is supplied or an override is recorded with an actor and a reason. | the sender's send state, its warm-up position and whether that position was invalidated. | `none` | `required` | `required` | `F4`, `G5`, `L6` |
| `sender_limit.set` | "How much may this send, how fast, and with what spacing" — one decision, not three. | `control` | `reversible` | `confirm_once`<br>*departs:* raised from auto: one call declares how much this capability may send, how fast and with what spacing, over limits somebody else may have declared — the read before repeating is the limits in force and who declared each. The derivation table admits confirm_once where a call may overwrite state someone else owns only in the compensatable column, so declaring it on a reversible control is a raise. | the limits in force and who declared each. | `none` | `required` | `required` | `F1` |
| `warmup_plan.set` | "Define the ramp this sender follows, and whether it is running". | `control` | `reversible` | `confirm_once`<br>*departs:* raised from auto: warm-up is a state machine with a position, and that position is what sender.resume refuses on — a recorded restriction invalidates it — so redefining the ramp overwrites the state that governs whether the sender may send at all. | the current plan, position and whether the position is valid. | `none` | `required` | `not_applicable` | `F4`, `F11` |
| `message_element.set` | "The mandatory elements every message from this sender carries" — legal identification block, postal address where required, the channel's required stop artefacts each separately (on email: header, one-click endpoint, visible link), tracking domain. | `control` | `reversible` | `confirm_once`<br>*departs:* raised from auto: the call overwrites what every message sent afterwards is legally held to, and the unsubscribe mechanism is three separate artefacts — a header, a machine-actionable endpoint that actually honours a request, and a visible link in the body — each separately required, configured and checked, where header presence proves only the first. | the elements currently in force. | `none` | `required` | `not_applicable` | `F7` |
| `sender.reserve` | "Claim one unit of allowance so parallel work cannot spend it twice". | `control` | `reversible` | `auto` | the reservation ledger for this sender and window. | `none` | `required` | `required` | `A6`, `F3` |
| `sender.release` | "Give the claim back". | `control` | `reversible` | `auto` | the reservation's state. | `none` | `required` | `required` | — |
| `sender.summarize` | "This sender's numbers over a window" — failures by class, complaints with their publisher and denominator, deferrals, throttles. | `read` | `reversible` | `auto` | nothing at stake | `none` | `none` | `not_applicable` | `F6`, `M4` |
| `restriction.record` | "The platform has restricted this sender" — including the ones we only learned about from a refusal. | `control` | `irreversible` | `auto`<br>*protective floor:* the protective floor: recording an event that already happened outside our control derives auto whatever its reversibility, and waiting for permission to record a restriction is the destructive choice — the invalidated warm-up position and the recurrence count both hang off this record. | the restriction ledger for this sender: an identical open restriction must not be double-counted into the recurrence count. | `none` | `required` | `required` | `F4`, `K2` |
| `restriction.appeal` | "Appeal it where the platform offers a route — and say plainly when it does not". | `act` | `irreversible` | `confirm_each`<br>*departs:* raised from confirm_once: an appeal is written content submitted under a named human's identity, usually with one chance. | the appeal state for this restriction: none / submitted / decided. | `none` | `required` | `not_applicable` | `F5` |
| `sender_pool.create` | "Group these capabilities so work can rotate across them". | `control` | `compensatable` | `confirm_once` | the pool's existence and membership. | `none` | `required` | `not_applicable` | — |
| `sender_pool.update` | "Change who is in the pool and how work is routed across it" — including sticky per recipient, which on conversational channels is correctness and not optimisation. | `control` | `reversible` | `confirm_once`<br>*departs:* raised from auto: the call carries the pool's membership and its routing policy, and rotation is not a cure — where a budget's scope is the pool, the organisation or the recipient, rotating across senders moves the problem, and sticky per recipient is correctness on conversational channels rather than optimisation, so this overwrites state that live conversations depend on. | the pool's current membership and routing policy. | `none` | `required` | `required` | `F10` |
| `sender_pool.list` | "What pools exist, who is in them, and how do they route?" | `read` | `reversible` | `auto` | nothing at stake | `none` | `none` | `not_applicable` | — |
| `sender_pool.delete` | "Dissolve the pool" — refused while campaigns bind it unless a replacement target is supplied; the capabilities themselves are untouched. | `control` | `compensatable` | `confirm_once` | the pool's existence and what still binds it. | `none` | `required` | `not_applicable` | `F8` |
| `sending_domain.register` | "Declare a domain we send from". | `control` | `compensatable` | `confirm_once` | the domain's registration state. | `none` | `required` | `required` | — |
| `sending_domain.list` | "Which domains do we send from, and what is each one's compliance state as of when?" | `read` | `reversible` | `auto` | nothing at stake | `none` | `none` | `not_applicable` | — |
| `sending_domain.retire` | "Stop treating this as a domain we send from" — refused while any sender on it has live enrolments or open conversations, unless a rebind target is supplied. | `control` | `compensatable` | `confirm_once` | the domain's state and what is still bound to it. | `none` | `required` | `not_applicable` | `F8` |
| `authentication_requirement.list` | "What has to be published for this domain to authenticate" — publishing it is not ours to do. | `read` | `reversible` | `auto` | nothing at stake | `none` | `none` | `not_applicable` | — |
| `domain_compliance.check` | "Per publisher, per requirement: pass, fail or unknown — and name the failing requirement". | `read` | `reversible` | `auto` | nothing at stake | `none` | `none` | `required` | `F6`, `F7` |
| `domain_reputation.get` | "The named signals about this domain, each with its publisher, scale, window and denominator" — including blocklist listings and the dataset each came from. | `read` | `reversible` | `auto` | nothing at stake | `metered`<br>*conditional:* none unless a signal comes from a paid dataset — then metered.<br>*basis:* per dataset queried, where a signal comes from a paid dataset<br>*meter:* `dataset` | `required`<br>*conditional:* required where the read is metered. | `required` | `F6` |
| `message_compliance.check` | "Check this rendered message against the requirements it will actually be held to" — required elements, a working unsubscribe checked properly, and the reputation of every domain it links to. | `read` | `reversible` | `auto` | nothing at stake | `none` | `none` | `required` | `E14`, `F7` |
| `placement_test.create` | "Send this to a monitored set of addresses and see where it lands". | `act` | `irreversible` | `confirm_each` | the test ledger — a test already running for this message must not be started twice. | `metered`<br>*basis:* per test<br>*meter:* `test` | `required` | `not_applicable` | — |
| `placement_test.get` | "What did the test say, per mailbox provider" — typed as simulated placement, never as our inbox rate. | `read` | `reversible` | `auto` | nothing at stake | `none` | `none` | `required` | `M2` |
| `messaging_registration.submit` | "Register the brand and the use case, because on this channel we may not send at all until it is approved". | `act` | `compensatable` | `confirm_once` | the registration's state: none / pending / approved / rejected. | `metered`<br>*conditional:* metered where the channel charges for a registration; none where it does not.<br>*basis:* per registration, where the channel charges for one<br>*meter:* `registration` | `required` | `not_applicable` | — |
| `messaging_registration.get` | "What is the registration's status, and on refusal what must change?" | `read` | `reversible` | `auto` | nothing at stake | `none` | `none` | `not_applicable` | — |
| `approved_content.submit` | "Submit content for platform pre-approval, where the platform gates the content rather than the sender". | `act` | `compensatable` | `confirm_once` | the content's state: none / pending / approved / rejected / paused. | `none` | `required` | `not_applicable` | `L3` |
| `approved_content.get` | "Approval status and quality state" — including whether the platform has paused it under us. | `read` | `reversible` | `auto` | nothing at stake | `none` | `none` | `required` | — |
| `approved_content.retire` | "Withdraw it from use" — the correct fix when it is the content that got flagged and not the sender. | `control` | `compensatable` | `auto` | the content's state and what is still bound to it. | `none` | `required` | `required` | `F5`, `L6` |
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall