「email」の検索結果

When the user wants to find, qualify, and build a list of prospects to reach out to — across B2B SaaS, general B2B, or local small businesses. Also use when the user mentions "prospecting," "build a prospect list," "find prospects," "find leads," "lead gen list," "find SaaS companies that," "find B2B companies," "find local businesses," "ICP-fit accounts," "who should we go after," "outbound list," "target account list," "find clients near me," "businesses without websites," "prospect research," or "qualified leads." Use this for the list-building and qualification phase. For writing the outbound copy after the list is built, see cold-email. For deep competitive research on specific accounts, see competitor-profiling.

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

When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product. Also use when the user mentions "marketing plan," "growth plan," "GTM plan," "go-to-market plan," "AARRR plan," "90-day marketing plan," "12-month marketing roadmap," "fractional CMO plan," or "fCMO plan." Generates an exhaustive 13-section plan structured by AARRR (Acquisition, Activation, Retention, Referral, Revenue), customized to the client's current budget, team, and stage, mapped to future funding milestones, cross-referenced with the 139-idea marketing-ideas library and an embedded 17-section current-state audit rubric, with a full marketing operations stack showing which skills and MCP/API integrations execute each part. Outputs a Notion-paste-ready markdown document. For positioning and ICP context before planning, see product-marketing. For stage-specific deep work, see onboarding, signup, emails, referrals, pricing.

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

When the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing strategies,' 'marketing tactics,' 'ways to promote,' 'ideas to grow,' 'what else can I try,' 'I don't know how to market this,' 'brainstorm marketing,' or 'what marketing should I do.' Use this as a starting point whenever someone is stuck or looking for inspiration on how to grow. For specific channel execution, see the relevant skill (ads, social, emails, etc.).

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

Audits and optimizes websites for search engine visibility (SEO) and AI search citation (GEO), covering technical health, E-E-A-T content scoring, domain authority, structured data, rich results, and entity signals. Use when running SEO audits, diagnosing traffic drops or ranking losses, generating Schema.org JSON-LD, checking Core Web Vitals, crawlability, robots.txt, sitemaps, hreflang, backlinks, planning content strategy or site migrations, fixing indexing issues, or optimizing for AI Overviews, ChatGPT, and Perplexity. NOT for paid ads (PPC/SEM), social media strategy, email marketing, or general web development unrelated to search.

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

A curated marketing stack guide for SaaS startups — tools, channels, and metrics organized by growth stage. Know exactly which tools to adopt and when. By @WeiYipei.

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

Ready-to-use KOL cold outreach templates — DM scripts for Twitter, email pitches, and follow-up sequences designed to get replies from busy influencers. Tested across 500+ creator partnerships. By @WeiYipei.

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

Triage long email threads for an insurance context, identify the most recent actionable message, extract key context, infer intent (e.g., missing documents, follow-up/reminder, payment, status), and decide whether to reply or take further action.

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

Route new policy briefing, policy update, regulatory update deck, regulatory change deck, compliance change summary, legal update deck, or legal/product policy presentation requests here before generic AIPPT. Use this whenever the user wants a new policy interpretation deck with timelines, impacts, risks, and recommended actions. Do not use this scene pack for email memos, FAQ-only outputs, compliance copy polishing, or non-deck legal writing.

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

Write churn prevention and win-back playbooks — risk intervention sequences, save conversation guides, and win-back email campaigns. Use when asked to "prevent churn", "save at-risk customers", "win back churned customers", or "build a save play".

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

Optimize customer onboarding — map the activation sequence, identify drop-off points, design the aha moment, and produce the onboarding email sequence. Use when asked to "fix onboarding", "improve activation", "time-to-value is too slow", or "customers aren't getting started".

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

Media and podcast outreach personalizer — takes a story angle and target journalist or host list and produces personalized pitch emails per target. Use when asked to "write media pitches", "pitch this story to journalists", "get us on podcasts", "write press outreach", or "personalize pitches for these contacts".

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

