agentleFS
athina-aiathina-ai/goose-skills/skills/marketing/improve-search-visibility-question-set/SKILL.md

improve-search-visibility-question-set

Skill1.3k starsChanged 23 days agoMITView on GitHub

Step of the improve-search-visibility playbook: drafts and scores the buyer-question set in AI and Google forms and groups it into page clusters. Run improve-search-visibility instead; not for direct use.

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:

    Cover every audience the site sells to: If the site sells to more than one buyer or carries more than one positioning, include questions …

    line 15

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

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

question-set

Reads: ../improve-search-visibility/references/question-list.md, ../improve-search-visibility/references/battlegrounds.md; brand summary, products, audience, competitors (gooseworks:brand_read, gooseworks:competitor_read); research-audience's research/audience/voc-bank.md and research-market's research/market/demand.md if present; customer language via gooseworks:knowledge_search with source_types: ["document", "evidence"] (query "Voice-of-customer bank — customer questions, objections, words customers use"); Search Console export if shared; the previous search/questions.md and search/page-map.md on re-runs.

Does: 0. Cover every audience the site sells to. If the site sells to more than one buyer or carries more than one positioning, include questions for each, so the decisions message can ask which buyer to win.

  1. Re-run: reuse the saved set, then top it up to the mix — at least 3 brand-accuracy questions and every audience the site sells to — before anything runs; propose at most 3 other additions or swaps with reasons; keep ids stable — the same id always means the same words: a reworded question gets a new id and the old one is marked retired (reworded → Q<n>, v<N>), so the next run never compares different wordings.
  2. First run: draft 18–20 candidates across the stage mix in both forms, never with the brand name in non-brand questions; 3–6 brand-accuracy questions always; local variants per city for physical businesses.
  3. Score value (buying intent 1–5, ../improve-search-visibility/references/question-list.md) × winnability (1–3) provisionally with a one-line reason each; drop to the best 12–15. A brand name that is a common word always carries the category in brand questions. Pre-launch: category questions plus one name-collision question only.
  4. Cluster and weight. Group the questions into clusters (one cluster = one page that should answer them); with a Search Console export, sum each cluster's impressions as its demand weight and add any high-impression query the list missed. These clusters are the page map's rows.
  5. Pick the key questions yourself (the 3–5 highest value × winnability) and run the set — no approval before the free pass. The first message shows the set grouped by cluster for edits; edits apply to the paid top-up and the next runs.

Writes: search/questions.md in the saved-set format (version, date, country, language, engines, runs·route line, the table with a cluster column). Never: invents search volumes or "how many people ask this". Demand comes from Search Console, Google Trends or autocomplete (free), Keyword Planner when the brand shares it, or a vendor prompt-volume estimate the brand already has — always labelled with its source, estimates as estimates; otherwise "no demand data, ranked by judgment".

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.