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

67%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Academic Writing/conference-abstract-adaptor/SKILL.md

Quality

Content

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with concrete commands, parameters, and a working script, and its file references are correctly structured one level deep. However, it is heavily padded with generic boilerplate that buries the skill-specific content, and its workflow describes an abstract meta-process rather than the concrete abstract-adaptation steps.

Suggestions

Remove the generic boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Output Contract, Failure Handling, User Checkpoints, Quick Validation) and consolidate the duplicated error/fallback guidance into one concise Error Handling section to cut the body roughly in half.

Rewrite the Workflow so its steps reflect the concrete adaptation sequence (load abstract, identify sections, count words/chars against the target conference limit, compress, output) rather than a generic meta-process, keeping the validation checkpoint and fallback inline.

Move the conference format table and parameters into a reference file (or trim to essentials) so SKILL.md reads as a lean overview that signals detail one level deep, consistent with the existing references/audit-reference.md pattern.

Dimension	Reasoning	Score
Conciseness	The ~210-line body is padded with generic boilerplate (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Output Contract, Failure Handling, User Checkpoints, Quick Validation) that restates error-handling philosophy Claude already knows and repeats the same missing-input/fallback guidance across multiple sections, matching the 'verbose; padded with unnecessary context' anchor.	1 / 3
Actionability	Concrete executable commands ('python -m py_compile scripts/main.py', 'python scripts/main.py --abstract my_abstract.txt --conference ASCO'), a complete Parameters table, copy-paste-ready Usage examples, and a real bundled script provide fully executable, specific guidance as required by the score-3 anchor.	3 / 3
Workflow Clarity	The five-step Workflow lists a sequence with an explicit scope-validation step (step 2) and a fallback loop (step 5), but the steps are generic meta-process ('use the packaged script path or the documented reasoning path') rather than a concrete sequence of the actual adaptation task, so checkpoints relative to the real work remain implicit, fitting 'steps listed but validation gaps / checkpoints implicit'.	2 / 3
Progressive Disclosure	References are one level deep and well-signaled (the References section links to the real references/audit-reference.md, and scripts/main.py is referenced throughout), but the overview is bloated with inline boilerplate that should be removed or split out, matching 'content that should be separate is inline' rather than the 'content appropriately split' score-3 anchor.	2 / 3
	Total	8 / 12 Passed

Description

85%

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, third-person, and clearly states both what the skill does and when to use it, with a distinct conference-abstract niche. Its main gap is trigger-term coverage: it omits the concrete conference names and common phrasings (e.g. 'word count', 'reformat') a user would naturally say.

Dimension	Reasoning	Score
Specificity	The phrase 'Adapt scientific abstracts to conference-specific word limits, section rules, and formatting constraints' lists multiple concrete adaptation targets (word limits, section rules, formatting constraints), matching the 'lists multiple specific concrete actions' anchor rather than the score-2 'some actions, not comprehensive' anchor.	3 / 3
Completeness	It explicitly answers both 'what' ('Adapt scientific abstracts to conference-specific word limits, section rules, and formatting constraints') and 'when' ('use when reshaping an existing abstract for submission'), with an explicit 'use when' trigger clause, satisfying the score-3 anchor and avoiding the score-2 cap for missing trigger guidance.	3 / 3
Trigger Term Quality	Natural terms like 'scientific abstracts', 'conference', 'word limits', and 'submission' are present, but common variations a user would actually say (specific conference names like ASCO/ASGCT, 'word count', 'reformat', 'trim to length') are missing, fitting 'some relevant keywords but missing common variations' rather than full coverage.	2 / 3
Distinctiveness Conflict Risk	The niche of conference-specific scientific abstract adaptation with triggers like 'conference-specific word limits' and 'reshaping an existing abstract for submission' is clearly distinct and unlikely to trigger for unrelated skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: aipoch/medical-research-skills
Commit: 7cc5680

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.