paper-citation-integrity-gate

Deterministic citation-count and provenance gate for meta-paper-write. Checks the citation_map summary against the numeric paper citation target without trusting an LLM verdict.

Quality

70%

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-citation-integrity-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 an exemplar of concise, well-structured documentation for a simple deterministic gate, though it stops short of showing the SUMMARY contract format or the explicit recovery loop that would make it fully actionable.

Suggestions

Include a concrete example of the machine-readable SUMMARY line (field names and expected integer values) so the parsed contract is unambiguous.

Add a brief note on what callers should do when the gate blocks — fix invalid/weak citations and re-run — to make the validation feedback loop explicit.

Dimension	Reasoning	Score
Conciseness	The four-sentence body is lean and efficient, assumes competence, and avoids explaining concepts Claude already knows; every token earns its place.	5 / 5
Actionability	The block/warn rules are concretely enumerated ('blocks when distinct cited keys are below target or any cited entry is invalid or weak', 'unused... reported as a warning'), but no executable example is given and the machine-readable SUMMARY line format is referenced without being shown.	3 / 5
Workflow Clarity	As a single-purpose gate the action is unambiguous and outcomes (block vs. warning) are well-defined, but the recovery feedback loop on a block (fix and re-run) is only implied, not spelled out.	4 / 5
Progressive Disclosure	The skill is under 50 lines with no need for external references; content is well-organized under one heading and the executable logic is appropriately delegated to the entrypoint script audit.py rather than inlined.	5 / 5
	Total	17 / 20 Passed

Description

62%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 concrete and highly distinct, precisely conveying what this internal gate does, but it lacks an explicit 'Use when...' trigger clause and leans on technical pipeline jargon rather than natural user phrasing.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use after citation_map to enforce the paper's numeric citation target deterministically and reject invalid or weak citations.'

Broaden trigger phrasing with more natural terms such as 'verify citation count', 'check bibliography coverage', or 'validate cited keys' rather than only internal pipeline identifiers.

Dimension	Reasoning	Score
Specificity	Names several concrete actions — 'citation-count and provenance gate', 'Checks the citation_map summary against the numeric paper citation target', 'without trusting an LLM verdict' — with only minor coverage gaps, fitting between the 1-2-action and comprehensive anchors.	4 / 5
Completeness	It clearly states what the skill does, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Keywords like 'citation', 'citation target', and 'provenance' are domain-relevant, but the phrasing is internal-pipeline jargon ('citation_map summary', 'for meta-paper-write') rather than natural terms a user would say, missing common variations.	3 / 5
Distinctiveness Conflict Risk	The description carves out a clear, narrow niche tied to a named parent pipeline ('citation-count and provenance gate for meta-paper-write'), making conflict with other skills minimal.	5 / 5
	Total	15 / 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-citation-integrity-gate/SKILL.md
Commit: 94ac35e

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