Compare  ·  CLI & API Wrappers

marketing-plan vs yeet

Which CLI wrapper is right for you?

Notable score gap. marketing-plan scores meaningfully higher; see individual reviews for nuance.


01 — TL;DR

If you need reusability above all else, pick marketing-plan (4.9/5). yeet (3.7/5) is a reasonable alternative if you're already in its source ecosystem. They overlap in CLI wrapper territory.


02 — At a glance

Side by side

marketing-plan

4.9/5

Category
CLI & API Wrappers
Source
skillsmp.com
Tier
Reviewed
First published
2026-07-28
Trigger clarity
5.0
5.0
Output specificity
5.0
5.0
Scope precision
5.0
5.0
Self-containment
5.0
5.0
Reusability
4.0
4.0

yeet

3.7/5

Category
CLI & API Wrappers
Source
github:openai/skills
Tier
Reviewed
First published
2026-05-19
Trigger clarity
5.0
5.0
Output specificity
5.0
5.0
Scope precision
5.0
5.0
Self-containment
5.0
5.0
Reusability
3.5
3.5

03 — Dimension breakdown

Where they differ

  1. Trigger clarity. trigger clarity: marketing-plan and yeet score essentially the same (5.0 vs 5.0). Neither has an edge here.
  2. Output specificity. output specificity: marketing-plan and yeet score essentially the same (5.0 vs 5.0). Neither has an edge here.
  3. Scope precision. scope precision: marketing-plan and yeet score essentially the same (5.0 vs 5.0). Neither has an edge here.
  4. Self-containment. self-containment: marketing-plan and yeet score essentially the same (5.0 vs 5.0). Neither has an edge here.
  5. Reusability. reusability: marketing-plan is clearly stronger (4.0 vs 3.5). For workloads where this dimension matters, prefer marketing-plan.
04 — The decision

Which to pick

When to choose marketing-plan

  • Your workload emphasizes reusability — marketing-plan scores 4.0 vs 3.5 here.
  • You weight community adoption — marketing-plan's upstream repo has 41,168 stars vs 19,581.
  • The CLI wrapper convention you're working in matches marketing-plan's scope.

When to choose yeet

  • You prefer the official source — yeet comes from github:openai/skills, marketing-plan from skillsmp.com.
  • The CLI wrapper convention you're working in matches yeet's scope.
05 — Use cases

Scenario by scenario

Scenario Winner Why
Agent must auto-select between many CLI wrappers either Trigger clarity decides — clearer triggers reduce routing errors.
Output must be a specific file format or structured data either Output specificity determines whether downstream tools can rely on the result.
Skill must be readable and complete out of the box either Self-containment matters when you're not the original author.
Cross-team or cross-project reuse expected marketing-plan Reusability separates one-off scripts from durable building blocks.
06 — FAQ

Common questions

Which is better, marketing-plan or yeet?
marketing-plan ranks higher overall (4.9 vs 3.7 on our 0–5 rubric). That said, the better choice depends on which dimensions matter most for your use case.
Are marketing-plan and yeet both free to use?
Both skills are free and open-source (or freely licensed). marketing-plan: See source repo. yeet: See source repo. Installation has no cost; usage costs depend on the underlying LLM tokens consumed when you invoke the skill.
Can I install both marketing-plan and yeet at the same time?
Yes. Agent skills are not exclusive — an agent runtime (Claude Code, Codex, etc.) can have many skills installed and route to whichever matches the current task. Installing both is a low-cost way to keep your options open.
Where do these skills come from?
marketing-plan is sourced from skillsmp.com (curated marketplace). yeet is sourced from github:openai/skills (official). We verify each skill across multiple sources where possible; marketing-plan appears in 1 source, yeet in 1.

445 words · Tier S (same-cluster)