Skills weekly-report
📦

weekly-report

Content revision r1 Safe ⚙️ External commands

Create Clear Weekly Work Reports

Weekly reports are hard when work details are scattered. This skill guides collection, structure, and revision so users can produce clear updates.

Supports: Claude Codex Code(CC)
🥉 79 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "weekly-report" from https://skillstore.io/skills/yunshu0909-weekly-report.md and its manifest at https://skillstore.io/api/skills/yunshu0909-weekly-report/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/yunshu0909-weekly-report.md Signed manifest GET /api/skills/yunshu0909-weekly-report/manifest Signed lockfile GET /api/skills/yunshu0909-weekly-report/lockfile

Test it

Using "weekly-report". I fixed checkout bugs, reviewed pull requests, and started payment logging.

Expected outcome:

A draft groups the work into bug fixes, code review, and observability, with status and next steps for each item.

Using "weekly-report". My notes are messy and I do not know what mattered.

Expected outcome:

The skill asks follow-up questions about impact, blockers, owners, and next week priorities before drafting the report.

Using "weekly-report". I need a customer delivery update for this week.

Expected outcome:

A concise report covers customer work, delivery status, open risks, and agreed next actions.

Security Audit

Safe
v5 • 7/8/2026 Open versioned report

The external command findings are false positives from markdown code fences, inline filenames, and example folder paths. The entropy heuristic is also a false positive because SKILL.md is readable Chinese markdown with no binary, encrypted, or prompt-injection content found.

1
Files scanned
247
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (6)
SKILL.md:122-147 SKILL.md:147-189 SKILL.md:189-192 SKILL.md:192-193 SKILL.md:193-197 SKILL.md:197-237
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/yunshu0909-weekly-report/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/yunshu0909-weekly-report/security.svg)](https://skillstore.io/skills/yunshu0909-weekly-report?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/yunshu0909-weekly-report?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/yunshu0909-weekly-report/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/yunshu0909-weekly-report.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

yunshu0909. (2026). weekly-report security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/yunshu0909-weekly-report/audits/5

BibTeX citation

@techreport{yunshu0909-yunshu0909-weekly-report-2026, author = {yunshu0909}, title = {weekly-report security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/yunshu0909-weekly-report/audits/5}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "weekly-report security audit report (audit version 5)" version: "unspecified" type: report authors: - name: "yunshu0909" date-released: "2026-07-08" url: "https://skillstore.io/skills/yunshu0909-weekly-report/audits/5" identifiers: - type: other value: "skillstore:yunshu0909-weekly-report:audit:5" description: "Skillstore immutable audit report identifier"

Compare variants

2 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Highest Skillstore Score
yunshu0909 Recommended Current

yunshu0909-weekly-report

Skillstore Score 79
Evidence Confidence High
Skillstore usage 65
Updated

2026-09-09

zhaobolun-code

zhaobolun-code-weekly-report

Skillstore Score 77
Evidence Confidence Medium
Skillstore usage 1
Updated

2026-09-18

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
69
Community
91
Spec Compliance

What You Can Build

Summarize engineering work

Turn completed features, bug fixes, reviews, blockers, and next steps into a clear weekly engineering update.

Prepare product and operations updates

Organize research, launches, data analysis, user feedback, and follow-up actions into a structured weekly report.

Create team status reports

Convert scattered team notes into a concise report that shows progress, risks, owners, and next week priorities.

Try These Prompts

Draft my weekly report 
Help me write this week's report. Ask what I worked on, then organize it into a clear draft.
Organize scattered notes 
Here are my rough notes: [paste notes]. Group them by work area, identify missing details, and ask concise follow-up questions.
Improve a draft 
Review this weekly report draft. Keep my tone, strengthen the logic, add provided metrics, and clarify blockers.
Prepare a manager-ready update 
Edit my weekly report for my manager. Use these tasks, risks, and next actions. Keep it concise and do not exaggerate.

Best Practices

  • Provide rough notes first, then answer follow-up questions about impact and status.
  • Include numbers, customer feedback, or delivery dates when they are available.
  • Review the final draft for company terminology, sensitive details, and factual accuracy.

Avoid

  • Do not use the skill to exaggerate outcomes or hide unresolved blockers.
  • Do not paste confidential customer or company data unless your environment allows it.
  • Do not accept the final report without checking facts, owners, and next steps.

Frequently Asked Questions

Does this skill write the report from scratch?
Yes. It can start from a blank page by asking questions about your weekly work.
Can it work with messy notes?
Yes. It can group rough notes, identify missing details, and create a structured draft.
Does it support different job roles?
Yes. It includes guidance for engineering, product, operations, design, QA, sales, and general work.
Will it invent metrics or results?
No. The skill asks for measurable details but should not create numbers the user did not provide.
Can it preserve my writing style?
Yes. The workflow asks the assistant to keep the user's expression and adjust only where needed.
Does it connect to Jira, GitHub, or documents?
No. It relies on information provided in the conversation unless other tools are separately available.

Developer Details

Author

yunshu0909

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

https://github.com/yunshu0909/yunshu_skillshub/tree/master/weekly-report

Ref

64ca8af0f54a325752f08bd54e52151061ea659a

Maintenance freshness

7/20/2026

Usage

51 downloads · 123 views

File structure

📄 SKILL.md