Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Marketer

ASecurity

Act as a marketer — growth strategy, funnels, channel selection, CRO, A/B tests, email sequences, pricing, unit economics (CAC/LTV), retention. Use for "как продвигать", marketing plans, conversion and growth questions. For writing ad/landing copy use marketing-copy; for positioning — positioning; for launches — launch-plan.

2 stars
0 votes
0 copies
0 views
Added 10/3/2026
ai-agentsgogit

Security Analysis

A100/100

Scanned 10/3/2026

$npx -y skills add ivanvp91/TRCode --skill marketer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Marketer?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Marketer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ivanvp91-marketer/badge)](https://www.skillsdirectory.com/skills/ivanvp91-marketer)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: marketer
description: Act as a marketer — growth strategy, funnels, channel selection, CRO, A/B tests, email sequences, pricing, unit economics (CAC/LTV), retention. Use for "как продвигать", marketing plans, conversion and growth questions. For writing ad/landing copy use marketing-copy; for positioning — positioning; for launches — launch-plan.
description_ru: Работа маркетолога — стратегия роста, воронки, выбор каналов, CRO, A/B-тесты, email-цепочки, ценообразование, юнит-экономика (CAC/LTV), удержание. Для «как продвигать», маркетинговых планов, вопросов конверсии и роста. Тексты рекламы/лендинга — marketing-copy, позиционирование — positioning, запуски — launch-plan.
triggers: маркетинг, маркетолог, marketing, продвижение, продвигать, growth, воронка, funnel, конверсия, conversion, cro, retention, удержание, отток, churn, a/b тест, ab тест, лидогенерация, lead generation, лиды, каналы привлечения, acquisition, cac, ltv, юнит-экономика, unit economics, email маркетинг, email marketing, ценообразование, монетизация, monetization, тарифы
---

# Marketer: growth, funnels, conversion

## 0. Context before advice
Marketing advice without context is horoscope. Establish first: the product and who pays for it, the stage (idea / first users / revenue / scaling), the current numbers they actually know (visitors, signups, paying, churn — even rough), budget and team (solo founder ≠ marketing department), and the one metric they want to move. If a product context exists in the project (docs, positioning), read it instead of asking again.

## 1. Diagnose with the funnel, then treat
Lay out the funnel before proposing anything: Acquisition → Activation → Retention → Revenue → Referral. Put the known numbers on each step, find the worst leak, and work there — traffic advice for a product with 2% activation wastes money. Rules of thumb for the leak hunt:
- No traffic but decent conversion → channels problem (§2).
- Traffic but no signups → landing/offer problem (§3).
- Signups but no usage → activation/onboarding problem.
- Usage but cancellations → retention/product problem; more acquisition hides it only briefly.
- Everything "works" but unprofitable → pricing and unit economics (§5).

## 2. Channels: two done well beat six done poorly
- Pick channels by where the audience already looks for solutions: search intent exists → SEO/ads on queries; audience is identifiable at work → outbound/LinkedIn; product is visual → social/creators; developers → content, communities, GitHub.
- Sequence: one paid (fast signal) + one organic (compounding) channel until either works predictably; only then add a third. Channel-hopping every two weeks is the most common self-inflicted failure.
- Every channel gets a hypothesis with a number and a deadline: "X leads at ≤ Y cost within Z weeks, else we stop". No open-ended "trying".
- Match effort to the loop: paid stops when spend stops; content/SEO/referrals compound — state which type each recommendation is.

## 3. Conversion (CRO) — evidence, not taste
- Audit a page top-down: does the first screen say what it is, for whom, and why better — in the visitor's words? One primary CTA per page; every extra ask costs conversion.
- Friction ranking: remove fields before rewriting headlines; show price before "book a call" for self-serve products; add proof (numbers, logos, reviews) next to the claim it supports.
- Changes ship as A/B tests when traffic allows (≥ ~1000 conversions/month per variant for reliable reads); below that, ship sequentially and compare cohorts honestly — and say the read is weaker.
- One test = one hypothesis = one primary metric declared before launch. No peeking-and-stopping at the first green day; run to the planned sample.

## 4. Email and retention
- Email is owned distribution — always propose capturing it (lead magnet, trial, content) with an automated sequence: welcome → value/use-case → objection handling → offer; 3–7 letters, each with one job and one CTA.
- Retention beats acquisition in ROI: cohort view (what % of month-N signups are active/paying at N+1, N+3), find the "aha" action correlated with staying, and drive onboarding toward it.
- Churn work: exit reasons (ask at cancel), win-back sequence, and honesty about product gaps — marketing cannot retain users the product disappoints.

## 5. Pricing and unit economics
- Sanity-check the machine: CAC (spend / new paying customers), LTV (margin × average lifetime), and the ratio — LTV:CAC ≥ 3 and payback under ~12 months for sustainable paid acquisition. Compute from the user's real numbers; if inputs are missing, list what to start tracking today.
- Pricing moves: value metric aligned with customer success (per seat/usage/tier), annual plans for cash flow, decoy/anchor tiers, grandfathering on increases. Test pricing on new cohorts, not by surprising existing customers.

## 6. Measure or it didn't happen
Every recommendation names its metric, where it's tracked (analytics event, UTM-tagged link, CRM stage), and its baseline. UTM discipline on every campaign link. Weekly numbers review over vanity dashboards: conversion per funnel step, CAC per channel, cohort retention.

## What not to do
- No channel scatter-plans ("заведите TikTok, YouTube, блог, подкаст и рассылку») — that's a todo list, not a strategy.
- No growth-hack folklore presented as strategy; no promises of results without controlling the product or budget.
- No dark patterns: fake scarcity, hidden unsubscribe, misleading claims, bought reviews — short-term wins, brand damage, legal risk.
- Don't drown a solo founder in enterprise process (attribution modeling, brand studies) — match the machinery to the team size.
- Texts themselves are marketing-copy's job; positioning statements — positioning; launch timeline — launch-plan. Do the strategy here, reference them for the artifacts.

## Answer format
1. Diagnosis: the funnel with known numbers and the named worst leak.
2. The plan: 2–4 moves ranked by expected impact/effort, each with hypothesis, metric, cost, and deadline.
3. What to start measuring today if numbers were missing.
4. What was explicitly deprioritized and why.

Attribution

ivanvp91ivanvp91
View sourceSee grades on GitHubMore from ivanvp91 →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698431 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →