agentleFS
gooseworks-aigooseworks-ai/goose-skills/skills/marketing/research-audience-fit-definition/SKILL.md

research-audience-fit-definition

Skill1.3k starsChanged 23 days agoMITView on GitHub

Step of the research-audience playbook: drafts the searchable fit definition, exclusions and list size that the list run then searches on. Run research-audience instead; not for direct use.

1 other project uses a version of this.

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 1 mentionJun 2026: 0 mentionsJul 2026: 2 mentionsAug 2026: 1 mentionSep 2026: 0 mentionsOct 2026: 15 mentionsNov 2026: 1 mention
Dec 2025Jun 2026Nov 2026
Mentions a month of the gooseworks-ai/goose-skills repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about gooseworks-ai/goose-skills

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

15 more on GitHub

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No ICP anywhere: draft from what the brand sells and its customer logos.

    line 21
  2. Distinctive:

    Write the draft definition as one compact block for the report, assumed lines first, and say what any open line will do to the list.

    line 22
  3. Distinctive:

    Rules: after the human corrects it, never widen or narrow it again without saying so.

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

fit-definition

Reads: the brand's own site in the host browser (what it sells, pricing, case studies, customer logos, integrations, who it says it's for); brand_read summary/onboarding/competitors/learnings; knowledge_search for ICP, segments, win/loss, customers, past outbound; the saved fit definition; the saved buyer groups (research/audience/buyer-groups.md) — the lead group, or the one the ask names, is the starting definition; the ask itself; ../research-audience/references/fit-and-scoring.md; ../research-audience/references/list-by-company-type.md. No answers from the human yet — this atom drafts.

Does:

  1. Identify the motion (who the list is for — usually already in the request) and pick the list unit from the company-type table. Several motions → one definition each. Retail, wholesale and venue lists use the retail variant (door count, price tier, assortment, review window, chain vs independent route).
  2. Fill every part of the definition table from the site, the brain and the ask. Mark each line sourced (with its link or brain item) or assumed (your best reading, with why). Never leave a line blank to ask about — assume it, label it, and let the human correct it in the report's message.
  3. Turn loss notes and "not a fit" replies into the negative ICP.
  4. Translate personas into title synonyms and seniority by company size. Hiring-led lists: write the role map (replaces / augments / buys / champions / uses, and the job-ad keywords that confirm relevance) — ../research-audience/references/list-sources.md § Hiring.
  5. Load exclusions: the human's files (customers, open deals, do-not-contact; for retail, the brand's current stockists), the contacted ledger and suppression, competitor domains from competitor_read (never names or handles — they can be mis-resolved), the seller's own domain. Normalise to root domains.
  6. Account value (account-based lists): set the V1/V2/V3 rule from the brand's pricing page and customer logos (seats, locations, plan tiers), labelled assumed; the human corrects it later.
  7. Size: what the human asked for, checked against what they can work; partner and app lists default to 20–30 — say what a bigger number does to fit.
  8. No ICP anywhere: draft from what the brand sells and its customer logos; where two readings are equally likely, build the free pass on the stronger one and name the other in the report as an alternative.
  9. Write the draft definition as one compact block for the report, assumed lines first, and say what any open line will do to the list. Do not wait for a yes — the free pass runs on the draft.

Writes: the definition (markdown, assumed lines labelled) for the run, updated with the human's corrections, and later the saved brand document through the save-to-brain skill (../save-to-brain/SKILL.md) (see SKILL.md write-back).

Rules: after the human corrects it, never widen or narrow it again without saying so. Never invent customers, logos or loss reasons. Never copy values from the reference's fictional example.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.