「ci」の検索結果

Analyze live Ahrefs backlink, referring-domain, organic-keyword, and content data when an authorized Ahrefs connector is available. Use for Ahrefs-specific SEO evidence, not for estimates when no live connection exists.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of mouth,' 'viral loop,' 'refer a friend,' 'partner program,' 'referral incentive,' 'how to get referrals,' 'customers referring customers,' or 'affiliate payout.' Use this whenever someone wants existing users or partners to bring in new customers. For launch-specific virality, see launch.

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user asks to "build a win-back campaign", "re-engage lapsed subscribers", "run a re-permission / re-consent sweep", or "sunset my dead list"; produces a closed-loop reactivation program — a lapsed-cohort definition, a staged offer ladder, a re-consent (re-permission) capture step, and a sunset-confirm / suppression rule. Owns none of the SEND-N sub-item notes: engagement-decay / sunset is email-sequence-designer's and preference-center / frequency options is preference-frequency-manager's — this skill references those notes, it does not re-emit them. Not for the general lifecycle flows (welcome/cart/post-purchase) — use email-sequence-designer; not for the preference-center / opt-down ladder — use preference-frequency-manager; not for the consent record itself — use consent-registry; not for computing EQS or the N1 veto — use email-quality-auditor. 流失召回/重新授权/沉默用户清理

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user asks to "build battle cards", "prep the sales team for launch", or "write the internal launch FAQ"; produces the internal enablement kit for a sales-led launch — battle cards vs each named alternative (where we win / where they win / trap questions, every fact traceable), a sales talk track derived from the PR-FAQ spine, an objection-handling table (objection → response → evidence), internal FAQ + CS macros, and an internal launch announcement with embargo discipline. Not for the external message house — use message-house-builder; not for competitor tracking itself — use competitor-tracker or competitor-analysis; not for outbound sequences — use cold-outbound-sequencer. 销售赋能/battle card/销售叙事/异议处理/内部FAQ

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user asks to "build the norm card for this platform", "what are the char limits and visible-fold cutoffs here", "is the LinkedIn link-in-first-comment thing documented or folklore", or "which of our platform cards are stale"; maintains the dated, versioned per-platform norm cards in the references/platforms/ pack — char limits, visible-fold cutoffs, hashtag norms, format/aspect specs, link and first-comment placement, disclosure-label mechanics, algorithm emphases (e.g. 小红书 search+saves weighting) — every row labeled platform-documented (official doc, Measured) or Estimated-folklore (named source) with last-verified and review-by dates, and any card past its review date flagged stale rather than trusted. Extends the single pack in place; never forks a second one. Not for picking which channels to run — use channel-portfolio-planner. 平台规范卡/字符限制/折叠线/话题标签/算法侧重/过期标记

日本語の概要は準備中です。原文の説明を表示しています。

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 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 "make everyone tell the same story", "write our elevator pitch ladder", or "build a spokesperson Q&A and approved boilerplate pack"; derives from the narrative-registry canon, message house, and brand voice a repeatable enablement kit — an elevator ladder (10-second / 30-second / 2-minute), a spokesperson Q&A (tough questions with on-canon answers), an approved boilerplate/bio pack (25 / 50 / 100-word), and a do/don't language sheet — so sales, support, founders, and partners repeat one consistent story. Not for the launch-day runbook — use launch-day-conductor; not for finished per-channel copy — use content-writer or each discipline creative builder; not for launch-window battle cards — use sales-enablement-kit; this kit never adjudicates a claim. 叙事赋能包/电梯梯度/发言人问答/审定样板/该说不该说

日本語の概要は準備中です。原文の説明を表示しています。

Compatibility skill for paywall upgrade cro. Use when a user or upstream workflow invokes this name; route the task to `paywalls` while preserving the requested scope and source-specific intent.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user asks to "watch my list health over time", "flag decaying / unengaged subscribers on a schedule", "why is my open rate drifting down / bounces creeping up", or "build me a re-permission and prune worklist"; runs the scheduled SEND list-decay + suppression-drift watch — an engagement-recency cohort read (30/90/180/365-day), hard-bounce and spam-complaint trend vs benchmark, suppression-list growth/leakage check, and a segmented re-permission / sunset / prune worklist tied to SEND S (list hygiene) and E (engagement-decay) sub-items. Not for the one-time pre-send authentication pre-flight — use deliverability-qa; not for the consent/suppression record itself — use consent-registry; not for computing the EQS or enforcing vetoes — use email-quality-auditor. 邮件列表健康度监控/退订漂移/沉睡用户清理

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user asks to "write influencer outreach", "follow up with a creator", "pitch a journalist, hunter, or launch partner", or "negotiate partnership terms"; produces personalized pitches, multi-touch follow-up sequences, negotiation scripts with objection handling, and a status pipeline tracker — the shared outreach mechanics engine for creator, media/analyst, launch-partner, and social-selling / advocate-recruitment targets. Not for finalizing signed agreements — use contract-helper; not for media-list tiering, embargo terms, or press-release structure — use press-media-relations. 达人邀约建联/合作谈判话术

日本語の概要は準備中です。原文の説明を表示しています。