<What it does, one line>. Trigger phrases: <phrases>.
日本語の概要は準備中です。原文の説明を表示しています。
Use when deciding WHERE to point SEO effort, not how to write a page. Triggers: a new site or brand with no rankings and no authority ("cold start", "starting from zero", "nobody knows us"), deciding what to double down on, a page or cluster that ranks but earns nothing, hunting emerging or newly-coined keywords before competitors arrive, "should we build a cluster or one page", "what do we write next", "we get impressions but no clicks", "our traffic plateaued despite publishing", whether to chase a head term at all, or turning any of it into recurring automation. Also use when asked why an SEO effort stalled despite consistent output. NOT for writing an article, keyword expansion mechanics, or auditing a single tactic for penalty risk.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Core principle: the right move depends on whether you have data yet, and most bad SEO advice is given to the wrong one of those two situations. A site with no rankings and a site with a breadwinner page need opposite behavior. Advice that ignores which you are in is how efforts stall despite consistent output.
Distilled from two content properties run in production and the Search Console reads that
produced each rule. This is a first-party method: narrower than a general playbook, and
more trustworthy for it. Every rule traces to the failure or result behind it in
references/why-these-rules.md. Absolute traffic figures are withheld; the ratios and
thresholds are as observed.
| You are here if… | Playbook | Read |
|---|---|---|
| No rankings, no authority, <100 clicks/mo, possibly no content | A — Cold start | references/cold-start.md |
| GSC has real rows: something ranks, something earns clicks | B — With data | references/with-data.md |
Diagnose per cluster, not per site. A mature site opening a new territory is in Playbook A for that territory and Playbook B everywhere else — and that combination is the strongest position in the method.
Playbook A in one line: you cannot win an established term from zero authority, so hunt an emerging one, ship ONE page, and let day-7 / day-21 decide whether it was real.
Playbook B in one line: your own GSC already knows which page shapes win for you — find the breadwinner, extract the shape, diagnose whether it is position-limited or snippet-limited, compound it, and protect it while you do.
references/emerging-terms.md — the hunt. The wedge in both playbooks, and the only
thing that works in Playbook A. Where to look, in what order, and the seven gates a candidate
must pass.references/measurement.md — which metric scores which situation, the four query
families that never click, and the GSC traps that produce confident wrong conclusions.references/why-these-rules.md — the failure or result behind each rule.references/operationalize.md — turning either playbook into scheduled loops.Pull a 28-day GSC window ending 3 days back (GSC lags 2–3 days):
If these aren't available, say so and instrument first. Advising without them is guessing, and it is the most common failure mode in this whole area.
| Question | Short answer | Detail |
|---|---|---|
| Cold start, what now? | Instrument, then land ONE emerging term. Not a cluster. | cold-start |
| Cluster or one page? | One page until the term proves itself. Cluster after. | cold-start |
| How do I find emerging terms? | Your own saved stream → repo/release feeds → social listening → diff vs your pages | emerging-terms |
| Is this term worth it? | Seven gates; failing one drops it, and dropping is normal | emerging-terms |
| What do we double down on? | The page at ≥30% of clicks — and the archetype it belongs to | with-data |
| Ranks well, no clicks? | Screen the query mix first. Most such pages are not broken. | with-data, measurement |
| Traffic plateaued despite publishing | The cluster saturated. Open a new front, don't add pages to it. | with-data §7 |
| When do I stop land-grabbing? | Three computable numbers, never a vibe | measurement |
| How do I stop doing this by hand? | Four loop roles, never one loop | operationalize |
Derived from B2B content SEO on low-to-mid authority domains. The two-playbook split, the
measurement discipline, and the emerging-term method transfer broadly. The specific archetypes
in with-data.md do not — they are one property's, and yours must be extracted from your own
data. Local, e-commerce, and YMYL were never tested here; say so rather than extrapolating.
new-loop — build the scheduled loop that runs either playbook on a cadence. See
references/operationalize.md and assets/seo-loop-template.md.まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
<What it does, one line>. Trigger phrases: <phrases>.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill whenever the user wants to create or improve a presentation for an academic context — conference papers, seminar talks, thesis defenses, grant briefings, lab meetings, invited lectures, or any presentation where the audience will evaluate reasoning and evidence. Triggers include: 'conference talk', 'seminar slides', 'thesis defense', 'research presentation', 'academic deck', 'academic presentation'. Also triggers when the user asks to 'make slides' in combination with academic content (e.g., 'make slides for my paper on X', 'create a presentation for my dissertation defense', 'build a deck for my grant proposal'). This skill governs CONTENT and STRUCTURE decisions. For the technical work of creating or editing the .pptx file itself, also read the pptx SKILL.md.
日本語の概要は準備中です。原文の説明を表示しています。
Shortest English alias for web-adapt / universal-web-adaptation. Use this when adapting an unfamiliar public website generically before creating any site-specific rules.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to audit CLI adapter projects (like opencli) for missing output fields, then batch-generate fixes and submit PRs. Turns AI agents into adapter quality reviewers.
日本語の概要は準備中です。原文の説明を表示しています。
Operate professional paid advertising across Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, Apple, Amazon, Reddit, Pinterest, Snapchat, and X. Use for account intake, source-grounded audits, strategy, budget and measurement planning, creative production, experiments, reporting, monitoring, and explicitly approved campaign changes. Also trigger on PPC, paid social, retail media, attribution, tracking, landing pages, cross-platform conversion totals, negative keywords or search terms, beta-feature scoring, stale platform claims, API-token or credential setup, campaign deletion, and safe Claude Ads installation or uninstall.
日本語の概要は準備中です。原文の説明を表示しています。
Audit Amazon Ads profiles, regions, Sponsored Products, Sponsored Brands, Sponsored Display, DSP, portfolios, targeting, search terms, retail readiness, creative, budgets, ACOS, TACOS, reporting, and policy. Use for Amazon Ads, sponsored ads, Amazon PPC, ACOS, TACOS, ASIN advertising, Amazon DSP, or retail-media optimization.
日本語の概要は準備中です。原文の説明を表示しています。