CtrlK
BlogDocsLog inGet started
Tessl Logo

text-format-organizer

A local text formatting organizer for biomedical/academic writing; use it when you need to clean whitespace/line endings while preserving Markdown structures or when normalizing .docx/.md/.txt before submission or proofreading.

57

Quality

66%

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/Other/text-format-organizer/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 technical core (features, examples, CLI table, formatting rules) is concrete and actionable, but it is buried under substantial generic template boilerplate and duplicated validation sections, and the referenced script files are missing from the bundle. Workflow validation remains implicit rather than command-level.

Suggestions

Remove the generic boilerplate sections (When Not to Use, Required Inputs, Recommended Workflow, Output Contract, Validation and Safety Rules, Failure Handling, Input Validation, Deterministic Output Rules, Completion Checklist) or replace them with text-formatting-specific guidance; merge the duplicated 'Validation Shortcut' and 'Quick Validation' sections.

Provide the referenced bundle files (scripts/init_run.py, scripts/text_formatter.py) so the documented commands and the `from scripts.text_formatter import ...` example are actually executable, or reword references to match what is bundled.

Add a concrete validation checkpoint to the formatting workflow (e.g. run with --preview, diff against input, then write output) as an explicit validate-fix-retry loop rather than generic 'run a final validation pass' language.

DimensionReasoningScore

Conciseness

Roughly ten generic boilerplate sections ('When Not to Use', 'Required Inputs', 'Recommended Workflow', 'Output Contract', 'Validation and Safety Rules', 'Failure Handling', 'Input Validation', 'Quick Validation', 'Deterministic Output Rules', 'Completion Checklist') are template filler unrelated to text formatting, e.g. 'Do not fabricate measurements, references, findings, or conclusions'.

2 / 5

Actionability

Provides concrete executable code (TextFormatter/FormatOptions programmatic example), specific CLI commands with flags, and a parameter table, but the referenced scripts (scripts/init_run.py, scripts/text_formatter) are not present in the bundle so commands cannot actually run as-is.

4 / 5

Workflow Clarity

A sequence and a preview safety flag exist, but validation checkpoints are generic boilerplate ('Run a final validation pass') rather than concrete commands; given this rewrites/batch-processes files, the missing explicit validate-fix-retry loop caps the score at 3.

3 / 5

Progressive Disclosure

Sections are well-headed, but all content is inline with no reference files, the referenced scripts/ bundle is absent (broken references), and the 'Validation Shortcut' and 'Quick Validation' sections duplicate the same --help command.

3 / 5

Total

12

/

20

Passed

Description

83%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 strong: it explicitly covers both capability and trigger conditions with concrete file extensions and natural phrases. Minor gaps in action specificity and a slight overlap with generic formatting skills keep two dimensions at 4 rather than 5.

DimensionReasoningScore

Specificity

Lists several concrete actions ('clean whitespace/line endings', 'preserving Markdown structures', 'normalizing .docx/.md/.txt') but omits specifics like trailing-space stripping and tab/space conversion, so it falls just short of comprehensive.

4 / 5

Completeness

Explicitly states both what it is ('A local text formatting organizer for biomedical/academic writing') and when to use it ('use it when you need to clean whitespace/line endings ... before submission or proofreading') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural keywords including file extensions ('.docx/.md/.txt'), 'whitespace', 'line endings', 'Markdown', 'submission', and 'proofreading', though a few common synonyms a user might say are not exhaustively covered.

4 / 5

Distinctiveness Conflict Risk

The biomedical/academic submission niche gives it a clear identity, but core actions like whitespace cleaning and .md normalization overlap with general formatting skills, leaving minor conflict risk.

4 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 7 missing

Warning

Total

14

/

16

Passed

Repository
aipoch/medical-research-skills
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.