Agent skill

Report

by andrew-yangy in andrew-yangy/gru-ai

CEO dashboard with progressive disclosure — 3 tiers: headline (5 lines, default), summary (per-goal detail), deep (full weekly analysis).

MITAuto-check passedAgent Workflows

Install Report

skills CLI
$ npx skills add andrew-yangy/gru-ai --skill report -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install andrew-yangy/gru-ai report --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/andrew-yangy/gru-ai.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/report .claude/skills/report && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
report
GitHub stars
155
Token cost
~4k tokens
SKILL.md length
732 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
MIT

At a glance

CEO dashboard with progressive disclosure — 3 tiers: headline (5 lines, default), summary (per-goal detail), deep (full weekly analysis).

  • Works in 4 steps: Determine Tier → Gather Data → Generate Report → …
  • Agent Workflows work in your project
  • SKILL.md covers Role Resolution, Step 1: Determine Tier, Step 2: Gather Data and Step 3: Generate Report, plus 3 more sections
  • Calls git and npm

What it does

Report is an agent skill from andrew-yangy/gru-ai. CEO dashboard with progressive disclosure — 3 tiers: headline (5 lines, default), summary (per-goal detail), deep (full weekly analysis). Takes an optional argument: headline (default), summary, deep, or legacy aliases daily/weekly.

Its SKILL.md is about 4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows. It works with Git. The repository describes itself as: Autonomous AI agent team for one-man companies. Context engineering + harness engineering drive a pipeline that brainstorms, builds, reviews, and ships. The licence is MIT.

When your agent uses it

  • Agent Workflows work in your project

Example prompts

  • “/report”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Determine Tier
  2. Gather Data
  3. Generate Report
  4. Display Report

What it can do on your machine

Read from SKILL.md and the folder at commit 8fba479. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Report loads about 4k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 732 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from andrew-yangy/gru-ai at commit 8fba479, republished under its MIT licence (© andrew-yangy). 732 words, ~3,967 tokens.

