agentsclimarketplace

Performance marketer

Skill hartmut-ux/ai-marketing-team/skills/performance-marketer/.kimi/skills/performance-marketer

11 AI marketing skills for Kimi, Claude & Codex. Content strategy, PR, internal comms, change management, analytics & operations for SMEs and purpose-driven organisations.

Install
npx -y skills add hartmut-ux/ai-marketing-team --skill performance-marketer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 10 stars10 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Creates ad copy, Google Ads RSA headlines, A/B test plans, and campaign analysis for SME performance marketing. Handles paid search, paid social, email campaigns, and SEO content. Use when user asks about ads, campaigns, Google Ads, paid media, SEO, conversion optimization, or marketing performance metrics.

SKILL.md

1.1 KB, 180 tokens by cl100k_base, as published. Nobody here has run it

Performance Marketer — Kimi Code CLI wrapper

This is the Kimi Code CLI wrapper for performance-marketer. The full skill definition lives in shared/SKILL-CORE.md in the same skill folder.

When to use

Use when the user asks for:

  • /performance-marketer
  • "run performance-marketer"
  • Any trigger described in the core skill

How to invoke

In Kimi Code CLI:

/performance-marketer

Instructions

  1. Read shared/SKILL-CORE.md for the platform-agnostic workflow, rules, and examples.
  2. Execute the workflow using Kimi Code CLI tools.
  3. Load any referenced files from shared/ or subdirectories relative to this skill folder.

References

  • shared/SKILL-CORE.md — full skill definition

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most performance cost skills give in 180 tokens

Counted across 803 of the 1,058 authors here whose files we hold, read 2026-08-07

  • Keep skill files under 500 lines or tokensin 82 of 803, across 16 files
  • Use imperative form in instructionsin 80 of 803, across 9 files
  • Draft assertions while test runs are in progressin 75 of 803, across 9 files
  • Create two to three realistic test promptsin 74 of 803, across 9 files
  • Write skill descriptions to be pushyin 72 of 803, across 7 files
  • Save test cases to evals JSONin 72 of 803, across 6 files
  • Ask questions about edge cases and input formatsin 72 of 803, across 7 files
  • Save timing data immediately when runs completein 70 of 803, across 5 files
  • Include all trigger conditions in the skill descriptionin 69 of 803, across 3 files
  • Launch all test runs in a single turn or simultaneouslyin 69 of 803, across 3 files
  • Capture intent before writing a skillin 67 of 803, across 1 file
  • Import directly instead of barrel filesin 52 of 803, across 15 files

Said here and by no other author read

  • read the core skill definition file
  • execute the workflow using cli tools
  • load referenced files from shared directories

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.