Install walkthrough
Get the six Document Ops skills onto your Claude account, set up your brand once, and confirm they work. No commands to type.
A Claude plan with code execution turned on (Setup, step 1), and your download: six .skill files, one per skill.
Add the six skills
Each file is one skill:
brand-kit.skill: the brand setup, run once;sop-docx.skill: step-by-step procedures;qrg-builder.skill: one-page job aids;agenda-builder.skill: meeting agendas;minutes-builder.skill: meeting minutes;reqdoc-builder.skill: change records.
In the Claude web or desktop app, select Customize, then Skills › Add › Upload skill, and upload each file in turn. Setup walks through the screens. Every upload tested so far used the file renamed to end in .zip (a .skill file is a zip under another name); if a .skill file is not accepted, rename it and upload again.
If you already have a skill of your own that does the same job, such as your own SOP or agenda skill, switch it off on its page under Customize › Skills, or Claude may use it instead.
Tested in Claude Code, the claude.ai web app and the Claude desktop app. See compatibility.
Set up your brand
In a new chat, type brand: at the start of a message. It asks for your logo, colors, font and how you name documents, checks that every color can be read where the documents print it, and gives you two files to keep: brand.json and logo.png. The brand setup guide covers it in full. Skip it and every document still builds, in plain neutral colors.
Confirm it works
In a new chat, ask Claude to run one skill’s install check, for example: “Run the install check, check_deps.js, for sop-docx.” A pass means every file in that skill arrived. Do the same for each skill you want to confirm.
In each new chat
Where Claude keeps no folder between conversations, your brand travels with the chat: attach brand.json and logo.png to any chat where you build a document, with both names unchanged. Then ask for the document by name: an SOP, a quick reference, an agenda, the minutes, or a change record.
If it looks wrong
The upload was not accepted. Rename the file to end in .zip and upload it again.
Claude answered like a normal chat. Ask for the document by name. If it still does not start, the skill may be on a different account from the one you are signed in to, or a skill of your own may be answering instead. See Setup, “When it doesn’t work”.
The document is in plain colors, not your brand. The brand files were not in the chat. Attach brand.json and logo.png and ask again.
Using Claude Code instead
Extract each .skill file into your skills folder: ~/.claude/skills/ for every project, or .claude/skills/ inside one. unzip and 7-Zip read a .skill file as it is. The tar inside Git Bash cannot read a zip and fails with “This does not look like a tar archive”; use unzip. A skill in that folder does not reach your claude.ai account, and one on your account does not reach that folder.
Needs Node on the machine; the pack is tested on Node 20 and Node 24. Nothing else to install: each document skill carries its one library inside it.
Put your brand.json, with logo.png beside it, at the top of the project you build in, or in a folder above all your projects. Every skill looks in the path in HPW_BRAND_KIT, then the folder you build from, then each folder above it, then falls back to the neutral defaults. It never reads a brand from inside an installed skill folder.
To confirm each install, run its check from the folder you will build in. Exit 0 means every file is present:
The install guide in your download walks through every step with the output to expect.