agentleFS
athina-aiathina-ai/goose-skills/skills/marketing/research-audience-signals-and-hooks/SKILL.md

research-audience-signals-and-hooks

Skill1.3k starsChanged 23 days agoMITView on GitHub

For a list of companies, finds dated, linked timing signals from the last 90 days (funding, new leaders, hiring, launches), drops stale ones and noise, scores timing, and gives one personal hook per person from their recent public work. Facts only, no message copy. Use alone when you already have the company list and, for hooks, the people; otherwise run research-audience.

1 other project uses a version of this.

Trending

Quiet since March.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the athina-ai/goose-skills repository that our weekly crawl found: only 1 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

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

The biggest 1 of 1 mention linking to the repository that our crawl found. Each line is their own headline.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Rules: no URL, no signal. Never write outreach copy here — facts only.

    line 24

≈ “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

signals-and-hooks

Reads: account table; people (for hooks); ../research-audience/references/signals-and-hooks.md; champions list if the human supplied one.

Does:

  1. News first, per account: a web search for the company over the last 90 days (funding, new leader, launch, expansion, acquisition, layoffs, awards that matter to the buyer). Then the signals that matter for this motion (the reference table): careers page and job boards, company news and posts. Stop once one strong fresh signal is found unless a second is cheap. Anything from the last 14 days is a timely opening for the report.
  2. Record each as fact · URL · publish date · retrieved date · why now. Re-check job posts are still live.
  3. Drop anything past its window and anything on the noise list. Funding alone never makes an account tier A.
  4. Score timing by judgment against the anchors (strength, recency, capped at 40), with the reason written in the row.
  5. Per person (run again after people-and-contacts, from SKILL step 6), find one hook from their professional public activity in the last ~60 days; tie it to the pain. None found → "none found". Account rows (independent shops, chains) get one hook too, from the shop's recent posts or events. Never use banned topics.

Writes: signal_1/2 (+url, date), timing points, hook (+url).

Rules: no URL, no signal. Never write outreach copy here — facts only.

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.