Weekly
ballred/obsidian-claude-pkm
Facilitate weekly review process with reflection, goal alignment, and planning.
Write a weekly engineering status report for a team, service, or initiative.
MITAuto-check passed
Install Engineering Weekly Report
$ npx skills add mohitagw15856/pm-claude-skills --skill engineering-weekly-report -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills engineering-weekly-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/engineering-weekly-report .claude/skills/engineering-weekly-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 "engineering-weekly-report" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/engineering-weekly-report into .claude/skills/engineering-weekly-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "engineering-weekly-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/engineering-weekly-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 engineering-weekly-report -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills engineering-weekly-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/engineering-weekly-report .agents/skills/engineering-weekly-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 "engineering-weekly-report" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/engineering-weekly-report into .agents/skills/engineering-weekly-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "engineering-weekly-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 engineering-weekly-report -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills engineering-weekly-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/engineering-weekly-report .cursor/skills/engineering-weekly-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 "engineering-weekly-report" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/engineering-weekly-report into .cursor/skills/engineering-weekly-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "engineering-weekly-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/engineering-weekly-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 engineering-weekly-report -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills engineering-weekly-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/engineering-weekly-report .gemini/skills/engineering-weekly-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 "engineering-weekly-report" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/engineering-weekly-report into .gemini/skills/engineering-weekly-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "engineering-weekly-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 engineering-weekly-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 engineering-weekly-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/engineering-weekly-report .github/skills/engineering-weekly-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 "engineering-weekly-report" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/engineering-weekly-report into .github/skills/engineering-weekly-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "engineering-weekly-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 engineering-weekly-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 engineering-weekly-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/engineering-weekly-report .opencode/skills/engineering-weekly-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 "engineering-weekly-report" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/engineering-weekly-report into .opencode/skills/engineering-weekly-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "engineering-weekly-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
engineering-weekly-report- GitHub stars
- 1.4k
- Token cost
- ~2.1k tokens
- SKILL.md length
- 1,086 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Write a weekly engineering status report for a team, service, or initiative.
- Works in 5 steps: [Priority item] — [One sentence: what… → [Priority item] — [One sentence: what… → [Priority item] — [One sentence: what… → …
- Asked to write a team update
- SKILL.md covers Required Inputs, Output Format, Shipping Progress and Key Metrics, plus 8 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Engineering Weekly Report is an agent skill from mohitagw15856/pm-claude-skills. Write a weekly engineering status report for a team, service, or initiative. Use when asked to write a team update, weekly engineering report, sprint status email, or standing team communication to stakeholders. Produces a concise, scannable weekly report covering shipping progress, metrics, decisions, blockers, and next-week priorities.
Its SKILL.md is about 2.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 to write a team update
- Weekly engineering report
- Sprint status email
- Standing team communication to stakeholders
Example prompts
- “/engineering-weekly-report”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- [Priority item] — [One sentence: what done looks like and who owns it]
- [Priority item] — [One sentence: what done looks like and who owns it]
- [Priority item] — [One sentence: what done looks like and who owns it]
- [Priority item] — [One sentence: what done looks like and who owns it]
- [Priority item] — [One sentence: what done looks like and who owns it]
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
Engineering Weekly Report loads about 2.1k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 1,086 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). 1,086 words, ~2,140 tokens.
Download SKILL.mdSave it as
.claude/skills/engineering-weekly-report/SKILL.md (or your agent's skills folder).- name
- engineering-weekly-report
- description
- Write a weekly engineering status report for a team, service, or initiative. Use when asked to write a team update, weekly engineering report, sprint status email, or standing team communication to stakeholders. Produces a concise, scannable weekly report covering shipping progress, metrics, decisions, blockers, and next-week priorities.
Engineering Weekly Report
Produce a weekly engineering status report that a team can send to stakeholders, their engineering manager, and the team itself. The format is fixed week-over-week so readers know exactly where to look — shipping progress at the top, decisions in the middle, risks and next steps at the bottom. The report must be readable in under 2 minutes. Avoid prose walls: use bullet points, status tags, and short tables. If metrics are not provided, leave the metrics section with [data needed] markers rather than fabricating numbers.
Required Inputs
Ask for these if not already provided:
- Team name and report period — team name plus week number or date range (e.g., "Platform Team, Week 21, May 12–16")
- Work items shipped this week — what was completed and released or merged
- Work items in progress — what is actively being worked on, with rough percent-complete if known
- Blocked items — what is blocked, who owns the block, and what is needed to unblock
- Key decisions made — any architecture, process, or priority decisions made this week
- Decisions needed next week — any decisions that need to be made soon and who needs to make them
- Risks and escalations — anything that threatens next week's commitments or needs leadership visibility
- Next week's top priorities — the 3–5 things the team plans to accomplish next week
Optional but useful:
- Key metrics — reliability (error rate, p99 latency), velocity (story points completed), or other health indicators
- Team health notes — PTO, new joins, attrition, morale signals worth noting
- Sprint or iteration number — if the team runs sprints
Output Format
Engineering Weekly Report — [Team Name]
Week: [Week Number] | [Date Range, e.g., May 12–16, 2025] Author: [Name or Team Lead] Distribution: [e.g., Eng leadership, Product, Team]
Shipping Progress
Shipped This Week
| Item | Description | Impact |
|---|---|---|
| [Feature / Fix / Infra change] | [One-line description] | [Who benefits / what it unblocks] |
| [Feature / Fix / Infra change] | [One-line description] | [Who benefits / what it unblocks] |
| [Feature / Fix / Infra change] | [One-line description] | [Who benefits / what it unblocks] |
In Progress
| Item | Owner | Status | Target Ship |
|---|---|---|---|
| [Work item] | [Name] | [~40% / On Track / At Risk] | [Date or Sprint] |
| [Work item] | [Name] | [~70% / On Track / At Risk] | [Date or Sprint] |
| [Work item] | [Name] | [~20% / On Track / At Risk] | [Date or Sprint] |
Blocked
| Item | Blocked Since | Blocker Description | Owner | Needed To Unblock |
|---|---|---|---|---|
| [Work item] | [Date] | [What is blocking progress] | [Name] | [Specific ask — decision, resource, dependency] |
If no items are blocked: No active blockers.
Key Metrics
Metrics reported as of [Date]. Prior week in parentheses.
| Metric | This Week | Last Week | Trend | Target |
|---|---|---|---|---|
| Error rate (5xx) | [X%] | [X%] | [↑ / ↓ / →] | < [threshold] |
| p99 latency | [Xms] | [Xms] | [↑ / ↓ / →] | < [threshold] |
| Deployment frequency | [X deploys] | [X deploys] | [↑ / ↓ / →] | [target] |
| Story points completed | [X] | [X] | [↑ / ↓ / →] | [sprint target] |
| On-call page volume | [X pages] | [X pages] | [↑ / ↓ / →] | < [threshold] |
Metrics notes: [Any context that makes the numbers meaningful — e.g., "Error rate spike on Tuesday tied to downstream dependency outage, resolved by EOD."]
If metrics are not provided: replace table rows with [data needed — provide metric values for this section].
Decisions
Made This Week
| Decision | Rationale | Owner | Stakeholders Informed |
|---|---|---|---|
| [Decision description] | [Why — 1 sentence] | [Name] | [Yes / No — who] |
| [Decision description] | [Why — 1 sentence] | [Name] | [Yes / No — who] |
If no decisions were made: No major decisions this week.
Needed Next Week
| Decision | Context | Deadline | Decision Owner |
|---|---|---|---|
| [What needs to be decided] | [Why it matters, what happens if delayed] | [Date] | [Name or role] |
If no decisions are pending: No decisions pending.
Risks and Escalations
| Risk | Likelihood | Impact | Mitigation | Escalate To |
|---|---|---|---|---|
| [Risk description] | [High/Med/Low] | [High/Med/Low] | [What we're doing about it] | [Name/role if escalation needed] |
Escalations this week: [Any item that needs immediate leadership attention — call it out explicitly here, do not bury it in a table row. If none: "None."]
Team Health
| Item | Status |
|---|---|
| Team capacity this week | [X of Y people at full capacity] |
| PTO / out of office | [Names and dates, or "None"] |
| New joins / departures | [Name, role, and date, or "None"] |
| On-call this week | [Name] |
| On-call next week | [Name] |
Team notes: [Any morale, workload, or team dynamic signals worth surfacing — keep this factual and constructive. If nothing to note: omit this line.]
Show full SKILL.md (421 more words)Show less
Next Week's Priorities
The [3–5] things this team will ship or meaningfully advance next week.
- [Priority item] — [One sentence: what done looks like and who owns it]
- [Priority item] — [One sentence: what done looks like and who owns it]
- [Priority item] — [One sentence: what done looks like and who owns it]
- [Priority item] — [One sentence: what done looks like and who owns it]
- [Priority item] — [One sentence: what done looks like and who owns it]
Capacity risk: [If the team is at reduced capacity next week (PTO, incidents, etc.), note it here so stakeholders calibrate expectations.]
Appendix: Sprint Scorecard (if applicable)
| Sprint | Committed | Completed | Completion Rate | Carried Over |
|---|---|---|---|---|
| Sprint [N-1] | [X pts] | [X pts] | [X%] | [X pts] |
| Sprint [N] (current) | [X pts] | [X pts — partial] | [X% at midpoint] | TBD |
Questions or corrections: [Slack channel or email] | Next report: [Date]
Quality Checks
- Every blocked item names a specific owner and states what is concretely needed to unblock it — not just "waiting on X"
- Decisions-needed table includes a deadline and a named decision owner, not a vague "TBD"
- Metrics table is either populated with real numbers or explicitly marked
[data needed]— no fabricated metrics - Next week's priorities are written as outcomes ("ship X", "complete Y migration") not as activities ("work on X")
- Escalations that need leadership attention are called out explicitly in the Risks section — not just buried in a table row
- The entire report is readable in under 2 minutes — if it is longer than one printed page, trim it
- Report period (week number and date range) is clearly stated in the header
Anti-Patterns
- Do not fabricate metrics — if data is not available, mark the field as
[data needed]rather than estimating; stakeholders making decisions on invented numbers is actively harmful - Do not write next week's priorities as activities ("work on X") — they must be outcomes ("ship X", "complete Y migration") so stakeholders can evaluate whether the team delivered
- Do not bury escalations inside a risk table row — anything needing leadership attention must be called out explicitly in the Escalations section
- Do not list blocked items without naming a specific owner and a concrete unblocking action — "waiting on X" is not a blocker entry, it is a placeholder
- Do not write a report that exceeds two printed pages — length signals the author has not done the editorial work of deciding what matters to stakeholders
Example Trigger Phrases
- "Write a team update."
- "Write the weekly engineering report."
- "Write our sprint status email."
- "Update stakeholders on the team's week."
© 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/engineering-weekly-report of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Engineering Weekly 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 |
|---|---|---|---|---|---|---|
| Engineering Weekly Report this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Weeklyballred/obsidian-claude-pkm | 1.9k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Weeklykv0906/pm-kit | 138 | — | ~627 | Automated safety check: Notes | MIT | |
| Weekly Project Digeststhedotmack/claude-mem | 99k | — | ~3.5k | Automated safety check: Pass | Apache-2.0 | |
| Weekly Review PlanningNousResearch/hermes-agent | 252k | — | ~994 | Automated safety check: Pass | MIT | |
| Weekly Reviewalirezarezvani/claude-skills | 28k | — | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
Weekly
kv0906/pm-kit
Weekly review — 3-phase process (Collect/Reflect/Plan). An agent skill from kv0906/pm-kit.
Weekly Project Digests
thedotmack/claude-mem
Turns a project's claude-mem timeline into a week-by-week narrative, splitting it by ISO week and running one subagent per week that receives the prior week's carry-forward block.
Weekly Review Planning
NousResearch/hermes-agent
Weekly reset: commitments, stalled work, next-week plan. An agent skill from NousResearch/hermes-agent.
Weekly Review
alirezarezvani/claude-skills
A skill your agent uses when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says…
HTML Ppt Weekly Report
nexu-io/open-design
OpenDesign's weekly growth review: stars, installs, activation — the number, the driver, and the recommended move.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit 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.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
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.
Questions about Engineering Weekly Report
What does Engineering Weekly Report do?
Write a weekly engineering status report for a team, service, or initiative. Engineering Weekly Report is an agent skill from mohitagw15856/pm-claude-skills. Write a weekly engineering status report for a team, service, or initiative.
When should I use Engineering Weekly Report?
Engineering Weekly Report fits situations like: asked to write a team update; weekly engineering report; sprint status email; standing team communication to stakeholders.
How do I install Engineering Weekly Report in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill engineering-weekly-report -a claude-code`. Or copy the skill folder (skills/engineering-weekly-report in mohitagw15856/pm-claude-skills) into .claude/skills/engineering-weekly-report in your project. Claude Code loads it when a task matches its description.
How do I install Engineering Weekly Report in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill engineering-weekly-report -a codex`. Or copy the skill folder (skills/engineering-weekly-report in mohitagw15856/pm-claude-skills) into .agents/skills/engineering-weekly-report in your project. Codex loads it when a task matches its description.
Can I use Engineering Weekly 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 engineering-weekly-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/engineering-weekly-report, .gemini/skills/engineering-weekly-report, .github/skills/engineering-weekly-report and .opencode/skills/engineering-weekly-report in your project.
What does Engineering Weekly Report need to run?
SKILL.md names no scripts, command-line tools or credentials: Engineering Weekly Report is instructions for the agent only.
Does Engineering Weekly 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 Engineering Weekly 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 Engineering Weekly Report use?
Engineering Weekly 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 Engineering Weekly Report use?
About 2.1k tokens (SKILL.md is roughly 8.6k 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 Engineering Weekly Report?
Skills that share tags, products or a category with Engineering Weekly Report: Weekly (ballred/obsidian-claude-pkm, 1.9k stars), Weekly (kv0906/pm-kit, 138 stars), Weekly Project Digests (thedotmack/claude-mem, 99k stars) and Weekly Review Planning (NousResearch/hermes-agent, 252k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Engineering Weekly Report?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,433 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 8, 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.