Agent skill

Brayness Sync

by scott-fryxell in scott-fryxell/brayness

Sync changes from dev brayness/ to the published git mirror at skills/brayness-sync/published/.

MITAuto-check: notesDevelopment

Install Brayness Sync

skills CLI
$ npx skills add scott-fryxell/brayness --skill brayness-sync -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install scott-fryxell/brayness brayness-sync --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/scott-fryxell/brayness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/brayness-sync .claude/skills/brayness-sync && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
brayness-sync
GitHub stars
125
Token cost
~889 tokens
SKILL.md length
291 words
Files
4 (incl. references)
Skills in repo
27
Repo updated
First seen
Licence
MIT

At a glance

Sync changes from dev brayness/ to the published git mirror at skills/brayness-sync/published/.

  • Works in 6 steps: Detect - diff dev against the mirror for… → Plan - show what will be copied and… → Copy - commands in references/workflow.md. → …
  • Prepare release
  • SKILL.md covers Copy list (source of truth), Workflow and One-time migration note
  • Calls git and npm

What it does

Brayness Sync is an agent skill from scott-fryxell/brayness. Sync changes from dev brayness/ to the published git mirror at skills/brayness-sync/published/. Copies skills, extensions, bin, agent docs, and selected .pi/agent config while excluding secrets, sessions, nested .git dirs, and nodemodules. Validates the copy, shows git diffs, and proposes commits. Use for "sync brayness", "prepare release", or after major skill/extension changes.