Download SKILL.mdSave it as .claude/skills/report/SKILL.md (or your agent's skills folder).
name
report
description
CEO dashboard with progressive disclosure — 3 tiers: headline (5 lines, default), summary (per-goal detail), deep (full weekly analysis). Takes an optional argument: headline (default), summary, deep, or legacy aliases daily/weekly.

CEO Report

Role Resolution

Read .claude/agent-registry.json to map roles to agent names. Domain labels in this report use role titles (CTO, CPO, CMO, COO) -- resolve to actual agent names from the registry when generating output.


Generate a CEO report. Tier: $ARGUMENTS (default: headline)

Step 1: Determine Tier

Parse $ARGUMENTS:

  • If empty or "headline" or "h" → headline tier
  • If "summary" or "s" or "daily" or "d" → summary tier
  • If "deep" or "weekly" or "w" → deep tier

Step 2: Gather Data

What to read depends on the tier. Higher tiers include everything from lower tiers.

Headline Tier Data (minimal — fast)
  • .context/directives/*/directive.json — count active goals
  • .context/directives/*/projects/*/project.json — count active/completed/blocked projects, identify recently completed
  • .context/backlog.json — count P0 items needing CEO
  • .context/directives/*.json — count pending directives (filter by status: pending)
  • .context/reports/ — scan 3 most recent for unaddressed high-risk follow-ups
  • .context/healthchecks/latest/*.json — quick health status (pass/fail)
  • Run npm run type-check — build status (pass/fail only, don't show errors here)
Summary Tier Data (adds detail on top of headline)

All headline data, PLUS:

  • .context/vision.md — for context on what matters
  • .context/preferences.md — CEO standing orders
  • .context/intel/latest/*.json — latest scout outputs per agent
  • ~/.conductor/scheduler.json and ~/.conductor/scheduler.log — autopilot status
  • Recent directive reports — corrections caught data
  • Run git commands for recent changes:
bash
# Recent commits on main (last 24h)
git log --oneline --since="24 hours ago" main
# Active worktrees
git worktree list
# Recently modified context files
find .context/ -name "*.md" -mtime -1 -type f | head -20
  • Active projects with no recent progress
  • Failed/blocked initiatives from recent directives
  • OKR progress from .context/directives/*/directive.json
Deep Tier Data (adds weekly analysis)

All summary data, PLUS:

  • .context/reports/ — compute agent acceptance rates from all reports this week
  • .context/lessons/*.md topic files — any new lessons this week?
  • Commit activity distribution by area
  • All directive reports from the past 7 days
  • Previous weekly report for comparison (.context/reports/weekly-*.md)
  • Expand git log to 7 days: git log --oneline --since="7 days ago" main

Step 3: Generate Report

Headline Tier Format (default)

The headline is a 5-line status snapshot. The CEO should know the state of the world in <10 seconds.

# Status — {date}

Shipped: {N} projects completed | Blocked: {N} projects stalled | Needs CEO: {N} decisions pending
Health: {build pass/fail} | {security ok/N issues} | {N active goals}
Top action: {single most important thing the CEO should do next — e.g., "Review 2 high-risk follow-ups from auth-hardening directive" or "Nothing — all clear"}

Derivation rules for headline signals:

  • Shipped: Count projects where status changed to "completed" in the last 24h (compare project.json completed timestamps)
  • Blocked: Count active projects where all tasks are incomplete AND last modification > 7 days ago
  • Needs CEO: Count pending directives + P0 backlog items + unaddressed high-risk follow-ups from recent digests
  • Health: type-check pass/fail + healthcheck summary + active goal count
  • Top action: Priority order: (1) high-risk items needing decision, (2) blocked projects needing unblocking, (3) pending directives awaiting execution, (4) "Nothing — all clear"

If the CEO wants more detail: "Run /report summary for per-goal detail or /report deep for full analysis."

Summary Tier Format
# Summary Report — {date}

## External Intelligence (from latest /scout)
- **Technology (CTO)**: {summary + any act_now/this_week items}
- **Product (CPO)**: {summary + competitor moves}
- **Growth (CMO)**: {summary + channel opportunities}
- **Ecosystem (COO)**: {summary + framework updates}
{If no scout data: "No scout data yet — run /scout to gather external intelligence."}

## Internal Health (from latest /healthcheck)
- **Build status**: {type-check pass/fail}
- **Security**: {npm audit summary}
- **Operations**: {stale goals, backlog health}
{If no healthcheck data: "No healthcheck data yet — run /healthcheck."}

## Autopilot
{Read ~/.conductor/scheduler.json and ~/.conductor/scheduler.log}
- **Status**: {enabled/disabled}
- **Budget**: ${spent_today} / ${daily_max} ({pct}%)
- **Recent launches**: {list directives launched today, or "none"}
- **Last check**: {time of most recent check entry}
{If scheduler.json doesn't exist: "Not configured — run scripts/foreman.sh to initialize."}

## Corrections Caught (from recent directives)
{Read recent directive reports for Corrections Caught data.}
- **Last directive**: {name} — {violations_found} violations found, {violations_fixed} fixed
- **Standing Corrections verified**: {count} across {N} initiatives
{If no recent directive data: "No directive executed recently."}
{If violations were found: list each with correction name and resolution}

## What Changed
{Recent commits, summarized by area. Not a raw git log — group and summarize.}
{Active worktrees/branches and their status.}

## Project Inventory

{Read all .context/directives/*/directive.json and .context/directives/*/projects/*/project.json for project inventory.}

### Active Goals ({count})
| Goal | Active Projects | Done | Backlog | Status |
|------|----------------|------|---------|--------|
| {goal title} | {count} ({list names}) | {done_count} | {backlog_count} | {status badge} |

### Partially-Done Alerts
{For each active feature: read project.json embedded tasks, compute completion %. Flag features where:
- completion > 0% but < 100%
- AND last file modification in the feature folder > 7 days ago}

Warning: **{feature name}** ({goal}) — {X}% complete, stale {N} days
   Last activity: {date} | Tasks: {completed}/{total}

{If no partially-done alerts: "All active projects are either fresh or complete."}

### Completed But Not Archived
{Projects with status "active" but 100% task completion — should have status updated to "completed"}
- {project name} ({goal}) — 100% complete, still status: active

## What Needs Your Input
{Pending directives in directives/ (filter by status: pending) — list with one-line description each}
{High risk items awaiting decision from recent directives}
{Backlog items flagged for CEO decision}
{If nothing: "Nothing pending — all clear."}

## What's At Risk
{Build errors from type-check, if any}
{Stale active projects with no recent changes}
{Failed/blocked initiatives from recent directives}
{If nothing: "No risks identified."}

## Decision Queue

{Aggregate items needing CEO decision from multiple sources:}

