メニュー
Detect project type and route to the appropriate publication workflow. Routes R packages to the CRAN/JOSS pipeline, Python packages to PyPI publishing, or asks for clarification if ambiguous.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
This skill should be used when the user asks about research directions, open problems, future work, or follow-up research from the academic literature. Trigger phrases include "open problems in X", "what's next for Y", "future work for paper Z", "research directions on T", "salient follow-up research", "what should I work on next in", "find me follow-up research unrelated to my prior work", "broad survey of W", "neglected directions in V". Routes the request to the right Vista MCP tool, reads back the structured paper sections, and synthesizes research directions in the conversation.
Audit a book manuscript against Amazon KDP requirements: interior formatting, cover specs, metadata, and genre-specific checks. Handles technical books (LaTeX, math), fiction, and nonfiction. Produces a structured gap report with Critical and Warnings sections plus automation suggestions.
Orchestrate the full Amazon KDP publishing workflow: audit, listing craft, manuscript prep, cover generation, dashboard submission, pricing, publish. Phases gate each other. Handles both eBook and paperback. Manages MCP-driven cover generation or falls back to manual prep.
Discover latent themes in the metafunctor corpus. Use when the user wants to find implicit through-lines across their blog posts, surface recurring ideas they have not consciously framed as a series, or get candidate themes for a synthesis post. Reads titles, descriptions, and tags; proposes 3 themes that connect 4+ posts each, each with a single-sentence through-line. Output is a proposal, not a draft. Trigger phrases include "find themes in my posts", "what threads connect my writing", "latent themes in my corpus", "scribe".
Launch a multi-agent editorial review with 8 specialists (2 literature scouts plus 6 domain reviewers) orchestrated by an area-chair agent. Produces a unified report plus specialist reports in .papermill/reviews/. Updates .papermill/state.md.
Apply fixes from a multi-agent review report. Launches the reviser orchestrator, which triages the findings in .papermill/reviews/, dispatches section-writer specialists per finding domain, verifies each fix with the owning review specialist, and writes a revision report paired with the review. Closes the draft, review, revise loop. Updates .papermill/state.md.
| name | pub-pipeline |
| description | Detect project type and route to the appropriate publication workflow. Routes R packages to the CRAN/JOSS pipeline, Python packages to PyPI publishing, or asks for clarification if ambiguous. |
Detect the current project type and route to the appropriate publication workflow.
Check the current working directory for project type indicators:
| Check | Project Type | Route To |
|---|---|---|
DESCRIPTION file with Package: field | R package | /r-publish (the r-pub-pipeline skill) |
pyproject.toml or setup.py or setup.cfg | Python package | /pypi-publish (the pypi-publish skill) |
.tex sources plus a built .pdf, no package files | Academic paper | Not handled here: tell the user this looks like a paper and point at the papermill plugin |
| Multiple types detected | Ambiguous | Ask the user which workflow to run |
| None detected | Unknown | Ask the user what they want to publish |
Search the current directory for:
DESCRIPTION (R package indicator; verify it contains a Package: field)pyproject.toml, setup.py, setup.cfg (Python package indicators)*.tex plus a built *.pdf with neither of the above (academic paper: route the user to papermill)Read .claude/pub-pipeline.local.md if it exists. If missing, inform the user and offer to create one from the template at ${CLAUDE_PLUGIN_ROOT}/docs/user-config-template.md.
Based on detection, invoke the appropriate ecosystem skill. If the project type is ambiguous (e.g., both DESCRIPTION and pyproject.toml exist), present options to the user and ask which publication workflow to run.
| Ecosystem | Skills | Commands |
|---|---|---|
| R packages | cran-audit, joss-audit, joss-draft, r-pub-pipeline | /cran-audit, /joss-audit, /joss-draft, /r-publish |
| Python packages | pypi-publish | /pypi-publish |
${CLAUDE_PLUGIN_ROOT}/docs/user-config-template.md — Shared user config template