Compatibility skill for seo google. Use when a user or upstream workflow invokes this name; route the task to `seo-audit` while preserving the requested scope and source-specific intent.
日本語の概要は準備中です。原文の説明を表示しています。
2,788 件 ・ 関連度順
概要と使いどころ
Compatibility skill for seo google. Use when a user or upstream workflow invokes this name; route the task to `seo-audit` while preserving the requested scope and source-specific intent.
日本語の概要は準備中です。原文の説明を表示しています。
Compatibility skill for seo geo. Use when a user or upstream workflow invokes this name; route the task to `ai-seo` while preserving the requested scope and source-specific intent.
日本語の概要は準備中です。原文の説明を表示しています。
Compatibility skill for product marketing context. Use when a user or upstream workflow invokes this name; route the task to `product-marketing` while preserving the requested scope and source-specific intent.
日本語の概要は準備中です。原文の説明を表示しています。
Compatibility skill for seo backlinks. Use when a user or upstream workflow invokes this name; route the task to `offsite-signal-analyzer` while preserving the requested scope and source-specific intent.
日本語の概要は準備中です。原文の説明を表示しています。
Compatibility skill for referral program. Use when a user or upstream workflow invokes this name; route the task to `referrals` while preserving the requested scope and source-specific intent.
日本語の概要は準備中です。原文の説明を表示しています。
Compatibility skill for seo content. Use when a user or upstream workflow invokes this name; route the task to `content-strategy` while preserving the requested scope and source-specific intent.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "map our positioning", "name our competitive alternatives", or "pick a beachhead segment for the launch"; produces a Dunford-style positioning canvas — named competitive alternatives (including spreadsheet and status quo), unique attributes (verifiable, or routed to the claims ledger), value themes (attribute→benefit→value chains), a target beachhead segment scored on serviceability / pain intensity / reachability, and a one-sentence onlyness statement — the sole upstream of the message house and the entity-signal source for the canonical entity profile. Not for the message house or per-channel launch copy — use message-house-builder; not for audience/persona profiling itself — use audience-mapper; not for SEO keyword positioning — use keyword-research. 定位画布/竞争替代品/独特价值/滩头细分
日本語の概要は準備中です。原文の説明を表示しています。
Compatibility skill for seo drift. Use when a user or upstream workflow invokes this name; route the task to `performance-monitor` while preserving the requested scope and source-specific intent.
日本語の概要は準備中です。原文の説明を表示しています。
Compatibility skill for seo flow. Use when a user or upstream workflow invokes this name; route the task to `seo` while preserving the requested scope and source-specific intent.
日本語の概要は準備中です。原文の説明を表示しています。
Compatibility skill for schema markup. Use when a user or upstream workflow invokes this name; route the task to `schema` while preserving the requested scope and source-specific intent.
日本語の概要は準備中です。原文の説明を表示しています。
Compatibility skill for popup cro. Use when a user or upstream workflow invokes this name; route the task to `popups` while preserving the requested scope and source-specific intent.
日本語の概要は準備中です。原文の説明を表示しています。
Compatibility skill for seo hreflang. Use when a user or upstream workflow invokes this name; route the task to `seo-audit` while preserving the requested scope and source-specific intent.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "package our proof points", "build reusable stat cards and case snippets", or "put proof where each pillar makes its claim"; turns claims-ledger-approved proofs into reusable proof modules — stat cards, case snippets, testimonial blocks, comparison proofs — each pinned to a message-house pillar and the ledger claim ID it substantiates, and flags any pillar making a claim with no approved proof behind it. Never adjudicates a proof: unverified or ledger-absent proofs are marked '[needs source]' and routed to the claims candidates. Not for adjudicating or substantiating claims — use offer-claims-registry; not for fabricating a benchmark to fill a gap — a missing proof is flagged, not invented; not for scoring narrative quality — use narrative-quality-auditor. 证据模块/证据卡/客户案例/主张对齐
日本語の概要は準備中です。原文の説明を表示しています。
Compatibility skill for seo content brief. Use when a user or upstream workflow invokes this name; route the task to `content-strategy` while preserving the requested scope and source-specific intent.
日本語の概要は準備中です。原文の説明を表示しています。
Compatibility skill for seo dataforseo. Use when a user or upstream workflow invokes this name; route the task to `seo` while preserving the requested scope and source-specific intent.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "build our pitch deck narrative", "write a fundraising story", or "structure the sales pitch narrative"; derives from the narrative canon a company pitch/deck narrative — problem → the undeniable shift → product-as-hero → proof → the ask — as a slide-beat outline (one narrative beat per slide, with the claim ID each proof beat rests on), for both a sales pitch and a fundraising deck. Every proof beat is labeled Measured / User-provided / '[needs source]' and unverified ones route to the claims candidates. Not for the launch-window battle cards and talk track — use sales-enablement-kit; not for the durable message hierarchy or the arc itself — use message-system-architect / strategic-narrative-designer; not for finished deck visual design — out of scope; not for claim adjudication — use offer-claims-registry. 路演叙事/融资故事/销售 pitch/幻灯节拍
日本語の概要は準備中です。原文の説明を表示しています。
Compatibility skill for seo cluster. Use when a user or upstream workflow invokes this name; route the task to `content-strategy` while preserving the requested scope and source-specific intent.
日本語の概要は準備中です。原文の説明を表示しています。
Compatibility skill for seo ecommerce. Use when a user or upstream workflow invokes this name; route the task to `seo-audit` while preserving the requested scope and source-specific intent.
日本語の概要は準備中です。原文の説明を表示しています。
Compatibility skill for seo competitor pages. Use when a user or upstream workflow invokes this name; route the task to `competitors` while preserving the requested scope and source-specific intent.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "remember project context", review saved findings, initialize runtime memory, archive stale work, reconcile notes, or erase a subject; manages authorized HOT/WARM/COLD working memory across all disciplines while preserving registry event ownership and privacy controls. Not for changing canonical registry facts - route those through the owning registry. 项目记忆/跨会话
日本語の概要は準備中です。原文の説明を表示しています。
Compatibility skill for paid ads. Use when a user or upstream workflow invokes this name; route the task to `ads` while preserving the requested scope and source-specific intent.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "build programmatic SEO pages", "generate pages at scale", "rank on a high-authority third-party site", "borrow domain authority", "build a vs / alternative page", "do local SEO", "optimize a Google Business Profile", or "fix NAP" — one page-build router with four modes: programmatic (template × dataset systems), parasite (barnacle publishing on Medium/Reddit/LinkedIn/GitHub), comparison (vs / alternative pages in four formats), and local (GBP + NAP + citations + location pages), each with its own thin/duplicate, honesty, or reputation-abuse guardrail. Not for finding what to target — use keyword-research or content-gap-analysis; not for drafting one standalone article — use content-writer; not for scoring a page for publish — use content-quality-auditor. 程序化SEO/批量页面/寄生SEO/借势权重/对比页/vs页/替代页/本地SEO/谷歌商家档案/NAP一致性
日本語の概要は準備中です。原文の説明を表示しています。
Compatibility skill for launch strategy. Use when a user or upstream workflow invokes this name; route the task to `launch` while preserving the requested scope and source-specific intent.
日本語の概要は準備中です。原文の説明を表示しています。
Route complex marketing work across strategy, narrative, SEO/GEO, CRO, lifecycle, paid, social, influencer, launch, sales and measurement. Use for broad marketing plans, multi-channel work, or when the right specialist skill is unclear.
日本語の概要は準備中です。原文の説明を表示しています。