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

Marketing Strategy

ASecurity

Develop positioning, audience research, go-to-market strategy, channel budgets and measurable marketing experiments for a product or business.

12 stars
0 votes
0 copies
0 views
Added 10/6/2026
ai-agentsgo

Works with

cli

Security Analysis

A100/100

Scanned 10/6/2026

$npx -y skills add Nmor/the-council --skill marketing-strategy --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Marketing Strategy?

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

Security grade badge for Marketing Strategy
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/nmor-marketing-strategy/badge)](https://www.skillsdirectory.com/skills/nmor-marketing-strategy)

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: marketing-strategy
description: Develop positioning, audience research, go-to-market strategy, channel budgets and measurable marketing experiments for a product or business.
---

# Marketing strategy

> Size budget: 6 KB. Load only for a relevant marketing task.

## Establish the brief

Read the existing product, brand and customer evidence before proposing a strategy.
Identify the audience, problem, buying situation, geography, offer, business objective,
constraints and decision date. Reuse the project plan. Ask only for information that
changes the decision; continue with explicit assumptions where safe.
Distinguish user-provided facts, research, observed behavior and hypotheses. When a
claim depends on current competitors, channel costs or market conditions, verify it
using primary sources. Never invent interview findings, market size or demand.

## Build a defensible proposition

Describe the target customer's alternatives and why they would switch. Produce a
positioning statement, primary value proposition, message hierarchy and proof ledger:
claim, supporting evidence, audience, approved wording and unresolved gap. Explain
one or two useful trade-offs. Avoid unsupported superiority, testimonials and savings.
Use [entrepreneur](../entrepreneur/SKILL.md) for venture validation or unit economics,
[content-campaigns](../content-campaigns/SKILL.md) for execution and
[brand-creative-direction](../brand-creative-direction/SKILL.md) for the visual brief.

## Choose and measure a small set of experiments

Map awareness → evaluation → activation/purchase → retention to concrete user actions.
Select channels based on audience evidence and the available budget, team and lead time.
Provide a ranked experiment table with hypothesis, audience, asset, owner, spend cap,
primary metric, baseline (or unknown), measurement source, stop condition and review date.
Favor a few learnable experiments over an unsupported omnichannel plan.

Separate spend, leads, qualified leads, customers and retained customers. Specify the
attribution window and assumptions behind CAC, contribution margin and payback; show
ranges when uncertain. Reconcile event counts and deduplicate conversions. An impression
or click is not revenue. Use holdouts or controlled comparisons when practical; otherwise
state why the result is directional. Do not promise a conversion rate or ROI without data.

## Deliver and check

Deliver the requested strategy/brief, a prioritized experiment backlog and the evidence
needed to evaluate it. Verify arithmetic, audience fit, claim support and feasibility.
Record missing evidence and the next decision each experiment resolves. A draft is not
a launched campaign; creating a plan does not authorize spending, publishing or messaging.
When relevant, apply the project's privacy, advertising and accessibility requirements.
Check applicable rules from authoritative sources rather than guessing legal obligations.

Attribution

NmorNmor
View sourceSee grades on GitHubMore from Nmor →
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', ...

698621 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 →