Admins & Office Work16 min readUpdated Nov 1, 2026

How to Combine Claude Cowork and the Internal-Comms Skill for a Recurring Weekly 3P Update

Use Claude Cowork to gather the week's project material, then apply the internal-comms skill pattern to produce a consistent weekly 3P update.

claude coworkclaude skills3p updatesweekly reportingleadership updates

Workflow summary

Quote this workflow accurately

Markdown version
Best for
A weekly 3P update means Progress, Plans, Problems . It is meant to show leadership what moved, what comes next, and where a decision or support is needed. It often fails for one of two reasons: collecting updates fro...
Input
A Claude plan with Cowork available: Pro, Max, Ultra, Team, or Enterprise. Cowork is not listed as available on the Free plan. Team's unified experience may be in beta; Enterprise access can depend on administrator se...
Primary tool
Claude Skills and Claude Cowork
Output
Use Claude Cowork to gather the week's project material, then apply the internal-comms skill pattern to produce a consistent weekly 3P update.
Main risk
Archive or exclude old files from source inspection and request a dated source map. Remove recycled claims during review.
Verification step
Only current week files support current week claims; old reports remain historical context. Every significant Progress and Problem statement traces to a real source and a defensible date. Owners, deadlines, and decisi...

Continue from this article

Warning: This workflow combines agentic file inspection with reusable communication rules. Give Claude access only to the current reporting workspace; exclude confidential or unrelated records. Treat every generated statement as a draft until a person verifies the source, owner, date, and leadership implication. Never send a leadership update automatically.

Cowork requirements at a glance: Claude Cowork on Pro, Max, Ultra, Team, or Enterprise (subject to Team beta and Enterprise administrator settings); a current-week source set, reporting rules, a reviewer, and optional Skills access. For a local folder, start the task on Claude Desktop and keep that app open during local-file access. Cloud-only input does not require a running desktop computer.

Problem and who this is for

A weekly 3P update means Progress, Plans, Problems. It is meant to show leadership what moved, what comes next, and where a decision or support is needed. It often fails for one of two reasons: collecting updates from several documents takes too long, or the writer starts composing before checking what actually happened this week. The result can omit a blocker, promote a plan into completed work, or repeat last week's status as new progress.

This workflow is for executive assistants, operations coordinators, chiefs of staff, project administrators, and team leads who prepare the same 3P report every week. The output is a short leadership-ready draft supported by a prepared status file, an explicit unresolved-items list, and an approval checkpoint.

Why Cowork fits this workflow

Cowork is useful for the collection and preparation stage. Give it a narrow workspace, ask it to inventory current-week status notes, meeting summaries, project exports, and outstanding issues, and request a source-grounded draft input. It can structure the information and identify conflicts before you ask for a polished report.

The internal-comms skill is a separate writing layer. Anthropic maintains a public internal-comms skill example that explicitly includes 3P updates. It is a reference you can inspect and, if appropriate, install or adapt; it is not evidence that it is already enabled in every Claude account. For stricter team-specific reporting, use the private weekly-3p-writer skill developed below. Cowork prepares the facts; the skill applies a consistent communication format to the human-approved facts.

Claude Cowork is now available in Claude on desktop, web, and mobile. In the unified experience, describe the task in the conversation; if your account still shows a separate Cowork choice, select it. On Pro, Max, and Ultra, new Cowork tasks run in the cloud by default. A cloud session does not automatically have access to your entire computer or reporting folder.

Why not ordinary Claude chat or a skill alone?

A single chat can write a reasonable 3P when all the week's evidence is already attached. The recurring problem is deciding which files count, checking their dates and reliability, separating current from archived material, and preserving a review trail. A writing skill alone does not supply the evidence or certify it. A plugin is not required for this workflow.

| Component | Job | Boundary | | --- | --- | --- | | Cowork | Inspect authorized files; inventory and normalize the week's evidence | Do not finalize the leadership message before review | | Human reviewer | Confirm facts, ownership, blockers, sensitivities, and omissions | Approve the prepared input; do not assume the model verified it | | Public internal-comms skill or private weekly-3p-writer | Turn approved input into a stable, neutral 3P message | Do not introduce unsupported owners, dates, or success claims | | Human sender | Authorize distribution | No automatic email, chat, or publication |

