Localized reading guide
brand-stylePurpose, usage and source
Sets and updates the owner's brand look and output preferences, which every page and document the plugin produces then follows automatically. Captures the brand from a pasted website link or a plain-words description — never a hex code, color picker, or upload — previews it on a sample page, asks how they want their outputs delivered (visual artifacts, Word docs, markdown, Notion pages, Canva Docs, or best-for-the-skill), and saves both to the business profile. Runs inside smb-onboard on first setup and stands alone forever after. Use when the owner says "update my brand," "we rebranded," "change my colors," "make the reports match our new look," "change how you give me reports," "I want Word docs instead," or anything about the look or format of what the plugin hands them.
Source retrieved:
- Source repository
- anthropics/knowledge-work-plugins
- SKILL.md
small-business/skills/brand-style/SKILL.md- Repository stars
- 34,049
- Repository updated
- 2026-10-30
- Categories
- Documents
- Last collected
License: Apache-2.0
Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.
The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.
What this Skill does
Sets and updates the owner's brand look and output preferences, which every page and document the plugin produces then follows automatically. Captures the brand from a pasted website link or a plain-words description — never a hex code, color picker, or upload — previews it on a sample page, asks how they want their outputs delivered (visual artifacts, Word docs, markdown, Notion pages, Canva Docs, or best-for-the-skill), and saves both to the business profile. Runs inside smb-onboard on first setup and stands alone forever after. Use when the owner says "update my brand," "we rebranded," "change my colors," "make the reports match our new look," "change how you give me reports," "I want Word docs instead," or anything about the look or format of what the plugin hands them.
How the upstream workflow works
Step 1 — Show what is set now
Read the ## Business context block. If Brand colors, Logo, or Output preference exist, play them back in plain words first: "Right now your pages use a deep green and cream with your leaf logo, and you get visual pages. What's changing?" An owner updating one thing should not re-answer the rest. If nothing is stored yet (first run, usually inside smb-onboard), skip straight to capture.
Step 2 — Capture the brand, frictionlessly
Two paths, both costing the owner almost nothing: A website link. Fetch the site (WebFetch) and pull the logo URL, primary brand colors (from the CSS, theme, or social-preview image), and tagline. The owner does nothing but paste the link. Guidance in ../smb-onboard/reference/website-research.md. A plain-words description. "Forest green and cream," "navy and warm gray," "like a modern law firm." Translate the words to real colors yourself. Never ask for hex codes, color pickers, or file uploads. Branding costs one pasted link or one spoken sentence, nothing more. "Skip" is always an answer and means the clean house default.
Step 3 — Preview before saving
Render a small sample page as an HTML artifact in the house style (../../shared/artifact-style.md) with the candidate brand applied — a title, one stat tile, a short table, a status pill — so the owner sees the look on real components, not a color swatch. Ask one question: "Match?" If they adjust ("darker green," "less cream"), apply and re-preview. This loop is cheap; a wrong brand on every future page is not.
Requirements and setup
No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.
Limits and quality checks
No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.
Start with a safe trial
- Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
- Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
- Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
- Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.
Read further in the source
Related Skills
Translation and scope
This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.
This introduction refers to the pinned version below; current repository activity and collection time are shown separately.
- Pinned source
- Read the original ↗
- Source retrieved
- Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d- Source SHA-256
4fc74f9af424ab4b04338b9028a1e4302b59395f1ef5f7067b2131bf56df8ac9