Skip to content
Get packs

Guide · Agent skill

How to use the Brand Sweep and Profile Refresh agent skill

Updated · written with AI from the project's own documentation and checked against our catalogue data

The Brand skill is an agent skill: a folder of instructions and a small script that an AI agent such as Claude loads when you ask for a matching task. This one finds every public profile and site you own, such as your GitHub profile README, blog, company site, repo READMEs and LinkedIn, X or YouTube bios, and brings their wording up to date with what you are focused on now. After this guide you will know how to install it, what it needs, how to phrase a request, and what it will and will not publish without asking you.

Brand Sweep and Profile Refreshdanielmiessler/LifeOS · MIT

Quick start

  1. 1Download and unzip. Download the Brand ZIP from this page and unzip it into ~/.claude/skills/ or a project's .claude/skills/ folder, or upload it under Settings → Capabilities → Skills.
  2. 2Install Bun. The check script runs on the Bun runtime, so Bun must be available before the skill can validate your config.
  3. 3Write Surfaces.md. Create the config at LIFEOS/USER/CUSTOMIZATIONS/SKILLS/Brand/Surfaces.md with your source-of-truth files, surface inventory, update methods and approval gates.
  4. 4Run the check. Run bun ~/.claude/skills/Brand/Tools/Check.ts and fix any error it reports by following Setup.md.
  5. 5Ask for a sweep. Request a full brand update or a single surface in natural language, such as updating your GitHub profile README.
  6. 6Approve each surface. Review the rendered result of each surface and approve or reject it. Only approved surfaces are published.
  7. 7Check the run table. Read the run table to see what changed, the evidence for each change, and what was left unswept or rejected.

What the Brand skill makes the agent do

Your public presence drifts: project names change, focus statements go stale, links die and writing lists fall behind. The skill gives the agent one checklist covering every surface you list, and a repeatable way to check each one against your current focus.

The agent reads the facts from your own files at run time rather than from memory. It drafts changes, and it only publishes a surface after you have seen the rendered result and approved it. A second workflow refreshes an ideas page on your blog from ideas you have captured.

  • Sweeps every surface in your inventory, or only the ones you name.
  • Flags stale names, dead links and old claims on each surface.
  • Records every surface or idea in a run table: what changed, the evidence, and what was left unswept or rejected.
  • Does not write blog posts or social post copy; the skill excludes those.

Install the Brand skill from the ZIP

Download the Brand ZIP from this page and unzip it. Put the Brand folder in your personal skills directory at ~/.claude/skills/, or in a project's .claude/skills/ folder if you want it only for that project.

If you use the Claude apps instead, upload the skill under Settings → Capabilities → Skills.

  • Personal install: ~/.claude/skills/Brand/
  • Project install: .claude/skills/Brand/ inside the project folder
  • Claude apps: Settings → Capabilities → Skills, then upload
~/.claude/skills/Brand/Tools/Check.ts

Create your Surfaces.md config before the first run

The skill keeps all personal facts out of its own code. You list them once in a file called Surfaces.md, stored at LIFEOS/USER/CUSTOMIZATIONS/SKILLS/Brand/ inside your config root (the folder in $CLAUDE_CONFIG_DIR if set, otherwise ~/.claude).

The file needs a source-of-truth section, an inventory of surfaces with how each one is updated and what approval it needs, and the blog variables such as $BLOG_FEED. The Setup.md file in the skill explains what to fill in. Its checker validates the file on every run.

  • Inventory row for each surface, with its update mechanism and approval gate
  • Paths to the source files that state your current focus and bio facts
  • $BLOG_URL, $BLOG_FEED and $BLOG_REPO if you have a blog
  • Ideas page location and structure, if you use the ideas workflow

Run the check script

Both workflows start with a check script that reads Surfaces.md. It needs the Bun runtime. If the file or a required section is missing, or an inventory row has no update method or approval gate, the script exits with an error and points you to Setup.md. The agent then stops rather than guessing at your surfaces.

Run it yourself first to confirm your setup before asking for a sweep.

  • Requires Bun to execute Tools/Check.ts.
  • A non-zero exit means fix Surfaces.md, then re-run.
bun ~/.claude/skills/Brand/Tools/Check.ts

Ask for a sweep in plain language

You do not need a special command. The skill triggers on requests about updating your brand or profiles. Say what you want and, if relevant, which surface. A full sweep covers every row in the inventory; a scoped request touches only what you name.

Expect the agent to show you rendered output for each surface and wait for your approval before anything goes public. Surfaces you did not approve are reported as unswept.

  • "Run a brand update, everything feels stale" (full sweep)
  • "Update my GitHub front page based on recent focus" (one surface)
  • "Refresh the ideas page with my latest ideas" (ideas workflow)
  • "My bios are stale, sync my messaging"

Safety notes: scripts, network and approval

The skill runs a script (Tools/Check.ts) and uses the network to check links and read your blog feed. It names no specific API keys. Publishing relies on access you already have, such as git push rights to your repos or deploy access to your sites.

The design requires approval before every public change. Do not try to automate it unattended: that removes the check that keeps wrong or outdated wording from going live under your name.

  • Give the agent only the access to the surfaces you actually want it to change.
  • Review each rendered surface before approving it.
  • Check that the blog feed URL in Surfaces.md works; some blogs keep their feed at a non-standard path, so confirm it with curl before recording it.

What people use it for

  • Refreshing the GitHub profile README after a shift in your focus.
  • Updating outdated bios on X, LinkedIn and YouTube so they match your current work.
  • Removing old project names and dead links across a personal site and repo READMEs.
  • Refreshing the ideas page on your blog with ideas you have captured since the last update.

Frequently asked questions

How do I install the Brand agent skill?

Download the Brand ZIP from this page and unzip it into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder. In the Claude apps you can instead upload it under Settings → Capabilities → Skills.

What do I need to run the Brand skill?

You need the Bun runtime to execute the check script, a LifeOS USER config file named Surfaces.md describing your public surfaces, and access to those sites and repos, such as git push rights or deploy access. The blog feed URL should be recorded in the config as $BLOG_FEED.

Is the Brand skill free to use?

The source material lists the skill under the MIT licence. Check the licence file in the repository for the exact terms before reuse.

Why does the check script stop my run?

The script exits with an error when Surfaces.md is missing, lacks a required section, has an inventory row with no update mechanism or approval gate, or names a missing source file. The fix is to complete the config as described in Setup.md.

Can the Brand skill publish changes automatically?

It is designed not to. It only publishes a surface after you have seen the rendered result and approved it. Automating it without approval would defeat that safety design.

Does the Brand skill write blog posts or social posts?

No. The skill explicitly excludes writing blog posts and social post copy, and it also does not handle the content registry.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

Use the Brand skill if you maintain several public profiles and sites, already keep or are willing to write a Surfaces.md inventory, and want a repeatable, approval-gated way to bring them up to date. Pick something else if you only need help writing posts or copy, or if you want fully unattended publishing, which this skill is built to prevent.

Download the skill