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
Most recently taken up by
- gooseworks-ai/goose-skillsword for word, first seen Nov 1, 2026
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.
Other versions1 project uses a version of this.
Word for word · 1
- gooseworks-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-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
- research-competitorsSkill
- The first 60 shown.
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
- Distinctive: line 15
Cover every audience the site sells to: If the site sells to more than one buyer or carries more than one positioning, include questions …
≈ “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
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.
- 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. - 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.
- 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. - 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.
- 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".
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.