### From Recent Directives
{Scan .context/reports/ for the last 3 directive reports.
For each, check the "Follow-Up Actions" section for high-risk backlogged items.
Cross-reference with .context/backlog.json to see if they've been addressed.}

- **{action}** — Backlogged from {directive name} ({date})
  Risk: {high} | Status: {addressed/pending}

### From Backlogs
{Scan all .context/backlog.json for items explicitly marked as needing CEO decision
or items with Priority P0 that are not yet started}

### From Healthchecks
{Read .context/healthchecks/latest/*.json for high-risk findings}

{If nothing: "No pending decisions — all clear."}

## OKR Snapshot
{For each goal with OKRs:}
**{Goal Name}**
- KR-1: {description} — {status} ({metric}: {current} / {target})
- KR-2: ...
Deep Tier Format
# Deep Report — Week of {date}

## Executive Summary
{3-5 bullet overview of the week: what shipped, what's in progress, what needs attention}

## External Intelligence (from latest /scout)
- **Technology (CTO)**: {summary + action items}
- **Product (CPO)**: {summary + competitor moves}
- **Growth (CMO)**: {summary + opportunities}
- **Ecosystem (COO)**: {summary + framework updates}
- **Intelligence gathered this week**: {count by urgency level}
{If no scout data: "No scout data yet — run /scout."}

## Internal Health (from latest /healthcheck)
- **Build status**: {type-check pass/fail}
- **Security**: {npm audit summary, CVE count}
- **Operations**: {goal freshness, backlog health}
- **Auto-fixed this period**: {count and summary}
{If no healthcheck data: "No healthcheck data yet — run /healthcheck."}

## Autopilot
{Read ~/.conductor/scheduler.json and ~/.conductor/scheduler.log}
- **Status**: {enabled/disabled}
- **Budget**: ${spent_today} / ${daily_max} ({pct}%)
- **This week**: {count} directives auto-launched, {total estimated cost}
- **Errors this week**: {count, or "none"}
{If scheduler.json doesn't exist: "Not configured — run scripts/foreman.sh to initialize."}

## What Changed This Week
{Commits grouped by area with counts}
{Directives executed and their outcomes}
{Features completed or progressed}

## Project Inventory

{Read all .context/directives/*/directive.json and .context/directives/*/projects/*/project.json for project inventory.}

### Active Goals ({count})
| Goal | Active Projects | Done | Backlog | Status |
|------|----------------|------|---------|--------|
| {goal title} | {count} ({list names}) | {done_count} | {backlog_count} | {status badge} |

### Partially-Done Alerts
{For each active feature: read project.json embedded tasks, compute completion %. Flag features where:
- completion > 0% but < 100%
- AND last file modification in the feature folder > 7 days ago}

Warning: **{feature name}** ({goal}) — {X}% complete, stale {N} days
   Last activity: {date} | Tasks: {completed}/{total}

{If no partially-done alerts: "All active projects are either fresh or complete."}

### Completed But Not Archived
{Projects with status "active" but 100% task completion — should have status updated to "completed"}
- {project name} ({goal}) — 100% complete, still status: active

## What Needs Your Input
{Same as summary, but covering the full week}

## What's At Risk
{Same as summary, but covering the full week}
{Trend: are risks increasing or decreasing?}

## Decision Queue

{Aggregate items needing CEO decision from multiple sources:}

### From Recent Directives
{Scan .context/reports/ for the last 3 directive reports.
For each, check the "Follow-Up Actions" section for high-risk backlogged items.
Cross-reference with .context/backlog.json to see if they've been addressed.}

- **{action}** — Backlogged from {directive name} ({date})
  Risk: {high} | Status: {addressed/pending}

### From Backlogs
{Scan all .context/backlog.json for items explicitly marked as needing CEO decision
or items with Priority P0 that are not yet started}

### From Healthchecks
{Read .context/healthchecks/latest/*.json for high-risk findings}

{If nothing: "No pending decisions — all clear."}

## What Shifted This Week

{Compare current project inventory against what was reported in the most recent saved weekly report
in .context/reports/weekly-*.md}

### New Work Started
- {feature name} ({goal}) — started this week

### Completed This Week
- {project name} ({goal}) — status changed to completed

### Went Stale (no activity >7 days)
- {feature name} ({goal}) — last activity {date}

### Priority Changes
{Any backlog items that were promoted from /scout this week}

{If no previous weekly report exists: "First weekly report — no comparison available."}

## OKR Progress
{Full OKR breakdown per goal — same as summary but with week-over-week changes if prior report exists}

## Team Performance
{From recent scout reports in .context/intel/latest/:}
- **Proposals this week**: {count} ({count} approved, {count} rejected, {count} deferred)
- **By agent**:
  - CTO: {proposed} proposed, {accepted} accepted ({rate}%)
  - CPO: {proposed} proposed, {accepted} accepted ({rate}%)
  - CMO: {proposed} proposed, {accepted} accepted ({rate}%)
  - COO: {proposed} proposed, {accepted} accepted ({rate}%)

{From directive reports:}
- **Directives completed**: {count}
- **Initiatives**: {completed}/{total} ({rate}%)
- **Build success rate**: {pass}/{total} type-checks passed

{From directive reports this week:}
- **Corrections enforced**: {total corrections checked across all directives}
- **Violations caught**: {count} (by role: CTO {N}, CPO {N}, COO {N})
- **Violation types**: {which standing corrections were violated most}

## Corrections Caught This Week
{Aggregate corrections_check data from all directive reports this week:}

| Correction | Directive | Caught By (role) | Resolution |
|------------|-----------|-------------------|------------|
| {correction} | {directive} | {reviewer role} | {fixed/noted} |

- **Trend**: {more/fewer/same violations as last week}
{If no violations: "Clean week — all standing corrections respected across all directives."}

## Lessons Learned
{New entries in .context/lessons/ topic files from this week}
{If none: "No new lessons captured this week."}

## Recommendations
{COO-style operational recommendations:}
- What should the CEO focus on next week?
- Any goals that need re-prioritization?
- Any process improvements to consider?

Step 4: Display Report

Output the report directly to the CEO. Do NOT write it to a file unless the CEO asks.

For deep tier reports, also offer: "Would you like me to save this report to .context/reports/weekly-{date}.md?"

After any tier, remind: "Drill down with /report summary or /report deep for more detail." (Skip this line if already at deep tier.)

Show full SKILL.md (269 more words)Show less

Failure Handling

SituationAction
No OKR files existSkip OKR section, note "No OKRs tracked yet"
No scout data (intel/latest/)Skip external intelligence section, note "No scout data yet — run /scout"
No healthcheck data (healthchecks/latest/)Skip internal health section, note "No healthcheck data yet — run /healthcheck"
No scout data existsSkip team performance section, note "No scout/patrol data yet"
Type-check fails to runNote the error, skip build health section
No recent commitsNote "No commits in {timeframe}"
No directive reportsSkip directive outcomes section
No active projects foundNote "No active projects tracked yet" in Project Inventory
No tasks in a project.jsonSkip that feature in completion calculations
No previous weekly report for comparisonNote "First weekly report — no comparison available" in Shift Tracking
No conductor reports for Decision QueueNote "No directive history to scan"
No healthcheck data for Decision QueueSkip "From Healthchecks" subsection
No ~/.conductor/scheduler.jsonNote "Autopilot not configured" in Autopilot section
No ~/.conductor/scheduler.logNote "No scheduler activity yet"

Rules

NEVER
  • Create files without CEO requesting it (reports are displayed, not saved by default)
  • Run slow commands (no npm run build, no npm run lint)
  • Modify any files (this is a read-only operation)
  • Include raw git logs (always summarize and group)
ALWAYS
  • Read preferences.md before generating (summary and deep tiers)
  • Show concrete numbers (counts, percentages, dates)
  • Flag items needing CEO action prominently
  • Keep headline tier to exactly 3 lines of content (after the heading)
  • Keep summary reports under 5 minutes reading time
  • Keep deep reports under 15 minutes reading time
  • Group information by importance, not by source
  • Include drill-down hint after headline and summary tiers

© andrew-yangy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/report of andrew-yangy/gru-ai.

Open the folder on GitHubat commit 8fba479

Compare with similar skills

Report next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Report compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Report this skillandrew-yangy/gru-ai155—~4kAutomated safety check: PassMIT
Darwin Skill Optimizeralchaincyf/darwin-skill6.2k1 repos~4.7kAutomated safety check: PassMIT
CodeGraph Agent Evalcolbymchenry/codegraph74k—~950Automated safety check: PassMIT
Neat-Freak Knowledge CloseoutKKKKhazix/khazix-skills21k—~1.9kAutomated safety check: PassMIT
O2 Review Loopopenobserve/openobserve22k—~3.7kAutomated safety check: PassAGPL-3.0
Beads Task Memorygastownhall/beads28k—~1.2kAutomated safety check: PassMIT

Similar skills

  • Darwin Skill Optimizer

    alchaincyf/darwin-skill

    Scores SKILL.md files on a nine-dimension rubric, then improves them in a keep-or-revert loop with independent judge agents, test prompts, git history and human checkpoints.

    6.2k GitHub starsUsed in 1 repo~4.7k tokens
    Agent WorkflowsAuto-check passed
  • CodeGraph Agent Eval

    colbymchenry/codegraph

    Benchmarks how much CodeGraph helps a coding agent on a real repository, comparing runs with and without it for a chosen local or published version.

    74k GitHub stars~950 tokensUpdated 2 days ago
    Agent WorkflowsAuto-check passed
  • Neat-Freak Knowledge Closeout

    KKKKhazix/khazix-skills

    Brings project docs, agent rule files, authorized memory and leftover workspace files back in line with what the code and runtime actually do at the end of a work session.

    21k GitHub stars~1.9k tokensUpdated 8 days ago
    Agent WorkflowsAuto-check passed
  • O2 Review Loop

    openobserve/openobserve

    Splits a change into planner, coder and independent reviewer roles: you confirm a spec, a subagent implements it, and a separate reviewer checks each round's local WIP commit.

    22k GitHub stars~3.7k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Beads Task Memory

    gastownhall/beads

    Tracks multi-session work with dependencies in the bd issue tracker so the agent can find ready tasks and recover its context after conversation compaction.

    28k GitHub stars~1.2k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Searches past Claude Code, Codex and Cursor sessions and summarizes what was worked on, tried or decided, using extraction scripts instead of reading raw logs.

    24k GitHub stars~3.1k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from andrew-yangy/gru-ai

All 9 skills in this repo
  • Code Review Excellence

    andrew-yangy/gru-ai

    Provides comprehensive code review guidance for React 19, Vue 3, Rust, TypeScript, Java, Python, and C/C++.

    155 GitHub stars~1.7k tokensUpdated 7 mo ago
    Auto-check: notes
  • SEO Audit

    andrew-yangy/gru-ai

    Full website SEO audit with parallel subagent delegation. An agent skill from andrew-yangy/gru-ai.

    155 GitHub stars~731 tokensUpdated 7 mo ago
    Auto-check passed
  • Brainstorm

    andrew-yangy/gru-ai

    Structured brainstorm — from quick Socratic refinement to full C-suite strategy sessions.

    155 GitHub stars~3.2k tokensUpdated 7 mo ago
    Auto-check passed
  • Healthcheck

    andrew-yangy/gru-ai

    Internal codebase and operations health check — the CTO scans technical health, the COO checks operational health.

    155 GitHub stars~2.4k tokensUpdated 7 mo ago
    Auto-check passed
  • Smoke Test

    andrew-yangy/gru-ai

    Pipeline end-to-end smoke test -- creates a trivial directive, runs it through /directive, validates every pipeline step, and reports pass/fail with evidence.

    155 GitHub stars~941 tokensUpdated 7 mo ago
    Auto-check passed
  • Directive

    andrew-yangy/gru-ai

    Execute work through the directive pipeline — evaluate, plan, cast agents, build, review, and report.

    155 GitHub stars~2.8k tokensUpdated 7 mo ago
    Auto-check: warnings

Works with

Categories

Questions about Report

What does Report do?

CEO dashboard with progressive disclosure — 3 tiers: headline (5 lines, default), summary (per-goal detail), deep (full weekly analysis). Report is an agent skill from andrew-yangy/gru-ai. CEO dashboard with progressive disclosure — 3 tiers: headline (5 lines, default), summary (per-goal detail), deep (full weekly analysis).

When should I use Report?

Report fits situations like: agent Workflows work in your project.

How do I install Report in Claude Code?

Run `npx skills add andrew-yangy/gru-ai --skill report -a claude-code`. Or copy the skill folder (.claude/skills/report in andrew-yangy/gru-ai) into .claude/skills/report in your project. Claude Code loads it when a task matches its description.

How do I install Report in Codex?

Run `npx skills add andrew-yangy/gru-ai --skill report -a codex`. Or copy the skill folder (.claude/skills/report in andrew-yangy/gru-ai) into .agents/skills/report in your project. Codex loads it when a task matches its description.

Can I use Report in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add andrew-yangy/gru-ai --skill report -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/report, .gemini/skills/report, .github/skills/report and .opencode/skills/report in your project.

What does Report need to run?

Going by SKILL.md and its folder, Report needs the command-line tools its instructions call (git and npm).

Does Report access the network?

SKILL.md contains no URLs. Its commands use git and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Report safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Report use?

Report is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Report use?

About 4k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Report?

Skills that share tags, products or a category with Report: Darwin Skill Optimizer (alchaincyf/darwin-skill, 6.2k stars), CodeGraph Agent Eval (colbymchenry/codegraph, 74k stars), Neat-Freak Knowledge Closeout (KKKKhazix/khazix-skills, 21k stars) and O2 Review Loop (openobserve/openobserve, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Report?

andrew-yangy (a GitHub user) maintains it in andrew-yangy/gru-ai, which has 155 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on March 11, 2026.

Source: andrew-yangy/gru-ai on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.