Prerequisites

  • A Claude plan with Cowork available: Pro, Max, Ultra, Team, or Enterprise. Cowork is not listed as available on the Free plan. Team's unified experience may be in beta; Enterprise access can depend on administrator settings.
  • A limited current-week dataset with source dates and meaningful filenames, plus permission to process it in the organization's approved Claude environment.
  • Skills available and code execution enabled if you will install or use a skill. Anthropic documents Skills separately from Cowork, including some Free-plan availability; that does not mean Free includes Cowork.
  • A short standard format in 3p-format.txt and a leadership-watchouts.txt file of approved recurring escalation concerns.
  • A human owner who can validate the prepared status input and the final report.

Set up the reporting workspace

Use the same conceptual structure each week:

current-week/
archive-previous-weeks/
final-updates/
review-notes/
3p-format.txt
leadership-watchouts.txt

current-week/ contains only the present reporting period's source files. archive-previous-weeks/ is historical context, not current evidence. review-notes/ stores corrections and approvals. 3p-format.txt specifies audience, length, tone, Progress/Plans/Problems sections, and a conditional Support needed line. leadership-watchouts.txt lists standing issues to check, but it must never be treated as proof that those issues were active this week. Save the finished report in final-updates/ and retain the approved prepared input for auditability.

Choose one input path before starting:

  1. Desktop-connected local workspace: Set up this folder on your computer and connect only the reporting folder to Claude Desktop. Start the Cowork task on Desktop. Desktop must remain open while Claude reaches local files. You can later review that session on web or mobile. A new cloud task may fetch the local files it needs through the desktop bridge; it is not local-only processing.
  2. Cloud-available materials: Upload only the approved current-week files and the two rules documents to the Cowork session or a suitable account project. Do not assume a project created from a local folder appears as a browsable folder on mobile. Use downloaded outputs or manually save approved results to your reporting folder if direct local writeback is unavailable.

Confirm on your actual account whether each needed source is available to the chosen Cowork session, and whether the requested final-updates folder writeback is offered. If not, download and save the results manually.

The following JSON is a copy-and-paste instruction block, not a Claude API request or an importable Cowork configuration file:

{
  "project_name": "Recurring Weekly 3P Update",
  "project_purpose": "Prepare a traceable weekly status input, then write a 3P leadership update from the approved material.",
  "project_instructions": [
    "Use only current-week files unless I explicitly approve historical comparison.",
    "Never treat archive-previous-weeks as evidence of current-week progress.",
    "List each source filename, date, and the facts it supports.",
    "Prepare a status input first; stop for human approval before drafting the final 3P.",
    "Separate completed work, next plans, blockers, uncertainties, and watchouts.",
    "Do not invent progress, owners, dates, dependencies, or support requests.",
    "Use the selected communication skill only after the status input is approved.",
    "Do not send externally or overwrite source documents.",
    "Save reviewed outputs in final-updates where the current session supports it."
  ],
  "file_naming": "weekly-3p-update-yyyy-mm-dd"
}

This block describes desired behavior. Creating a folder or pasting JSON does not itself install a skill, bind files, or create a scheduled task.

Build or select the writing skill

Anthropic's public internal-comms skill explicitly covers 3P updates. Its public repository also contains an examples/3p-updates.md guide. Use it as a public reference after reviewing the package and license; verify whether the skill is available or enabled in your own account. It may not match your organization's required 3P sections, owners, or escalation conventions.

For a recurring team-specific report, create a private skill named weekly-3p-writer instead. Anthropic documents a skill folder with a Markdown instruction file and a name and description in YAML frontmatter. The public examples use SKILL.md. Use this starter file inside a weekly-3p-writer folder:

---
name: weekly-3p-writer
description: Draft source-grounded weekly Progress, Plans, Problems leadership updates from human-approved prepared status input using our team format.
---