Its SKILL.md is about 890 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/examples.md`, `references/validation.md` and `references/workflow.md`).

It sits in Development, covering Git workflow. It works with Git and npm. The repository describes itself as: A harness for the anxious digital mind. A safe place for creatives to keep their creative soul while exploring digital skills. The licence is MIT.

When your agent uses it

  • Prepare release
  • After major skill/extension changes

Example prompts

  • “sync brayness”
  • “prepare release”
  • “/brayness-sync”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Detect - diff dev against the mirror for the copy-list paths;
  2. Plan - show what will be copied and excluded; get approval.
  3. Copy - commands in references/workflow.md.
  4. Validate - checks in references/validation.md (no nested .git,
  5. Review - git diff in the mirror; walk the user through it.
  6. Commit - propose a message; commit only after approval.

What it can do on your machine

Read from SKILL.md and the folder at commit 71f10e2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Brayness Sync loads about 889 tokens when it runs, and up to ~3.5k if it reads all its reference files. Until then it costs about 100 tokens; SKILL.md has 291 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~100
When it runs · the whole SKILL.md, loaded when a task matches
~889
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:29
    sessions, npm/node_modules), `.env*`, nested `.git/`, `node_modules/`,
  • NoteMentions a .env fileSKILL.md:47
    no `.env`, no `node_modules`, structure intact). Stop on any failure.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from scott-fryxell/brayness at commit 71f10e2, republished under its MIT licence (© scott-fryxell). 291 words, ~889 tokens.

Download SKILL.mdSave it as .claude/skills/brayness-sync/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
brayness-sync
description
Sync changes from dev brayness/ to the published git mirror at `skills/brayness-sync/published/`. Copies skills, extensions, bin, agent docs, and selected .pi/agent config while excluding secrets, sessions, nested .git dirs, and node_modules. Validates the copy, shows git diffs, and proposes commits. Use for "sync brayness", "prepare release", or after major skill/extension changes.

Brayness Sync

One-way copy: dev root -> skills/brayness-sync/published/ (the git-tracked mirror for releases). Dev has working chaos (nested repos, secrets, sessions); the mirror stays clean and publishable. Every sync is reviewed - no blind sync.

Copy list (source of truth)

PathWhy
skills/skill catalog
extensions/extensions
bin/harness scripts and CLI wrapper
prompts/prompt templates
package.jsonapp dependency + scripts
AGENTS.md, README.mdagent docs
.ignore, .nvmrcrepo config
.pi/agent/settings.json, .pi/agent/models.jsonpi config
.pi/agent/npm/README.md, .pi/agent/npm/.gitignoreadd-on signposts
.pi/agent/extensionssymlink
.cursor/skills, .claude/skillsrepo-root symlinks (Cursor/Claude Code)

Never copy: .pi/agent/ anything else (auth, trust, caches, models-store, sessions, npm/node_modules), .env*, nested .git/, node_modules/, AGENTS.local.md, plans/, work/ projects, and skills/brayness-sync/published/ itself - the mirror is the target, never a source.

The plans viewer now lives in work/brayness/examples/plan-viewer/ - a product tree the mirror does not ship. package.json still names its scripts, so a published npm run plans points at a path that stays on the dev machine.

Sessions rule: transcripts may contain secrets or personal info. They stay in dev, always.

Workflow

  1. Detect - diff dev against the mirror for the copy-list paths; summarize what changed.
  2. Plan - show what will be copied and excluded; get approval.
  3. Copy - commands in references/workflow.md.
  4. Validate - checks in references/validation.md (no nested .git, no .env, no node_modules, structure intact). Stop on any failure.
  5. Review - git diff in the mirror; walk the user through it.
  6. Commit - propose a message; commit only after approval.

Worked examples: references/examples.md.

One-time migration note

The mirror may still have the pre-2026-08-06 layout (root settings.json, models.json, sessions/, npm/). First sync after the .pi/agent/ move: git mv those into .pi/agent/ in the mirror (or delete root sessions/ - it should never have shipped), then run the normal sync. Show the user this migration as its own diff before anything else.

© scott-fryxell, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in skills/brayness-sync of scott-fryxell/brayness.

  • SKILL.md
  • references/examples.md
  • references/validation.md
  • references/workflow.md

Open the folder on GitHubat commit 71f10e2

Compare with similar skills

Brayness Sync next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Brayness Sync compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Brayness Sync this skillscott-fryxell/brayness125—~889Automated safety check: NotesMIT
Migrate Internal Package into GhostTryGhost/Ghost56k—~3.8kAutomated safety check: PassMIT
Hunk Release Workflowmodem-dev/hunk9.6k—~3.8kAutomated safety check: PassMIT
AionUi Version BumpiOfficeAI/AionUi33k—~2.1kAutomated safety check: PassApache-2.0
ZCF Release AutomationUfoMiao/zcf6.1k—~3.4kAutomated safety check: PassMIT
Pullkaranhudia/borg-ui1.7k1 repos~1.2kAutomated safety check: PassAGPL-3.0

Similar skills

  • Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.

    56k GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check passed
  • Hunk Release Workflow

    modem-dev/hunk

    Maintainer workflow for preparing, publishing, verifying and curating Hunk releases, with confirmation gates before tags, publishes and public edits.

    9.6k GitHub stars~3.8k tokensUpdated 3 days ago
    DevelopmentAuto-check passed
  • AionUi Version Bump

    iOfficeAI/AionUi

    Automates an AionUi release: checks the latest AionCore release and its artifacts, updates package.json, writes the changelog, opens a PR and tags the release.

    33k GitHub stars~2.1k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Automates a version release with changesets: analyzes code changes, writes a bilingual CHANGELOG, bumps the version and commits through a release branch and pull request.

    6.1k GitHub stars~3.4k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Pull

    karanhudia/borg-ui

    Pull latest origin/main into the current local branch and resolve merge conflicts (aka update-branch).

    1.7k GitHub starsUsed in 1 repo~1.2k tokens
    DevelopmentAuto-check passed
  • Git Changes Reporter

    No-Trade-No-Life/Yuan

    生成结构化 git 变更报告(JSON + Markdown)。使用此技能当用户提到"git 变更"、"commit 摘要"、"代码审查"、"release note"、"近期改动"、"每日摘要",或需要分析指定 commit 区间的代码变更。包含三元组结构(设计意图、核心代码、影响范围)的语义化报告,适用于代码审查、发布说明、团队同步、CI/CD 等场景。

    352 GitHub stars~1.2k tokensUpdated 5 mo ago
    DevelopmentAuto-check passed

More from scott-fryxell/brayness

All 27 skills in this repo
  • Logo Finder

    scott-fryxell/brayness

    Find and install brand SVG logos via SVGL (https://svgl.app/) and Wikimedia Commons fallbacks into any project's static asset folder.

    125 GitHub stars~1.1k tokensUpdated 12 days ago
    Auto-check passed
  • Test Coverage

    scott-fryxell/brayness

    Write Vitest specs for Vue 3 JavaScript (Vite Plus, happy-dom, @vue/test-utils) and analyze V8 coverage + Fallow health to prioritize test-first refactors.

    125 GitHub stars~1.6k tokensUpdated 12 days ago
    Auto-check passed
  • Flexible Visual System

    scott-fryxell/brayness

    Derive a project's visual rules from its existing tokens, palette, type scale, logo, and icons (Intake), then generate raw SVG vector graphics from those rules as a small composable set (module…

    125 GitHub stars~1.9k tokensUpdated 12 days ago
    Auto-check passed
  • Hyperframes

    scott-fryxell/brayness

    Create video compositions, animations, title cards, overlays, captions, voiceovers, audio-reactive visuals, and scene transitions in HyperFrames HTML.

    125 GitHub stars~3.2k tokensUpdated 12 days ago
    Auto-check passed
  • Motion Systems

    scott-fryxell/brayness

    A skill your agent uses when designing or implementing motion for web interfaces, including CSS transitions and keyframes, linear() easing design, transform strategy (translate/rotate vs…

    125 GitHub stars~1.7k tokensUpdated 12 days ago
    Auto-check passed
  • Vue Inspect

    scott-fryxell/brayness

    Inspect live Vue 3 component state via agent-browser eval - no Devtools extension, no console.log.

    125 GitHub stars~779 tokensUpdated 12 days ago
    Auto-check passed

Works with

Categories

Questions about Brayness Sync

What does Brayness Sync do?

Sync changes from dev brayness/ to the published git mirror at skills/brayness-sync/published/. Brayness Sync is an agent skill from scott-fryxell/brayness. Sync changes from dev brayness/ to the published git mirror at skills/brayness-sync/published/.

When should I use Brayness Sync?

Brayness Sync fits situations like: prepare release; after major skill/extension changes.

How do I install Brayness Sync in Claude Code?

Run `npx skills add scott-fryxell/brayness --skill brayness-sync -a claude-code`. Or copy the skill folder (skills/brayness-sync in scott-fryxell/brayness) into .claude/skills/brayness-sync in your project. Claude Code loads it when a task matches its description.

How do I install Brayness Sync in Codex?

Run `npx skills add scott-fryxell/brayness --skill brayness-sync -a codex`. Or copy the skill folder (skills/brayness-sync in scott-fryxell/brayness) into .agents/skills/brayness-sync in your project. Codex loads it when a task matches its description.

Can I use Brayness Sync in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add scott-fryxell/brayness --skill brayness-sync -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/brayness-sync, .gemini/skills/brayness-sync, .github/skills/brayness-sync and .opencode/skills/brayness-sync in your project.

What does Brayness Sync need to run?

Going by SKILL.md and its folder, Brayness Sync needs the command-line tools its instructions call (git and npm).

Does Brayness Sync access the network?

SKILL.md contains no URLs. Its commands use git and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Brayness Sync safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Brayness Sync use?

Brayness Sync is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Brayness Sync use?

About 889 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.7k tokens, read only when the agent opens those files.

What are the alternatives to Brayness Sync?

Skills that share tags, products or a category with Brayness Sync: Migrate Internal Package into Ghost (TryGhost/Ghost, 56k stars), Hunk Release Workflow (modem-dev/hunk, 9.6k stars), AionUi Version Bump (iOfficeAI/AionUi, 33k stars) and ZCF Release Automation (UfoMiao/zcf, 6.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Brayness Sync?

scott-fryxell (a GitHub user) maintains it in scott-fryxell/brayness, which has 125 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on September 28, 2026.

Source: scott-fryxell/brayness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.