skills.rest
ArtRiv
ArtRivCOMMUNITY
Explore all skills by this author →
GitHub

gsd-session-report

Generate a SESSION_REPORT.md with outcomes, work summary, and token usage estimates.

Updated Feb 11, 2026
Search Tags:#documentation#workflow execution#estimation#handoff#token usage#outcomes#session report
One-click install
npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-session-report-artriv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-session-report
Source: https://github.com/ArtRiv/game-topicos-especiais/tree/main/.github/skills/gsd-session-report
Command: npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-session-report-artriv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It converts a rough end-of-session recap into a consistent, structured SESSION_REPORT.md that’s easy to review and share, including work summary, outcomes, and estimated token usage.

Core Features & Use Cases

  • Session report generation: Produces a SESSION_REPORT.md artifact suitable for post-session handoff or documentation.
  • Token usage estimation: Includes estimates of resource usage to support budgeting and future planning.
  • Work summary and outcomes: Organizes what was done and what was achieved in a clear format.

Use case example: after a development or support session, generate a report capturing tasks completed, resulting changes or findings, and estimated token costs for transparency.

Quick Start

Use the gsd-session-report skill to run the session-report workflow and produce a SESSION_REPORT.md artifact with outcomes, work summary, and token usage estimates.

Frequently Asked Questions about gsd-session-report

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

FAQPage Schema
How do I generate a session report for post-session documentation and handoff?▼

To generate a session report, execute the session-report workflow end-to-end from its specified path. This produces a structured SESSION_REPORT.md artifact capturing work summaries, outcomes, and estimated token usage for handoff.

What is the best way to document workflow execution outcomes for team review?▼

Documenting workflow execution outcomes is best handled by generating a structured session report. It organizes completed tasks and resulting findings into a consistent markdown format suitable for post-session review and sharing.

Can I use session notes to create a structured markdown report?▼

Yes, you can convert rough session notes into a structured markdown report. The workflow processes your end-of-session recap to produce a SESSION_REPORT.md deliverable with standardized sections for work performed and outcomes.

Does session report generation require any dependencies or external components?▼

Session report generation requires no external dependencies or components. You only need to execute the session-report workflow end-to-end from the specified workflow path to produce the final markdown artifact.

When should I use a structured session report instead of manual documentation?▼

You should use a structured session report when you need consistent post-session handoff documentation with token usage estimation. It is specifically designed for end-to-end workflow runs where standardized sharing and review are required.

Related Skills

Explore More Software Engineering Skills→
mbtzmbtz
1

obsidian-memory-capture

Capture Codex assistant answers from session JSONL files into Obsidian inbox notes.

Community
Intermediate
dobrinz123dobrinz123

gsd-session-report

Generate a structured SESSION_REPORT.md with outcomes and token usage estimates.

Community
Intermediate
GenproMMGenproMM

gsd-session-report

Generate session reports with token usage estimates and work summaries.

Official
Intermediate
gesmith0606gesmith0606

gsd-session-report

Generate a Markdown SESSION_REPORT.md with task summaries, outcomes, and token estimates.

Community
Intermediate