smith-report

Generate client-facing project reports from vault logs, git history, specs, and audits.

50|8|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/ATTCKDigital/smith --skill smith-report
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: smith-report
Source: https://github.com/ATTCKDigital/smith/tree/main/skills/smith-report
Command: npx skills add https://github.com/ATTCKDigital/smith --skill smith-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Smith Client Report Generator synthesizes vault session logs, git history, spec artifacts, and audit results into polished, client-facing narratives, saving time and improving project transparency.

Core Features & Use Cases

  • Generate client-facing reports by aggregating vault logs, git history, specs, and audits into a cohesive narrative.
  • Support multiple report types (progress, decisions, specs, full) and date ranges to cover any project period.
  • Produce deliverables suitable for clients or stakeholders with clear summaries, decisions, and changelogs.

Quick Start

Run smith-report with a date range and report type to generate a client-facing report for your project.

Frequently Asked Questions about smith-report

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

FAQPage Schema
How do I generate client-facing project reports from vault logs and git history?▼

Generate client-facing project reports by synthesizing vault session logs, git history, spec artifacts, and audit results into a cohesive narrative. You simply specify a date range and report type to aggregate multi-source data into a client-ready document.

What types of client reports can I create for project stakeholders?▼

Supported client report types include progress, decisions, specs, and full audit reviews. Each type synthesizes vault logs and audit data into a polished narrative tailored for stakeholder communication across a configurable project period.

Can I use vault session logs and spec artifacts to produce a period-based project narrative?▼

Yes, vault session logs and spec artifacts are aggregated alongside git history and audit results to produce period-based narratives. This synthesis transforms raw project data into a clear, client-ready narrative for any specified date range.

What's the best way to automate client communication for project audits and progress?▼

Automating client communication is best achieved by synthesizing audit results and vault logs into a narrative report. Configuring the report type and date range allows you to consistently produce client-ready deliverables covering decisions, specs, and progress.

Does generating project reports require multi-source data aggregation?▼

Yes, generating these project reports requires gathering multi-source data from vault session logs, git history, spec artifacts, and audit results. The skill applies this aggregation automatically to present a unified client-ready output.

When should I use a full audit review instead of a progress report?▼

Use a full audit review when you need comprehensive coverage of audit results across one or more projects, whereas a progress report focuses on period-based advancements. Both synthesize vault logs and git history into client-facing narratives.