---
name: research-results-intake
description: Use when the user has raw research materials such as Markdown, HTML, transcript text, notes, PDF summaries, or mixed result files and wants them normalized into a clean delivery-ready input package before generating a results brief, HTML delivery page, slides, or review bundle.
license: Proprietary - Medaibox Research Delivery Pack
---

# Research Results Intake

## Overview

Use this skill as the intake entry point for the Medaibox research delivery workflow.

This skill takes messy or mixed research materials and normalizes them into a stable delivery-ready starting point. It is the preferred first step when the user has raw notes, Markdown, HTML, transcript text, PDF/Word-derived text, or several partial result files that need to be organized before downstream delivery steps.

## When to Use

Use this skill when any of the following are true:

- The user has raw or mixed research materials and wants them consolidated.
- The user wants to turn notes, transcripts, or result fragments into a standard delivery workflow.
- The user wants to generate a results brief, HTML result page, slides, or a delivery bundle, but the source files are still messy.
- There are multiple input files and they need to be turned into one structured working draft.

Do not use this skill when the user already has a clean `results_brief.md`.

## Expected Inputs

Typical inputs include:

- Markdown result notes
- HTML pages
- transcript text
- structured or unstructured summaries
- extracted PDF / DOCX text
- mixed files that need consolidation

## Expected Outputs

This skill should produce:

- `intake_clean.md`
- `delivery_manifest.json`

Optional supporting outputs:

- `assets_index.json`
- `open_questions.md`

## Workflow

1. Inspect the input files and identify the primary source material.
2. Normalize the text into one clean Markdown working file.
3. Remove obvious duplication, noise, and formatting clutter.
4. Preserve useful structure such as headings, tables, bullet lists, and figure references.
5. Record source files and expected deliverables in `delivery_manifest.json`.
6. If key information is missing, write it into an “open questions” section rather than guessing.

## Reuse and Dependencies

Prefer reusing these existing skills when relevant:

- `markitdown`
- `pdf`
- `docx`
- `meeting-transcript`

Use bundled scripts in this skill for deterministic normalization rather than rewriting the same formatting logic manually each time.

## Bundled Resources

Expected bundled resources:

- `scripts/normalize_inputs.py`
- `scripts/init_delivery_manifest.py`
- `templates/intake-outline.md`

## Quality Bar

Before finishing, confirm that:

- `intake_clean.md` exists
- the content is readable and structured
- obvious duplicates and noise have been removed
- `delivery_manifest.json` includes source and target output intentions
- downstream skills can start from this output without redoing intake work
