PluginBench
Skill
Pass
Audit score 90

ccf-paper-to-exemplar

mikubaka88/ccfa-skills

Distill academic papers into reusable writing exemplar cards with source attribution preserved.

What is ccf-paper-to-exemplar?

Converts PDF papers into structured writing exemplar cards that capture methodology, evidence patterns, and citation techniques. Use this to build a personal library of writing patterns from academic sources, maintaining clear attribution and separating writing logic from source claims.

  • Extract full text and metadata from paper PDFs into a working cache
  • Analyze papers for story structure, abstract/introduction/method/evidence moves, and citation patterns
  • Generate exemplar cards with reusable writing techniques and anti-patterns to avoid
  • Register completed cards in a personal exemplar library with indexed lookup
  • Preserve source attribution and page anchors for verification
  • Coordinate with related skills (paper-writer, visual-composer, paper-reviewer) via handoff contracts

How to install ccf-paper-to-exemplar

npx skills add https://github.com/mikubaka88/ccfa-skills --skill ccf-paper-to-exemplar
Prerequisites
  • Python with pymupdf library installed for PDF extraction
  • Access to paper PDFs in local filesystem
  • Existing ccf-common and ccf-humanization skills installed for collaboration contracts
  • Optional: existing exemplar library or custom working directory structure
Claude Code
Cursor
Windsurf
Cline

How to use ccf-paper-to-exemplar

  1. 1.Identify the PDF file path and desired output location (defaults to ccfa-workfiles/exemplars/<source-id>/)
  2. 2.Run scripts/convert.py with --output-dir, --full-text, and --full-text-dir flags pointing to your working cache
  3. 3.Review extraction success and verify page markers in the generated skeleton card
  4. 4.Analyze the full paper for story pattern, abstract/introduction/method/evidence moves, and citation techniques
  5. 5.Fill the exemplar card template with writing patterns, source anchors, and anti-patterns to exclude
  6. 6.Register the completed card in your library by updating the exemplars index (optional)
  7. 7.Pass the card path and relevant writing moves to ccf-paper-writer for manuscript work

Use cases

Good for
  • Build a personal library of writing patterns from papers in your research area
  • Extract methodology and evidence presentation techniques from published work
  • Create venue-specific writing exemplars by analyzing papers from target conferences
  • Document reusable citation and argumentation patterns from high-quality sources
  • Maintain a searchable index of writing moves organized by source and topic
Who it's for
  • Academic writers and researchers building writing skill
  • Students learning to write papers by studying exemplars from published work
  • Teams maintaining shared writing pattern libraries across projects
  • Authors preparing manuscripts for specific venues

ccf-paper-to-exemplar FAQ

What's the difference between this skill and ccf-paper-writer?

This skill extracts and catalogs reusable writing patterns from existing papers. ccf-paper-writer uses those exemplar cards to draft new manuscripts. They work together: exemplars provide the patterns, writer applies them.

Do I need Python and pymupdf to use this skill?

Only if you're extracting new PDFs. If you're reusing an existing exemplar card that matches your source and scope, no extraction is needed.

Can I use this to copy text directly from papers?

No. The skill extracts writing moves and techniques while preserving source attribution. It captures how papers are structured and argued, not their specific wording.

Where should I store my exemplar cards?

The default is ccfa-workfiles/exemplars/<source-id>/ for working files, with completed cards registered in ../ccf-paper-writer/references/exemplars/cards/ and indexed in the exemplars index.

What happens if extraction fails or is incomplete?

Check the page markers and extraction logs in the cache. For equations, figures, or complex layouts, inspect the actual PDF pages. Do not treat empty extraction as a complete analysis.

Full instructions (SKILL.md)

Source of truth, from mikubaka88/ccfa-skills.


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 and reuse the same paths across skill transitions.

Collaboration Contract

Before specialist execution, read and apply ccf-humanization first, then ccf-common. 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; 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.