CtrlK
BlogDocsLog inGet started
Tessl Logo

organic-first-campaign

Grassroots-first campaign design for anyone being outspent — startups vs. incumbents, NGOs vs. corporate comms, movements vs. state-backed machines, solo brands vs. big-budget competitors. Ideates awareness, launch, fundraising, mobilization, community-build, counter-narrative, referral, founder-story, and coalition campaigns. Triggers on "campaign plan", "marketing strategy", "ad budget", "should I advertise", "paid vs organic", "launch plan", "grassroots", "low budget marketing", "NGO campaign", "outspent", "competitor has bigger budget", "how do I compete without money". Also trigger on any spend asymmetry, collapsing organic reach, rising CPAs, or a trust/credibility problem — even without the word "campaign". Nudge activation when the user debates buying ads, boosting posts, or hiring influencers; they are likely about to burn money on a channel that will not persuade.

67

Quality

81%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Discovery

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong, well-crafted skill description that excels across all dimensions. It clearly defines a specific niche (grassroots campaigns for budget-disadvantaged entities), lists concrete campaign types it can generate, and provides extensive natural trigger terms. The description also includes proactive activation guidance for edge cases, which is a sophisticated touch. Minor concern: the last sentence about 'nudge activation' and the editorial opinion ('they are likely about to burn money') adds slight opinionation that could be trimmed, but doesn't materially harm functionality.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'Ideates awareness, launch, fundraising, mobilization, community-build, counter-narrative, referral, founder-story, and coalition campaigns.' Also specifies concrete domains like startups vs. incumbents, NGOs vs. corporate comms, movements vs. state-backed machines.

3 / 3

Completeness

Clearly answers both 'what' (grassroots-first campaign design across multiple campaign types for outspent entities) and 'when' (explicit trigger phrases listed, plus situational triggers like 'when the user debates buying ads, boosting posts, or hiring influencers'). The 'Triggers on' clause serves as an explicit 'Use when' equivalent.

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms users would actually say: 'campaign plan', 'marketing strategy', 'ad budget', 'should I advertise', 'paid vs organic', 'low budget marketing', 'how do I compete without money', 'competitor has bigger budget'. These are highly natural phrases. Also includes conceptual triggers like 'spend asymmetry' and 'rising CPAs'.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive niche: grassroots-first campaigns specifically for entities being outspent. The framing around budget asymmetry and anti-paid-media positioning clearly distinguishes it from generic marketing or campaign skills. Unlikely to conflict with standard marketing strategy skills.

3 / 3

Total

12

/

12

Passed

Implementation

62%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is an extraordinarily thorough and well-structured campaign design skill with exceptional workflow clarity, rigorous validation gates, and highly actionable guidance at every stage. Its primary weakness is severe verbosity — the skill repeats key rules (anti-fabrication, capacity constraints) across multiple stages, includes persuasive arguments Claude doesn't need, and inlines detailed sub-processes that belong in reference files. The content would be significantly more effective at roughly 40-50% of its current length.

Suggestions

Move repeated rules (anti-fabrication, industry-peer rule, capacity constraints) to a single 'Standing Rules' section or a reference file, and reference them by name in each stage rather than restating them in full.

Move the 'Core Premise' empirical evidence and academic citations into a reference file (e.g., references/evidence-base.md) — Claude doesn't need to be persuaded of the skill's thesis, it just needs the decision rules.

Extract the detailed community-build sub-campaign, earned-media specificity rules, and ad-copy boost rules into reference files, keeping only the decision logic and pointers in the main SKILL.md.

Collapse the Failure Modes Quick Reference table — it duplicates every contract's failure modes and adds ~30 lines of redundant content.

DimensionReasoningScore

Conciseness

This skill is extremely verbose at ~500+ lines. It over-explains concepts Claude already understands (what MMF is, what diminishing returns are, how lift tests work), repeats the anti-fabrication rule at least 4 times across stages, restates failure modes in both the stage contracts AND a summary table, and includes extensive academic citations and empirical data that could be in reference files. The core premise section alone is ~20 lines of persuasive argument that Claude doesn't need to be convinced of. The principles section repeats guidance already stated in the stages.

1 / 3

Actionability

The skill provides extremely concrete, executable guidance at every stage: specific question sets, scoring rubrics (0-6 preconditions, 0-3 MMF), exact allocation percentages (70/30, 80/20), named lift-test templates with selection criteria, explicit capacity-cutting rules, community-build week-by-week sub-plans, and a complete output template with numbered sections. Every stage has clear inputs, outputs, and decision rules.

3 / 3

Workflow Clarity

The 7-stage workflow (1, 2, 3, 3a, 4, 5, 5b) is meticulously sequenced with formal contracts declaring inputs, outputs, preconditions, postconditions, and failure modes. Critical validation checkpoints are explicit: MMF gate at 3a can halt the entire workflow, Stage 5 has a mandatory stop-point awaiting user selection, capacity checks in 5b force cuts. The resume protocol ensures idempotency. Feedback loops are built into every destructive decision point.

3 / 3

Progressive Disclosure

The skill correctly references 7 external files in a references directory and defers detailed content to them (archetypes, channel tiers, sector riders, lift-test templates, etc.). However, the SKILL.md itself is monolithic — it contains enormous amounts of inline detail that could be in reference files (the full Stage 1 interview logic, the complete anti-fabrication rules, the community-build sub-campaign, the ad copy rules). The references section is well-organized but the main file is a wall of text that undermines the progressive disclosure pattern.

2 / 3

Total

9

/

12

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (753 lines); consider splitting into references/ and linking

Warning

Total

10

/

11

Passed

Repository
bencium/bencium-marketplace
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.