CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

conference-abstract-adaptor

Adapt scientific abstracts to conference-specific word limits, section rules, and formatting constraints; use when reshaping an existing abstract for submission.

Quality

68%

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-abstract-adaptor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 body has a genuinely useful core — executable commands, parameter tables, and a concrete conference-constraints table — but it is buried in ~150 lines of generic policy boilerplate that adds no skill-specific value. The operational workflow also never defines the manual reasoning path it defers to, and lacks output verification steps.

Suggestions

Remove the generic boilerplate sections (Risk Assessment, Security Checklist, Lifecycle Status, Evaluation Criteria, Response Template, Output Contract, User Checkpoints, Required Inputs, Failure Handling, Quick Validation) — they restate default Claude behavior and account for the majority of the file's length.

Replace the 5-step process-policy Workflow with a concrete adaptation sequence that includes a validation checkpoint, e.g.: load abstract → check word count and required sections against the Supported Conferences table → trim/reshape → re-verify word count before delivering.

Actually document the 'documented reasoning path' (the manual fallback for adapting an abstract without scripts/main.py), or move it into references/audit-reference.md, since the body defers to it repeatedly but never defines it.

DimensionReasoningScore

Conciseness

Roughly two-thirds of the ~215-line body is generic template boilerplate — 'Risk Assessment', 'Security Checklist', 'Lifecycle Status' (with 'Next Review Date: 2026-03-06'), 'Evaluation Criteria', 'Response Template', 'Output Contract', 'User Checkpoints', 'Required Inputs', 'Failure Handling' — that restates default Claude behavior rather than skill-specific knowledge. Only the Parameters, Usage, and Supported Conferences sections carry unique information, which keeps it above the pure-padding of anchor 1.

2 / 5

Actionability

The Usage section gives copy-paste-ready commands ('python scripts/main.py --abstract my_abstract.txt --conference ASCO') and the Supported Conferences table lists concrete limits and formats, covering common cases. However, the 'documented reasoning path' referenced repeatedly ('Use the packaged script path or the documented reasoning path') is never actually documented anywhere in the skill.

4 / 5

Workflow Clarity

The 5-step Workflow is generic process policy ('Confirm the user objective...', 'Validate that the request matches the documented scope...') rather than a concrete adaptation sequence, and it lacks an output verification checkpoint such as re-checking word count against the conference limit after trimming. Only a pre-flight 'python -m py_compile scripts/main.py' Quick Check is present, so checkpoints are missing or implicit.

3 / 5

Progressive Disclosure

The single reference (references/audit-reference.md) is clearly signaled, exists on disk, and is one level deep, and scripts/main.py is real; but the ~25 inline boilerplate sections (risk/security/lifecycle/contract templates) are content that belongs in a reference file or nowhere at all, leaving the overview itself hard to navigate — matching anchor 3's 'content that should be separate is inline'.

3 / 5

Total

12

/

20

Passed

Description

73%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 solid, third-person description that clearly states what the skill does and when to use it, with an appropriately narrow niche. Its main weaknesses are a single-verb capability statement and a 'when' clause covering only one trigger scenario.

DimensionReasoningScore

Specificity

'Adapt scientific abstracts to conference-specific word limits, section rules, and formatting constraints' names the domain and one concrete action with its constraint dimensions, but unlike the anchor-4 example's multiple distinct verbs ('extracts, fills, converts'), it offers a single action.

3 / 5

Completeness

Both parts are explicit: 'what' ('Adapt scientific abstracts to conference-specific word limits, section rules, and formatting constraints') and 'when' ('use when reshaping an existing abstract for submission'). The 'when' covers a single scenario and lacks the multi-trigger concrete phrasing of anchor 5, so it stops short of 5.

4 / 5

Trigger Term Quality

Natural terms like 'scientific abstracts', 'conference-specific word limits', 'submission', and 'reshaping' cover the domain well, but common variations users might say — specific conference names (ASCO, ASGCT), 'word count', 'call for abstracts' — are absent.

4 / 5

Distinctiveness Conflict Risk

Conference-specific abstract adaptation with word limits, section rules, and formatting constraints is a clear niche with distinct triggers; minimal conflict risk with generic writing or document skills.

5 / 5

Total

16

/

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-abstract-adaptor/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.