ccf-paper-to-exemplar

Pulls writing patterns from research papers and saves them as examples you can copy.

Installation
Run `npx skills add "https://github.com/mikubaka88/ccfa-skills" --skill "ccf-paper-to-exemplar"` to install this skill, then follow its SKILL.md instructions for my next request.

Paste this into Claude Code, Cursor, or any agent that can run commands.

SKILL.mdShow the author's original SKILL.md
---
name: ccf-paper-to-exemplar
description: "Distill supplied paper PDFs into writing exemplar cards and register a requested personal library. Use for PDF to writing exemplar, 写作范例, and reusable paper-writing patterns. Preserve source attribution and transfer writing logic only. Figure reconstruction, manuscript drafting, and review have separate owners."
metadata:
  ccf_skill_controls:
    handoff_question_mode: partial
    respect_session_denylists: true
    protect_idea_scope_in_writing: true
    private_material_safety: moderate
    shared_controls: ../ccf-common/references/
---

# Paper-to-Exemplar

## Family File Contract

Before writing, resolve the canonical output and one stable working directory per task/artifact. Reuse explicit or established task paths; otherwise use project-root `ccfa-workfiles/<purpose>/<artifact-id>/`, with `source/`, `assets/`, `cache/`, and `build/` only as needed. Update current files in place; do not scatter intermediates or create iteration copies. Preserve inputs and required evidence; clean only verified disposable files created by this task. Use UTF-8 text I/O and check Chinese text after saving or rendering. For file work, apply [artifact-contracts.md](../ccf-common/references/artifact-contracts.md) and reuse the same paths across skill transitions.

## Collaboration Contract

Before specialist execution, read and apply [ccf-humanization](../ccf-humanization/SKILL.md) first, then [ccf-common](../ccf-common/SKILL.md). At every handoff, reuse their applicable active rules or refresh missing/changed ones. Both preflights are required even without prose; detailed editing, experiment, and maintenance modes run only when relevant.

Keep one integrating owner and actively use other skills to resolve missing prerequisites or check material findings. Reuse applicable evidence; do not skip necessary groundwork to save tokens. Before finalizing, integrate contributions and verify affected results. Follow the conditional [cooperation routes](../ccf-common/references/routing.md); avoid unrelated stages and duplicate reports.

## Scope And Shared Controls

Distill supplied paper PDFs into reusable writing patterns, preserving source attribution and scientific meaning. This skill owns exemplar cards; manuscript drafting belongs to `ccf-paper-writer`, visual reconstruction to `ccf-visual-composer`, and scientific review to `ccf-paper-reviewer`.

Follow `../ccf-common/references/handoff-modes.md`, `../ccf-common/references/task-modes.md`, and `../ccf-common/references/artifact-contracts.md`. Resolve existing card/library and cache paths before writing. Preserve no-new-files requests by editing a named existing card or returning the analysis in context. Conversion alone does not authorize global library/default changes.

## Workflow

1. Identify PDF paths, source versions, desired writing patterns, optional venue, and authorized destination. Reuse a completed card and extraction when they match the same source and requested scope; a new source version requires checking the affected analysis.
2. If extraction is needed, run `scripts/convert.py` with explicit `--output-dir`, `--full-text`, and `--full-text-dir` pointing to the chosen working cache. For a new project, the shared default is `ccfa-workfiles/exemplars/<source-id>/`, with extraction in `cache/`; preserve established paths. The converter preserves existing cards and creates only missing skeletons. `--full-text-dir` is optional; omitting it preserves the legacy output layout. Python with `pymupdf` is required for extraction, not for reusing a valid existing card.
3. Check extraction success and page markers. Analyze the relevant full source in coherent sections; use search and targeted ranges for a local card update. Inspect actual PDF pages when equations, figures, or reading order affect interpretation. Do not substitute an abstract-only analysis for a full-paper exemplar or treat empty extraction as complete.
4. Recover the source's story, abstract/introduction/method/evidence moves, citation patterns, and reusable techniques. Do not force a limitations ending. Use `../ccf-paper-writer/references/prose-quality-guardrails.md` to exclude defensive habits, artificial labels, formula dumping, unsupported hype, and mechanical prose from the advice.
5. Fill or revise the existing card in place using the section headings generated by `scripts/convert.py` and established cards: Story Pattern, Abstract Moves, Introduction Moves, Method Moves, Evidence Moves, Citation Patterns, Reusable Techniques, and Do-Not-Copy Boundary. Record title, venue/year when verified, source identity/version, and relevant page/section anchors. Add Excluded Anti-Patterns only when the source supplies a material example. Keep writing moves separate from source claims and distinctive wording.
6. When library registration is requested, use `../ccf-paper-writer/references/exemplars/cards/` or the user's existing library and update `../ccf-paper-writer/references/exemplars/index.md` without duplicate entries. Preserve unrelated cards; a matching filename alone does not prove the same source. Keep raw extraction in the working cache, outside the reusable card library.
7. Update `../ccf-paper-writer/references/custom-format/default-user-format.md` only when default selection is requested. A venue-only request can select an existing relevant card through the index instead of extracting another PDF. Load `../ccf-paper-writer/references/venue-guides/index.md` only when venue-family classification is unclear.
8. Verify that completed cards have no `[ANALYZE]` or `[MANUAL]` placeholders, source references are accurate, and output/cache paths are orderly. Return the canonical card paths and the useful writing patterns; report actual registration/default changes only when performed. Do not echo the full PDF extraction or add generic next-action menus.

## Writer Handoff

Pass the selected card path, source identity, and relevant writing moves. The writer decides whether a style reference is needed for its task; a paragraph edit does not automatically load default or venue card bundles. For full manuscripts or explicit style adaptation, select from `../ccf-paper-writer/references/exemplars/index.md` and load only matching sections/cards. Preserve existing user defaults without treating them as mandatory reading for every writing request.

Ships with 1 supporting file:

  • scripts/convert.py

Mirrored from the author's public source. Install counts from the open skills registry.

The systems behind these skills get built for partners every week.

Partner with us