handover-generator

Name: handover-generator
Availability: InStock
Author: 1000ssam

Parse file names to extract metadata and generate structured Markdown handover documents.

7|2|Updated Feb 1, 2026

Search Tags:#automation #documentation #markdown #handover #administrative #filename-metadata

Ready to run

npx skills add https://github.com/1000ssam/skills-for-teachers --skill handover-generator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: handover-generator
Source: https://github.com/1000ssam/skills-for-teachers/tree/main/skills/handover-generator
Command: npx skills add https://github.com/1000ssam/skills-for-teachers --skill handover-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of structured, multi-section handover documents by analyzing file names of local government or organizational documents, extracting metadata such as organization, document number, and type, and then generating a coherent Markdown report.

Core Features & Use Cases

Automated metadata extraction from file names to drive documentation.
Category-based organization and generation of a Markdown handover with sections, timelines, and appendices.
Optional docx export via Pandoc and validation against the source file set.

Quick Start

Provide Claude Code with a folder path to your saved documents and ask it to generate a Markdown handover report.

Frequently Asked Questions about handover-generator

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

FAQPage Schema

How do I generate a handover report from local document filenames?▼

Markdown handover documents are generated by parsing local filenames to extract metadata such as organization, document number, and type, then categorizing and assembling the data into a structured, multi-section report with appendices.

What is the best way to automate metadata extraction from administrative documents?▼

Automated metadata extraction from administrative documents is achieved by parsing file names to identify organization, document number, and type, then categorizing files to drive the structured generation of a Markdown handover report.

Can I export the Markdown handover document to docx?▼

Yes, you can export the Markdown handover document to docx format. The generation workflow includes an optional docx conversion step via Pandoc, allowing you to produce a Word document alongside the standard Markdown report output.

Does the handover generator validate the document output against source files?▼

Yes, the handover generator validates the document output against the source file set. It implements a deterministic workflow with validation and clear error handling to ensure the generated Markdown report accurately reflects the parsed local documents.

What file naming convention is needed to extract handover metadata automatically?▼

Extracting handover metadata automatically requires local filenames to contain identifiable organizational details, such as the organization name, document number, and document type. The tool parses these specific filename elements to categorize administrative documents accurately.

Are there limitations when parsing filenames for administrative handover documentation?▼

Limitations when parsing filenames for handover documentation arise if file names lack clear organizational metadata, document numbers, or type indicators. The deterministic workflow relies on consistent file naming to categorize documents and assemble the Markdown report with appendices.