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

If Claude Skills is new to you

Skills are reusable folders of instructions, resources, and optional scripts that Claude can load when a task matches the Skill description. Anthropic's current help says Skills are available on Free, Pro, Max, Team, and Enterprise plans when code execution is enabled.

For this workflow, you only need the basics: create a folder with a Skill.md file, ZIP the folder, upload it in Claude under Customize > Skills, enable it, and test that Claude routes weekly 3P writing requests to the Skill. The Claude Skills tool hub is useful further reading, but the setup steps you need are included below.

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 specific: Cowork gathers and normalizes the week's source material from a local workspace, then a custom Skill shapes the final Progress, Plans, Problems update in the team's house style.

This workflow is for admins, project coordinators, chiefs of staff, and ops leads who have recurring weekly reporting and want the same 3P structure every time.

Why Cowork fits this workflow

The hard part is not only writing a 3P update. The harder recurring work is gathering the current week's material from a local workspace, excluding old material, creating a prepared input file, and saving the finished update back to the same reporting workspace.

Cowork fits that pattern because it can work with the files and folders you choose in Claude Desktop. That lets you keep each weekly run grounded in a stable folder structure instead of rebuilding the context from scratch in a chat window. For this workflow, Cowork is the reusable workspace and source-gathering layer.

Use Cowork to inspect the current-week folder, separate current facts from archived history, create a verified status input file, and place the final output where next week's process can find it.

Why not normal Claude chat or just a Skill?

Normal Claude chat can draft one useful 3P update if you paste all of the source context into the conversation. It is weaker for a recurring folder-based workflow because you still have to gather the files, decide what is current, exclude old weeks, paste or attach the right material, and save the result yourself every time.

A Skill can standardize the writing format, but it does not inspect and organize a local weekly workspace by itself. Use the internal-comms Skill as the repeatable formatting and communication layer after Cowork has prepared the current week's material.

The practical division is simple:

| Tool | Best role in this workflow | | --- | --- | | Claude Cowork | Gather and normalize source material from the current weekly workspace. | | internal-comms Skill | Format the approved prepared input into a consistent Progress, Plans, Problems update. | | Normal Claude chat | Draft only when all source material is already pasted or attached in the chat. |

What skill you will use in this workflow

You can use Anthropic's official internal-comms Skill as the communication pattern for this workflow, or build a private custom Skill called weekly-3p-writer if your team needs stricter house style rules. The Skill's job is to take normalized weekly status material and produce a concise 3P update with stable headings, neutral blocker language, and unresolved items left visible.

Cowork and the Skill have different jobs. Cowork handles workspace-level gathering, file inspection, and normalization. The Skill handles the final writing rules after Cowork has prepared the source material.

This task deserves a Skill because the final weekly update should not change shape every Friday. The custom Skill keeps the same Progress, Plans, Problems sections, team tone, support-needed line, and uncertainty rules across recurring runs.

Prerequisites

• Claude Desktop with Cowork access on a paid Claude plan.
• Claude Skills available and code execution enabled.
• One local weekly reporting folder or Cowork project.
• A standard 3P format your audience already understands.
• A small leadership-watchouts.txt file for standing concerns, known deadlines, or recurring blockers.
• A reviewer who can confirm that owners, dates, blockers, and support-needed lines are accurate.

Set up this workflow as a Cowork project

Create one Cowork project for the recurring weekly report. In Claude Desktop, open Cowork, create a project from scratch or from an existing local folder, and name it something clear such as Recurring Weekly 3P Update.

Use a small folder structure that stays the same every week:

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

Use current-week for only this week's notes, meeting summaries, status exports, and project updates. Move old material into archive-previous-weeks so Cowork does not treat it as current evidence. Save approved leadership updates in final-updates, and keep review corrections or recurring reviewer comments in review-notes.

Put your preferred 3P structure in 3p-format.txt. Put standing leadership concerns, deadlines, sensitive topics, and recurring escalation rules in leadership-watchouts.txt.

Add project instructions so you do not have to paste the same setup every week. Adapt this starter block:

{
  "project_name": "Recurring Weekly 3P Update",
  "project_purpose": "Use Claude Cowork to inspect the current week's project material, create a verified status input file, and then use the internal-comms Skill to produce a consistent Progress, Plans, Problems update.",
  "project_instructions": [
    "Use only files in the current-week folder unless I explicitly approve another source.",
    "Do not pull material from archive-previous-weeks into the current report unless I ask for historical comparison.",
    "Create a verified status input file before drafting the final 3P update.",
    "Keep completed work, upcoming plans, blockers, open questions, and leadership watchouts separate.",
    "Do not smooth over uncertainty or missing information.",
    "Use the internal-comms Skill only after the prepared input file has been reviewed.",
    "Save final updates in the final-updates folder with the date in the file name."
  ],
  "file_naming": "weekly-3p-update-yyyy-mm-dd"
}

