achemso-latex-manuscript

Write ACS-style manuscript sections against the local achemso LaTeX template, using deterministic template edits and preserving BibTeX structure.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./writing_skills/achemso-latex-manuscript/SKILL.md

Quality

Content

68%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.

A lean, well-structured instruction-only skill that correctly defers bulk content to bundled template assets, but it lacks any validation or feedback loop in its editing workflow and omits the concrete edit examples (a SEARCH/REPLACE sample, fragment naming) that would make it fully executable.

Suggestions

Add a validation checkpoint to the workflow, e.g. 'After edits, compile-check the fragment with bash (pdflatex/lacheck) and fix reported errors before returning section_tex' — the bash tool is already suggested but never given a verification role.

Include one concrete example of an apply_aider_edits SEARCH/REPLACE block against the achemso shell so the edit format is copy-paste ready.

Specify where section fragments live and how they are named in the writable run workspace, and trim the duplicated read-only-asset instructions between Workflow and Template discipline.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes LaTeX competence with no concept explanations, but has minor redundancy: 'do not try to edit the read-only mounted asset directly' (Workflow step 2) repeats 'The mounted asset is reference-only; any edited TeX should live under the writable run workspace' (Template discipline), and Quick Start's 'Read these assets first' duplicates Workflow step 1.	4 / 5
Actionability	Guidance is mostly executable: specific tools ('Use apply_aider_edits for deterministic SEARCH/REPLACE edits'), exact mounted paths, and concrete output artifacts ('section_tex', 'latex_artifact_refs'). Falls short of anchor 5 because no example SEARCH/REPLACE block, section-fragment naming convention, or placement rule is shown.	4 / 5
Workflow Clarity	The six steps give a clear sequence, but there is no validation checkpoint for a document-manipulation workflow — no compile check via the suggested bash tool, no verify step after edits, and no fix-and-retry loop — which caps workflow clarity at 3 per the feedback-loop guidance.	3 / 5
Progressive Disclosure	Well-organized overview with one-level-deep, purpose-labeled references, and both cited asset files (achemso-demo.tex, achemso-demo.bib) exist in the bundle. Not anchor 5: the two ../_references/*.md links resolve outside the skill bundle and cannot be verified from the bundle structure, and the Quick Start/Workflow duplication slightly blurs navigation.	4 / 5
	Total	15 / 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.

A specific, distinctive, third-person description that clearly states what the skill does, but it entirely omits when to use it. Adding an explicit trigger clause with natural synonyms (.tex, LaTeX draft, journal submission) would raise both completeness and trigger quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the writing lane is producing an ACS journal draft, an achemso-based .tex manuscript, or when sections must match the ACS template structure.'

Add natural trigger synonyms and file extensions ('.tex', 'LaTeX manuscript', 'journal submission draft') to broaden keyword coverage.

Optionally enumerate the concrete capabilities slightly (e.g. 'draft, revise, and assemble section-level .tex fragments') for fuller coverage.

Dimension	Reasoning	Score
Specificity	Names several concrete actions ('Write ACS-style manuscript sections', 'deterministic template edits', 'preserving BibTeX structure') with minor gaps in coverage; falls short of anchor 5's comprehensiveness since only three capabilities are named and 'deterministic template edits' is a method qualifier more than a distinct action.	4 / 5
Completeness	The 'what' is clear (write ACS-style sections against the achemso template with deterministic edits and preserved BibTeX), but there is no 'Use when...' clause or any equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Natural niche keywords are present ('ACS-style', 'achemso LaTeX template', 'manuscript sections', 'BibTeX') that a chemist drafting a paper would actually say, but common variations like '.tex', 'LaTeX draft', or 'journal submission' are missing.	4 / 5
Distinctiveness Conflict Risk	'achemso' and 'ACS-style' define a clear niche with distinct triggers and minimal conflict risk; only a generic LaTeX-writing skill could plausibly overlap, and the ACS/achemso qualifiers exclude that.	5 / 5
	Total	16 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
relative_links	Relative link issues: 2 suspicious	Warning

	Total	14 / 16 Passed

Repository: fernandezbaptiste/CatMaster
Path: writing_skills/achemso-latex-manuscript/SKILL.md
Commit: c87fc76

Reviewed: 2 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.