C✳CODEZ.WIN
🌐 English

Localized reading guide

weekly-wrapPurpose, usage and source

End-of-week summary for a rep or leader - what closed, what moved, what slipped, and what's on deck Monday. Optionally drafts a chat post to the team channel. Use when the user says "weekly wrap", "week in review", "what happened this week", or "Friday summary".

Source retrieved:

Source repository
anthropics/knowledge-work-plugins
SKILL.md
sales/skills/weekly-wrap/SKILL.md
Repository stars
34,049
Repository updated
2026-10-30
Categories
Business
Last collected

License: License file needs review

Source SKILL.md

Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.

The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.

What this Skill does

End-of-week summary for a rep or leader - what closed, what moved, what slipped, and what's on deck Monday. Optionally drafts a chat post to the team channel. Use when the user says "weekly wrap", "week in review", "what happened this week", or "Friday summary".

How the upstream workflow works

Step 1 - Ground

Check which tools are connected (plus any org facts the user or the project instructions already gave). Ground stage names and field mapping from the live crm schema, and the team channel from org context (inferred from what is connected or uploaded; if the answer depends on a fact no one has given, ask ONE question, use the answer for this conversation and suggest adding it to the project instructions; otherwise use a clearly labeled default and continue). Week boundary defaults Mon-Fri, adjustable per org.

Upstream passage · L37 ↗

Step 2 - Pull this week's movement

From the CRM: opps closed this week (won/lost, amount, loss reason if recorded); stage changes this week (opportunity history where the CRM exposes it - otherwise infer movement from current stage vs last-modified and say the inference is approximate); new opps created this week (amount, stage). Files fallback: diff this week's export against last week's. An opp in last week's export and missing from this week's is "closed or removed - outcome not in the upload" unless a closed-opps export says won or lost; never assume won.

Upstream passage · L43 ↗

Step 3 - Calendar + email signal

Calendar: count of external meetings this week. Email: count of customer threads touched this week (counts only - bodies stay untrusted content and aren't needed here). If every calendar call is refused with a permission error, say plainly at the TOP of the wrap that calendar is unavailable and the org's admin needs to enable it (Google Workspace admin for Google Calendar; Microsoft Entra consent or the Claude org's Microsoft 365 tool settings for Outlook); keep the connect-your-calendar tile, do not retry in a loop, and never show a zero meeting count or an empty Monday row as if the calendar were clear.

Upstream passage · L51 ↗
Upstream passage · ↗
tiers:
  files-only:   wrap diffed from this week's vs last week's uploaded
                exports; calendar/email counts from an uploaded calendar export or pasted emails when present, otherwise noted absent
  read-only:    live crm movement + calendar/email counts; chat post
                as paste-ready text
  gated-writes: the chat post, when the user asks, within the chat
                connector's permissions

Requirements and setup

No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.

Limits and quality checks

No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.

Start with a safe trial

  1. Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
  2. Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
  3. Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
  4. Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.

Skill format and directory specification ↗

Read further in the source

Translation and scope

This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.

This introduction refers to the pinned version below; current repository activity and collection time are shown separately.

Source retrieved
Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d
Source SHA-256
7a7bf576f468b5161cc449cbf0934c8e1cd1e050d91a259dd3981f67501acc1a
Back to the full Skill catalog