Skip to content
cccskills
FreePublished on GitHubEnglish overview

Brand

Use this skill to review public profiles, websites, and repository READMEs against a configured inventory and current source materials. It identifies outdated focus, names, links, and featured writing, then prepares updates for individual surfaces for approval.

OriginalShow the original description

The principal brand integrity system: sweeps and refreshes brand/focus messaging across every public surface (GitHub profile README, blog, company site, marketing site, repo READMEs, LinkedIn/X/YouTube bios) to current focus, names, star counts, and flagship writing, from one surface inventory in USER config. USE WHEN brand update, update my brand, brand sweep, refresh my profiles, update my GitHub profile, github front page, profile README, my bios are stale, sync my messaging, update my ideas page, refresh the ideas page, ideas page on the blog. NOT FOR the content registry, writing blog posts, or social post copy.

danielmiessler/LifeOS19,635 stars(GitHub 19,635 + cccskills 0)

Run score Not tested

See how to install

Good for

  • Refreshing a GitHub profile README
  • Checking whether public bios reflect current work
  • Updating messaging across websites and repository READMEs
  • Refreshing an ideas page from recent ideas

Overview

What it does

This skill reviews public pages listed in a configuration, including a GitHub profile README, blog, company or marketing sites, repository READMEs, and LinkedIn, X, and YouTube profiles. It reads current focus, names, published information, and featured writing from the configured sources of truth. It then identifies outdated descriptions and links and prepares proposed updates for each page. It can also update an ideas page. When changes are carried out, it records what changed for each page and the evidence used to check it.

When it helps

Use it when biographies or descriptions may be out of date across several profiles and websites, or when you want their names and current focus to match. It can also bring recent ideas to the ideas page on your blog.

Example requests

  • “Update the brand information across my public profiles.”
  • “Review my GitHub profile to match my current focus.”
  • “Add my new ideas to the ideas page.”

Notes

The pages, update methods, and source materials must be listed in the user’s Surfaces.md settings. Work does not start if that file is missing or incomplete. Before updates go live, the rendered result for each page is checked and you approve the change.

This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.

Document check

AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).

SafetyAre sending data, deleting files, and running commands disclosed?
AGoodEach rendered public change requires the user's approval first.
Easy setupDoes it need few tools or API keys, and are they documented?
BPartly lackingSurfaces.md must list pages and update details; Setup.md guides setup.

Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 28, 2026. Treat it as a guide and read the original before installing.

Disagree? Request a re-evaluation

Tell us which point is wrong and why. No login needed. We will check it against the SKILL.md, redo the evaluation, and show the result here.

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

Files included (5)

  • SKILL.md4.7 KB
  • Intents/BrandUpdate.md3.5 KB
  • Intents/UpdateIdeasPage.md3.2 KB
  • Setup.md3.9 KB
  • Tools/Check.ts4.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Brand

A person's brand is spread across a dozen public surfaces that drift out of sync: old project names, stale focus statements, dead links, outdated writing lists. This skill is the one place that knows every surface, how each one updates, and what "current" means, so a single BrandUpdate run brings them all back into line.

Source of truth for what the brand currently is: the files listed under ## Source-of-truth reads in Surfaces.md (focus and missions, what is live, bio facts) plus the freshest posts from the blog feed ($BLOG_FEED). Never duplicate those facts into this skill; read them at run time.

Ideal State

  • Every surface a run touches says what the principal is focused on now, as read from the USER inventory and source-of-truth files at run time, never from memory or this skill.
  • Nothing goes public under the principal's name before they have seen the rendered result and approved that one surface.
  • Every run ends with a table in its run ISA naming each surface or idea, what changed and the evidence, including what was left unswept or rejected.
  • A missing or invalid Surfaces.md stops the run at Check.ts with a pointer to Setup.md; no surface is ever swept from guesses.

Intent Routing

IntentTriggerFile
BrandUpdate"brand update", "brand sweep", "update my GitHub profile", "refresh my bios/profiles"Intents/BrandUpdate.md
UpdateIdeasPage"update my ideas page", "refresh the ideas page", "parse my latest ideas"Intents/UpdateIdeasPage.md
FileRead when
Setup.mdfirst-time setup, or Check.ts exits non-zero

