Migrate Internal Package into Ghost
TryGhost/Ghost
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.
Sync changes from dev brayness/ to the published git mirror at skills/brayness-sync/published/.
$ npx skills add scott-fryxell/brayness --skill brayness-sync -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install scott-fryxell/brayness brayness-sync --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "brayness-sync" agent skill from https://github.com/scott-fryxell/brayness/tree/main/skills/brayness-sync into .claude/skills/brayness-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brayness-sync", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/scott-fryxell/brayness/tree/main/skills/brayness-syncType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add scott-fryxell/brayness --skill brayness-sync -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install scott-fryxell/brayness brayness-sync --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/scott-fryxell/brayness.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/brayness-sync .agents/skills/brayness-sync && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "brayness-sync" agent skill from https://github.com/scott-fryxell/brayness/tree/main/skills/brayness-sync into .agents/skills/brayness-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brayness-sync", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add scott-fryxell/brayness --skill brayness-sync -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install scott-fryxell/brayness brayness-sync --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/scott-fryxell/brayness.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/brayness-sync .cursor/skills/brayness-sync && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "brayness-sync" agent skill from https://github.com/scott-fryxell/brayness/tree/main/skills/brayness-sync into .cursor/skills/brayness-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brayness-sync", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/scott-fryxell/brayness.git --path skills/brayness-sync--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add scott-fryxell/brayness --skill brayness-sync -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install scott-fryxell/brayness brayness-sync --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/scott-fryxell/brayness.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/brayness-sync .gemini/skills/brayness-sync && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "brayness-sync" agent skill from https://github.com/scott-fryxell/brayness/tree/main/skills/brayness-sync into .gemini/skills/brayness-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brayness-sync", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install scott-fryxell/brayness brayness-syncInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add scott-fryxell/brayness --skill brayness-sync -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/scott-fryxell/brayness.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/brayness-sync .github/skills/brayness-sync && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "brayness-sync" agent skill from https://github.com/scott-fryxell/brayness/tree/main/skills/brayness-sync into .github/skills/brayness-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brayness-sync", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add scott-fryxell/brayness --skill brayness-sync -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install scott-fryxell/brayness brayness-sync --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/scott-fryxell/brayness.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/brayness-sync .opencode/skills/brayness-sync && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "brayness-sync" agent skill from https://github.com/scott-fryxell/brayness/tree/main/skills/brayness-sync into .opencode/skills/brayness-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brayness-sync", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
brayness-syncSync 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/. 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.
6 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 71f10e2. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
gitnpmFrom the folder's file list and the shell code blocks in SKILL.md.
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.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
sessions, npm/node_modules), `.env*`, nested `.git/`, `node_modules/`,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.
The full file from scott-fryxell/brayness at commit 71f10e2, republished under its MIT licence (© scott-fryxell). 291 words, ~889 tokens.
.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.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.
| Path | Why |
|---|---|
skills/ | skill catalog |
extensions/ | extensions |
bin/ | harness scripts and CLI wrapper |
prompts/ | prompt templates |
package.json | app dependency + scripts |
AGENTS.md, README.md | agent docs |
.ignore, .nvmrc | repo config |
.pi/agent/settings.json, .pi/agent/models.json | pi config |
.pi/agent/npm/README.md, .pi/agent/npm/.gitignore | add-on signposts |
.pi/agent/extensions | symlink |
.cursor/skills, .claude/skills | repo-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.
references/workflow.md.references/validation.md (no nested .git,
no .env, no node_modules, structure intact). Stop on any failure.git diff in the mirror; walk the user through it.Worked examples: references/examples.md.
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
SKILL.md and 3 other files (references) in skills/brayness-sync of scott-fryxell/brayness.
Open the folder on GitHubat commit 71f10e2
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Brayness Sync this skillscott-fryxell/brayness | 125 | — | ~889 | Automated safety check: Notes | MIT | |
| Migrate Internal Package into GhostTryGhost/Ghost | 56k | — | ~3.8k | Automated safety check: Pass | MIT | |
| Hunk Release Workflowmodem-dev/hunk | 9.6k | — | ~3.8k | Automated safety check: Pass | MIT | |
| AionUi Version BumpiOfficeAI/AionUi | 33k | — | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| ZCF Release AutomationUfoMiao/zcf | 6.1k | — | ~3.4k | Automated safety check: Pass | MIT | |
| Pullkaranhudia/borg-ui | 1.7k | 1 repos | ~1.2k | Automated safety check: Pass | AGPL-3.0 |
TryGhost/Ghost
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.
modem-dev/hunk
Maintainer workflow for preparing, publishing, verifying and curating Hunk releases, with confirmation gates before tags, publishes and public edits.
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.
UfoMiao/zcf
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.
karanhudia/borg-ui
Pull latest origin/main into the current local branch and resolve merge conflicts (aka update-branch).
No-Trade-No-Life/Yuan
生成结构化 git 变更报告(JSON + Markdown)。使用此技能当用户提到"git 变更"、"commit 摘要"、"代码审查"、"release note"、"近期改动"、"每日摘要",或需要分析指定 commit 区间的代码变更。包含三元组结构(设计意图、核心代码、影响范围)的语义化报告,适用于代码审查、发布说明、团队同步、CI/CD 等场景。
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.
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.
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…
scott-fryxell/brayness
Create video compositions, animations, title cards, overlays, captions, voiceovers, audio-reactive visuals, and scene transitions in HyperFrames HTML.
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…
scott-fryxell/brayness
Inspect live Vue 3 component state via agent-browser eval - no Devtools extension, no console.log.
Categories
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/.
Brayness Sync fits situations like: prepare release; after major skill/extension changes.
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.
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.
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.
Going by SKILL.md and its folder, Brayness Sync needs the command-line tools its instructions call (git and npm).
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.
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.
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.
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.
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.
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.