CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

event-research-follow-up

Research business events, organize photo leads and attendee rosters, qualify companies with evidence, and prepare or execute explicitly approved event follow-up with verified delivery records.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./event-research-follow-up/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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-sequenced, safety-conscious instruction skill with good reference routing and real validation checkpoints, held back by repeated authorization caveats and a lack of concrete artifacts (no example table formats, no code for the screening arithmetic it mandates). The two 3-scoring dimensions are fixable without restructuring: dedupe the caveats and add one worked example each for the outputs and the code-based screening steps.

Suggestions

State the no-sending/no-standing-authority rule once in 'Authority and privacy' and refer back to it, removing the repetitions in sections 1, 2, 4, 5, and 6.

Add a small example of the required 'event priority table' and 'distinct-company shortlist' (column headers plus one sample row) so the section-5 output is unambiguous.

Provide a minimal code sketch or field schema for the mandated in-code screening (date windows, dedup keys, cost ledger) and the learning.jsonl entry format.

DimensionReasoningScore

Conciseness

Mostly efficient domain-specific policy with no generic concept explanations, but it could be tightened: the no-sending/no-standing-authority caveat is repeated across sections 1, 2, 4, 5, and 6 ("Research approval alone does not authorize these actions", "never grants sending authority", "No external messages, CRM writes... follow from screening approval"), and the repository telemetry preamble is boilerplate. Not 4: the repetition exceeds 'minor instances that could be trimmed'; not 2: nothing explains concepts Claude already knows.

3 / 5

Actionability

Some concrete guidance exists ("use `python3 telemetry/version_check.py`", "Set a pass limit...: exact event candidates, maximum pages or roster records, time checkpoint and total approved cost", "Write misses and corrections to local `learning.jsonl`", a defined output list), but key details are missing: "Apply date windows, deduplication, thresholds and cost arithmetic in code" gives no code or schema, and the required "event priority table" and "distinct-company shortlist" have no example format. Not 4: common cases are not covered by copy-paste-ready specifics; not 2: there is substantially more than high-level hints.

3 / 5

Workflow Clarity

A clear numbered sequence (select workflow → screen → company/offer review → evaluator/spend → conversation plan → lifecycle) with most checkpoints present: cache-reuse conditions ("Reuse a result only when its input hash, questions, model, scope and evaluation contract match"), a failure fallback ("If access fails, use one ordinary available read-only fallback... then record the limitation"), and a verification list ("Verify counts against page/export totals, identities against sources, budget against receipts"). Not 5: checkpoints are embedded in prose rather than explicit validate→fix→retry loops, and the batch-screening validation is described but not operationalized.

4 / 5

Progressive Disclosure

Five well-signaled, one-level-deep references (verified: all five files exist in references/ and none reference further files), each routed by task ("For photo priorities... read references/event-leads.md"; "Before scheduling or sending... read references/outreach-execution.md"). Not 5: the body itself inlines substantial policy detail (evaluator contracts, spend ledgers, lifecycle gates) that could live in a reference, so the split is good but not clean.

4 / 5

Total

14

/

20

Passed

Description

71%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 specific, lifecycle-complete description with good domain keywords, weakened only by the complete absence of any 'when to use this' trigger guidance. Adding a "Use when..." clause with event-synonyms (conference, trade show, attendee list) would resolve both remaining gaps at once.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user attended or is researching a business event, conference, or trade show and wants attendee or photo-lead follow-up."

Include common synonyms such as "conference", "trade show", "attendee list", and "networking event" so natural user phrasings match the trigger terms.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions covering the full lifecycle — "Research business events", "organize photo leads and attendee rosters", "qualify companies with evidence", "prepare or execute explicitly approved event follow-up with verified delivery records" — matching the comprehensive-coverage anchor. Not 4: the actions span research, organization, qualification, execution, and delivery records with no coverage gap for the domain.

5 / 5

Completeness

The 'what' is clearly and comprehensively stated, but there is no 'Use when...' clause or any equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline. Not 4: the 'when' is not merely implicit-and-improvable — it is entirely absent.

3 / 5

Trigger Term Quality

Good natural keyword coverage: "business events", "photo leads", "attendee rosters", "event follow-up" — phrases a user with this need would plausibly say. Not 5: common synonyms and variations like "conference", "trade show", "attendee list", or "networking event" are missing, so a few natural terms are absent.

4 / 5

Distinctiveness Conflict Risk

The event-photo-leads/roster/follow-up niche is fairly distinct with domain-specific triggers, though it could minorly overlap with generic lead-generation or outreach skills. Not 5: the closing phrase "event follow-up with verified delivery records" is less uniquely identifying than file-extension-based triggers, and adjacent CRM/outreach skills share some vocabulary.

4 / 5

Total

16

/

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

ericosiu/ai-marketing-skills

Path

event-research-follow-up/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.