matter-intake

Collect and standardize new matter information into matter.md, history.md, and a log entry.

Updated May 28, 2026
One-click install
npx skills add https://github.com/gtgspot/clegal --skill matter-intake-gtgspot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: matter-intake
Source: https://github.com/gtgspot/clegal/tree/main/litigation-legal/skills/matter-intake
Command: npx skills add https://github.com/gtgspot/clegal --skill matter-intake-gtgspot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Intake a new matter — uniform questions covering identification, conflicts, source, risk triage, materiality, outside counsel, owners, legal hold, and key dates; writes matter.md and history.md and appends a structured row to _log.yaml. Use when the user says "new matter", "intake this matter", or wants to bring a new matter into the portfolio.

Core Features & Use Cases

  • Uniform intake workflow that seeds matter.md, history.md, and a log entry for portfolio visibility.
  • Generates a slug and ensures a unique log row for each matter.
  • Supports later updates with a consistent narrative and event history.

Quick Start

Initiate a uniform matter intake by collecting all fields and generating matter.md, history.md, and a new log row.

Frequently Asked Questions about matter-intake

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

FAQPage Schema
How do I standardize new matter intake for portfolio visibility?

Standardizing new matter intake involves collecting uniform fields for identification, conflicts, and risk triage, then generating a matter.md file, a seeded history.md, and a structured log row in _log.yaml.

What information is needed for a legal matter intake workflow?

A legal matter intake workflow requires details on identification, conflicts checks, source, materiality, outside counsel, assigned owners, legal hold status, and key dates to ensure complete portfolio visibility and accurate risk triage.

How does matter.md generation work with frontmatter and slug creation?

Matter.md generation works by creating a unique slug for the new matter and using frontmatter to structure the standardized intake data, ensuring each matter has a unique log row and consistent narrative for future updates.

Can I use this approach to perform conflicts checks and assign matter owners?

Yes, you can use this approach to perform conflicts checks and assign matter owners, as the uniform intake workflow explicitly collects this information to standardize the new matter before seeding records.

What is the best way to log new matters into a portfolio system?

The best way to log new matters into a portfolio system is appending a structured row to _log.yaml, which links the generated slug, matter.md, and history.md records for consistent portfolio visibility and event tracking.

When should I initiate a uniform matter intake process?

You should initiate a uniform matter intake process when a user says "new matter" or "intake this matter," signaling the need to bring a new legal matter into the portfolio with standardized records.