Report

Posts a project report to a chat destination, at the cadence asked for. Daily: a delta-only standup of overnight signals across every repo the project spans (opened/merged PRs and CI, the latest browser smoke, BUILD-ORDER drift, open-PR state, stale previews). Weekly: an executive recap/retro (merged PRs, shipped epics, deploys per app repo, a retro digest). PMO: the weekly operational report with scrum/DORA/doc-ops metrics and a story deck, or the on-demand monthly stakeholder packet with a metrics sheet. Use when the product owner asks to "post the standup", "run the daily standup", "what ha

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add danybgoode/golden-frijoles --skill report
Manual install
git clone --depth 1 https://github.com/danybgoode/golden-frijoles.git /tmp/golden-frijoles
mkdir -p ~/.claude/skills
cp -r /tmp/golden-frijoles/skills/plugins/golden-frijoles/skills/report ~/.claude/skills/report

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Report — one skill, three cadences

> **Running this skill's scripts.** Each `node scripts/<name>.mjs <args>` below means, from the project root:
> `if [ -f scripts/<name>.mjs ]; then node scripts/<name>.mjs <args>; else npx -y @golden-frijoles/kit@1.17.5 <name> <args>; fi`
> The project's own copy always wins. The kit needs no install and copies nothing into the repo. If npx fails on
> the network or the registry (ENOTFOUND, ECONNREFUSED, ETIMEDOUT, E404, a proxy error), report **could not
> look: the kit is unreachable**, not a broken project, and offer to retry online or to copy the script into
> `scripts/`. This covers the scripts the kit carries (`frijoles-kit --list`). Any other `scripts/` command here is
> project tooling: if the project lacks it, say so and stop. Never re-implement a script's logic inline.
> If a script prints `GF-NEEDS-SETTING {"key",…}`, ask the user that question once, save the answer with
> `npx -y @golden-frijoles/kit@1.17.5 config set <key> <value>` (always the kit, never local-wins: a project
> may own an unrelated `scripts/config.mjs`), tell them they can change it later the same way, and run the
> script again if it exited 7.

One skill, three chapters. Read the chapter for the cadence asked for and follow it exactly, from its first line;
each runs its own script, which does the aggregation, so never re-implement a report inline. Paths in a chapter are
relative to this skill's base directory.
Read the full skill on GitHub

Details

Skill name
report
Path
skills/plugins/golden-frijoles/skills/report/SKILL.md
Repo updated
17 November 2026

FAQ

What does the Report skill do?

Posts a project report to a chat destination, at the cadence asked for. Daily: a delta-only standup of overnight signals across every repo the project spans (opened/merged PRs and CI, the latest browser smoke, BUILD-ORDER drift, open-PR state, stale previews). Weekly: an executive recap/retro (merged PRs, shipped epics, deploys per app repo, a retro digest). PMO: the weekly operational report with scrum/DORA/doc-ops metrics and a story deck, or the on-demand monthly stakeholder packet with a metrics sheet. Use when the product owner asks to "post the standup", "run the daily standup", "what ha

How do I install the Report skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add danybgoode/golden-frijoles --skill report. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Related skills

Babysit PR

danybgoode/golden-frijoles

Advisory PR watch for a single open PR — retries flaky CI (re-runs failed workflow runs) and surfaces merge conflicts via one comment; never merges, never a required check. Use when the product owner asks to "babysit this PR", "check on open PRs", "retry flaky CI", "is this PR stuck", "why isn't this PR moving", or as the nightly ops routine's third step (once per open PR across the project's repos). Runs scripts/babysit-pr.mjs, which does the gh reads, the retry, and the comment post. A clean PR (no conflict, no failing checks) gets NO comment — this tool never adds nightly noise to a healthy

Git & Code ReviewIn 1 list

Build Order Sync

danybgoode/golden-frijoles

Regenerates Roadmap/00-ideas/BUILD-ORDER.md when it has drifted from the SSOT (each epic README's frontmatter status:) and opens a claude/ docs PR with the fix — never hand-edits the board. Use when the product owner asks to "sync the build order", "regenerate BUILD-ORDER.md", "check board drift", "is the build-order board stale", "open a build-order PR", or as the nightly ops routine's first step. Runs scripts/build-order-sync.mjs, which does the check, the regen, and (on real drift) the branch/commit/ push/PR — this skill just invokes it and reports the result.

Git & Code ReviewIn 1 list

Doc Hygiene

danybgoode/golden-frijoles

Keeps the always-read session-start docs (this project's AGENTS.md, Roadmap/WAYS-OF-WORKING.md, Roadmap/LEARNINGS.md, Roadmap/README.md poster) from re-bloating after the one-time de-noise sweep. Use when the product owner asks to "check doc hygiene", "measure LEARNINGS size", "is LEARNINGS bloated again", "run the doc hygiene report", or as the weekly Routine C hygiene pass. Runs scripts/doc-hygiene.mjs, reviews its flagged candidates against the source docs, and emits a dated advisory report. Never edits Roadmap docs — proposals only, the product owner or the builder hand-merges.

Writing & ContentIn 1 list

Brag Doc From Git

agentkitco/agentkit-dev-skills

Build an evidence-based brag doc or self-review draft from your merged PRs and commits, leaving visible gaps where results are unknown. Use for review season, promotion cases or resumes.

Git & Code ReviewIn 1 list

Dependency Upgrade

agentkitco/agentkit-dev-skills

Upgrade one dependency at a time by reading its changelog, planning for breaking changes, updating code and proving it still builds and passes. Use to bump, update or migrate a package.

Git & Code ReviewIn 1 list

PR Description

agentkitco/agentkit-dev-skills

Write a pull request title and description from the actual diff and commits, with what changed, why, how it was tested and what to review. Use when asked to write or improve a PR description.

Git & Code ReviewIn 1 list

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.