CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

conference-poster-pitch

Use conference poster pitch for academic writing workflows that need structured execution, explicit assumptions, and clear output boundaries.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Academic Writing/conference-poster-pitch/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.

The skill is genuinely executable — real script, correct parameters table, concrete run commands, and a sensible validated workflow with a fallback. Its main weakness is heavy template padding: recycled description text, circular section cross-references, duplicated check commands, and generic checklists that spend tokens without adding skill-specific value.

Suggestions

Cut the template filler: the verbatim-recycled description sentence, the "See `## X` above" cross-reference lines, the duplicated Quick Check / Audit-Ready Commands section, and the generic Security Checklist, Evaluation Criteria, and Lifecycle Status blocks — fold any skill-specific parts into references/audit-reference.md.

Replace the vague "Structured elevator pitch format" output description with the actual pitch structure the script should produce (e.g., hook → key finding → approach → takeaway per duration).

Remove or contextualize the time-sensitive "Next Review Date: 2026-03-06" (already stale) since it penalizes the body without adding actionable guidance.

DimensionReasoningScore

Conciseness

The body is noticeably padded: it recycles the description verbatim into a broken sentence ("Use this skill when the task needs Use conference poster pitch for…"), contains circular filler ("See `## Prerequisites` above", "See `## Usage` above", "See `## Workflow` above"), duplicates the same two commands in both "Quick Check" and "Audit-Ready Commands", and carries generic template blocks (Security Checklist, Evaluation Criteria, Lifecycle Status with a time-sensitive "Next Review Date: 2026-03-06"). It is anchor 2 (several unnecessary padded sections) rather than 1 because it never explains basic concepts Claude already knows — the waste is boilerplate, not tutoring.

2 / 5

Actionability

Commands are concrete and executable: `python -m py_compile scripts/main.py`, `python scripts/main.py --help`, and three realistic invocations (e.g., `--poster-title "CRISPR Therapy for Sickle Cell Disease" --duration 60`) matching a Parameters table that mirrors the actual script. Minor gap: the deliverable itself is described only as "Structured elevator pitch format" with no stated structure, so it is anchor 4 (mostly executable, minor gaps) rather than 5.

4 / 5

Workflow Clarity

The five-step Workflow has a real pre-flight checkpoint (the py_compile "Quick Check" run before deeper execution), a defined fallback ("If `scripts/main.py` fails, report the failure point, summarize what still can be completed safely"), and scope-stop rules in Input Validation. It is not 5 because the workflow steps themselves are abstract (e.g., "Return a structured result that separates assumptions…") while the concrete commands live in a separate section; not a destructive/batch operation, so the 3-cap does not apply.

4 / 5

Progressive Disclosure

The bundle is used appropriately: one real one-level-deep reference clearly linked with its purpose ([references/audit-reference.md] — "Supported scope, audit commands, and fallback boundaries") and a packaged script at `scripts/main.py`, both verified to exist. Minor organization gaps — inlined template blocks (Security Checklist, Evaluation Criteria) that belong in the reference, and circular "See X above" cross-references — keep it at anchor 4 rather than 5.

4 / 5

Total

14

/

20

Passed

Description

45%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 names its niche but never states a concrete action, recycling the skill name instead of saying what it produces (elevator pitches for poster sessions). Trigger language leans on process boilerplate rather than natural user phrases, weakening both completeness and distinctiveness.

Suggestions

State the concrete action up front, e.g., "Generate 30-second, 60-second, and 3-minute elevator pitch scripts for academic conference poster sessions."

Add natural trigger terms users would actually say, such as "Use when preparing for a poster session, practicing an elevator pitch, or presenting research at a conference."

Drop the process-meta language ("structured execution, explicit assumptions, and clear output boundaries") from the description and keep it in the body, so the trigger surface stays distinctive from other academic-writing skills.

DimensionReasoningScore

Specificity

The description names the domain ("conference poster pitch", "academic writing workflows") but the operative language is abstract properties — "structured execution, explicit assumptions, and clear output boundaries" — rather than concrete actions; it never states what the skill actually does (e.g., "generate elevator pitches"). It matches anchor 2 (domain named, actions minimal/generic) rather than 3, which requires 1-2 concrete actions.

2 / 5

Completeness

The "what" is circular — "Use conference poster pitch" reuses the skill name instead of describing the action — and the "when" ("workflows that need structured execution…") is generic process framing rather than concrete trigger phrases. A 'Use…for' clause is present so it is not capped below 3, but it is clearly weaker than anchor 4's explicit what-plus-when pairing.

3 / 5

Trigger Term Quality

"conference poster pitch" and "academic writing" are terms a user might naturally say, but common variations ("elevator pitch", "poster session", "presenting my poster") are missing, and the trigger is diluted with process jargon ("structured execution") no user would say. This sits at anchor 3 (some relevant keywords, missing variations) and not 4, which requires good natural-term coverage.

3 / 5

Distinctiveness Conflict Risk

"conference poster pitch" is a fairly niche phrase, but it is paired with the broad trigger "academic writing workflows" that would overlap many other academic-writing skills in the same package. It is somewhat specific but could still overlap with similar skills (anchor 3), not 4, which needs only minor overlap risk.

3 / 5

Total

11

/

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/Academic Writing/conference-poster-pitch/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.