# Weekly 3P Writer

Use only when the reviewer has approved the prepared weekly status input. Do not inspect additional sources or invent facts.

## Required format
1. Progress: completed work with source-supported owner or date where known.
2. Plans: upcoming actions, owners, and dates only when supported.
3. Problems: blockers, operational implications, and unresolved dependencies in neutral language.
4. Support needed: one line only when the approved input states a concrete leadership decision or request.
5. Confirmation needed: unresolved names, dates, claims, and missing evidence.

## Guardrails
- Never convert planned work into completed work.
- Never infer an owner, deadline, cause, metric, or promise.
- Distinguish current-week facts from archived context.
- Mark uncertainty as [CONFIRM].
- Keep the report concise, factual, and appropriate for leadership.
- Draft only; never send.

Anthropic's custom skill guide describes ZIP packaging with the skill directory as the root, adding and enabling the skill under Customize > Skills, and testing activation with example requests. Read and inspect the files before uploading. Avoid scripts, credentials, or unnecessary resources. The public examples and Help Center use different filename capitalization, so follow the current upload validator if it requests a specific spelling.

Check that the chosen public or private skill is enabled for the reporting account and that a trial 3P request actually uses it. Skill invocation is not guaranteed by a prompt that names the skill.

Numbered workflow: from this week's evidence to the final 3P

1. Collect and isolate the current week's inputs

Move or copy only this week's notes, meeting decisions, project status exports, and relevant blockers into current-week/. Keep old weeks archived. Put approved standing escalation criteria into leadership-watchouts.txt; do not include sensitive personnel notes or unrelated documents. Give files descriptive names and dates.

2. Ask Cowork to prepare an evidence-based status input

Start the task in Claude Desktop if it must inspect the local folder. For approved files supplied directly in a cloud session, start in the applicable Claude surface. Use this JSON prompt:

{
  "task": "Inspect the current reporting week and prepare a source-grounded 3P status input, not the final leadership update",
  "input": {
    "current_week": "current-week or explicitly attached current-week sources",
    "format": "3p-format.txt",
    "standing_watchouts": "leadership-watchouts.txt",
    "archive": "archive-previous-weeks, excluded unless separately approved"
  },
  "rules": [
    "Inventory source filenames and dates before summarizing.",
    "Separate Progress evidence, next Plans, Problems, watchouts, and unresolved items.",
    "Mark conflicts, missing dates, unclear ownership, and unsupported claims as [CONFIRM].",
    "Do not treat a standing watchout as a current fact without current evidence.",
    "Do not copy historical progress into the current week.",
    "Do not draft a polished 3P or contact leadership yet.",
    "Do not rename, delete, or overwrite source files."
  ],
  "output": {
    "source_inventory": "Filename, date, and contribution of each source",
    "prepared_status_input": "Progress, Plans, Problems, and support requests separated with source references",
    "conflicts_and_gaps": "Claims needing a human decision or further evidence",
    "approval_gate": "Stop and ask the reviewer to approve or revise this input"
  }
}

If Claude cannot reach a referenced local folder, stop and fix access. Do not let it manufacture an update from the format file or the prior report.

3. Verify the status input

Compare each claimed milestone to the actual file or source system. Check whether a completed item is merely planned, whether an owner or due date came from evidence, and whether any open blocker was omitted. Review leadership-watchouts.txt separately. Document approved changes in review-notes/; only then treat the status input as verified. If sources disagree, carry the disagreement into [CONFIRM] until resolved.

4. Run a small skill trigger test

Using a sanitized approved sample, ask: "Apply my weekly-3p-writer skill to these approved status facts; include Progress, Plans, Problems and a support-needed line only if supported." Check the headings and the absence of invented details. If the custom skill does not activate, check its description and enabled status. The plain 3p-format.txt rules provide a manual fallback if the skill is unavailable.

5. Draft from the approved input, using the writing skill

