Source: raw/The_1_Claude_Skill_I_Can_t_Live_Without.md (Brand Print, current method); raw/Claude_Cowork_SKILLS_Clearly_Explained_how_to_create_them_for_beginners.md (brand applicator, earlier method); raw/5_Mind-Blowing_NEW_Use_Cases_for_Claude_Skills.md (branded deck + brand guidelines skill, earliest method) Creator: Eliot Prince URL: https://www.youtube.com/watch?v=pWa2QWEUu6o (Brand Print, 9:05, published 2026-08-03); https://www.youtube.com/watch?v=g4ke3Yqlmhk (Cowork skills for beginners, 20:42, published 2026-03-27); https://www.youtube.com/watch?v=4867-EkHWzM (5 use cases, 14:49, published 2025-12-12) Duration: 9:05 / 20:42 / 14:49 Platform: YouTube Published: 2026-08-03 (latest of three)

Eliot Prince calls his brand skill “the number one Claude skill that pretty much underpins everything I do”. It holds his logos, fonts, colour palette, approved colour pairings and output templates, and other skills defer to it, so invoices, proposals, Word documents, PDFs, slides, dashboards and web pages come out branded without restating the brand each time. He has shown three versions of the build across 2025-12, 2026-03 and 2026-08. The August 2026 Brand Print method adds a separate brand audit step before the skill is built, which fixes the main failure of the earlier one-shot builds: guessed colours and font roles.

Key Takeaways

  • One brand skill, referenced by other skills. Eliot says it “links to all other skills and outputs I create”. In the Record a skill demo, the generated report skill’s branding file says to pull everything from the brand skill, and he stacks it with his voice and teaching-dashboard skills in one request.
  • Current method (2026-08): three steps. (1) Collect every brand asset into one folder. (2) Run a brand audit prompt that produces a written brand specification. Correct it. (3) Run a build prompt that turns the corrected spec into the skill.
  • The audit step is the upgrade. The audit lists the assets, extracts palettes, maps the typography hierarchy against the guidelines, catalogues font-file coverage and logo variants, and flags what it inferred and the questions it cannot answer. Eliot: answer those questions, “otherwise it’s just going to be a little bit off”. The corrected spec (“brand specification V2”) is useful to the business on its own.
  • Approved pairings matter more than the palette. Every version extracts rules for which colours go together (forest background → lime text; purple on yellow), not only hex codes. This is what keeps output from “throwing random colors and fonts and logos together”.
  • What a finished brand skill contains: a main instruction file (when to run it, brand identity at a glance, colour system, approved pairings, typography, logo-usage rules), an assets folder (logo and icon files, font files), references (brand guidelines, sample decks and documents), and in the March 2026 build, output recipes for specific formats: an HTML artifact, a React dashboard, a PDF report.
  • Run it on top of context. Eliot runs the skill inside his “second brain” project, which holds his business details, so “create a branded invoice for …” produces the invoice without him supplying an address or billing details. The same pattern produced a branded VIP-workshop proposal from project knowledge.
  • Claude Design versus the brand skill (Eliot, 2026-08). He used Claude Design deliberately for serious design work (keynote slides) and called it “slightly detached” from daily work. The brand skill is for fast everyday output. Since 2026-09-16 Claude Design works inside conversations (Claude Cowork § One Claude), so the “detached” point is dated. Whether Design now reads a user’s brand skill is unverified.
  • Known limits. Custom fonts may not render in a generated PowerPoint unless embedded; Eliot’s Word output embedded them. Some extracted colours come back marked as inferred and must be checked against the guidelines.

The three builds

DateNameInputsMethodNotes
2025-12Branded deck, then brand guidelines skillA Keynote template; later a brand-guidelines document, font files, logos, a colour-combination chartPrompt: read the built-in PPTX skill plus the skill creator skill and build a “branded deck” skill. Second pass: skill creator builds a brand-guidelines skill from the uploaded filesSkills were then under Settings → Capabilities, and Anthropic’s built-in brand-guidelines (Anthropic’s own brand) and theme-factory (10 preset themes) skills sat in the same list. Deck output was “pretty bang on” except custom fonts. Historical UI.
2026-03Brand applicatorA Cowork project pointed at the brand-assets folder (fonts, logos, a colour PDF, guidelines)One prompt: “build a brand applicator Claude skill … act as a brand designer … extract everything and then build the skill”, run with skill creator onOutput included output recipes per format. Saved with Copy to your skills.
2026-08Brand PrintOne desktop folder of assets, added as a folder (not a full project, since it is a one-time job)Audit prompt → answer flagged questions → build promptCurrent method. Cowork mode in the desktop app, chosen so Claude can “run more autonomously”.

Try It

  1. Collect the assets into one folder: logo files (all variants), font files, the brand-guidelines PDF, any colour chart, and two or three finished on-brand documents or decks as references.
  2. Run the audit. Eliot’s prompt opens: “You’re a brand systems analyst. I want you to audit my brand assets and produce a brand specification precise enough that another AI could apply my brand.” Point it at the folder. His full prompt is in his AI Recipe Vault and is not reproduced in the transcript.
  3. Correct the spec. Go through every flagged item and every colour marked as inferred. Answer the questions at the bottom. Save the corrected spec as a file.
  4. Build the skill. Prompt: “The audit is correct. Now build me a Claude skill called Brand Print that applies this brand to any output I ask for.” Include reference decks and documents so it learns layouts as well as colours.
  5. Review, then Save skill. Check that the assets folder contains the actual font and logo files, not only their names.
  6. Test on three formats inside a project that holds your business context: an invoice (PDF), a proposal (Word), a slide deck. Check logo placement, approved pairings and font embedding.
  7. Wire other skills to it. In each existing skill’s branding section, replace any branding rules with “use the Brand Print skill”.

Implementation

Tool/Service: Claude desktop app (Cowork mode in the 2026-03 and 2026-08 builds); built-in skill creator skill (must be toggled on under Customize → Skills); built-in PPTX/DOCX skills for document output.

Setup: See Try It. Skills saved in one surface are available across chat and Cowork, according to Eliot’s 2026-03 video.

Cost: No extra cost stated; included with paid plans.

Integration notes:

  • Pair it with a voice skill: Eliot stacks a “write in my voice” skill, the brand skill and a format skill (dashboard, AI recipe) in one request.
  • For a team, a brand skill can be shared across an organisation account without download and upload (Eliot, 2026-03). The mechanics were not shown.

Open Questions

  • Exact prompts. Only the opening lines of the audit and build prompts appear in the transcript. The full text is behind the AI Recipe Vault link.
  • Claude Design after the merge. Does in-conversation Claude Design (2026-09) pick up a user’s brand skill, or does it still need its own design system?
  • Font embedding across formats. Word embedding is reported working. PPTX and web-page font handling for non-Google fonts are not tested in the sources.