spend-gate
Skill1.3k starsChanged 22 days agoMITView on GitHub
Shared step of the marketing playbooks (make-static-ads, research-market, run-paid-campaigns, work-with-creators): gets the human's yes before any credits are spent. Shows the price exactly as quoted, or asks for one yes to a credit ceiling for paid data reads, stays under it and logs each charge. Also covers scheduled runs. Loaded by those playbooks; not for direct use.
2 other projects use 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
- KrishP147/skillstheir own version, first seen Oct 13, 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 versions2 projects use a version of this.
Word for word · 1
- athina-ai/goose-skills★ 1.3k100% same
Edited · 0
None found.
Wrote their own version · 1
- KrishP147/skills★ 37same name
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
- outcomes-ledgerSkill
- 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
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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
- Very specific: line 21
Ask the tool for its quote (its dry run, quote_only, or gooseworks:data_price_provider for fal and ElevenLabs calls).
- Distinctive: line 23
Ask for a yes to that quote.
- Distinctive: line 24
If an answer comes back as a card waiting for a press, follow the server's card rule and wait for the human.
- Distinctive: line 42
Stop at the ceiling: If the next call would cross it, stop.
- Distinctive: line 45
If the human declines or trims the top-up, the free result stands.
- Distinctive: line 49
Create every automation paused.
≈ “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
spend-gate
No credit is spent before the human's yes in this conversation. Money is always a credit number exactly as GooseWorks gives it — never dollars, never your own total presented as a price. Never name tools, endpoints or vendors to the marketer: describe the work in plain words ("Reddit threads about dog allergies, newest first").
Pick the branch by the tool:
A. Engine-quoted work (ads, photos, video, any tool with a dry run or a price check)
Managed marketing data: marketing_data_describe is free. marketing_data_lookup defaults to quote_only: true. Read the returned maximum credits and expiry, then request approval for that exact bounded work. Submit the same request with its quote token, the approved ceiling and the user’s words. A new request or expired quote needs a fresh quote. An existing approval may cover later calls only when it explicitly named that same bounded plan and total ceiling: quote each call, preserve the original approval words, and set its maximum no higher than the remaining approved credits. Ask again only for changed scope or more budget. Log every returned charge and deduct it before the next call; the tool’s per-call cap is not a cumulative plan limit. Free continuation pages inside that approved plan need no second spending approval. A capped quote is a maximum, not a claim about final usage. Never treat discovery, a successful quote or a fixture as proof that a paid data read ran.
- Ask the tool for its quote (its dry run,
quote_only, orgooseworks:data_price_providerfor fal and ElevenLabs calls). - Show each quote exactly as given. Several quotes are shown one by one, never added up by you.
- Ask for a yes to that quote. Submit only after it; a changed plan needs a new quote and a new yes.
- If an answer comes back as a card waiting for a press, follow the server's card rule and wait for the human.
B. Proxy data reads (no price check exists) — one yes
Covers gooseworks:data_call_provider / gooseworks:data_post_provider with ScrapeCreators, gooseworks:competitor_research with mentions, and capped imports (gooseworks:knowledge_sync, gooseworks:knowledge_import with a source, gooseworks:ads_library_scrape for Google). Endpoint paths, query keys and recency options: proxy-endpoints.md in this folder.
Paid reads deepen a free result; they are never the starting point. Offer them only after the playbook's free pass, in the same message as the draft answer (../marketing-guide/research-pattern.md (in the marketing-guide skill)), and ask once.
- Read the price history:
research/credits-log/<YYYY-MM>.mdfor this month and last (the scope in themarketing-guideskill §2). - Plan the top-up with a cap on every row (pages per query, items per page, comments per post, profiles per list) and say in plain words what it adds to the free result.
- Estimate and ask one yes to "up to N credits", labelled an estimate:
- with history: N from the logged charges for these kinds of reads;
- with no history: never invent a price. Say what the top-up adds and roughly how many reads it takes, that the first read shows the real price, and let the human name the ceiling in the same yes ("up to how many credits?"); with no number given, run only the probe call and report its price before anything else. The first call runs as the probe inside that same ceiling — never a separate yes. Caps that tools take in their own unit (a few import tools take a small dollar cap) are described in words — "a small capped import" — and the credits charged are reported afterwards; never quote the dollar figure.
- Run inside it. Run the probe call first and keep its results. If the real per-call charge means the plan cannot fit, trim the plan to fit the ceiling — never cross it; ask again only if the human wants more. Then the cheapest and most decisive rows first; stop a row when it saturates. Calls that depend on earlier results (comments on the posts a search finds) fit inside the same ceiling. A playbook may reserve part of the ceiling for a named purpose (research-market's crisis reserve for its listening).
- Log every charge as it comes back, in
research/credits-log/<YYYY-MM>.md(same scope as step 1; read it, add the row, write the whole file back):date | playbook | tool/endpoint | query kind | items | credits"Query kind" describes the read ("brand name search, TikTok, past month"), never a private person's name or contact. - Stop at the ceiling. If the next call would cross it, stop. A failed call is retried once only when its error says that is safe; a bad path or key is logged, never guessed again.
- Report: credits charged against the ceiling, in plain words. Endpoint detail stays in the log.
If the human declines or trims the top-up, the free result stands; name what the paid reads would have added as a gap ("not read: TikTok comments — top-up not approved").
C. Scheduled runs (automations)
- Create every automation paused. Switch it on only on the human's yes in this conversation.
- The yes names any standing per-run data ceiling ("up to N credits per run"); the run writes that ceiling into its prompt and logs every charge. Without one, a scheduled run uses free sources only and never spends on data.
- The coworker's own run cost is not priced in advance: say so, and after the first run show the credits it used (
gooseworks:automation_list) so the human can pause it. - A yes given in chat never carries over to a scheduled run unless it was given as a standing per-run ceiling.
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.

