claude-anvil

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.

Display a read-only dashboard for paper project status: stage, thesis, experiments, review history, venue, and suggested next action. Reads .papermill/state.md.

Fork an in-flight research-agent run at its current checkpoint into a named branch with its own state, log, and attempts, sharing the parent's goal and findings read-only. Use to pursue a competing strategy without disturbing the main line. The synthesize skill later compares branches.

Resume an interrupted research-agent run. Re-launches the researcher with instructions to read .research/state.md and log.md, reorient, and continue from the documented current focus. Use after a context compression, session restart, or explicit pause.

Show the current state of an in-flight research-agent run from .research/state.md, log.md, and attempts/. Read-only summary of cycles, sub-problems, hypothesis statuses, eval trend, and current focus.

Force a research-agent run to conclude. Launches the researcher in synthesis mode: it reads state.md and log.md, writes .research/synthesis.md with outcome, key findings, failed approaches, open questions, and recommendations, then exits. Use when current results are good enough or the agent is stalling.

Use when writing cross-referenced sections in a bookwright project. Covers the header comment block template, label-naming conventions, when to use prose-only vs Cref, forward-reference documentation, and the integration-check baseline.

Cross-post blog content to social platforms. Crier is MCP-native; the tools handle mechanics while this skill provides judgment context they can't: rewrite guidelines, platform culture, workflow tips.

Use when encrypting, decrypting, signing, or managing confidential content. Smart routing across three tools: cryptoid for Hugo site encryption, pagevault for HTML and file encryption, and gpg for file-level encryption and signing.

Use mf (metafunctor) to manage papers, projects, series, and content for the metafunctor.com Hugo site. Also covers site architecture, taxonomies, front matter conventions. For cross-posting, use the crier plugin. Invoke from ANY repo; mf works globally.

Launch a multi-agent writing system with specialist writers for literature, formal content, methodology, and results, orchestrated by a lead author. Produces a manuscript draft and section-level artifacts in .papermill/drafts/. Updates .papermill/state.md.

Initialize a paper repository: discover structure, infer format, gather author info, and create .papermill/state.md. On existing repos, refresh mode adds missing schema fields without overwriting data. Migrates legacy .papermill.md to .papermill/state.md automatically.

Design paper structure: generate a section-by-section outline with purpose, key content, estimated length, and narrative arc. Adapts to paper type and venue conventions. Updates .papermill/state.md.

Perform final pre-submission checks: formatting, citations, figures, metadata, and build verification. Systematic checklist identifies remaining issues and suggests fixes.

Conduct a systematic literature survey. Reads the thesis from .papermill/state.md, searches academic sources, classifies references, identifies gaps, generates BibTeX, and updates the state file. Can launch the surveyor agent for deeper autonomous search.

Develop, verify, or refine mathematical proofs: strategy selection, logical-correctness checks, gap identification, and clear presentation. Works with existing drafts or constructs from scratch.

Identify and evaluate publication venues. Considers scope, impact factor, review timeline, acceptance rate, and fit. Produces a ranked shortlist with submission strategy guidance. Updates .papermill/state.md.

Evaluate R package and paper.md against the full JOSS reviewer checklist. Covers software requirements, paper format, and community standards. Gap report with Critical, Warnings, and Passed sections, plus fix recommendations.

Draft a JOSS paper.md and paper.bib. Discovers existing manuscripts first, then synthesizes package analysis, competing packages, and the required sections (Summary, Statement of Need, State of the Field, Software Design, Research Impact, AI Disclosure).

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.

Audit a Python package's metadata, verify tests pass, build distributions, test on TestPyPI, then publish to PyPI. Validates name, version, readme rendering, and dependency requirements. Handles credential setup and trusted publishers.

Orchestrate the full R publication pipeline: CRAN submission for distribution, JOSS paper for DOI and peer review, optionally a JSS methods paper. Coordinates audits, drafting, and review cycles.

When and how to use the repoindex plugin surface (MCP tools, agents, slash commands) for collection queries, release prep, activity summaries, and tag discipline. Use when users ask repoindex questions, mention their repo catalog, or want to know which repoindex tool fits their task.

Launch an autonomous research agent that iterates toward a goal through proofs, code, simulations, tests, and counterexample search. Fire-and-forget mode: the agent runs autonomously and writes all results to .research/ in the target project.

Use when working in a project with a worldbuilding documentation ecosystem (docs/ or lore/ directory). Provides the documentation-first methodology: canonical hierarchy, doc roles (timeline, lore, characters, systems), propagation discipline, and the dual canonical and exploratory workflow.

Use when drafting prose sections for a bookwright (technical non-fiction) project. Encodes the Bernoulli-textbook workflow: atom-outward design, deferral discipline, running threads, page budgets, Path A subagent pattern, header comment block convention.

Use when drafting or executing a paired notebook for a bookwright chapter. Covers when notebooks are required vs optional, numerical-sanity-target convention, exec-from-fresh-kernel requirement, and stack-specific execution commands (Jupyter/R Markdown/Quarto).

Craft the four marketing artifacts for an Amazon KDP listing: blurb (with HTML formatting), keywords, BISAC categories, and author bio. Reads manuscript context to generate variants, then saves outputs to the user config. These four artifacts determine discoverability and conversion on Amazon.

Design rigorous experiments for a research paper: hypothesis formulation, variable identification, methodology selection, and success criteria. Produces a structured experiment plan with reproducibility in mind.

Design Monte Carlo simulations for theoretical validation: sample size determination, convergence diagnostics, and result presentation. Specialized for statistical methodology papers.

Extract or refine a paper's central claim and novelty via Socratic dialogue or existing-draft analysis. Two modes: extract from a draft, or explore and sharpen a new idea. Updates .papermill/state.md.

Audit an R package against CRAN Repository Policy and submission requirements. Produces a gap report with Critical (must fix), Warnings (should fix), and pass/fail assessment per requirement type. Offers automated fixes where possible.

Use when writing fiction, editing fiction prose, reviewing chapters, or drafting scenes. Covers prose craft, dialogue mechanics, scene structure, and common failure modes in AI-assisted fiction. Trigger phrases: "write fiction", "edit chapter", "prose review", "scene draft", "dialogue check", "fiction craft", "edit this scene", "review my prose".