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-20-measurement.md

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

# Family 20 — Measurement

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

*The organisation around the work* · 10 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 |
|---|---|---|---|---|---|---|---|---|---|
| `engagement.summarize` † | "How is this doing?" — one measure set over one scope, grouped the way the question actually needs. | `read` | `reversible` | `auto` | nothing at stake, but two runs are only the same number if as-of, window, basis, denominator and detection method all match. | `none` | `none` | `required`<br>*conditional:* one row per group, each with its own envelope. | `E5`, `F6`, `M1`, `M2`, `M3`, `M4`, `M5`, `M6`, `M7` |
| `engagement_event.list` | "Show me the rows behind the number" | `read` | `reversible` | `auto` | nothing at stake | `none` | `none` | `required` | `A14`, `M2`, `M5` |
| `funnel.summarize` | "The whole ladder, stage by stage, with each stage's declared denominator and how well each stage can be known at all" | `read` | `reversible` | `auto` | nothing at stake | `none` | `none` | `required` | `I1`, `M1`, `M3` |
| `opportunity.summarize` | "What came out the far end, and what was it worth — under which attribution model, on whose authority?" | `read` | `reversible` | `auto` | nothing at stake — and these values move retroactively, so a figure is only meaningful with its as-of. | `none` | `none` | `required` | `M1` |
| `attribution.explain` | "Why was this outcome credited here, and what would a different model have said?" | `read` | `reversible` | `auto` | nothing at stake | `none` | `none` | `required` | — |
| `response_time.summarize`<br>*questions:* 5 | "How fast do we actually pick things up" — an inbound lead from arrival to first human touch, a reply from arrival to answer — by owner, route, source and hour of day. | `read` | `reversible` | `auto` | nothing at stake | `none` | `none` | `required` | `K1`, `K8`, `M1` |
| `metric.describe` | "What does this measure actually mean here, what was it mapped from, what can it be grouped by, and how much can it be trusted?" | `read` | `reversible` | `auto` | nothing at stake; read it before planning anything around a measure | `none` | `none` | `required` | `M1`, `M2` |
| `metric.compare`<br>*questions:* 13 | "Two arms, side by side" — the counts, the sample size this comparison needs, the interval around each rate, and whether there is enough data to say anything at all. | `read` | `reversible` | `auto` | nothing at stake — but re-reading and stopping when it looks good invalidates the result, so the intended sample size, the observed sample size and the number of reads are all returned. | `none` | `none` | `required` | `M4`, `M7` |
| `export.request`<br>*questions:* 24 | "Get me a bounded extract for reporting" — never the route for a subject access request, which is `privacy_request.fulfill`. | `control` | `reversible` | `confirm_once`<br>*departs:* raised because an extract moves personal data out of the system where its handling rules are enforced. | the state of the export already requested under this key | `metered`<br>*conditional:* metered where the extract consumes an allowance.<br>*basis:* per call<br>*meter:* `request` | `required`<br>*conditional:* a replayed export produces a second copy of personal data. | `not_applicable` | `A13` |
| `export.get`<br>*questions:* 24 | "Collect the extract" | `read` | `reversible` | `auto` | nothing at stake; the extract is stable once complete | `none` | `none` | `not_applicable` | — |
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