CtrlK
BlogDocsLog inGet started
Tessl Logo

luma-event-campaign

DRAFT. Use when running a Luma-centered GTM event campaign: pull/export guests, enrich and score, draft invites and social, stage email+LI sequences paused for approval, and wire registration sync. Not installed by deepline skills.

72

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%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-structured, lean orchestration skill with excellent workflow gating (pilot-first enrich, paused campaigns, human approval) and a terminal checklist. Its main weaknesses are a broken reference layer — template files are cited but missing from the bundle, and the existing references/checklist.md is never linked — and unspecified operational details (enrichment provider, scoring criteria).

Suggestions

Create the referenced templates/ files (invite-email.md, linkedin-dm.md, social-announcement.md, speaker-bio.md, voice.md) or remove the references, so the messaging-pack step points at real content.

Link references/checklist.md from SKILL.md (e.g., a 'Full campaign timeline: see references/checklist.md' line) so the existing pre-launch/day-of checklist is discoverable.

Specify the enrichment provider and validation rule (what counts as an 'unsafe email') and give a concrete scoring rubric for hot/warm/low/skip, so the enrich-and-score step is fully executable without inference.

DimensionReasoningScore

Conciseness

The ~100-line body is lean: tables, checklists, and terse step lists with zero concept explanation. Every section carries operational content ('Pilot enrich on ≤10 rows before full waterfall', 'Write guests.normalized.csv'), matching the score-5 anchor ('lean and efficient; every token earns its place'). Not 4 because there is no over-explanation to trim — the repeated 'paused' emphasis is deliberate safety reinforcement, not padding.

5 / 5

Actionability

Concrete guidance throughout: named artifacts ('guests.normalized.csv', 'guests.scored.csv', 'out/copy/'), named segments ('hot/warm/low/skip'), pilot size (≤10 rows), and template placeholders. As an instruction-only skill the absence of code is acceptable per the rubric's scoring notes. Falls to 4 rather than 5 because key details are missing — the enrichment provider/method is unspecified, the scoring rubric is only 'ICP + TAL + seniority', and the referenced 'templates/' files do not exist in the bundle.

4 / 5

Workflow Clarity

A clearly sequenced 7-step flow with explicit validation checkpoints and feedback loops for batch operations: a 10-row pilot enrich with 'Full run only after pilot lookback', campaigns left 'paused' until human approval, 'Never auto-send from this skill', and a terminal output checklist. Matches the score-5 anchor ('explicit validation steps; feedback loops for error recovery; checklists'), satisfying the rubric's requirement for validation in batch/outbound operations.

5 / 5

Progressive Disclosure

The body references 'templates/voice.md', 'templates/invite-email.md', 'templates/linkedin-dm.md', 'templates/social-announcement.md', and 'templates/speaker-bio.md', but no templates/ directory exists in the bundle — four of those paths are dead. Meanwhile the one bundle file that does exist, 'references/checklist.md', is never referenced from SKILL.md, so its timeline content is undiscoverable. This fits the score-3 anchor ('some structure but could be better organized; references present but not clearly signaled'); not 4 because dead references and an orphaned bundle file are more than minor organization gaps.

3 / 5

Total

17

/

20

Passed

Description

92%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: explicitly states both what it does and when to use it, with concrete enumerated actions and a well-scoped niche. The only weakness is trigger phrasing that leans on jargon (GTM, LI) and misses a few natural synonyms. The 'DRAFT.' prefix and 'Not installed by deepline skills' line are administrative noise but do not obscure the trigger.

DimensionReasoningScore

Specificity

The description lists five concrete actions — 'pull/export guests, enrich and score, draft invites and social, stage email+LI sequences paused for approval, and wire registration sync' — giving comprehensive coverage of the campaign lifecycle. This matches the score-5 anchor ('multiple specific concrete actions; comprehensive coverage') rather than score 4, which would require minor gaps in coverage.

5 / 5

Completeness

Both 'what' and 'when' are explicit: 'Use when running a Luma-centered GTM event campaign' is a concrete trigger phrase, followed by the enumerated capabilities. Matches the score-5 anchor exactly; not 4 because the 'when' clause is fully explicit rather than merely present.

5 / 5

Trigger Term Quality

Good natural keywords: 'Luma', 'event campaign', 'guests', 'invites', 'registration sync'. However 'GTM' and 'LI' are insider shorthand, and common variations like 'webinar', 'event marketing', or spelled-out 'LinkedIn' are missing. Fits the score-4 anchor ('good keyword coverage; a few natural terms missing'), not 5, since synonym coverage is not comprehensive.

4 / 5

Distinctiveness Conflict Risk

'Luma-centered GTM event campaign' carves out a clear niche with distinct triggers; minimal risk of firing for unrelated skills. The 'Not installed by deepline skills' note further scopes it. Matches the score-5 anchor ('clear niche with distinct triggers; minimal conflict risk').

5 / 5

Total

19

/

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
getaero-io/gtm-eng-skills
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.