Install any skill in seconds. Free to start, no credit card required.
Get Started Free →aperivue/sync-submission
Audit SSOT-to-submission drift and create journal submission manifests from canonical manuscript artifacts.
Passed 16 of 20 test cases with the skill, and 4 of 20 without it.
and 21 more in the full report
14 fixed4 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/3/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our figures for a JACC submission are stored in submission/chest/figures. We need to audit figure file sizes and file extensions before uploading to the portal. What file size cap causes a figure bounce for JACC, and what format restriction applies to SNAPP portals?
| Checked | Without skill | With skill |
|---|---|---|
| identifies the 25 MB file size limit for JACC figures | Missed | Passed |
| identifies that SNAPP rejects PNG files | Missed | Passed |
The instructions your model reads when the skill loads.
Keep the canonical manuscript and journal-specific submission packages from drifting apart.
Treat submission/{journal}/ as derived output and record whether it is current, stale, or frozen.
project.yaml, or a direct canonical manuscript path.chest, ryai, academic_radiology.audit: compare existing submission against canonical source.build: copy canonical source and optional declared final artifacts, preserving file bytes, and write metadata.freeze: freeze the chosen byte snapshot with its available check context (not submission approval).python "${CLAUDE_SKILL_DIR}/scripts/sync_submission.py" audit --project-root . --journal chest
python "${CLAUDE_SKILL_DIR}/scripts/sync_submission.py" build --project-root . --journal chest
python "${CLAUDE_SKILL_DIR}/scripts/sync_submission.py" freeze --project-root . --journal chest --status submitted
For double-blind journals, sweep author identifiers across all upload artifacts:
python "${CLAUDE_SKILL_DIR}/scripts/blind_sweep.py" \
--registry _shared/authors/author_registry.yaml \
--files submission/{journal}/supplementary/*.md submission/{journal}/cover_letter.md \
--backup-dir .cache/blind_sweep_backup
The registry is a project-local YAML mapping author identifiers (full names, native scripts, initials with/without periods, email, ORCID) to role labels (e.g., "Reviewer 1"); schema in scripts/author_registry_example.yaml. Never commit a populated registry to a public repository, because it lists the authors' identities — keep it next to the manuscript.
| Artifact | Path | Purpose |
|---|---|---|
| Submission metadata | submission/{journal}/.journal_meta.json | Source hash, status, canonical path |
| Sync audit | qc/submission_sync_{journal}.json | Drift result consumed by orchestrator |
| Manifest update | artifact_manifest.json | Submission package registry |
test cases passed, vs 4 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.