The project instructions are the repeatable operating layer. The files provide the weekly facts. The Skill provides the final communication format.

How to gather the source material

1. Create one workspace per project or reporting stream.
2. Put the current week's notes, exports, memos, meeting summaries, and status updates in that workspace.
3. Keep one small file called 3p-format.txt with your preferred structure, length, audience, and tone.
4. Keep one small file called leadership-watchouts.txt with standing concerns, executive priorities, deadlines, or risks to check.
5. Archive old weeks into a clearly separate folder so Cowork does not mix them into the current run.
6. Keep raw source files separate from the final output so you can inspect what Cowork used.

Build the custom skill for this workflow

Create a folder named weekly-3p-writer. Inside it, create a file named Skill.md. Paste the starter Skill below, then edit it so it matches your team's house style, level of detail, and leadership audience.

When the folder is ready, ZIP the folder itself so the ZIP file contains weekly-3p-writer/Skill.md at the root. In Claude, open Customize > Skills, upload the ZIP file, and enable the Skill before you run the workflow.

Use this as a starting template, not a perfect final Skill:

---
name: weekly-3p-writer
description: Use a reusable 3P writing skill after Claude Cowork gathers and normalizes the week's material across files, notes, and updates.
---

# Weekly 3P Writer

Use this skill after Cowork or another preparation step has already gathered the week's source material.

## What this skill should do
- Turn normalized status material into a concise 3P update.
- Keep the structure identical across weekly runs.
- Surface unresolved items clearly.

## Guardrails
- Do not invent progress.
- Do not merge progress and plans.
- Keep blockers neutral.
- Assume Cowork gathered the source material, but still treat the final output as reviewable by a human.

## Examples
- Use this week's normalized project material to write a 3P update.
- Apply my weekly 3P writer after Cowork gathers the source files.
- Draft a consistent leadership update in 3P format.

Optional official Anthropic skill

Anthropic's official internal-comms skill is a useful public reference for internal updates. It can be a shortcut when you need a general internal communication shape and do not need to maintain a separate private Skill.

Use the private weekly-3p-writer Skill for this recurring workflow when one team needs the same 3P sections, tone, escalation language, support-needed line, and house style every week.

Skill-creator helper

Anthropic's official skill-creator skill can help draft or refine your private Skill before you upload it. Review the generated files before enabling any Skill, especially if it includes scripts or bundled resources.

Why this should be a custom skill, not a one-off prompt

Cowork can gather the week's material, but the final 3P still needs stable writing rules. A custom Skill keeps the same sections, blocker language, support-needed pattern, and uncertainty handling available every week. That lowers prompt rewrite friction and makes the output easier for leadership to scan over time.

If the official internal-comms Skill already gives you the tone and structure you need, use it as the formatting layer instead of creating a private Skill. The key point is the same: keep Cowork responsible for gathering and preparing the files, then use a Skill for the repeatable communication shape.

Skill trigger test

After enabling weekly-3p-writer, test it before the full Cowork run is finalized. Use a short prepared status sample with completed work, planned work, blockers, and one unclear item.

Try prompts like:

• Apply my weekly 3P writer to this prepared status material.
• Use the 3P workflow after Cowork finishes gathering the week's notes.
• Draft a concise 3P update from this normalized source set.
• Turn this prepared weekly status file into Progress, Plans, Problems with unresolved items visible.

If Claude does not appear to use the Skill, revise the Skill description so it clearly mentions Cowork, normalized weekly material, 3P updates, Progress, Plans, Problems, and recurring leadership updates.

Numbered workflow steps

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

Open Claude Desktop, switch to Cowork, and select the current weekly workspace or Cowork project. Ask Cowork to inspect only the current week's files and prepare one normalized source file for the writer stage.

Use wording like:

Prepare this workspace for a weekly 3P update. Inspect only the current week's material. Create one normalized status file that separates completed work, planned work, blockers, open questions, and items needing confirmation. Do not write the final 3P yet.

Cowork's output should be a prepared source file or clearly labeled summary, not the final leadership update.

2) Review the prepared input file

Before using the Skill, check Cowork's prepared input file. Confirm that completed work, next plans, blockers, open questions, and leadership watchouts are separated. Remove anything that belongs to a previous week unless you intentionally asked for historical comparison.

The prepared input file is the control point. If it is wrong, fix it before asking for the final 3P update.

3) Create or enable the Skill

