CtrlK
BlogDocsLog inGet started
Tessl Logo

events

When the user wants to plan, run, sponsor, speak at, or get pipeline from events — webinars, conferences, trade shows, meetups, dinners, workshops, virtual summits, or user conferences. Also use when the user mentions 'event marketing,' 'field marketing,' 'run a webinar,' 'webinar funnel,' 'show-up rate,' 'should we sponsor,' 'sponsor a conference,' 'trade show booth,' 'booth strategy,' 'event ROI,' 'badge scans,' 'event follow-up,' 'speaking slot,' 'CFP,' 'conference talk,' 'host a dinner,' 'user conference,' or 'virtual summit.' Covers all four roles: hosting, sponsoring/exhibiting, speaking, and attending. For product launch moments, see launch. For the partnership side of joint webinars, see co-marketing. For ongoing community programs, see community-marketing. For podcast appearances, see public-relations. For the email sequences themselves, see emails.

71

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-structured strategy skill: dense with opinionated, non-obvious heuristics, numerically concrete, clearly sequenced across the before/during/after arc, and correctly split into an overview plus four real one-level-deep reference files. It is an instruction-only skill with no code, which the rubric does not penalize; the residual losses come from minor rhetorical padding and the absence of explicit feedback loops.

DimensionReasoningScore

Conciseness

Nearly every line carries a non-obvious heuristic ('A meeting booked two weeks out is worth ten hopeful hallway collisions,' '8–14 seats, no pitch') rather than generic explanation Claude already knows. Minor rhetorical padding remains ('often the best ROI in the building,' 'directional, not a law — but the decay is real and fast') that could be trimmed, so it sits at efficient-with-minor-overexplanation rather than lean.

4 / 5

Actionability

Concrete, specific guidance throughout: numeric parameters (15–30 named targets, 8–14 dinner seats, 24–48 hour follow-up window, 1–3 week pre-booking), a worked outreach micro-script ('15 min at the coffee bar Tuesday'), and decision tables for formats and metric tiers. Falls short of fully executable only because the hands-on mechanics (outreach copy, funnel detail) are deliberately deferred to the reference files and related skills.

4 / 5

Workflow Clarity

Clear sequenced workflow: 'Before Starting' batching of role/outcome/ICP/budget, role selection, portfolio selection, then a Before/During/After arc with a numbered attending playbook. Decision checkpoints exist ('Pick a primary — events that try to do everything measure nothing,' go/no-go cost-per-meeting math), but there are no explicit validate-and-correct feedback loops — acceptable here since no destructive or batch operations are involved.

4 / 5

Progressive Disclosure

The body is a genuine overview with well-signaled, one-level-deep references — all four linked files (webinar-funnel.md, sponsorship-roi.md, speaking.md, event-portfolio-strategy.md) exist in references/ and are linked inline at the point of need. Cross-links between reference files are lateral, not nested chains, so navigation stays one level deep.

5 / 5

Total

17

/

20

Passed

Description

95%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: third-person voice, explicit what-and-when, exhaustive natural trigger phrases, and proactive disambiguation against five adjacent skills. The only soft spot is that the capability verbs are moderately high-level rather than fully concrete, which costs a point on specificity.

Suggestions

State one or two concrete deliverable actions (e.g., 'build the target list, design the follow-up sequence, model cost per qualified meeting') alongside the role verbs to sharpen the 'what.'

Trim a couple of the less distinct trigger phrases to reduce length without losing coverage.

DimensionReasoningScore

Specificity

Concrete verbs — 'plan, run, sponsor, speak at, or get pipeline from events' — plus explicit coverage of 'all four roles: hosting, sponsoring/exhibiting, speaking, and attending' and a full format enumeration. Not a 5 because the actions themselves are moderately high-level (no mechanical specifics of what the skill actually does), but coverage is broad with only minor gaps.

4 / 5

Completeness

Explicitly answers 'what' (plan/run/sponsor/speak/attend across the four roles and nine event formats) and 'when' twice over — 'When the user wants to...' and 'Also use when the user mentions [18 trigger phrases]' — with concrete trigger phrasing throughout.

5 / 5

Trigger Term Quality

Extensive natural user phrasing: 'run a webinar,' 'should we sponsor,' 'trade show booth,' 'event ROI,' 'badge scans,' 'speaking slot,' 'CFP,' 'host a dinner,' 'show-up rate,' plus synonyms ('event marketing,' 'field marketing'). This matches the comprehensive-synonyms anchor.

5 / 5

Distinctiveness Conflict Risk

Clear niche (event marketing) with explicit boundary disambiguation: 'For product launch moments, see launch... For the partnership side of joint webinars, see co-marketing... For ongoing community programs, see community-marketing... For podcast appearances, see public-relations. For the email sequences themselves, see emails.' 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
coreyhaines31/marketingskills
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.