Progressive Jpeg
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing image assets, markup, and CDN or build transforms related to Use progressive JPEG encoding.
Report on an epic or initiative deeper than a status bullet — child work broken down by status, the riskiest unfinished pieces, and honest suggested cuts to hit the date.
MITAuto-check passed
Install Epic Progress Report
$ npx skills add mohitagw15856/pm-claude-skills --skill epic-progress-report -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills epic-progress-report --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/epic-progress-report .claude/skills/epic-progress-report && rm -rf skills-srcUse ~/.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/
Install the "epic-progress-report" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/epic-progress-report into .claude/skills/epic-progress-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "epic-progress-report", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/epic-progress-reportType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill epic-progress-report -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills epic-progress-report --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/epic-progress-report .agents/skills/epic-progress-report && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "epic-progress-report" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/epic-progress-report into .agents/skills/epic-progress-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "epic-progress-report", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill epic-progress-report -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills epic-progress-report --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/epic-progress-report .cursor/skills/epic-progress-report && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "epic-progress-report" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/epic-progress-report into .cursor/skills/epic-progress-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "epic-progress-report", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/epic-progress-report--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill epic-progress-report -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills epic-progress-report --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/epic-progress-report .gemini/skills/epic-progress-report && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "epic-progress-report" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/epic-progress-report into .gemini/skills/epic-progress-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "epic-progress-report", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills epic-progress-reportInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill epic-progress-report -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/epic-progress-report .github/skills/epic-progress-report && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "epic-progress-report" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/epic-progress-report into .github/skills/epic-progress-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "epic-progress-report", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill epic-progress-report -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills epic-progress-report --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/epic-progress-report .opencode/skills/epic-progress-report && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "epic-progress-report" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/epic-progress-report into .opencode/skills/epic-progress-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "epic-progress-report", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
epic-progress-report- GitHub stars
- 1.4k
- Token cost
- ~1k tokens
- SKILL.md length
- 531 words
- Files
- 1
- Skills in repo
- 1,322
- Repo updated
- First seen
- Licence
- MIT
At a glance
Report on an epic or initiative deeper than a status bullet — child work broken down by status, the riskiest unfinished pieces, and honest suggested cuts to hit the date.
- Works in 5 steps: Remaining work, not just percent. Report… → Status by child, honestly. Blocked and… → Name the riskiest pieces. Dependencies,… → …
- Asked for an epic progress report
- SKILL.md covers What This Skill Produces, Required Inputs, Framework: Progress You Can… and Output Format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Epic Progress Report is an agent skill from mohitagw15856/pm-claude-skills. Report on an epic or initiative deeper than a status bullet — child work broken down by status, the riskiest unfinished pieces, and honest suggested cuts to hit the date. Use when asked for an epic progress report, where are we on this initiative, break down epic status, or what can we cut to ship on time. Produces the completion picture by child status, the critical-path and riskiest remaining work, a scope-cut menu with impact, and a straight call on whether the target date is realistic.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked for an epic progress report
- Where are we on this initiative
- Break down epic status
- What can we cut to ship on time
Example prompts
- “/epic-progress-report”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Remaining work, not just percent. Report what's left and how hard it is — the last 20% is often the risky 80%.
- Status by child, honestly. Blocked and not-started are different from in-progress; don't average them into a comforting number.
- Name the riskiest pieces. Dependencies, unknowns, and the one hard component are where dates die — call them out.
- Offer cuts, don't just warn. A scope-cut menu with impact turns "we might slip" into a decision the team can make.
- Give a straight date call. "On track," "at risk — here's why," or "won't make it without cuts." Vague green status is the enemy.
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Epic Progress Report loads about 1k tokens when it runs. Until then it costs about 129 tokens; SKILL.md has 531 words of instructions outside code blocks.
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 mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 531 words, ~1,011 tokens.
Download SKILL.mdSave it as
.claude/skills/epic-progress-report/SKILL.md (or your agent's skills folder).- name
- epic-progress-report
- description
- Report on an epic or initiative deeper than a status bullet — child work broken down by status, the riskiest unfinished pieces, and honest suggested cuts to hit the date. Use when asked for an epic progress report, where are we on this initiative, break down epic status, or what can we cut to ship on time. Produces the completion picture by child status, the critical-path and riskiest remaining work, a scope-cut menu with impact, and a straight call on whether the target date is realistic.
Epic Progress Report
"Epic is 60% done" is the least useful sentence in delivery — 60% of what, and is the remaining 40% the easy part or the terrifying part? This breaks the epic into its child work by status, surfaces the pieces most likely to blow the date, and — instead of just reporting — offers a cut menu and an honest read on whether the deadline survives contact with reality.
What This Skill Produces
- The completion picture — child items grouped by status (done / in progress / not started / blocked), with what % and which work remains
- The riskiest remaining work — the unfinished pieces most likely to slip (unknowns, dependencies, the hard 20%)
- The cut menu — what could be descoped or deferred, and the impact of each cut
- The date call — will it make the target as-is; if not, what has to give
Required Inputs
Ask for these if not provided:
- The epic & its children — the stories/tasks under it and their statuses (a board export or list)
- The target date & goal — what "done" means for this epic and when it's needed
- Dependencies & unknowns — anything waiting on another team, or work that's still fuzzy
- Who it's for — a standup, a stakeholder, or a go/no-go — tunes depth and bluntness
Framework: Progress You Can Act On
- Remaining work, not just percent. Report what's left and how hard it is — the last 20% is often the risky 80%.
- Status by child, honestly. Blocked and not-started are different from in-progress; don't average them into a comforting number.
- Name the riskiest pieces. Dependencies, unknowns, and the one hard component are where dates die — call them out.
- Offer cuts, don't just warn. A scope-cut menu with impact turns "we might slip" into a decision the team can make.
- Give a straight date call. "On track," "at risk — here's why," or "won't make it without cuts." Vague green status is the enemy.
Output Format
Show full SKILL.md (214 more words)Show less
Epic: [name] · target [date] · for [audience]
Completion
| Status | Count | Which work |
|---|---|---|
| ✅ Done | ||
| 🔨 In progress | ||
| ⬜ Not started | ||
| ⛔ Blocked |
Riskiest remaining
- [item] — why it's risky (unknown / dependency / complexity).
Cut menu (to protect the date)
| Could cut/defer | Saves | Impact if cut |
|---|
Date call
On track / At risk / Won't make it without cuts — because [reason].
Quality Checks
- Remaining work is described, not just a percentage
- Children are grouped by real status (blocked ≠ in-progress ≠ not-started)
- The riskiest unfinished pieces are named with why
- A concrete cut menu with impact is offered, not just a risk warning
- A straight date call is made — not a vague "green"
- No invented statuses — unknowns are marked unknown
Anti-Patterns
- A single % with no breakdown — hides where the risk is.
- Averaging blocked and not-started into a reassuring number.
- Warning of slip with no options — leaves the reader stuck.
- Watermelon status (green outside, red inside) — a comfortable date call that isn't true.
- Guessing a child's status instead of flagging it unknown.
Example Trigger Phrases
- "Give me an epic progress report for the checkout revamp."
- "Where are we really on this initiative, and can we cut to hit the date?"
- "Break down this epic's status by child work and flag the risky bits."
- "Is this epic going to make the deadline? What would we have to drop?"
© mohitagw15856, 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 skills/epic-progress-report of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Epic Progress 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Epic Progress Report this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1k | Automated safety check: Pass | MIT | |
| Progressive Jpegthedaviddias/Front-End-Checklist | 74k | — | ~426 | Automated safety check: Pass | MIT | |
| Initiate SetupNousResearch/hermes-agent | 252k | — | ~2.3k | Automated safety check: Pass | MIT | |
| Breakdown Epic Pmgithub/awesome-copilot | 40k | 1 repos | ~575 | Automated safety check: Pass | MIT | |
| Progressive Buildingn8n-io/n8n | 207k | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Epic Games AutomationComposioHQ/awesome-claude-skills | 77k | 3 repos | ~742 | Automated safety check: Pass | None |
Similar skills
Initiate Setup
NousResearch/hermes-agent
Run the first-run setup chat in the Hermes desktop app. An agent skill from NousResearch/hermes-agent.
- Official
Breakdown Epic Pm
github/awesome-copilot
Prompt for creating an Epic Product Requirements Document (PRD) for a new epic.
- Official
Progressive Building
n8n-io/n8n
Load before build-workflow and before scoping or planning new workflows and feature additions, including requests spanning multiple workflows.
Epic Games Automation
ComposioHQ/awesome-claude-skills
Automate Epic Games tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.
- Official
Create Epic Recap
DataDog/datadog-agent
A skill your agent uses when an engineer or manager asks to recap, summarize, or post an update on a Jira Epic — a progress update for an in-progress Epic (how far along it is, what's shipped so…
More from mohitagw15856/pm-claude-skills
All 1,322 skills in this repoExit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Offer Comparison
mohitagw15856/pm-claude-skills
Compare two or more job offers as total-comp curves over four years — vesting cliffs, bonuses, 401(k) match, and the crossover year computed, not vibed.
Refinance Breakeven
mohitagw15856/pm-claude-skills
Compute the month a refinance actually starts saving money — payment delta, breakeven month, and total interest on both paths including the term-reset trap.
Rent Vs Buy
mohitagw15856/pm-claude-skills
Model rent-vs-buy honestly — year-by-year net position for both paths including the assumption everyone drops (the renter invests the difference), with a breakeven horizon instead of a verdict.
Questions about Epic Progress Report
What does Epic Progress Report do?
Report on an epic or initiative deeper than a status bullet — child work broken down by status, the riskiest unfinished pieces, and honest suggested cuts to hit the date. Epic Progress Report is an agent skill from mohitagw15856/pm-claude-skills. Report on an epic or initiative deeper than a status bullet — child work broken down by status, the riskiest unfinished pieces, and honest suggested cuts to hit the date.
When should I use Epic Progress Report?
Epic Progress Report fits situations like: asked for an epic progress report; where are we on this initiative; break down epic status; what can we cut to ship on time.
How do I install Epic Progress Report in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill epic-progress-report -a claude-code`. Or copy the skill folder (skills/epic-progress-report in mohitagw15856/pm-claude-skills) into .claude/skills/epic-progress-report in your project. Claude Code loads it when a task matches its description.
How do I install Epic Progress Report in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill epic-progress-report -a codex`. Or copy the skill folder (skills/epic-progress-report in mohitagw15856/pm-claude-skills) into .agents/skills/epic-progress-report in your project. Codex loads it when a task matches its description.
Can I use Epic Progress 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 mohitagw15856/pm-claude-skills --skill epic-progress-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/epic-progress-report, .gemini/skills/epic-progress-report, .github/skills/epic-progress-report and .opencode/skills/epic-progress-report in your project.
What does Epic Progress Report need to run?
SKILL.md names no scripts, command-line tools or credentials: Epic Progress Report is instructions for the agent only.
Does Epic Progress Report access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Epic Progress 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 Epic Progress Report use?
Epic Progress 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 Epic Progress Report use?
About 1k tokens (SKILL.md is roughly 4k 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 Epic Progress Report?
Skills that share tags, products or a category with Epic Progress Report: Progressive Jpeg (thedaviddias/Front-End-Checklist, 74k stars), Initiate Setup (NousResearch/hermes-agent, 252k stars), Breakdown Epic Pm (github/awesome-copilot, 40k stars) and Progressive Building (n8n-io/n8n, 207k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Epic Progress Report?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,431 GitHub stars. The repository holds 1,322 skills in this directory. The repository was last updated on October 7, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.