CtrlK
BlogDocsLog inGet started
Tessl Logo

newsletter-generation

Use this skill when the user requests to generate, create, write, or draft a newsletter, email digest, weekly roundup, industry briefing, or curated content summary. Supports topic-based research, content curation from multiple sources, and professional formatting for email or web distribution. Trigger on requests like "create a newsletter about X", "write a weekly digest", "generate a tech roundup", or "curate news about Y".

64

Quality

77%

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/public/newsletter-generation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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, genuinely actionable workflow guide with strong sequencing and a validation checklist, but it is a single ~340-line monolith with real redundancy. Splitting templates and examples into reference files and trimming duplicated general-writing advice would raise both conciseness and progressive disclosure.

Suggestions

Move the per-format structure templates, the full newsletter output template, and the Adaptation Examples into a references/ file (e.g. references/templates.md) and reference them from the workflow phases, keeping SKILL.md as a lean overview.

Delete the 'Core Capabilities' section and the 'Notes' items that restate the workflow and Quality Checklist (current-date usage, attribution, quality-over-quantity), leaving each point stated once.

Cut or compress the 'Writing Standards' and tone-calibration tables, which restate general writing principles Claude already knows, down to the few newsletter-specific rules (source every claim, link inline, standalone-value summaries).

DimensionReasoningScore

Conciseness

The body is mostly domain-specific and useful (search query templates, per-format structures, checklist), but several sections explain things Claude already knows or restate other sections: the 'Writing Standards' table ('Use headers, bold text, bullet points, and short paragraphs', 'cut filler ruthlessly', 'Write like a knowledgeable friend'), the 'Core Capabilities' list duplicating the workflow and When-to-Use sections, and the Notes section repeating checklist items like the current-date and attribution guidance already stated above. It fits anchor 3 (mostly efficient, some unnecessary explanation) rather than 2 because the bulk is genuinely non-obvious guidance; not 4 because the padded sections are repeated in at least three places.

3 / 5

Actionability

Concrete, near-copy-paste guidance dominates: search query templates ('[topic] news [current month] [current year]'), full structure templates per format, a complete markdown output template, header/footer blocks, a parameter table with defaults, and a save path. It is not 5 because some steps remain high-level and unexecutable — 'Conduct thorough research using web search', 'All links are functional — Verified URLs' states a check without any method to perform it, and the audience-tone table is advisory rather than procedural.

4 / 5

Workflow Clarity

The four-phase workflow (Planning → Research & Curation → Writing → Assembly & Polish) is clearly sequenced with numbered steps, a parameters table, and an explicit 11-item Quality Checklist as a validation checkpoint before finalizing. Not 5 because there are no error-recovery/feedback loops (e.g., what to do when a checklist item fails, or when research yields insufficient sources); not 3 because the checklist is an explicit, well-placed checkpoint and the sequence has no gaps.

4 / 5

Progressive Disclosure

There are no bundle files at all (no references/, scripts/, or assets/ exist) and ~340 lines live inline in SKILL.md. Section headers are clear and navigation within the file is easy, but bulk content that clearly belongs in separate reference files — the four per-format structure templates, the ~60-line output template, the Adaptation Examples, and the audience tone-calibration table — is inlined. This matches anchor 3 (good structure, but content that should be separate is inline); not 4 because there is no file-level split at all despite the length.

3 / 5

Total

14

/

20

Passed

Description

91%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 that explicitly states both capabilities and trigger conditions with natural user phrasings and good synonym coverage. Its only weaknesses are a slightly generic 'professional formatting' capability claim and minor overlap risk with research/summarization skills.

DimensionReasoningScore

Specificity

The description lists several concrete capabilities — 'topic-based research, content curation from multiple sources, and professional formatting for email or web distribution' — plus named output types (digest, roundup, briefing, curated summary). It falls just short of the 5 anchor because 'professional formatting' is somewhat generic and the coverage of actions is less comprehensive than the multi-action exemplar.

4 / 5

Completeness

It explicitly answers both questions: 'what' via 'Supports topic-based research, content curation from multiple sources, and professional formatting for email or web distribution' and 'when' via 'Use this skill when the user requests to generate...' plus 'Trigger on requests like...'. Both are concrete and explicit, matching the top anchor.

5 / 5

Trigger Term Quality

It comprehensively covers natural terms and their synonyms — 'newsletter, email digest, weekly roundup, industry briefing, curated content summary' — and adds concrete trigger phrasings users would actually say: 'create a newsletter about X', 'write a weekly digest', 'generate a tech roundup', 'curate news about Y'. This matches the comprehensive-synonyms anchor; nothing common is missing.

5 / 5

Distinctiveness Conflict Risk

The newsletter niche is clear with distinct trigger phrases, but 'curated content summary' and the research/curation capability create minor overlap risk with general research or summarization skills (the body itself notes pairing with deep-research). Mostly distinct with minor overlap, matching anchor 4 rather than 5.

4 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 7 missing

Warning

Total

15

/

16

Passed

Repository
bytedance/deer-flow
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.