easypaper-interactive-metadata-build

Use this skill when the user has a folder of research materials and wants Claude to co-author the metadata in conversation instead of running the one-shot SDK pipeline silently.

The two paths are complementary:

Path	Driver	Interaction	Use when
SDK one-shot (generate_metadata_from_folder)	EasyPaper internal LLM	None	Batch, CI, or fast autonomous extraction
This skill	Claude Code	High	Single high-value paper, atypical folder, or ambiguity requiring user input

Both paths produce metadata that can be consumed by easypaper-paper-from-metadata.

Output Contract

The final JSON must validate as PaperGenerationRequest and include:

• title, idea_hypothesis, method, data, experiments
• references
• materials_root
• figures
• tables
• optional template_path, style_guide, target_pages, generation flags, and output settings

Each figure/table object follows the SDK shape:

{
  "id": "fig:h<12hex>",
  "caption": "...",
  "description": "...",
  "section": "",
  "file_path": "relative/posix/path/to/asset.png",
  "wide": false,
  "auto_generate": false,
  "generation_prompt": null
}

Tables use the same shape with tab: ids.

Path Handling

Folder-derived metadata uses the SDK convention:

• materials_root: resolved source-folder path.
• figures[].file_path and tables[].file_path: relative POSIX paths under materials_root.
• Do not convert folder-derived figure/table paths to absolute paths in the saved metadata.
• template_path may be omitted or written relative to the saved metadata file location when the template is part of the same portable project.

Downstream generation resolves figure/table assets via materials_root first. The generation command or example loader normalizes operational fields such as template_path and local code_repository.path before calling the SDK.

ID Generation

When operating in cold mode, generate stable ids the same way as the SDK: