outcomes-ledger
Skill1.3k starsChanged 23 days agoMITView on GitHub
Shared step of the marketing playbooks (research-audience, write-outreach, work-with-creators): keeps the brand's record of the prospects or creators that were handed over. Tracks a status for each person, permanent opt-outs, re-check dates and dated lessons, which the next run reads. Loaded by those playbooks; not for direct use.
1 other project uses a version of this.
Trending
More talk lately.about the whole repository
Most recently taken up by
- athina-ai/goose-skillsword for word, first seen Nov 9, 2026
Who's talking about gooseworks-ai/goose-skills
- akhmadilham/pinax-registry“[Skill Proposal]: goose-skills”GitHub · Nov 3, 2026
- sudosubin/agents.nix“agent-skills.github.gooseworks-ai.goose-skills: 0-unstable-2026-10-20 → 0-unstable-2026-10-23”GitHub · Oct 23, 2026
- gooseworks-ai/gooseworks“Route focused marketing requests to existing playbook steps”GitHub · Oct 22, 2026
- sudosubin/agents.nix“agent-skills.github.gooseworks-ai.goose-skills: 0-unstable-2026-10-17 → 0-unstable-2026-10-20”GitHub · Oct 20, 2026
- sudosubin/agents.nix“agent-skills.github.gooseworks-ai.goose-skills: 0-unstable-2026-10-16 → 0-unstable-2026-10-17”GitHub · Oct 17, 2026
The biggest 5 of 20 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 20
Talked about on GitHub (20 times).
On GitHub · 20
- Nov 3, 2026[Skill Proposal]: goose-skills — akhmadilham/pinax-registry0 reactions · 1 comment
- Oct 23, 2026agent-skills.github.gooseworks-ai.goose-skills: 0-unstable-2026-10-20 → 0-unstable-2026-10-23 — sudosubin/agents.nix0 reactions
- Oct 22, 2026Route focused marketing requests to existing playbook steps — gooseworks-ai/gooseworks0 reactions
- Oct 20, 2026agent-skills.github.gooseworks-ai.goose-skills: 0-unstable-2026-10-17 → 0-unstable-2026-10-20 — sudosubin/agents.nix0 reactions
- Oct 17, 2026agent-skills.github.gooseworks-ai.goose-skills: 0-unstable-2026-10-16 → 0-unstable-2026-10-17 — sudosubin/agents.nix0 reactions
15 more on GitHub
- Oct 16, 2026[Candidate] gooseworks-ai/goose-skills - large collection (295 SKILL.md files) — ProSkillsMD/proskills0 reactions · 1 comment
- Oct 16, 2026agent-skills.github.gooseworks-ai.goose-skills: 0-unstable-2026-10-12 → 0-unstable-2026-10-16 — sudosubin/agents.nix0 reactions
- Oct 13, 2026agent-skills.github.gooseworks-ai.goose-skills: 0-unstable-2026-10-06 → 0-unstable-2026-10-12 — sudosubin/agents.nix0 reactions
- Oct 6, 2026agent-skills.github.gooseworks-ai.goose-skills: 0-unstable-2026-10-05 → 0-unstable-2026-10-06 — sudosubin/agents.nix0 reactions
- Oct 5, 2026agent-skills.github.gooseworks-ai.goose-skills: 92b02ac → f76cec4 — sudosubin/agents.nix0 reactions
- Oct 5, 2026agent-skills.github.gooseworks-ai.goose-skills: 80b0c5e → 92b02ac — sudosubin/agents.nix0 reactions
- Oct 5, 2026agent-skills.github.gooseworks-ai.goose-skills: 0-unstable-2026-10-04 → 0-unstable-2026-10-05 — sudosubin/agents.nix0 reactions
- Oct 4, 2026agent-skills.github.gooseworks-ai.goose-skills: 0-unstable-2026-10-03 → 0-unstable-2026-10-04 — sudosubin/agents.nix0 reactions
- Oct 4, 2026agent-skills.github.gooseworks-ai.goose-skills: af5944c → 770e3c2 — sudosubin/agents.nix0 reactions
- Oct 3, 2026agent-skills.github.gooseworks-ai.goose-skills: init at 0-unstable-2026-10-03 — sudosubin/agents.nix0 reactions
- Oct 2, 2026Preserve angle evidence through local video script planning — gooseworks-ai/gooseworks0 reactions
- Aug 5, 202622 skills have links.github pointing at something that is not a skill directory — gaia-research/gaia-skill-tree0 reactions · 7 comments
- Jul 16, 2026Skill submission: goose-skills (growth/GTM library by GooseWorks) — numman-ali/n-skills0 reactions
- Jul 16, 2026Add goose-skills to Collections — BehiSecc/awesome-claude-skills0 reactions · 1 comment
- May 3, 2026Import skill: linkedin-post-research — jettyio/agent-runbooks0 reactions
Other versions1 project uses a version of this.
Word for word · 1
- athina-ai/goose-skills★ 1.3k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository180 other files it gives its agents.
- goose-adsSkill
- goose-product-photosSkill
- goose-video-localSkill
- goose-videoSkill
- gooseworksSkill
- make-custom-videoSkill
- ad-policy-checkSkill
- analyze-performance-call-and-learnSkill
- analyze-performance-diagnoseSkill
- analyze-performance-intakeSkill
- analyze-performance-rank-and-readSkill
- analyze-performance-revenue-joinSkill
- analyze-performanceSkill
- claims-gateSkill
- email-lifecycle-broadcast-plannerSkill
- email-lifecycle-flow-writerSkill
- email-lifecycle-lifecycle-auditSkill
- email-lifecycle-offer-mathSkill
- email-lifecycle-send-checkSkill
- email-lifecycleSkill
- honest-reviewSkill
- improve-search-visibility-citation-checkSkill
- improve-search-visibility-entity-footprintSkill
- improve-search-visibility-fix-writerSkill
- improve-search-visibility-page-and-foundation-checkSkill
- improve-search-visibility-question-setSkill
- improve-search-visibilitySkill
- improve-search-visibility-store-listing-auditSkill
- make-content-content-briefSkill
- make-contentSkill
- make-content-source-to-unitsSkill
- make-content-two-pass-editSkill
- make-static-ads-ad-copySkill
- make-static-ads-claims-extractSkill
- make-static-ads-composeSkill
- make-static-ads-concept-gridSkill
- make-static-ads-copy-variantsSkill
- make-static-ads-find-referencesSkill
- make-static-ads-fix-rejectedSkill
- make-static-ads-graphic-requestSkill
- make-static-ads-render-reviewSkill
- make-static-adsSkill
- marketing-data-accessSkill
- marketing-guideSkill
- plan-campaign-brief-and-assetsSkill
- plan-campaign-budget-and-testsSkill
- plan-campaign-channel-decisionSkill
- plan-campaign-goal-chainSkill
- plan-campaignSkill
- research-audience-account-sourcingSkill
- research-audience-fit-definitionSkill
- research-audience-people-and-contactsSkill
- research-audience-score-segment-qaSkill
- research-audience-segment-passSkill
- research-audience-signals-and-hooksSkill
- research-audienceSkill
- research-competitors-category-passSkill
- research-competitors-edge-casesSkill
- research-competitors-rival-passSkill
- research-competitorsSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 40
Read the ledger. If it does not exist, create it with the header.
- Very specific: line 78
Never contact anyone, never send, never mark a row contacted on the agent's own inference.
- Distinctive: line 79
Never require outcomes to continue a run.
- Distinctive: line 80
Never drop a suppression to reach a list size.
- Distinctive: line 81
Never move personal contact data into the brain.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
outcomes-ledger
Every list a playbook hands over gets acted on outside GooseWorks: the human emails the prospects, messages the creators. This atom is how what happened comes back, so the next run never repeats a person who said no and gets better from what worked. It never contacts anyone and never requires outcomes: no outcomes, carry on.
Parameters (the loading playbook sets them)
entity: person | entity: creator | |
| Loaded by | research-audience (writes rows when a list is shown), write-outreach (updates statuses from replies and results) | work-with-creators |
| Ledger file | research/audience/ledger.csv | creators/roster.csv |
| Lessons document (file → brand document) | research/audience/lessons/<YYYY-MM-DD>.md → Outreach lessons — <Brand> — <YYYY-MM-DD> | creators/lessons/<YYYY-MM-DD>.md → Creator lessons — <Brand> — <YYYY-MM-DD> |
| Entity columns (after the required ones) | segment, tier, value_tier, signal_type, email_status, region_flag, email, email_candidate, profile_url, root_domain, route, sequence_id, opener_id, first_touch_date, last_touch, reply_category, recontact_after | role, tier, deal_structure, vetting_depth, wave, wave_criterion, wave_result, quoted_rate, then the roster's own columns |
| Status values | listed · contacted · replied · meeting · not-a-fit · bounced · unsubscribed · do-not-contact | shortlisted · contacted · replied · quoted · declined · signed · posted · never-again |
| Suppressing statuses (permanent) | bounced · unsubscribed · do-not-contact | never-again |
| Timed exclusions (not suppression) | not-a-fit — the account is skipped for 6 months, then eligible again; contacted with no reply after the sequence ended — the person is skipped for 12 weeks on every channel (cool-down) | declined — skipped until the human re-opens it |
| Match keys, in order | email (or email_candidate) → profile URL → name + root domain; account rows: root domain + route | handle + platform → profile URL |
| Grouped by (for lessons) | segment, tier, signal type, email status, region flag, sequence, opener and touch, reply category | role, tier, deal structure, vetting depth, wave |
| Re-check | recheck_by = date listed + 30 days | revet_by = vetted on + 30 days |
Files and scope
- Brand coworker workspace (
file_*scope agent = the brand'scoworker_agent_idfrom thebrand_readlist). No coworker → the default workspace with every path prefixedbrands/<brand-slug>/, and tell the human teammates won't see it. - Read before write:
file_writereplaces the whole file. Read the ledger, change rows, write it back complete. - Every row a playbook shows the human is ledgered at the moment it is shown — sample rows included — not only at handover. Rows from a sample whose definition the human then rejected get status
listed-sample-rejectedand are not excluded later (the person was never handed over for outreach). - Required columns, first and in this order (both entities):
row_type, key, key_hash, name_or_handle, account_or_platform, date_listed, list_id, status, status_date, suppressed, suppressed_reason, suppressed_date, recheck_by|revet_by, outcome, notes.keyis the first available match key (person: email, else profile URL, else name + root domain; creator:platform:handle). Then the entity columns above, then the loading playbook's own columns. Never drop a column on write-back; unknown columns are kept as they are. - A new entity (another playbook wanting a ledger) needs its row in the tables above, added by this atom's owner — ask before loading it.
On every run (before any new sourcing)
- Read the ledger. If it does not exist, create it with the header; carry on.
- Flag stale rows for free: rows past
recheck_by/revet_bythat are not yet contacted. Tell the human in one line ("12 people from the 2026-09-10 list haven't been contacted and are past their re-check date"). Re-checking them is paid → the loading playbook's spend step (thespend-gateskill,../spend-gate/SKILL.md). - Ask for outcomes once, never require them — in the run's closing decisions, never before the first result: "Anything to report since
<last list date>— replies, meetings, bounces, unsubscribes, declines, quotes? Paste, upload, or tell me in a sentence." Creators past a wave's read window (increators/<date>/wave-1.md): also ask for each creator's views, orders on their code or link, and whether they posted. No answer → skip to step 6. - Match each reported outcome to a row by the match keys in order. Unmatched lines are shown back, never guessed onto a row. A
stop, unsubscribe, complaint or bounce from an address not in the ledger gets a suppression-only row: thekey_hash, the reason and the date — never the address (§ Suppression without personal data). Keeping the raw address needs the human's yes, asked once in the closing decisions. - Update
status,status_date,outcome— and for people,first_touch_datewhen the first send is reported (never overwritten afterwards; it anchors rates and the cool-down),last_touch,reply_category, andrecontact_afterfor a "not now, try in<month>" reply (and for creatorsquoted_ratewhen reported). Creators with wave results: score each against itswave_criterion→wave_result=win · partial · miss · no-data. A suppressing status setssuppressedwith reason and date, and reduces the row to its suppression form (below); a timed exclusion setsoutcomeand the date it lapses. Suppression is permanent: a suppressed row is excluded from every later run, of every list, and is never un-suppressed except by the human's own words. - Exclude: hand the loading playbook the full exclusion set — every suppressed
key_hash(the playbook hashes each candidate's keys the same way and drops any match), every live timed exclusion (including rows whoserecontact_afterdate hasn't come), plus every key already listed and not yet resolved (so the next batch never repeats a person) — but notlisted-sample-rejectedrows.
Lessons (only when outcomes came back)
- Compare by the entity's groupings (person: read replies and fixes with write-outreach's
references/reading-results.md— many "not relevant" → targeting, many "wrong person" → titles, bounces → list hygiene): reply and meeting rate (person) or reply, quote-vs-range, post rate and result vs the wave criteria (creator). - Sample size (one rule everywhere): person — under 50 contacted in a group → counts and what to watch only, no rates judged; 50+ but under ~10 positive replies → "directional only"; creator — under ~5 in a group → "directional only". Said in the lesson.
- Propose changes to the loading playbook's own rules (signal weights, segments, negative ICP; roles, tiers, price bands, vetting weights) and get the human's yes before any saved definition or plan changes.
- Save the lessons to the entity's lessons file, then as a dated brand document through the
save-to-brainskill (../save-to-brain/SKILL.md) (versioned: keep-history, tags[<playbook>, lessons]). It opens with "Do this first, because…" and the one change the numbers support most. Numbers and groups only — no names, emails, handles of private people or contact data. Named-creator operational notes ("missed the posting window twice") stay in the roster file'snotes, never in the brain. - A lesson becomes a brand learning only through the
save-learningskill (../save-learning/SKILL.md): the human's own words, one idea each, retiring its own superseded ones, text starting[outreach YYYY-MM-DD](research-audience),[outreach-copy YYYY-MM-DD](write-outreach) or[creators YYYY-MM-DD](work-with-creators).
With run-memory (the run-memory skill)
The ledger and the run records hold different things and must agree:
- The ledger is the per-row truth — every person's or creator's status, dates and outcome. Nothing else stores rows.
- A run record holds only the summary — counts and rates by the groupings above, for a stated window — plus the ledger's path. It never holds a row, a key, a name, an email, a handle or a profile URL.
- Recount, don't carry. Each run's "since last time" recomputes its numbers from the ledger (statuses and dates as they stand today), never copies them from the last record. When a recount differs from what the last record said (the marketer reported outcomes late, a row was corrected), the ledger wins and the new record says "restated:
<what changed>". - Lessons and records: a lessons file is the analysis of outcomes (dated, keep-history); the run record links it and lists its proposed changes as recommendations with ids, so the next run can check whether they were adopted and what they did.
- Statuses a run record cites are only the ones the marketer reported into the ledger — never inferred.
Suppression without personal data
A suppression must last forever, but the person's details must not. So:
key_hash= SHA-256 (hex, prefixedsha256:) of the normalised key: email lower-cased and trimmed; profile URL lower-cased with no protocol,www., query or trailing slash; name + root domain lower-cased, single-spaced, joined by@; creatorsplatform:handlelower-cased. The same rule hashes every new candidate, so a suppressed person is blocked from every later list without the ledger keeping who they are.- When a row is suppressed (bounced, unsubscribed, do-not-contact, never-again): keep
key_hash,suppressed,suppressed_reason,suppressed_date,list_id; blank every other personal field (key, name, email, email_candidate, profile URL, route, notes). Counts by segment stay countable fromlist_idand the reason. - Compute the hash with the host's code tool (shell or code execution). A host that can't compute one: don't store the address at all — tell the human to add it to their own sending tool's suppression list, and ask once whether to keep the raw address here so it stays blocked; store it only on their yes, labelled
raw, kept on your yes (<date>). - Rows the human pastes or uploads for scoring follow the same rule when they become suppressed.
Retention
Rows never contacted 12 months after date_listed are deleted from the ledger. Suppression rows are kept forever, in their hashed form only. Say how many were removed.
Never
- Never contact anyone, never send, never mark a row
contactedon the agent's own inference. - Never require outcomes to continue a run.
- Never drop a suppression to reach a list size.
- Never move personal contact data into the brain.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

