paper-length-gate

Deterministic artifact-backed manuscript readiness gate for meta-paper-write. Validates the workspace LaTeX artifact before compilation while leaving final page-count enforcement to compile_pdf.

Quality

62%

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 ./src/opensquilla/skills/bundled/paper-length-gate/SKILL.md

Quality

Content

78%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 is a lean, well-structured overview that delegates implementation to the bundled audit script and clearly communicates the two-run validation workflow and the compile_pdf boundary, with only actionability limited by the absence of inline executable detail.

Dimension	Reasoning	Score
Conciseness	The ~130-word body is lean and assumes Claude's competence; it states the input contract, what is checked, and the boundary with compile_pdf without explaining concepts Claude already knows.	5 / 5
Actionability	The body concretely describes the input contract (JSON with paper contract and manifest, MANUSCRIPT_PATH pointing to a non-empty .tex) and what is checked, but provides no executable code or commands in the body itself — execution is delegated to the entrypoint script.	3 / 5
Workflow Clarity	A clear two-run sequence with a feedback loop is described ('report-only preflight ... drive one bounded authoring repair; a second fail-closed run must pass before compilation'), with most validation checkpoints present though the repair bounding is not fully detailed.	4 / 5
Progressive Disclosure	The SKILL.md is a concise overview with logic correctly separated into scripts/audit.py (wired via the entrypoint); for a sub-50-line single-purpose skill this well-organized structure earns the top score with no nested references.	5 / 5
	Total	17 / 20 Passed

Description

46%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 specific and well-bounded, clearly separating this gate from compile_pdf, but it is written in technical jargon and lacks an explicit 'Use when...' trigger clause, which limits trigger-term quality and completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use before compiling a manuscript in meta-paper-write to confirm the LaTeX artifact is ready.'

Replace some technical jargon ('artifact-backed', 'meta-paper-write') with natural terms users would say ('paper', 'manuscript length', 'LaTeX readiness').

List the concrete checks performed (document structure, citations, body scale) to lift specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('manuscript readiness gate for meta-paper-write') and one concrete action ('Validates the workspace LaTeX artifact before compilation'), but does not list multiple specific actions, so it is not comprehensive.	3 / 5
Completeness	It clearly states what the skill does ('Validates the workspace LaTeX artifact before compilation') but provides no explicit 'Use when...' trigger clause; the 'when' is only weakly implied by 'before compilation', which caps completeness at 3.	3 / 5
Trigger Term Quality	The phrasing is dominated by technical jargon ('Deterministic artifact-backed', 'meta-paper-write', 'compile_pdf') with only generic domain keywords ('manuscript', 'LaTeX'); it lacks the natural phrases a user would actually say.	2 / 5
Distinctiveness Conflict Risk	It carves a clear niche ('manuscript readiness gate for meta-paper-write') and explicitly distinguishes itself from compile_pdf ('leaving final page-count enforcement to compile_pdf'), with only minor overlap risk within the closely related paper-authoring ecosystem.	4 / 5
	Total	12 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: TokenRhythm/opensquilla
Path: src/opensquilla/skills/bundled/paper-length-gate/SKILL.md
Commit: 94ac35e

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