What are Claude Code Skills?

Claude Code Skills are reusable prompt templates stored as markdown files in your project's .claude/skills/ directory. They let you codify best practices and common workflows into slash commands that Claude follows consistently.

How do I create a Claude Code Skill?

Create a markdown file in .claude/skills/ with instructions for Claude. The filename becomes the command name — for example, .claude/skills/code-review.md can be invoked with /code-review during a Claude Code session.

Can I share skills with my team?

Yes. Skills stored in .claude/skills/ can be committed to version control so every team member has access to the same standardized workflows. You can also organize skills into subdirectories by category.

What is the difference between project and global skills?

Project skills (.claude/skills/) are specific to the current project and are committed to git. Global skills (~/.claude/skills/) are personal skills available across all your projects.

weekly-report-gxp

New

GitHub TrendingGeneralby G-xps

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.

Community PluginView Source

Overview

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.

Install & Usage

Create the skills directory

mkdir -p .claude/skills

Download the skill file

mkdir -p .claude/skills && curl -o .claude/skills/weekly-report-gxp.md https://raw.githubusercontent.com/G-xps/weekly-report-gxp/main/SKILL.md

Invoke in Claude Code

/weekly-report-gxp

View source on GitHub

Security Audits

LicenseUnknownSourceWarnRepositoryPass

Frequently Asked Questions

What is weekly-report-gxp?

How to install weekly-report-gxp?

To install weekly-report-gxp, create the .claude/skills directory in your project, then run the curl command to download the skill file. Once installed, invoke it in Claude Code with /weekly-report-gxp.

What is weekly-report-gxp best for?

weekly-report-gxp is a community categorized under General. Created by G-xps.