Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →docxology/infrastructure-publishing
Skill for the publishing infrastructure module providing academic publishing workflows including BibTeX CLI citation generation, APA/MLA citation helper functions, DOI management, Zenodo publication, arXiv submission preparation, GitHub releases, PyPI and TestPyPI package distribution, static-site deployment to GitHub Pages / Cloudflare Pages / Netlify, multi-target long-horizon archival (IPFS Pinata, Web3.Storage, Software Heritage), a central platform registry, and publication readiness valida
Passed 25 of 25 test cases with the skill, and 5 of 25 without it.
and 30 more in the full report
20 fixed5 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 20 test cases the skill fixed. Same model, same prompt, with and without the skill.
I want to run `run_uploads` from the upload runner module to verify target assets without executing real network uploads. What flag on `run_uploads` controls dry-run mode?
| Checked | Without skill | With skill |
|---|---|---|
| Passes commit=False to run_uploads. | Missed | Passed |
The instructions your model reads when the skill loads.
Academic publishing and dissemination tools for research projects.
For the release-operator workflow, start with
docs/guides/publication-runbook.md.
It is the front door for standalone public GitHub mirrors, real Zenodo DOI
minting, new-version releases, optional mirrors, status blocks, and archival
handoff.
| Path | Use when |
|---|---|
infrastructure.publishing.zenodo | Zenodo deposit, upload, publish, DOI |
infrastructure.publishing.github | GitHub release + assets |
infrastructure.publishing.arxiv | arXiv tarball from manuscript tree |
infrastructure.publishing.pypi | PyPI / TestPyPI package distribution |
infrastructure.publishing.static_site | GitHub Pages, Cloudflare Pages, or Netlify deployment |
infrastructure.publishing.archival | IPFS Pinata, Web3.Storage, Software Heritage, Zenodo mirror |
infrastructure.publishing.registry | Enumerate or look up all platform adapters |
Root exports (infrastructure.publishing) resolve directly to the canonical subpackages; import clients and adapters from their implementation homes.
from infrastructure.publishing import PublicationMetadata, extract_publication_metadata
metadata = extract_publication_metadata([Path("manuscript/01_introduction.md")])
The publication: block in manuscript/config.yaml records durable identifiers
(doi, version_doi, version_record, github_repository, repository_url).
The publication.published_artifacts key — a {platform_name: durable_url} map —
records artifacts published outside those fields (e.g. an IPFS CID or a
HuggingFace dataset URL) and is consumed by status_report.py to mark those
platforms as published.
test cases passed, vs 5 / 25 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.