problem-solving

A set of structured methods for solving difficult marketing problems. It covers issues such as overly complicated campaigns, creative blocks, repeated problems, limiting assumptions, and uncertainty about reaching larger audiences.

In plain words
What is it for?
Use it to simplify campaigns, generate new creative directions, identify recurring patterns, question assumptions, and think through how an idea could scale.
Why use it?
It gives you a defined way to examine a stuck problem instead of relying only on brainstorming or guesswork.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/aitytech/agentkits-marketing/problem-solving
Any agent
npx skills add aitytech/agentkits-marketing --skill problem-solving
Clone the repo
git clone --depth 1 https://github.com/aitytech/agentkits-marketing

Made for: Claude Code, Codex.

Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,278 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00066 $0.02278
Opus 5 $0.00033 $0.01139
Sonnet 5 $0.00013 $0.00456
Haiku 4.5 $0.00007 $0.00228

Measured 2d ago against content hash 79f79c1e3f8a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

problem-solving scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/problem-solving/SKILL.md · 316 lines

How it starts

The opening of the file, as written. The whole thing — 316 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Marketing Problem-Solving

Systematic techniques for solving complex marketing challenges, breaking through creative blocks, and optimizing campaigns.

Language & Quality Standards

CRITICAL: Respond in the same language the user is using. If Vietnamese, respond in Vietnamese. If Spanish, respond in Spanish.

Standards: Token efficiency, sacrifice grammar for concision, list unresolved questions at end.


When to Use This Skill

Apply problem-solving techniques when facing:

  • Campaign Complexity Spirals - Campaign keeps adding features/channels, becoming unwieldy
  • Creative Innovation Blocks - Stuck in conventional approaches, need breakthrough ideas
  • Recurring Campaign Patterns - Same issues appearing across multiple campaigns
  • Assumption Constraints - Limited by industry "truths" or conventional wisdom
  • Audience Scale Uncertainty - Unclear how strategy scales from niche to mass market
  • General Stuckness - Progress halted, unclear how to move forward

Core Techniques

1. Simplification Cascades

Problem: Campaign complexity spiraling out of control

When to use:

  • Campaign has too many channels, messages, or touchpoints
  • Team overwhelmed by execution complexity
  • Budget spread too thin across tactics
  • Message diluted across too many variations

How it works:

  1. List all campaign elements (channels, messages, segments, assets)
  2. Identify the 20% that drives 80% of results
  3. Ruthlessly cut the rest
  4. Reassess and repeat if still complex

Marketing example:

Problem: Product launch campaign across 8 channels, 15 assets, 4 segments
↓ Simplification Round 1
Focus: Top 3 channels (email, LinkedIn, blog), 6 core assets, 2 key segments
↓ Simplification Round 2
Core: Email + LinkedIn, 3 assets (landing page, case study, email sequence), 1 primary segment
Result: Focused execution, better results, manageable workload

See: ./references/simplification-cascades.md


2. Collision-Zone Thinking

Problem: Creative blocks, conventional approaches not working

Read the full file on GitHub · 316 lines

Files

What ships with it

7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 316 lines · 66 tokens per session scan A 79f79c1e3f8a

Subscribe to this mod's changes

problem-solving is a skill published in the GitHub repository aitytech/agentkits-marketing (594 stars, last pushed 4d ago), licensed MIT. It adds 66 tokens to every session and 2,278 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

cost-efficiency-analyzer

Analyzes cost structure, cost efficiency, and expense management from P&L data. Use when the user asks about costs, expenses, COGS, operating expenses, cost ratios, cost control, spending efficiency, margin compression from cost side, or wants to understand where money is going. Also use for "are we spending too…

awslabs/agentcore-samples · 98 tokens

multi-quarter-trend-analysis

Analyzes financial trends across multiple quarters by comparing P&L metrics over time. Use when the user wants to see trends, patterns, trajectories, or directional movement across 3 or more quarters. Also use for "how are we trending", "show me the trend", "track performance over time", "quarter over quarter…

awslabs/agentcore-samples · 82 tokens

executive-financial-briefing

Generates a concise executive-level financial briefing or summary suitable for a CEO, CFO, or board presentation. Use when the user asks for a summary, briefing, executive summary, board update, financial overview, financial health check, or "how is the business doing". Covers the full P&L picture in one page. Also…

awslabs/agentcore-samples · 95 tokens

quarterly-kpi-calculator

Calculates quarterly financial KPIs from P&L data. P&L figures can be provided directly by the user or fetched from the financial data MCP server. Use when the user wants KPI calculations such as Gross Margin %, EBITDA Margin %, Operating Expense Ratio, or Revenue Growth % QoQ. Also use for quarterly performance…

awslabs/agentcore-samples · 84 tokens

revenue-growth-analyst

Deep-dives into revenue growth patterns, growth rates, and growth quality. Use when the user asks specifically about revenue growth, top-line performance, sales growth, revenue acceleration or deceleration, growth trajectory, or wants to understand what is driving revenue changes. NOT for cost or margin analysis …

awslabs/agentcore-samples · 72 tokens

earnings-snapshot

Generate a concise earnings and fundamental snapshot for a stock, covering valuation, recent earnings news, and analyst positioning.

awslabs/agentcore-samples · 26 tokens