agentsclimarketplace
Sign in

Weekly report gxp

Skill 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.From its SKILL.md

Install
npx -y skills add G-xps/weekly-report-gxp

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.2 KB, 430 tokens by cl100k_base, as published. Nobody here has run it

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

  1. 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.

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.

What ships with it: 34 files

2325.0 KB alongside SKILL.md, 8 of them executable

assets/

examples/

references/

scripts/

ui/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.