abstract-trimmer

Precision editing tool that reduces abstract word count through intelligent compression techniques, maintaining scientific rigor while meeting strict journal and conference requirements.

Quality

30%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./scientific-skills/Academic Writing/abstract-trimmer/SKILL.md

Quality

Discovery

32%

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 identifies a clear niche (academic abstract compression) but suffers from missing explicit trigger guidance and lacks concrete action verbs. The language is somewhat vague ('intelligent compression techniques') rather than specific about what operations are performed.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when user needs to shorten an abstract, reduce word count for submission, or meet journal/conference length requirements'

Replace vague phrases like 'intelligent compression techniques' with specific actions such as 'removes redundant phrases, consolidates sentences, eliminates filler words'

Include natural user terms like 'too long', 'word limit', 'character limit', 'shorten', 'trim', 'cut down'

Dimension	Reasoning	Score
Specificity	Names the domain (abstract editing) and general action (reduces word count, compression), but lacks concrete specific actions like 'removes redundant phrases', 'shortens sentences', or 'eliminates filler words'.	2 / 3
Completeness	Describes what it does (reduces abstract word count) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Contains some relevant terms ('abstract', 'word count', 'journal', 'conference') but misses common user phrases like 'shorten my abstract', 'too long', 'word limit', 'character count', or 'trim'.	2 / 3
Distinctiveness Conflict Risk	The focus on 'abstract' and 'journal/conference requirements' provides some distinctiveness, but 'compression techniques' and 'editing tool' could overlap with general writing or editing skills.	2 / 3
	Total	7 / 12 Passed

Implementation

27%

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

This skill suffers from severe verbosity and poor organization, repeating the same description multiple times and including extensive boilerplate that doesn't help Claude execute the task. The actionable content (CLI commands, parameter tables, trimming strategies) is buried among redundant sections and self-referential links to non-existent content. The core value proposition - how to intelligently compress abstracts - is delegated entirely to an external script without explaining the compression logic.

Suggestions

Remove all redundant content: the description appears 4+ times, and sections like 'See ## Features above' reference content that appears later - consolidate into a single, lean structure

Cut boilerplate sections (Security Checklist, Risk Assessment, Lifecycle Status, full Response Template) that don't help Claude execute the trimming task

Add explicit validation step after trimming: 'Verify trimmed abstract still contains: all numerical results, p-values, confidence intervals, and core findings'

Show the actual compression techniques inline rather than just delegating to scripts/main.py - Claude needs to understand HOW to trim, not just how to call a script

Dimension	Reasoning	Score
Conciseness	Extremely verbose with massive redundancy - the description is repeated multiple times, sections reference other sections that don't exist ('See ## Features above'), and includes extensive boilerplate (security checklists, risk assessments, lifecycle status) that adds little value for Claude's execution.	1 / 3
Actionability	Provides concrete CLI commands and parameter tables which are useful, but the actual trimming logic is delegated to an external script without showing how compression works. The audit-ready commands are executable, but the core skill (how to actually trim abstracts) is a black box.	2 / 3
Workflow Clarity	Multiple workflow sections exist but are redundant and scattered. The 'Example run plan' and 'Workflow' sections provide steps, but there's no explicit validation checkpoint for verifying the trimmed abstract maintains scientific accuracy before finalizing - critical for a tool that modifies research content.	2 / 3
Progressive Disclosure	Monolithic document with poor organization - references non-existent sections ('See ## Features above' when Features comes later), duplicates content across sections, and buries the actual useful information (strategies, parameters) among boilerplate. The references/ folder is mentioned but content structure is chaotic.	1 / 3
	Total	6 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: aipoch/medical-research-skills
Commit: 4a48721

Reviewed: about 15 hours 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.