source-packet

Organize and inventory sources into a verifiable source map.

4|1|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/m2ai-portfolio/m2ai-skills-pack --skill source-packet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-packet
Source: https://github.com/m2ai-portfolio/m2ai-skills-pack/tree/main/skills/source-packet
Command: npx skills add https://github.com/m2ai-portfolio/m2ai-skills-pack --skill source-packet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organizes and inventories sources to produce a verifiable source map that clarifies knowns, unknowns, and potential conflicts before creating any deliverable.

Core Features & Use Cases

  • Inventory and ID sources with status, reliability tier, and basic metadata
  • Generate a conflict log and a gap analysis to highlight human-decision points
  • Output a structured Source Packet to anchor downstream work (decks, reports, workbooks)

Quick Start

Organize your documents into a single source map before starting any deck, report, or workbook.

Frequently Asked Questions about source-packet

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

FAQPage Schema
How do I create a verifiable source map before building a report?

To create a verifiable source map, you inventory and ID sources with status, reliability tier, and metadata to produce a structured Source Packet anchoring downstream work.

What is the best way to inventory data sources and identify conflicts across multiple files?

Inventorying data sources involves defining an intake and governance workflow that logs conflicts and identifies gaps across files, highlighting human-decision points for auditable outputs.

How do I perform a gap analysis on source documents before creating a deck?

Performing a gap analysis on source documents requires organizing files into a single map to reveal knowns, unknowns, and conflicts, ensuring you clarify gaps before creating any deck.

Does source governance workflow handle reliability tiering and metadata intake?

Yes, source governance workflow handles reliability tiering and basic metadata intake by defining a structured process to inventory and ID sources before generating deliverables.

When do I need to organize and inventory sources into a structured packet?

You need to organize and inventory sources into a structured packet before creating decks, reports, or workbook artifacts to reveal knowns, unknowns, and potential conflicts.