CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

marketing-loops

When the user wants a recurring marketing job an AI agent runs on a cadence or trigger, or asks what a weekly or daily automated check should do, remember, and when it should stop: SEO and ads checks, churn watches, outbound triage. For one-off ideas, see marketing-ideas. For the test loop, see ab-testing.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

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

A well-engineered orchestration skill: the body carries the decision rules (cadence, checkpoints, when-not-to-loop, anti-patterns) while all bulk content is correctly pushed one level deep into a verified, well-signaled reference bundle. The main flow is actionable and clearly sequenced. Remaining upside is minor: trim framing prose and surface one inline worked example of a completed loop spec.

Suggestions

Tighten the motivational framing (e.g. the 'you'd otherwise do manually (and forget)' and 'liability, not an asset' sentences) to pure directive statements.

Include one short inline filled-out loop example (all nine anatomy parts, a few lines each) so users see a complete spec without opening loop-template.md.

DimensionReasoningScore

Conciseness

The body is dense with skill-specific operational judgment (the cadence table, the check/act split, the nine-part anatomy, anti-patterns) and avoids explaining concepts Claude already knows, but a few framing sentences could be trimmed — e.g. 'turns a marketing task you'd otherwise do manually (and forget) into an always-on system' and 'is a liability, not an asset'. This puts it at anchor 4 (efficient, minor instances that could be trimmed) rather than anchor 5's every-token-earns-its-place.

4 / 5

Actionability

Guidance is concrete throughout: exact context-file paths to check, a five-step numbered flow, specific cadences per signal, named scheduling tools ('/loop', 'ScheduleWakeup', 'CronCreate') with a concrete cron example ('0 9 * * 1' for Mondays 9am), and a readiness gate for authored loops. It misses anchor 5 only because no worked filled-out loop example appears inline — the before/after example lives one reference deep in loop-template.md.

4 / 5

Workflow Clarity

The 'How to Use' flow is a clear five-step sequence with an explicit human-checkpoint step, and the anatomy table mandates self-checks, state/idempotency, and stop/bail-out with error handling, plus an authoring gate ('if you can't answer the self-check... the loop isn't ready to run'). It sits at anchor 4 rather than 5 because the main flow's validation checkpoints are stated as requirements rather than as explicit verify-then-proceed steps with feedback loops.

4 / 5

Progressive Disclosure

The 116-line body is a genuine overview: the 913-line catalog, guardrails, state patterns, template, orchestration guide, and both operator specs all live in references/, every referenced file exists, each is introduced with a clear purpose statement at the point of mention, and references are one level deep (the only 'references/' mentions inside bundle files point to other skills' files, not nested files in this bundle). This matches anchor 5: clear overview, well-signaled one-level-deep references, easy navigation.

5 / 5

Total

17

/

20

Passed

Description

87%Weight 40%Scale 1-5

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

A strong description: explicit and specific trigger guidance, concrete example job types, and clear routing disambiguation against sibling skills. It stays in third person and avoids fluff. The only soft spot is that capability coverage is expressed as example loops rather than a complete action list.

DimensionReasoningScore

Specificity

The description lists several concrete specifics — 'SEO and ads checks, churn watches, outbound triage' plus 'what a weekly or daily automated check should do, remember, and when it should stop' — naming the domain and multiple concrete job types. It falls short of anchor 5 because it enumerates example loop types rather than a comprehensive list of actions the skill itself performs, and slightly exceeds anchor 3's '1-2 concrete actions'.

4 / 5

Completeness

Both 'what' and 'when' are explicitly answered: the when is 'When the user wants a recurring marketing job an AI agent runs on a cadence or trigger, or asks what a weekly or daily automated check should do, remember, and when it should stop', and the what is those recurring checks/watches/triage jobs with memory and stop conditions — concrete trigger phrases throughout, matching anchor 5. Anchor 4 doesn't fit because the when-clause is already explicit and specific, not merely present.

5 / 5

Trigger Term Quality

Natural trigger phrases are well covered: 'recurring marketing job', 'cadence or trigger', 'weekly or daily automated check', 'churn watches', 'outbound triage' — phrasings a user would plausibly say. A few natural synonyms ('monitor', 'scheduled', 'alert/digest') are missing, so it matches anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (recurring/cadence-based marketing jobs) and explicitly disambiguates adjacent skills — 'For one-off ideas, see marketing-ideas. For the test loop, see ab-testing' — so conflict risk within the marketing skill family is minimal, matching anchor 5.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

coreyhaines31/marketingskills

Path

skills/marketing-loops/SKILL.md

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.