pub-pipeline

This skill should be used when the user asks to "KDP audit", "check manuscript formatting", "is my book ready for KDP", "Amazon publishing requirements", "Kindle formatting check", "manuscript readiness", "book formatting audit", "prepare for Amazon KDP", or mentions KDP/Amazon publishing compliance. It audits a book manuscript against Amazon KDP (Kindle Direct Publishing) requirements for both eBook and paperback formats, handling technical books (LaTeX, math-heavy) and fiction/general nonfiction.

This skill should be used when the user asks to "craft Amazon listing", "write book blurb", "KDP blurb", "book description", "Amazon keywords", "book categories", "KDP listing", "improve my blurb", "help with book marketing metadata", or mentions creating or refining the marketing copy for a book on Amazon KDP. It generates blurb, keywords, categories, and author bio — the four artifacts that determine discoverability and conversion on Amazon.

This skill should be used when the user asks to "publish on KDP", "publish my book", "Amazon book publishing", "Kindle Direct Publishing", "self-publish", "publish on Amazon", "KDP workflow", "submit to Amazon KDP", "publish to Kindle", or mentions Amazon/KDP book publishing. It guides the complete workflow for publishing a book through Amazon KDP, handling both technical books and fiction/nonfiction.

This skill should be used when the user asks to "publish to PyPI", "upload to PyPI", "PyPI release", "publish my Python package", "package for PyPI", "submit to PyPI", "PyPI submission", or mentions PyPI publishing. It guides the complete workflow: auditing package metadata, running tests, building distributions, testing on TestPyPI, and publishing to PyPI.

This skill should be used when the user asks to "publish my package", "publication pipeline", "get this published", "how do I publish this", or mentions publication without specifying an ecosystem. It detects the project type (R package, Python package, or book manuscript) and routes to the appropriate ecosystem-specific publication skill.

This skill should be used when the user asks to "audit for CRAN", "check CRAN readiness", "prepare for CRAN submission", "CRAN check", "is my package CRAN ready", "submit to CRAN", or mentions CRAN submission compliance. It audits an R package against CRAN Repository Policy and submission requirements, producing a structured gap report with actionable fixes.

This skill should be used when the user asks to "audit for JOSS", "check JOSS readiness", "JOSS reviewer checklist", "prepare for JOSS submission", "is my package JOSS ready", "JOSS requirements", or mentions JOSS submission compliance. It evaluates an R package and its paper.md against the complete JOSS reviewer checklist, producing a structured gap report.

This skill should be used when the user asks to "draft a JOSS paper", "write paper.md", "create JOSS paper", "write JOSS submission", "draft paper.md for JOSS", or mentions writing a JOSS software paper. It analyzes an R package and drafts a complete paper.md and paper.bib following JOSS format requirements and patterns from successful R package papers.

This skill should be used when the user asks to "publish my R package", "R publication pipeline", "get this R package published", "CRAN and JOSS pipeline", "publish to CRAN and JOSS", or mentions an end-to-end R package publication workflow. It orchestrates the full CRAN → JOSS → (optionally JSS) publication pipeline for R packages, coordinating audits, paper drafting, and review cycles.