briefing

Generate a markdown project briefing from MCP knowledge data.

24|9|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/norrietaylor/distillery --skill briefing-norrietaylor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: briefing
Source: https://github.com/norrietaylor/distillery/tree/main/skills/briefing
Command: npx skills add https://github.com/norrietaylor/distillery --skill briefing-norrietaylor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This knowledge-management skill condenses scattered notes, meeting transcripts, and updates into a single, project-wide dashboard that highlights recent entries, pending corrections, expiring items, stale knowledge, and items needing review.

Core Features & Use Cases

  • Solo and team knowledge briefing: generate a current overview for a project.
  • Display sections for Recent Entries, Corrections, Expiring Soon, Stale Knowledge, and Unresolved items, plus Team Activity and Related items when multiple authors are present.
  • Leverage MCP tools to fetch data, compute relationships, and surface a readable Markdown briefing for quick decision-making.

Quick Start

Ask for a project briefing to generate the latest knowledge dashboard.

Frequently Asked Questions about briefing

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

FAQPage Schema
How do I generate a knowledge dashboard from scattered project notes and updates?

To generate a knowledge dashboard, you can request a project briefing to automatically aggregate recent entries, corrections, expiring items, stale knowledge, and unresolved work into a concise Markdown overview for quick decision-making.

Can I get a team knowledge briefing that tracks multiple authors and related entries?

Yes, team knowledge briefing supports multiple authors by automatically detecting team activity, surfacing related entries from teammates, and including the review queue alongside standard project sections in the Markdown output.

How does MCP API orchestration work for fetching and synthesizing project knowledge?

MCP API orchestration works by coordinating distillery_list, distillery_relations, and distillery_search calls to fetch project data, compute relationships, and synthesize the results into a readable Markdown briefing with gracefully omitted empty sections.

What is the best way to track stale knowledge and expiring items in a knowledge-management workflow?

The best way to track stale knowledge and expiring items is to generate a project briefing, which automatically identifies and surfaces these categories in dedicated sections to help you prioritize corrections and updates.

Do I need any specific dependencies or components to generate a project knowledge briefing?

No specific dependencies or components are required to generate a project knowledge briefing, as the skill operates independently and orchestrates necessary MCP API data fetching internally to compose the Markdown dashboard.

Why are empty sections omitted from my project knowledge briefing?

Empty sections are omitted gracefully from the project knowledge briefing to ensure the Markdown dashboard remains concise and readable, displaying only sections like Recent Entries, Corrections, or Team Activity when they contain relevant data.