paper-source-readiness-gate

Validates curated bibliography coverage against citation targets before paper drafting begins.

6.8k|540|Updated May 6, 2026
One-click install
npx skills add https://github.com/opensquilla/opensquilla --skill paper-source-readiness-gate
Or copy as Structured Prompt for Agentâ–¼
Please help me install this Agent Skill.
Skill: paper-source-readiness-gate
Source: https://github.com/opensquilla/opensquilla/tree/main/src/opensquilla/skills/bundled/paper-source-readiness-gate
Command: npx skills add https://github.com/opensquilla/opensquilla --skill paper-source-readiness-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Academic paper drafting pipelines can waste significant effort generating sections only to discover the curated sources cannot support the required citation count. This gate audits the source pack and bibliography deterministically before any expensive drafting work begins.

Core Features & Use Cases

  • Citation Target Verification: Parses CITATION_TARGET from the paper contract or preferences and confirms it is a machine-readable integer greater than zero.
  • Cross-Reference Consistency Checks: Verifies usable keys appear in PRIMARY_REFERENCES and the BibTeX bibliography, and that declared counts match verified counts.
  • Locator Validation: Confirms each usable bibliography entry carries a valid HTTPS URL, DOI, or arXiv identifier via strict BibTeX field parsing.
  • Use Case: In an automated meta-paper writing workflow, run this gate immediately after source curation; it exits non-zero with concrete found/required counts and blocker details when coverage is insufficient, halting the pipeline before section generation.

Quick Start

Run the readiness gate on my paper contract, source pack, and bibliography JSON to confirm the curated references meet the citation target before drafting.

Frequently Asked Questions about paper-source-readiness-gate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate citation coverage before writing a paper draft?â–¼

Pass a JSON payload containing the paper contract, paper preferences, structured source pack, and BibTeX bibliography to the audit script via stdin. It compares verified usable references against CITATION_TARGET and exits non-zero with blockers when coverage is insufficient.

What input format does the source readiness audit expect?â–¼

The audit expects a JSON object on stdin with paper_contract, paper_preferences, source_pack, and bibliography fields. The source pack must declare SOURCE_STATUS, CITATION_TARGET, USABLE_REFERENCE_COUNT, USABLE_KEYS, and PRIMARY_REFERENCES sections.

Does the bibliography audit verify DOI and arXiv identifiers?â–¼

Yes, the audit parses top-level BibTeX fields and accepts entries with a valid HTTPS URL in url or howpublished, a DOI matching the 10.xxxx pattern, or an arXiv eprint identifier. Entries lacking any valid locator are reported as blockers.

Why does the source readiness gate fail with duplicate field errors?â–¼

The gate rejects source packs containing duplicate SOURCE_STATUS, CITATION_TARGET, USABLE_REFERENCE_COUNT, USABLE_KEYS, or primary-reference sections, since ambiguous declarations make coverage counts unreliable. Consolidate each field into a single occurrence.

When should this citation gate run in a paper writing pipeline?â–¼

Run it immediately after source curation and before experiment design, outlining, or section writing. It is a deterministic internal gate, not user-invocable, designed to stop drafting early when verifiable references fall below the target.