When the user wants to create or update their product marketing context document — 'positioning,' 'ICP,' 'ideal customer profile,' 'who is my target audience,' or avoiding repeated foundational info across marketing tasks. Run at the start of a project: it creates `.agents/product-marketing-context.md`, which all other marketing skills read.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants SEO pages generated at scale from templates plus a dataset — "programmatic SEO," "pSEO," "directory pages," "location pages," "[keyword] + [city] pages," "integration pages," "generate 100 pages," "templated landing pages." For auditing an existing site, see seo-audit. For planning, see content-strategy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a GitHub Pull Request with full AI review. Human approves and merges.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to plan, design, or implement an A/B test or experiment — "split test," "variant copy," "multivariate test," "hypothesis," "statistical significance," "how long should I run this test," or comparing two versions. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, full variations — for any paid platform; 'ad copy variations,' 'RSA headlines,' 'bulk ad copy,' 'creative testing,' 'write me some ads.' For campaign strategy and targeting, see paid-ads. For landing page copy, see copywriting.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants content cited by LLMs or surfaced in AI-generated answers — 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'AI Overviews,' 'optimize for ChatGPT/Perplexity/Claude,' 'AI citations,' 'zero-click search.' For traditional technical/on-page audits, see seo-audit. For structured data, see schema-markup.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to set up, improve, or audit analytics tracking and measurement — "GA4," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "tracking plan," "attribution," "Mixpanel," "Segment," "are my events firing," or how to measure marketing results. For A/B test measurement, see ab-test-setup.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Architectural decision advisor for cloud, data, and SaaS distributed systems. Use when the user asks "should we use X or Y", weighs a tradeoff, or needs a decision matrix, scaling analysis, cost-at-scale review, data-tier design, multi-tenancy model, or API/resilience guidance. For full technical blueprints, use enterprise-design.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a feature branch from the default branch with a descriptive, conventional name.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to reduce churn or build retention systems — 'cancel flow,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'customers are leaving.' For post-cancel win-back sequences, see email-sequence. For in-app upgrade paywalls, see paywall-upgrade-cro.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Rigorous security and data privacy scan for cloud deployments. Covers GCP infrastructure hardening, data privacy (PII/GDPR/CCPA), API security, container security, and compliance. Audits deployed infrastructure and config — not a code-diff review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write B2B cold emails and follow-up sequences that get replies — "cold outreach," "prospecting email," "outbound email," "SDR emails," "nobody's replying to my emails." Covers subject lines, openers, body copy, CTAs, personalization, and multi-touch follow-ups. For warm/lifecycle sequences, see email-sequence. For sales collateral beyond emails, see sales-enablement.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Commit staged work with a conventional message after the quality gate passes. Use when the user asks to commit; never commits on a failing gate.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants competitor comparison or alternative pages for SEO and sales enablement — 'alternative page,' 'vs page,' '[Product] vs [Product],' 'battle card,' 'competitor teardown.' Covers four formats: singular/plural alternatives, you vs competitor, competitor vs competitor. For sales-specific competitor docs, see sales-enablement.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Connect, authenticate, and verify any SaaS CLI tool. Reads credentials from `.env`. Never prints secrets.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to plan content strategy or decide what topics to cover — "what should I write about," "blog strategy," "topic clusters," "editorial calendar," "content pillars," "content roadmap," "I don't know what to write." For writing individual pieces, see copywriting. For SEO audits, see seo-audit. For social media, see social-content.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sync 7 days of GitHub activity (commits, PRs, issues, reviews) into a structured context dump. Optionally pull from Slack, GDrive, or Asana if configured. Use at the start of a session to get fully caught up before coding.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to edit, review, or improve existing marketing copy — 'edit this copy,' 'proofread,' 'polish this,' 'tighten this up,' 'too wordy,' 'sharpen the messaging.' Use when copy exists and needs improving, not rewriting from scratch. For writing new copy, see copywriting.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to write, rewrite, or improve marketing copy for any page — homepage, landing, pricing, feature, about, or product pages; "headline help," "CTA copy," "value proposition," "tagline," "hero section," "make this more compelling," "conversion copy," or complete Figma-ready full-page copy (see Full-Page Mode below). For email copy, see email-sequence. For popups, see popup-cro. For editing existing copy, see copy-editing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run analytics queries against any database using plain English — BigQuery (bq CLI), PostgreSQL, MySQL, SQLite, or any DB with a CLI/MCP/API. Use when you need to pull metrics, analyze data, or answer business questions without writing SQL.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Act as a Senior Data Visualization Designer for dashboards, analytics pages, and chart-driven UI built in Recharts / visx / D3 / Plotly — chart-type decision tree, dashboard layout heuristics, color-blind safe palettes, empty/loading/error states, library trade-offs. For a one-off chart or plot, prefer a platform-native charting skill (e.g. dataviz) when present.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Connect to any database — Cloud SQL, PostgreSQL, Snowflake, Databricks, Athena, Presto, or Oracle.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sync documentation with what shipped: refresh READMEs, guides and API references, and prune stale mentions. Use once a feature lands or when asked to refresh docs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to create or optimize an email sequence, drip campaign, or lifecycle email program — "nurture sequence," "onboarding emails," "welcome series," "re-engagement," "email automation," "email cadence," or any multi-email automated flow. For cold outreach, see cold-email. For in-app onboarding, see onboarding-cro.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.