How do I install the Weekly Report Gxp skill?

Run npx skillmds@latest add g-xps/weekly-report-gxp in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Weekly Report Gxp safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Weekly Report Gxp?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Weekly Report Gxp free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Weekly Report Gxp?

G-xps (@g-xps) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Weekly Report Gxp by g-xps — Agent Skill

Name: Weekly Report Gxp
Author: G-xps

Weekly Report Gxp

Generate developer weekly reports for one person or a team from git commits, todo/issues, meeting notes, and user-provided report content. Use when the user asks to create a weekly report, specify a member such as GXP, summarize coding work plus meetings, or export a polished HTML weekly report.

G-xps 0b911d9 7 files · 46.8 KB Updated Sep 17, 2026

File contents

Weekly Report GXP

Generate developer weekly reports with member attribution. Prefer the deterministic scripts in scripts/ and keep the report grounded in local project data.

Workflow

Confirm or infer report period. Default to current Monday through Sunday.
Resolve target members. If the user specifies names, filter output to those members. If not, generate a team report.
Collect sources:
- Git commits with scripts/collect_git.py.
- Todo/issue files with scripts/parse_tasks.py.
- Meeting notes with scripts/parse_meetings.py.
- Manual content with scripts/parse_user_content.py.
Aggregate with scripts/aggregate_report_data.py.
Render HTML with scripts/render_report.py using assets/styles.css.

Inputs

members.json: maps real member names to git authors, emails, short names, and mention aliases.
todo.md, TODO.md, issues.md, ISSUES.md, or tasks.json: task status and owners.
meeting-notes.md or meetings/*.md: meeting attendees, decisions, risks, and action items.
problems.md/json, growth.md/json, knowledge.md/json, risks.md/json, next-plans.md/json, or user-input.json: manual report content.

Read references/input-formats.md when creating or debugging input files. Read references/data-schema.md before changing aggregation or rendering. Read references/report-sections.md before changing report layout.

Output

Write generated files under a user-specified output directory, or weekly-report-output/ by default:

report-data.json
weekly-report-<member-or-team>-<end-date>.html

Notes

If the target project is not a git repository, continue with tasks, meetings, and manual content.
Do not invent accomplishments. Use empty-state text when a section has no data.
Preserve the user's Chinese names and wording in report content.
This skill outputs HTML only.

---name: weekly-report-gxpdescription: Generate developer weekly reports for one person or a team from git commits, todo/issues, meeting notes, and user-provided report content. Use when the user asks to create a weekly report, specify a member such as GXP, summarize coding work plus meetings, or export a polished HTML weekly report.---# Weekly Report GXPGenerate developer weekly reports with member attribution. Prefer the deterministic scripts in `scripts/` and keep the report grounded in local project data.## Workflow1. Confirm or infer report period. Default to current Monday through Sunday.2. Resolve target members. If the user specifies names, filter output to those members. If not, generate a team report.3. Collect sources: - Git commits with `scripts/collect_git.py`. - Todo/issue files with `scripts/parse_tasks.py`. - Meeting notes with `scripts/parse_meetings.py`. - Manual content with `scripts/parse_user_content.py`.4. Aggregate with `scripts/aggregate_report_data.py`.5. Render HTML with `scripts/render_report.py` using `assets/styles.css`.## Inputs- `members.json`: maps real member names to git authors, emails, short names, and mention aliases.- `todo.md`, `TODO.md`, `issues.md`, `ISSUES.md`, or `tasks.json`: task status and owners.- `meeting-notes.md` or `meetings/*.md`: meeting attendees, decisions, risks, and action items.- `problems.md/json`, `growth.md/json`, `knowledge.md/json`, `risks.md/json`, `next-plans.md/json`, or `user-input.json`: manual report content.Read `references/input-formats.md` when creating or debugging input files. Read `references/data-schema.md` before changing aggregation or rendering. Read `references/report-sections.md` before changing report layout.## OutputWrite generated files under a user-specified output directory, or `weekly-report-output/` by default:- `report-data.json`- `weekly-report-<member-or-team>-<end-date>.html`## Notes- If the target project is not a git repository, continue with tasks, meetings, and manual content.- Do not invent accomplishments. Use empty-state text when a section has no data.- Preserve the user's Chinese names and wording in report content.- This skill outputs HTML only.

Frequently asked questions