Write media pitches and press releases — journalist outreach emails, podcast pitch scripts, newsletter sponsor pitches, and press release copy. Use when asked to "pitch journalists", "write a press release", "reach out to podcasts", or "get media coverage".

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

Use when the user asks Claude Code to read or write Odysseus data (todos, email, calendar, memory, documents) or to launch/monitor/stop a Cookbook model-serve task through the scoped Claude Agent API. Requires ODYSSEUS_URL and ODYSSEUS_API_TOKEN.

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

Use when the user asks Codex to read or write Odysseus data (todos, email, calendar, memory, documents) or to launch/monitor/stop a Cookbook model-serve task through the scoped Codex Agent API. Requires ODYSSEUS_URL and ODYSSEUS_API_TOKEN.

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

Prevents private infrastructure details (node hostnames, internal project names, local usernames and personal emails, absolute home paths, private and VPN IP ranges) from leaking into public repositories through commits, PRs, docs or release artifacts. Use when working in a public or soon-to-be-public repo, before commits or releases, when writing deployment docs for an OSS project, or when the user asks to "set up the privacy guard", "install privacy-guard", "check for leaks", "protect this public repo". Bootstraps a pre-commit hook backed by a gitignored local denylist plus gitleaks.

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

Build an interactive account org chart, leadership map, buying committee, or manager/report neighborhood around a person. Use for decision makers, reporting-line candidates, stakeholder mapping, and warm intro paths. Skip standalone email lookup and unrelated cross-company prospecting.

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

ACCESS-GATED beta. Deepline Monitors are provider event feeds (job posts, email replies, funding, intent) that stream into your warehouse and trigger plays. Only use if you have monitor access: run `deepline monitors status` first; if it reports no access, do NOT use this recipe — tell the user to contact the Deepline team.

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

DRAFT. Use when running a Luma-centered GTM event campaign: pull/export guests, enrich and score, draft invites and social, stage email+LI sequences paused for approval, and wire registration sync. Not installed by deepline skills.

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

Use for Deepline GTM work that searches, enriches, scores, collects signals, or automates a workflow: find companies or people, enrich a CSV, find emails or LinkedIn, compare providers, build a waterfall, create a webhook or cron, or write a Play. For live information work, run a small heterogeneous experiment, exploit the observed winner, and reopen misses. Skip pure copywriting and non-GTM research.

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

When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," or "overlay." For forms outside of popups, see form-cro. For general page conversion optimization, see page-cro.

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

Use Verify for snapshot testing in .NET. Approve API surfaces, HTTP responses, rendered emails, and serialized outputs. Detect unintended changes through human-reviewed baseline files.

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

Personal research-paper radar. Fetches the latest papers and code repos for the user's keyword subscriptions across arXiv, Crossref (IEEE/ACM), Semantic Scholar, GitHub, HuggingFace, Papers with Code and RSS; deduplicates against history; then YOU (the assistant) expand the queries, filter for computer-science relevance, write Chinese summaries, detect hot sub-fields, and emit a Markdown + HTML digest (optionally emailed). Use when the user asks to "run my paper radar / 文献雷达", "check for new papers", "what's new in my topics", "今天有什么新论文 / 最新文献", "today's research digest", or to configure their keyword subscriptions / sources / schedule.

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

Build stateful AI agents using the Cloudflare Agents SDK. Load when creating agents with persistent state, scheduling, RPC, MCP servers, email handling, or streaming chat. Covers Agent class, AIChatAgent, state management, and Code Mode for reduced token usage.

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

When the user wants high-converting copy for landing pages, headlines, cold emails, X/LinkedIn posts, video intros, or SEO titles — and already knows their audience. Also use when the user mentions "blitz copy", "dopamine copywriting", hooks, or asks to rewrite flat copy that explains instead of sells. For audience research first, use the understand-customers skill.

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