Data & Config

Every personal fact (the public-surface inventory with URLs, repo paths, handles and update mechanisms; the ideas-page location and structure; the blog and feed facts $BLOG_URL, $BLOG_FEED, $BLOG_REPO; per-surface rules) lives in <configRoot>/LIFEOS/USER/CUSTOMIZATIONS/SKILLS/Brand/Surfaces.md (configRoot is $CLAUDE_CONFIG_DIR when set, else ~/.claude). This skill body is generic.

Both intents start with bun ~/.claude/skills/Brand/Tools/Check.ts. It validates Surfaces.md and, when the file or a required section is missing, exits non-zero and points at the guide. First-time setup: Setup.md.

Gotchas

  • Use the feed URL recorded in Surfaces.md ($BLOG_FEED). A blog's feed often lives somewhere other than the obvious paths (/feed.xml, /rss.xml, /atom.xml), so confirm the working one with curl before recording it.

Examples

Example 1: Full brand sweep

User: "Run a brand update — everything feels stale"
→ BrandUpdate intent, full sweep
→ A drift table in the run ISA covers every inventory row; each fix went live only after the owner approved that surface

Example 2: Single surface

User: "Update my GitHub front page based on recent focus"
→ BrandUpdate intent, scoped to the GitHub profile surface
→ The README is pushed after approval of its GitHub render; every other surface is listed as unswept

Example 3: Ideas page

User: "Refresh the ideas page with my latest ideas"
→ UpdateIdeasPage intent
→ New principal-original ideas are on the live page, verified by screenshot after an approved deploy; rejected captures are listed with reasons

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

AnnualReports

FreeSummary

Find and fetch vendor cybersecurity reports, then compare their findings on topics such as ransomware, breaches, cloud security, and AI. Analyses identify the reports consulted and cite each figure by vendor, year, and report, including where sources disagree.

  • Find reports in a cybersecurity topic area
  • Fetch a specific vendor report
  • Compare ransomware findings across reports
danielmiessler/LifeOS19.6KUpdated Oct 28, 2026

Compare a component's own design needs with the goals of the larger system through three structured passes. The result identifies conflicts, recommends an appropriate scope, and assesses whether the proposed design fits the whole.

  • Choosing between a service, a library, and inline code
  • Comparing feature requests with product goals
  • Checking how new components fit an existing system
danielmiessler/LifeOS19.6KUpdated Oct 28, 2026

Aphorisms

FreeSummary

Find quotes that fit a text’s themes, with attribution and a short reason for each suggestion. Add sourced quotes, research thinkers, and organize a quote collection by theme and usage history to avoid repetition.

  • Finding a fitting quote for a newsletter
  • Saving sourced quotes without duplicates
  • Researching a thinker’s quotes by theme
danielmiessler/LifeOS19.6KUpdated Oct 28, 2026

Art

FreeSummary

Create blog illustrations, technical diagrams, comparisons, comics, and icons through workflows tailored to each format. The skill guides composition, color, and model selection, then stages generated images for review before they are used in a project.

  • Creating blog header illustrations
  • Explaining a system with a technical diagram
  • Visualizing comparisons and timelines
danielmiessler/LifeOS19.6KUpdated Oct 28, 2026

ArtDirection

FreeSummary

Assess the visual quality of images, films, slides, and site captures against a brief and craft criteria. Two vision judges score the work and rank defects, guiding bounded revision; delivery is gated on a passing critique, with human calibration labels recorded separately.

  • Reviewing a render and listing the most important visual defects
  • Iterating on a film or slide deck until it meets a defined bar
  • Checking whether an image reads as professional
danielmiessler/LifeOS19.6KUpdated Oct 28, 2026

ArXiv

FreeSummary

Find arXiv papers by topic, research category, or paper ID. Retrieve titles, authors, abstracts, and links, check new submissions, and add AlphaXiv's AI-generated overviews when available to help decide which papers to read.

  • Checking new AI and machine learning papers
  • Finding papers on a specific research topic
  • Looking up a paper by its ID or arXiv URL
danielmiessler/LifeOS19.6KUpdated Oct 28, 2026

See all skills by danielmiessler

Report a problem with this skill