agentsclimarketplace

Weekly report gxp

Skill G-xps/weekly-report-gxp

用于开发人员生成精美周报的skill,遵守开发规范

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.

What its author says it does

Copied from the file, not written here

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.

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.

Gives 0 of the 12 instructions most docs writing skills give in 430 tokens

Counted across 1,637 of the 3,044 authors here whose files we hold, read 2026-08-06

  • announce the skill at startin 54 of 1637, across 21 files
  • convert legacy doc files before editingin 45 of 1637, across 7 files
  • predict questions readers might askin 42 of 1637, across 3 files
  • Generate clarifying questions for initial contextin 42 of 1637, across 3 files
  • Create document scaffold with placeholder textin 42 of 1637, across 3 files
  • Brainstorm content options for each sectionin 42 of 1637, across 3 files
  • Test document with fresh context-less instancein 42 of 1637, across 3 files
  • ask interview questions one at a timein 42 of 1637, across 26 files
  • include exact file paths in every taskin 42 of 1637, across 15 files
  • Apply surgical edits during refinementin 41 of 1637, across 2 files
  • Offer structured workflow or freeformin 40 of 1637, across 1 file
  • Ask for document meta-contextin 40 of 1637, across 1 file

Said here and by no other author read

  • Prefer deterministic scripts over generated logic
  • Infer or confirm the target report period
  • Default to the current Monday through Sunday
  • Filter output to user-specified member names
  • Generate a team report if no members are specified
  • Collect git commits using the provided script

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. 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.