CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

article-format-adjustment

Adjust academic paper formatting and convert between DOCX/LaTeX/Markdown when you need to meet a journal or school template requirement.

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/article-format-adjustment/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

48%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 presents a clear pipeline, accurate CLI flags for init_run.py, and strong emphasis on validation, but it is padded with generic boilerplate sections and contains factual drift from the bundle: two broken validation commands, a referenced module that does not exist, a non-executable Python example, and unlisted built-in template assets. Trimming the boilerplate and reconciling commands with the actual scripts would substantially raise quality.

Suggestions

Remove or consolidate the generic boilerplate sections ('When Not to Use', 'Required Inputs', 'Recommended Workflow', 'Output Contract', 'Validation and Safety Rules', 'Deterministic Output Rules', 'Completion Checklist') into a few concrete, skill-specific rules, and drop the duplicated validation-command section.

Fix the validation shortcut to a command that actually runs (e.g., 'python scripts/init_run.py --list-formats'), remove the non-existent 'format_validator.py' module listing, and delete the fabricated 'Expected output format' block.

Make the Python example executable as written: import via the real entry point (e.g., from init_run import FormatAdjusterApp) or correct the import path and call apply_format(text) with its actual single-argument signature, and document the built-in journal configs in assets/formats/ instead of leaving them unmentioned.

DimensionReasoningScore

Conciseness

The ~240-line body contains several padded, low-value sections: 'When Not to Use', 'Required Inputs', 'Recommended Workflow', 'Output Contract', 'Validation and Safety Rules', 'Deterministic Output Rules', and 'Completion Checklist' are generic boilerplate Claude already knows (e.g., 'Do not use this skill when the user asks for fabricated results'), and the same broken validation command is repeated twice ('Validation Shortcut' and 'Quick Validation'). This is noticeably verbose with multiple unnecessary sections, matching anchor 2 rather than 3 because the padding is systematic rather than incidental.

2 / 5

Actionability

The CLI examples are concrete and their flags match init_run.py's actual argparse, but key examples are not executable as written: both validation shortcuts invoke 'python scripts/format_adjuster.py --help' though that script has no argparse/main, the Python example uses 'from scripts.format_adjuster import FormatAdjuster' (no scripts package or __init__.py exists; the modules use flat sibling imports) and calls 'adjuster.apply_format(md, config)' while the real signature is 'apply_format(text)'. Broken primary-adjacent examples plus a referenced-but-missing module ('format_validator.py') go beyond the 'minor gaps' of a 4, but the verified CLI path keeps it above 2.

3 / 5

Workflow Clarity

The 'Processing pipeline' gives a clear 5-step sequence (detect, convert to Markdown, apply rules, validate, convert to target) with an explicit validation step, and 'Failure Handling' plus 'Completion Checklist' supply checkpoints and recovery guidance. It falls short of 5 because the documented checkpoint commands are non-functional (format_adjuster.py has no CLI) and the 'Expected output format' block describes a result file the command never produces, leaving validation more asserted than runnable.

4 / 5

Progressive Disclosure

Sections are well organized and script references are one level deep, but measured against the actual bundle the structure is inconsistent: 'format_validator.py' is cited as a core module yet does not exist, and assets/formats/ with 18 built-in journal config JSONs is never mentioned in SKILL.md. Additionally, the full configuration schema, CLI parameters, and a long Python example are inlined in SKILL.md rather than split into reference files, matching anchor 3.

3 / 5

Total

12

/

20

Passed

Description

70%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 a single concise sentence in third-person voice that covers what the skill does and when to use it, with concrete format names and a clear journal/school trigger. It could be stronger by enumerating more capabilities (citation styles, typography, templates) and additional natural trigger terms such as 'manuscript' or file extensions.

DimensionReasoningScore

Specificity

The description names the domain ('academic paper formatting') and two concrete actions ('Adjust academic paper formatting', 'convert between DOCX/LaTeX/Markdown'), matching the anchor for 1-2 concrete actions without comprehensive coverage. It does not reach 4 because it omits other advertised capabilities such as citation-style switching, typography rules, and journal-template application; it is above 2 because the actions are concrete rather than generic.

3 / 5

Completeness

It explicitly answers 'what' ('Adjust academic paper formatting and convert between DOCX/LaTeX/Markdown') and 'when' ('when you need to meet a journal or school template requirement'), so the Use-when guidance is present. The 'when' clause is a single condition that could be more explicit and specific (e.g., enumerating submission-format conversion or typography-rule triggers), which is exactly the 4 anchor rather than the fully explicit multi-trigger phrasing of a 5; it is above 3 because both what and when are stated.

4 / 5

Trigger Term Quality

Good keyword coverage including 'academic paper', 'journal', 'school template', and the format names 'DOCX/LaTeX/Markdown' that users naturally mention. A few natural terms are missing ('manuscript', 'thesis', 'citation/reference style', explicit file extensions like '.docx' or '.tex'), so it falls short of the comprehensive-synonym coverage of a 5 but is clearly better than the sparse keyword sets of 3.

4 / 5

Distinctiveness Conflict Risk

The niche is mostly distinct: 'academic paper' plus 'journal or school template requirement' targets manuscript submission formatting specifically, limiting conflict with generic document skills. There remains minor overlap risk with closely related document-conversion or general formatting skills, so it fits the 4 anchor rather than the minimal-conflict clear-niche of 5.

4 / 5

Total

15

/

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/Other/article-format-adjustment/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.