{
  "task": "Draft a concise weekly 3P leadership update from the human-approved prepared status input",
  "input": {
    "approved_status_input": "PASTE OR ATTACH THE HUMAN-APPROVED STATUS INPUT",
    "writing_skill": "enabled internal-comms or private weekly-3p-writer",
    "format_rules": "3p-format.txt",
    "watchouts": "approved and verified items only"
  },
  "rules": [
    "Use the approved input as the only source of current-week facts.",
    "Write Progress, Plans, and Problems as separate sections.",
    "Write a Support needed line only when a source supports a specific ask.",
    "Keep blockers factual and neutral; mark unresolved items [CONFIRM].",
    "Never add unsupported owners, deadlines, outcomes, or new claims.",
    "Do not send, post, or publish the update."
  ],
  "output": {
    "leadership_update": "Concise 3P draft with conditional Support needed line",
    "review_flags": "Unverified claims requiring follow-up before distribution"
  }
}

6. Review the draft with a person who knows the work

Compare the result with the approved input, not just with the last report. Check current dates, owner assignments, sensitive project language, status claims, and the support-needed request. Send only the reviewed version through the organization's ordinary communication channel. Do not allow Claude to send it automatically.

7. Save the reviewed output and archive deliberately

Use the naming pattern weekly-3p-update-yyyy-mm-dd. Save the approved draft and the prepared status input in final-updates/ when folder writeback is available, or download and save them manually. Keep old material in the archive; do not grant Claude permission to delete or move previous source files just to tidy the workspace.

Make the workflow repeat weekly without bypassing review

A weekly schedule is useful for collecting and preparing the input, not for mailing a report without supervision. In Claude, open the Scheduled sidebar and create a recurring weekly task that requests only source inventory, normalization, and [CONFIRM] flags. Anthropic removed /schedule from the slash-command picker on October 29, 2026; typing it may fill a scheduling request, but the sidebar is the clearer starting point.

  • Cloud-only scheduled preparation: With approved cloud-available sources, a scheduled Cowork task can run without your computer awake or Claude Desktop open.
  • Local-folder scheduled preparation: A scheduled task can reach a connected local folder only while Claude Desktop is open and available. The schedule itself can run in the cloud, but file access is still dependent on that bridge.
  • Human gate: At the scheduled run's end, request a prepared status file and unresolved-items list. Open and approve them manually, then launch the separate writing step. Do not assume a scheduled task can obtain approval later while nobody is present.

In this Claude account, confirm the Scheduled sidebar is available, the permitted frequency, the skill is usable in the scheduled session, and all current-week sources are accessible at run time. If not, run the preparation step manually.

For future weekly runs use this repeatable preparation prompt:

{
  "task": "Prepare the weekly 3P source review for human approval",
  "scope": "current-week only; archived material excluded",
  "rules": [
    "Inventory current sources and cite the filename and date for each claimed fact.",
    "Separate completed work, plans, problems, standing watchouts, and unclear items.",
    "Do not produce or send a final 3P until a human approves the input.",
    "If sources are unavailable, report blocked instead of inventing progress."
  ],
  "deliverables": [
    "Prepared status input",
    "Source map",
    "Unresolved-items list"
  ]
}

Expected output

A successful weekly run produces a current-week source inventory, prepared status input, visible [CONFIRM] items, a short Progress/Plans/Problems draft, a conditional Support needed line, and a saved review trail. The source inventory should let someone trace a claim back to the weekly note or status export it came from. The finished message is still sent by a human.

Tool-specific instructions, permissions, and safety

Cowork uses Manually approve, Automatically approve, and Skip all approvals permission terminology. Automatically approve uses safety checks and can ask for approval; Skip all approvals removes automatic checks. These modes do not replace the article's separate approve-the-evidence requirement. Use Manually approve for this cautious reporting workflow, and do not grant permission to delete or modify sources. Permanent deletion still requires explicit approval.

Claude's plugins are account-saved, not inherently local-only, but this article does not require one. If you add a connector or plugin, get organizational authorization and give it the smallest permissions possible. A connector does not make all internal data suitable for a leadership recap.

