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

Warning: This workflow mixes agentic file handling and reusable formatting rules. Limit Cowork to the weekly project workspace and keep sensitive files out unless they are truly needed for the report.

Cowork requirements at a glance: Claude Desktop, a paid Claude plan (Pro/Max/Team/Enterprise), and Cowork research preview access.

If Claude Cowork is new to you

Start with the Claude Cowork explainer page in the site's Tools menu before you run this workflow. Cowork runs in Claude Desktop and can work on the local files you choose to share. For related examples, see the Claude Cowork tool hub and the Anthropic Workflows series. In a hybrid workflow, let Cowork gather and process files, then let a Skill shape the final output format.

If Claude Skills is new to you

Start with the Claude Skills explainer page in the site's Tools menu before you run this workflow. The short version is that Skills are reusable instruction bundles Claude can load for repeatable work. The public skills repository also makes good reference material when you want to copy the pattern into a private skill for your own team. You can also browse the Claude Skills tool hub and the Anthropic Workflows series.

Problem and who this is for

A weekly 3P update goes wrong in two common ways. Either you gather the weekly material manually and waste time, or you draft too early and the report reflects what is easiest to write rather than what actually happened. The hybrid fix is simple: let Cowork gather and prep the material, then let the internal-comms skill shape the final update.

This workflow is for admins, project coordinators, chiefs of staff, and ops leads who have recurring weekly reporting.

Prerequisites

• Claude Desktop with Cowork.
• Claude Skills access.
• One local weekly reporting folder or Cowork project.
• A standard 3P format your audience already understands.

How to gather the source material

1. Create one workspace per project or reporting stream.
2. Put the current week's notes, exports, memos, and email summaries in that workspace.
3. Keep one small file called 3p-format.txt with your preferred structure and length.
4. Archive old weeks into a subfolder so Cowork does not mix them into the current run.
5. If there is a standing leadership concern, record it in leadership-watchouts.txt.

Numbered workflow steps

1) Use Cowork to gather and normalize the weekly source material

{
  "task": "Prepare a weekly project status input set for a 3P update",
  "input": {
    "workspace_folder": "LOCAL FOLDER PATH",
    "format_file": "3p-format.txt",
    "watchouts_file": "leadership-watchouts.txt"
  },
  "rules": [
    "Inspect only the current week's material.",
    "Create one clean summary input file for the final writer stage.",
    "Separate completed work, next actions, blockers, and open questions.",
    "Do not write the final 3P yet."
  ],
  "output": {
    "verified_status_input_file": "Path to the prepared input file",
    "missing_or_unclear_items": "What still needs human confirmation"
  }
}

2) Review the prepared input file

This is the checkpoint between gathering and writing. Fix anything obviously wrong here instead of in the final 3P.

3) Apply the internal-comms skill pattern to write the final 3P

{
  "task": "Write a weekly 3P leadership update from a prepared status input file",
  "input": {
    "prepared_status_input": "PASTE THE CONTENTS OF THE VERIFIED INPUT FILE",
    "format_file": "PASTE 3p-format.txt IF NEEDED",
    "tone": "brief, factual, leadership-ready"
  },
  "rules": [
    "Use the prepared file as the source of truth.",
    "Write only in the Progress, Plans, Problems structure.",
    "Keep uncertainty visible rather than smoothing it over.",
    "End with one line naming the main support needed, if any."
  ],
  "output_format": {
    "type": "plain_text",
    "headings": [
      "Progress",
      "Plans",
      "Problems"
    ]
  }
}

4) Save the output back into the recurring workspace

This matters because next week's run gets easier when the folder already contains one good prior example and a stable format file.

Tool-specific instructions

Why the hybrid setup works

• Cowork is better at workspace-level gathering, file inspection, and local-file handling.
• The internal-comms skill is better at turning normalized input into a standard internal communication format.
• Use the Claude Cowork explainer and Claude Skills explainer pages in the site's Tools menu if either feature is new to you.

Quality checks

1. The final 3P reflects only the current week's material.
2. The prepared input file and the final 3P agree on the main completed items, next actions, and blockers.
3. Nothing from archived weeks leaks into the current report.
4. The final report is short, scannable, and stable enough to reuse next week.

Common failure modes and fixes

Archived material contaminates the current week

Fix: move old weeks into a clearly separate archive folder outside the current working workspace.

The final 3P misses an important blocker

Fix: edit the prepared input file before the writing step instead of asking the final step to improvise.

The workflow feels too heavy

Fix: keep the workspace small. A hybrid workflow is strongest when the same reporting rhythm happens every week.

Sources Checked

• Anthropic Claude Help Center: Get started with Cowork (accessed 2026-03-23) https://support.claude.com/en/articles/13345190-get-started-with-cowork
• Anthropic Claude Help Center: Installing Claude Desktop (accessed 2026-03-23) https://support.claude.com/en/articles/10065433-installing-claude-desktop
• Anthropic Claude Help Center: Use Cowork safely (accessed 2026-03-23) https://support.claude.com/en/articles/13364135-use-cowork-safely
• Anthropic Claude Help Center: Organize your tasks with projects in Cowork (accessed 2026-03-23) https://support.claude.com/en/articles/14116274-organize-your-tasks-with-projects-in-cowork
• Anthropic Claude Help Center: What are Skills? (accessed 2026-03-23) https://support.claude.com/en/articles/12512176-what-are-skills
• Anthropic Claude Help Center: Use Skills in Claude (accessed 2026-03-23) https://support.claude.com/en/articles/12512180-use-skills-in-claude
• GitHub: internal-comms skill in elliepetalmedia/skills (accessed 2026-03-23) https://github.com/elliepetalmedia/skills/tree/main/skills/internal-comms

Quarterly Refresh Flag

Review on 2026-06-21 to confirm any updates to Claude Skills, Cowork availability, mobile dispatch requirements, project behavior, and supported setup paths.