reports

Stores and retrieves timestamped reports by category routing.

1|Updated May 12, 2026
One-click install
npx skills add https://github.com/ltdrew/Agent-brain-2 --skill reports-ltdrew
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reports
Source: https://github.com/ltdrew/Agent-brain-2/tree/main/skills/reports
Command: npx skills add https://github.com/ltdrew/Agent-brain-2 --skill reports-ltdrew

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often generate and share numerous reports that must be organized, indexed, and quickly retrievable. This skill provides timestamped storage with category-based routing to simplify access and reduce search time.

Core Features & Use Cases

  • Timestamped storage of reports to enable chronological retrieval.
  • Keyword- or category-based routing to map queries to the correct report set.
  • Load the latest report for a given category and surface its content for immediate use.

Quick Start

Save a new report with a category, then retrieve the latest report by category.

Frequently Asked Questions about reports

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

FAQPage Schema
How do I organize and retrieve timestamped team reports by category?

Timestamped team reports are organized and retrieved using category-based routing, which maps queries to the correct report set and enables fast chronological access to the latest briefings.

What is the best way to store periodic briefings so I can load the latest one quickly?

Periodic briefings are stored with standardized report frontmatter and a lightweight search index, allowing you to load the latest report for a given category and surface its content immediately.

How does category-based routing work for meeting notes and dashboards?

Category-based routing for meeting notes and dashboards works by applying a routing map that directs keyword or category queries to the correct timestamped report set, simplifying access and reducing search time.

Do I need standardized report frontmatter to use this retrieval approach?

Yes, standardized report frontmatter is required to store and route timestamped reports correctly, alongside a routing map for categories and a lightweight search index to support fast lookups.

Can I retrieve historical reports chronologically using a search index?

Yes, timestamped storage enables chronological retrieval of historical reports, while a lightweight search index supports fast lookups to locate specific past briefings or meeting notes by category.

What are the limitations of using category-based routing for report retrieval?

Category-based routing requires maintaining a routing map and standardized frontmatter for every report; without these structural elements, the lightweight search index cannot accurately map or retrieve stored briefings.