For questions about Cowork setup, see the Claude Cowork tool hub and the Claude Skills tool hub. For additional examples, see the Anthropic Workflows series.

Quality checks

  1. Only current-week files support current-week claims; old reports remain historical context.
  2. Every significant Progress and Problem statement traces to a real source and a defensible date.
  3. Owners, deadlines, and decisions are not invented and unresolved items retain [CONFIRM] labels.
  4. Plans never become completed Progress in the writing stage.
  5. The final update uses consistent headings, neutral blocker language, and a support request only where supported.
  6. The scheduled run has not skipped human approval or automatically sent anything.
  7. The status input, final draft, and any corrections are available for future auditing without implying the model remembers them automatically.

Common failure modes and fixes

Last week's progress appears as new work

Archive or exclude old files from source inspection and request a dated source map. Remove recycled claims during review.

The skill produces a polished but inaccurate report

Correct the prepared input and rerun the writing stage. A skill improves presentation consistency, not source truth.

The scheduled task runs but no local status files are found

Check Claude Desktop availability and connected-folder access. Report blocked for that run, not a blank or invented leadership update. Consider supplying the minimum approved files directly to a cloud session if policy permits.

The weekly task consumes too much setup time

Keep current-week/ small, maintain a stable 3p-format.txt, and isolate one reporting stream. A custom skill is worthwhile when the team uses the same structure consistently; otherwise a saved format file and manual prompt may be simpler.

A support-needed request is stronger than the evidence

Replace the assertion with a clearly labeled question or [CONFIRM], and ask the owner to approve the request before distribution.

Sources Checked

  • Anthropic, Get started with Claude Cowork (accessed 2026-11-01): https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork
  • Anthropic, Use Claude Cowork on web, desktop, and mobile (accessed 2026-11-01): https://support.claude.com/en/articles/15520349-use-claude-cowork-on-web-desktop-and-mobile
  • Anthropic, Claude Cowork product guide: Getting started (accessed 2026-11-01): https://claude.com/resources/guides/claude-cowork-product-guide/getting-started
  • Anthropic, Cowork changelog (accessed 2026-11-01): https://claude.com/docs/cowork/changelog
  • Anthropic, What are skills? (accessed 2026-11-01): https://support.claude.com/en/articles/12512176-what-are-skills
  • Anthropic, How to create custom skills (accessed 2026-11-01): https://support.claude.com/en/articles/12512198-how-to-create-custom-skills
  • Anthropic, Use plugins in Claude (accessed 2026-11-01): https://support.claude.com/en/articles/13837440-use-plugins-in-claude-cowork
  • Anthropic public internal-comms Skill example (accessed 2026-11-01): https://github.com/anthropics/skills/blob/main/skills/internal-comms/SKILL.md
  • Anthropic public skill-creator example (accessed 2026-11-01): https://github.com/anthropics/skills/blob/main/skills/skill-creator/SKILL.md

Quarterly Refresh Flag

Review on 2027-02-01 for account-specific skill availability, custom skill upload and activation, Claude unified UI, scheduled task source access, and permission model changes.

Something off in this workflow?

Related Workflows

How to Use Claude Skills to Turn Scattered Project Notes Into a Weekly 3P Leadership Update

Use Claude Skills to turn scattered project notes, meeting bullets, and deadline fragments into a clean Progress, Plans, Problems leadership update.

Read Workflow

How to Use Claude Cowork to Turn a Folder of Drafts Into a Board or Leadership Meeting Packet

Use Claude Cowork to inventory meeting drafts, resolve missing or duplicate files, and assemble a board packet with human approval and without overwriting sources.

Read Workflow

How to Turn a Calendar of Meetings Into a Weekly Executive Brief With AI

Convert a week of meetings into a clear executive brief with outcomes, decisions, and follow ups using ChatGPT, Claude, or Gemini.

Read Workflow
Reader Feedback

Help keep PromptedWork sharp

Share a broken step, outdated prompt, or general feedback. This is only for improving this specific workflow.