If this is your first run, decide whether the official internal-comms Skill is enough or whether you need a private weekly-3p-writer Skill. If you already created your private Skill, open Claude's Skills settings and confirm the Skill is enabled before writing the final update.

This is the handoff point between the two tools: Cowork prepared the material, and the Skill now controls the final writing shape.

4) Run a quick trigger test

Before the final run, paste a short sample from Cowork's prepared file and ask:

Apply my weekly 3P writer to this prepared status material. Keep Progress, Plans, and Problems separate, keep blockers neutral, and flag unresolved items instead of guessing.

Check that Claude writes in the 3P format, uses the prepared material as the source of truth, and does not invent progress, owners, dates, or causes.

5) Run the actual workflow with the Skill active

Paste or attach Cowork's full normalized source file, plus 3p-format.txt and leadership-watchouts.txt if needed. Ask Claude:

Use the internal-comms Skill, following my 3P format, to draft this week's leadership update from the normalized status material Cowork prepared. Use Progress, Plans, and Problems as the headings. Keep the update concise, keep blockers neutral, surface unresolved items, and end with one support-needed line only if the source material supports it.

The Skill should shape the final message. Cowork should not be asked to improvise the final writing rules after the source file is already prepared.

6) Review the 3P before sending

Do a human review before the update goes to leadership. Check:

• Does the final 3P reflect only the current week's material?
• Do completed work, next actions, and blockers match Cowork's prepared source file?
• Are owners, dates, and dependencies present only when the source supports them?
• Are blockers neutral and factual?
• Are unresolved items visible instead of smoothed over?
• Did archived or old-week material stay out of the final update?

Fix the prepared source file if the problem is upstream. Fix the Skill if the source is right but the writing shape is wrong.

7) Save, send, or reuse the result

Save the final 3P back into the recurring workspace beside the prepared source file. That gives next week's run a useful example and makes review easier.

If the format works, keep weekly-3p-writer enabled and reuse it after each Cowork gathering pass. Update the Skill when your team's reporting style or leadership expectations change.

Future weekly runs

After the first setup, the weekly run should be shorter. Reuse the same Cowork project, keep the same folder structure, place only the current week's material in current-week, and let the project instructions carry the standing context.

Start with a short prompt:

Create this week's 3P update from the current-week folder.

If you want the prompt to be more explicit, use this:

{
  "task": "Create this week's 3P update from the current-week folder.",
  "rules": [
    "Use the project instructions.",
    "Inspect only the current-week folder.",
    "Prepare a verified status input file first.",
    "Ask for approval before writing the final 3P update.",
    "Apply the internal-comms Skill only after the input file is approved."
  ]
}

The workflow gets easier because the project instructions, project memory, stable weekly folder structure, and internal-comms Skill all carry part of the repeatable setup. You still review the prepared input and final 3P, but you do not have to rebuild the process from a blank chat each week.

Tool-specific instructions

Claude Cowork

Use Cowork for file handling, workspace inspection, and normalization. Keep its instructions focused on gathering and preparing the source set. Do not let Cowork silently mix archived weeks into the current report, and review its plan before it acts on local files.

Claude Skills

Use the internal-comms Skill, or a private weekly-3p-writer Skill if your team needs stricter rules, as the main writing tool. The Skill should encode your team's 3P structure, final tone, blocker language, support-needed rule, and uncertainty handling.

Use the official skill-creator skill only as a helper for drafting or improving your private Skill. Treat the Claude Skills tool hub as further reading for broader setup context, not a prerequisite for this workflow.

Normal Claude chat

Use normal Claude chat when all source material is already pasted or attached and you only need one draft. For this recurring weekly workflow, normal chat is less useful because it does not maintain the same local project workspace, folder boundaries, prepared input file, and output location.

Official public skill reference

The internal-comms public Skill is a useful formatting layer for internal updates. It is not a substitute for Cowork's workspace role, because it does not gather, inspect, and organize the local weekly folder by itself. Use a private weekly 3P Skill when the team expects the same house style, section rules, and escalation language every week.

Quality checks

1. Cowork inspected only the current week's workspace material.
2. The prepared source file and final 3P agree on completed work, next actions, blockers, and open questions.
3. The final 3P uses the same Progress, Plans, Problems structure every week.
4. Nothing from archived weeks leaks into the current report.
5. Unresolved owners, dates, dependencies, and blockers remain visible.
6. The final report is short, scannable, and ready for human approval before sending.

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, then rerun Cowork's normalization step.

Cowork writes the final 3P too early

Fix: tell Cowork to stop at a normalized source file. Use weekly-3p-writer for the final writing pass.

The final 3P misses an important blocker

Fix: edit the prepared input file before the writing step instead of asking the final Skill run to improvise missing source material.

The workflow feels too heavy

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