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.

59

Quality

67%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/ads/capabilities/newsletter-sponsorship-finder/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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.

The content is actionable and well-structured, with concrete search templates, a scoring rubric, and a ready-to-use output format. Its chief gap is the absence of validation checkpoints in the batch enrichment workflow, which the rubric caps at 3 for workflow clarity.

Suggestions

Add an explicit validation step after Phase 3, e.g. verify each enriched newsletter has at minimum a name, URL, and audience estimate before scoring, and re-fetch or drop incomplete entries.

Include one fully worked example with literal values (e.g. a sample 'DevOps' search run) so the placeholders are unambiguous.

Add a brief output-verification note in Phase 5 confirming the markdown file was written and contains at least one Tier 1/2/3 entry.

DimensionReasoningScore

Conciseness

The body is efficient and avoids explaining concepts Claude already knows; it stays task-focused with templates and rubrics, with only minor trimmable padding in the Tips section keeping it just below a 5.

4 / 5

Actionability

Provides concrete search-query templates, named directories (Swapstack/Paved/Substack), an explicit point-based scoring rubric, a helper-script invocation, and a full output template; minor gaps remain because the queries use [industry] placeholders rather than worked literal examples.

4 / 5

Workflow Clarity

The five phases are clearly sequenced, but there are no validation/verification checkpoints for the batch enrichment of many newsletters; the rubric caps workflow clarity at 3 for batch operations lacking validation.

3 / 5

Progressive Disclosure

Single well-organized SKILL.md with clear section headers, the helper script correctly separated under scripts/, and no nested references; the inlined output template is reasonable for this skill size, leaving only minor organization gaps.

4 / 5

Total

15

/

20

Passed

Description

66%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.

The description is specific and well-scoped to a distinct niche, clearly communicating what the skill returns. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness and slightly weakens trigger discoverability.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user wants to find newsletters to sponsor or advertise in for a target audience.'

Add natural trigger synonyms such as 'newsletter advertising', 'sponsor a newsletter', and 'email newsletter' alongside 'sponsorship opportunities'.

Consider stating the discovery actions more concretely to push specificity toward 5 (e.g. 'searches the web, queries Swapstack/Paved/Substack directories, and researches competitor sponsorships').

DimensionReasoningScore

Specificity

Names the domain plus several concrete actions ('Discovers newsletters through web search, newsletter directories, and industry research') and the returned fields (name, author, audience, topic, rates, contact); not quite a 5 because the discovery methods are described at a high level rather than as distinct comprehensive actions.

4 / 5

Completeness

Clearly states what the skill does, but lacks any explicit 'Use when...' trigger clause; per the rubric a missing explicit trigger guidance caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms a user would say ('newsletters', 'sponsorship opportunities', 'target audience/industry'), but misses common variations such as 'newsletter advertising', 'sponsor a newsletter', or 'email newsletter'.

4 / 5

Distinctiveness Conflict Risk

The newsletter-sponsorship niche is clear and largely distinct, with only minor overlap risk against generic 'find newsletters' or research skills.

4 / 5

Total

15

/

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.

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.