Source: raw/Claude_Cowork_+_Skills_is_Your_NEW_Content_System.md (https://www.youtube.com/watch?v=l1y3IeC_eJ0) Creator: Grace Leung Platform: YouTube Duration: 17:16 Published: 2026-03-14 Skill level: Intermediate (Cowork plus a little Claude Code; one Python upload script)

Grace Leung, an AI-for-marketing educator, builds a content system for a demo cafe brand (“Goldie Coffee”) from one project folder, a set of project skills and an Excel content planner. Cowork does the drafting and image generation; Claude Code does the steps that call external APIs (uploading media to Notion and drafts to WordPress). It covers four pipelines: repurposing, carousels, ad creative and blog posts. Recorded in March 2026, before Cowork and chat merged (2026-09-16), so the mode-switching and scheduling details are dated (see Open Questions).

Key Takeaways

  • Three layers. A context layer (brand knowledge, voice, audience, products), a skill layer (reusable instructions for each task) and an orchestration layer (Claude with tools connected, reading inputs, running skills, writing outputs).
  • A spreadsheet is the control panel. The content planner has one tab per content type. Each row holds the input requirements, a status, and the output file path. Prompts say “do the rows with an empty status, then update the planner”, so the sheet doubles as the job queue and the log.
  • Folder layout. A system folder (brand context, project skills, scripts), working folders per channel (Ads, SEO, social), a CLAUDE.md as the project system prompt, and the content planner.
  • Cowork did not read project-level skills by itself (March 2026). Grace says Cowork “doesn’t automatically read the project level skills like Claude Code does”. Her fix: add a line to CLAUDE.md pointing at the skills folder, or put the same instruction in Cowork’s global instructions in settings.
  • Style libraries for visuals. For carousels and ads she keeps a folder of reference styles plus a written style guide file, so Claude “doesn’t have to analyze every image in real time”. She tells it to use the references as guidance, not to copy them rigidly.
  • Cowork for drafting, Claude Code for API uploads. Pushing images and drafts to Notion and WordPress ran in Claude Code, because those steps upload media “through external API calls”.
  • Parallel agents happen on their own. Cowork spun up parallel agents in every demo without being asked. Grace: “99% of time you don’t need to create subagent manually inside Claude Cowork.”
  • Nothing here is publish-ready. Grace says to review voice before posting, and that the ad creatives still had wrong logos and taglines. Blogs need your own insights and data added.

The four pipelines

1. Repurposing (start here)

  • She calls it the highest-ROI task because nothing new is created.
  • Input: three existing blog posts in the social input folder. The Nano Banana MCP is installed for visuals (see Nano Banana).
  • Output: 9 posts and 6 visuals. Each post lists its source, format, hook and visual direction (so a teammate can make the visual). LinkedIn posts follow a post framework file. A newsletter draft comes with subject-line options and a suggested CTA.
  • She asked for visuals with no text in them.

2. Carousels

  • Inputs: a carousel style library (several distinct styles plus a style guide file) and the planner’s carousel tab.
  • Prompt: read the planner, create a carousel for each row with an empty status, update the planner when done.
  • Result: five carousel tasks launched in parallel through a “carousel post designer” skill, 23 visuals across platforms, grouped by campaign with post copy. Styles varied on purpose. Logos were inconsistent because no logo file had been supplied.
  • Schedule it. In the same conversation she used the built-in /schedule command to run the workflow every Friday at 9:00 AM. Her tip: only schedule tasks that need no human approval mid-run.

3. Distribution to Notion

  • A reusable Python script in the system scripts folder uploads media to Notion with an API key. Claude calls it whenever it needs to upload.
  • In Claude Code (desktop app, same project folder, Notion MCP connected): read the planner, create a Notion content-calendar entry for each row whose “scheduled on Notion” status is empty, upload the visuals, update the planner.
  • Result: six carousel posts on the Notion calendar with title, scheduled publish date, platform, status, post copy and attached images. The team reviews and comments there.

4a. Ad creative

  • An ad-creative style library of high-performing static and carousel ad references, plus an ad style guide.
  • An ads/input folder for reference images (product shots, competitor references, studio backgrounds). She supplied two product images.
  • The planner’s Ad tab holds campaign name, products and offers, goals and platform.
  • Step 1, briefs: an “ad creative brief” skill wrote five briefs in parallel. Each has campaign overview, target audience, key message, hook variations and creative directions.
  • Step 2, creatives: a “creative designer” skill reads the briefs. Her system defaults to five creatives per brief, so five campaigns gave 25 images, saved next to each brief. The product reference images carried through.
  • Her advice: supply more reference images to get closer to what you want.

4b. Blog posts to WordPress

  • A blog content brief template and an “AI search blog writing” skill. Briefs (in output/SEO) cover topic and keyword strategy, content angle, structure and format, and AI-search optimization notes.
  • The planner holds target topic, angle, brief file path and status.
  • Cowork wrote the drafts in parallel, then generated a header image for each. She says the run took about 15 minutes. Drafts include a table of contents, key takeaways and bullet structure.
  • Claude Code then pushed seven drafts to WordPress, with header images, through a WordPress MCP tool. Tip: if you hit the context limit, run /compact, or split the work across separate Claude Code sessions.

Try It

  1. Make one project folder: system/ (context, skills, scripts), one folder per channel, CLAUDE.md, and content-planner.xlsx with one tab per content type and status and output_path columns.
  2. If Cowork doesn’t pick up your project skills, add a line to CLAUDE.md that says where the skills folder is.
  3. Start with repurposing: put three existing posts in an input folder and ask for posts, a newsletter and text-free visuals, each tagged with source, format and hook.
  4. For visuals, build a style library folder plus a one-page style guide before generating anything. Add your logo file early.
  5. Drive every batch from the planner (“rows with empty status”), and have Claude write the output path and status back.
  6. Run the steps that upload to Notion or WordPress in Claude Code, with a saved upload script, and keep everything as drafts for human review.
  7. Schedule the batches that need no approval mid-run.

Implementation

  • Tool/Service: Claude desktop app (Cowork and Claude Code modes as of March 2026), project skills, Nano Banana MCP, Notion MCP plus a Python upload script, WordPress MCP, Excel.
  • Setup: folder layout and planner above; skills named in the video are “carousel post designer”, “ad creative brief”, “creative designer” and “AI search blog writing”. Their contents are not shown.
  • Cost: not stated.
  • Integration notes: the Notion upload script uses a Notion API key. Grace’s templates sit in her paid “AI growth system for marketing” program. The video is sponsored by HubSpot, which offers a free “Claude Cowork Stack: 12 advanced prompts” guide; it was not fetched.

Open Questions

  • Scheduling is outdated. Grace says scheduled tasks “will only run while your Claude desktop is open”. That matches March 2026. Since July 2026 scheduled tasks in cloud projects run with no device online, and since October they attach to projects (see Claude Cowork). A local-folder system like this one still needs the desktop app for file access.
  • Do project skills load on their own now? The “Cowork doesn’t read project-level skills” note is from March, before the September merge. Not checked against current behaviour or docs.
  • Is the Cowork/Claude Code split still needed? She moved to Claude Code for API uploads. Whether merged Claude can run the Notion and WordPress steps without switching was not tested here.
  • Timings and counts (9 posts, 23 visuals, 25 ads, about 15 minutes for blogs) are from one demo, not benchmarks.
  • The skill files, planner template and Python script are not public in the video.