CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

conference-tweet-generator

Generates academic conference tweets and summaries by filtering abstracts, translating content, and creating engaging titles. Use when you need to process conference abstracts into social media content.

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 ./scientific-skills/Other/conference-tweet-generator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%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 core Workflow section is a reasonably concrete 5-step procedure, but it is buried in ~70 lines of generic boilerplate sections that could apply to any skill, with contradictory validation instructions and no example of the expected output format. Cutting the boilerplate, resolving the validation contradictions, and adding one example tweet/summary would substantially improve it.

Suggestions

Delete the generic template sections (When to Use, Key Features, Dependencies, Required Inputs, Output Contract, Validation and Safety Rules, Failure Handling, Deterministic Output Rules, Completion Checklist) and keep only the task-specific Workflow, Requirements, and When Not to Use content.

Resolve the contradiction between 'Quick Validation' ('No local script validation step is required') and 'Validation Shortcut' (run scripts/validate_skill.py --help), and either make the script perform meaningful validation or remove it and the sections referencing it.

Add a concrete example of the expected output (one structured abstract summary and one tweet title in the 'Year Conference | Content' format) so 'Format the output as a structured summary' is unambiguous.

DimensionReasoningScore

Conciseness

Roughly half the body is generic template boilerplate ('Use this skill when the request matches its documented task boundary', 'Keep output field names stable...', 'Confirm all required inputs were present and valid') that applies to any skill and adds no domain knowledge, matching the 'noticeably verbose; several padded sections' anchor. Not 1 because it never explains domain concepts Claude already knows.

2 / 5

Actionability

The Workflow gives concrete steps with a named tool ('tavily_search'), a real reference file ('references/drug_dictionary.md'), and a title format, but key details are missing: 'Format the output as a structured summary' has no example format, and the packaged script is a stub unrelated to the task. Fits the 'some concrete guidance but incomplete' anchor; not 4 because the gaps are more than minor.

3 / 5

Workflow Clarity

The 5-step Workflow is clearly sequenced, but it contains no validation checkpoints, and the validation guidance is contradictory — 'Quick Validation' says 'No local script validation step is required' while 'Validation Shortcut' instructs running scripts/validate_skill.py --help. Fits the 'steps listed but validation gaps' anchor; not 4 due to these contradictions.

3 / 5

Progressive Disclosure

The single reference (references/drug_dictionary.md, verified to exist) is clearly signaled and one level deep, but the body carries substantial generic inline content with no navigational value and contains a mis-pointed cross-reference ('See ## Workflow above' in Implementation Details points to a section that appears later). Fits the 'some structure but could be better organized' anchor; not 4 because organization is impaired.

3 / 5

Total

11

/

20

Passed

Description

78%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 a solid two-sentence what+when statement with several concrete actions and an explicit 'Use when' clause. Its main limitation is trigger richness: a few natural synonyms (Twitter/X posts, conference coverage) would strengthen it.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'filtering abstracts, translating content, and creating engaging titles' — matching the 'several specific actions with minor gaps' anchor. Not 5 because parts of the pipeline (background search, output format) are absent; not 3 because coverage goes beyond 1-2 actions.

4 / 5

Completeness

Both 'what' (generates tweets/summaries by filtering, translating, titling) and an explicit 'when' ('Use when you need to process conference abstracts into social media content') are present. Not 5 because the when-clause is a single formulation without the richer concrete trigger phrases of the 5-anchor example.

4 / 5

Trigger Term Quality

Natural terms users would say are present: 'conference', 'abstracts', 'tweets', 'social media', 'summaries'. A few natural variations are missing (e.g., 'Twitter/X posts', 'conference coverage'), fitting the 'good coverage, a few natural terms missing' anchor rather than the comprehensive 5-anchor.

4 / 5

Distinctiveness Conflict Risk

The niche is clear — academic conference abstracts processed into social media content — with distinct triggers and minimal overlap risk with other skills, matching the 5-anchor.

5 / 5

Total

17

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Other/conference-tweet-generator/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.