archaeology-discussion

Generate 9-section cultural heritage excavation report discussions with automatic citations.

Updated Nov 11, 2025
One-click install
npx skills add https://github.com/younga1234/test2 --skill archaeology-discussion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: archaeology-discussion
Source: https://github.com/younga1234/test2/tree/main/.claude/skills/archaeology-discussion
Command: npx skills add https://github.com/younga1234/test2 --skill archaeology-discussion

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates end-to-end generation of a culture heritage standard '고찰' (discussion) by analyzing three core data sources: the completed excavation reports, scholarly papers, and nearby comparative site reports. It outputs a full 9-section discussion aligned with Cultural Heritage Administration guidelines, reducing manual effort, saving time, and lowering complexity for archaeologists and heritage researchers.

Core Features & Use Cases

  • End-to-end pipeline: From data ingestion to final discussion document, all in one command.
  • Multi-source synthesis: Integrates primary excavation data, literature, and regional comparisons into a cohesive narrative.
  • Template-driven output: Adheres to the 2021 Cultural Heritage Administration standard for structure, citations, and terminology.
  • Traceable evidence flow: Ensures claims are backed by表/도/유구/층위 data and dating results.
  • Use Case: A researcher triggers the pipeline on a project with 1_main_report, 2_papers, and 3_comparison_sites to produce a publication-ready 고찰 draft.

Quick Start

Trigger the pipeline with the command "고찰 작성해줘" in a project root that contains 1_main_report, 2_papers, and 3_comparison_sites to generate the complete 고찰 output.

Frequently Asked Questions about archaeology-discussion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate archaeology excavation report discussion writing?

Automate archaeology discussion writing by running the pipeline on a project containing 1_main_report, 2_papers, and 3_comparison_sites directories. The Skill synthesizes data across these sources to generate a complete 9-section discussion aligned with Cultural Heritage Administration standards, eliminating manual composition.

Can I generate archaeological discussions from multiple data sources automatically?

Yes. This Skill integrates primary excavation reports, scholarly papers, and comparative site data into a cohesive discussion. It performs cross-referencing, evidence extraction, and citation management across all three sources, producing a validated discussion_final.md output.

What does a Cultural Heritage Administration standard discussion template include?

The standard 고찰 (discussion) structure contains 9 sections covering evidence synthesis, dating results, regional context, and comparative analysis. This Skill automates formatting, terminology alignment, and citation insertion to meet 2021 guidelines without manual editing.

How does the Skill extract and cross-reference archaeological data?

The pipeline ingests excavation tables, stratigraphic data, C14-dating results, and literature references, then validates claims against source evidence. It traces data flow through phases 1–3 (collection, synthesis, validation) to ensure all discussion points are traceable to original findings.

Can I use this Skill without modifying the input data structure?

Yes. The Skill requires only three standard input directories (1_main_report, 2_papers, 3_comparison_sites) and operates under read-only constraints using Grep, Glob, and Read tools. No preprocessing or format conversion of source files is necessary.

What output format does the discussion generation produce?

The Skill outputs discussion_final.md, a publication-ready markdown file structured in the 9-section Cultural Heritage Administration format with automated citations, evidence references, and terminology compliance. The output is ready for peer review or submission.