CtrlK
BlogDocsLog inGet started
Tessl Logo

newsletter-sponsorship-finder

Find newsletters relevant to a target audience/industry for sponsorship opportunities. Discovers newsletters through web search, newsletter directories, and industry research. Returns newsletter name, author, estimated audience, topic focus, sponsorship rates (if available), and contact info.

70

Quality

85%

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

87%

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

The body is a lean, highly actionable workflow with a clear phased sequence and a well-placed one-level reference to a verified helper script. Its main gap is the absence of validation/verification checkpoints for the batch newsletter-enrichment work, which caps workflow clarity.

Suggestions

Add an explicit verification step between discovery and ranking, e.g. confirm each newsletter's signup URL resolves and that sponsorship contact/rate info is current before scoring.

Include a short error-recovery loop for the helper script (handle the 403/blocked case noted in search_newsletters.py by falling back to WebSearch) inside the workflow rather than only in the script.

De-duplicate the input list (the Inputs section and Phase 1 repeat the same fields) and show the helper script command once to tighten the body further.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what newsletters or sponsorship are, and every section (phases, queries, scoring rubric, output template) earns its place; only minor redundancy (Inputs vs Phase 1, the helper command shown twice) keeps it from being perfectly tight.

3 / 3

Actionability

Provides concrete search queries, a real executable helper script (verified at scripts/search_newsletters.py with exact invocation), a point-valued scoring rubric, and a copy-paste-ready output markdown template — all directly executable guidance.

3 / 3

Workflow Clarity

Five phases are clearly sequenced, but this is a batch operation over many newsletters with no explicit validation or verification checkpoint and no error-recovery feedback loop, which per the rubric caps workflow clarity at 2.

2 / 3

Progressive Disclosure

Well-organized sections with one clearly-signaled, one-level-deep reference to the helper script (no nested reference chains) and easy navigation; the inline scoring rubric and output template are appropriately kept in the main file for single-pass execution.

3 / 3

Total

11

/

12

Passed

Description

82%

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

The description is specific, actionable, and well-differentiated with natural trigger terms, but it omits any explicit 'Use when...' guidance for when Claude should invoke the skill. Adding a trigger clause would raise completeness to full marks.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user wants to find newsletters to sponsor for a specific target audience or industry.'

Include common natural variations users might say, such as 'newsletter advertising', 'newsletter ads', or 'email newsletter sponsorship', to broaden trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Find newsletters', 'Discovers newsletters through web search, newsletter directories, and industry research', and a specific enumeration of returned fields (name, author, estimated audience, topic focus, sponsorship rates, contact info), matching the anchor for multiple specific concrete actions.

3 / 3

Completeness

Clearly answers 'what' the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance for when Claude should use it, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Uses natural terms a user would actually say — 'newsletters', 'sponsorship opportunities', 'target audience', 'industry', 'audience' — giving good coverage rather than technical jargon or generic phrasing.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (newsletter sponsorship discovery for a target audience/industry) with distinct triggers, making it unlikely to fire for the wrong skill.

3 / 3

Total

11

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
gooseworks-ai/goose-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.