Agent skill

Downstream Sync

by mrchantey in mrchantey/beet

Refresh every downstream repo (beetatproto, beetconnect, beetegress, beetesp, beeteval) with beet's AGENTS.md marker block, its MIT/Apache licenses and shared config files.

Apache-2.0Auto-check passedAgent Workflows

Install Downstream Sync

skills CLI
$ npx skills add mrchantey/beet --skill downstream-sync -a claude-code

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

GitHub CLI
$ gh skill install mrchantey/beet downstream-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/mrchantey/beet.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/downstream-sync .claude/skills/downstream-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
downstream-sync
GitHub stars
135
Token cost
~1.1k tokens
SKILL.md length
447 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
Apache-2.0

At a glance

Refresh every downstream repo (beetatproto, beetconnect, beetegress, beetesp, beeteval) with beet's AGENTS.md marker block, its MIT/Apache licenses and shared config files.

  • Works in 3 steps: rustfmt.toml, LICENSE-MIT.txt,… → AGENTS.md inherited block: everything… → CLAUDE.md -> AGENTS.md symlink.
  • Tasks that involve Agent instruction files
  • SKILL.md covers Downstream repos, What is synced, Skills are not synced and The contract, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Downstream Sync is an agent skill from mrchantey/beet. Refresh every downstream repo (beetatproto, beetconnect, beetegress, beetesp, beeteval) with beet's AGENTS.md marker block, its MIT/Apache licenses and shared config files. Use after changing AGENTS.md, the licenses or rustfmt.toml.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Agent instruction files. It works with Bluesky. The repository describes itself as: A malleable engine built on interoperable standards. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Agent instruction files

Example prompts

  • “/downstream-sync”

Workflow steps

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

  1. rustfmt.toml, LICENSE-MIT.txt, LICENSE-APACHE.txt: verbatim copies of beet's, so every downstream formats like beet and is dual licensed…
  2. AGENTS.md inherited block: everything between the markers is replaced with beet's current AGENTS.md (the working tree version, so…
  3. CLAUDE.md -> AGENTS.md symlink.

What it can do on your machine

Read from SKILL.md and the folder at commit 75be3c1. 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

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown and bash).

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

  • Network

    No URLs in SKILL.md.

    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

Downstream Sync loads about 1.1k tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 447 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~63
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

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 passed

The automated check found no risky patterns in SKILL.md.

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 mrchantey/beet at commit 75be3c1, republished under its Apache-2.0 licence (© mrchantey). 447 words, ~1,143 tokens.

Download SKILL.mdSave it as .claude/skills/downstream-sync/SKILL.md (or your agent's skills folder).
name
downstream-sync
description
Refresh every downstream repo (beet_atproto, beet_connect, beet_egress, beet_esp, beet_eval) with beet's AGENTS.md marker block, its MIT/Apache licenses and shared config files. Use after changing AGENTS.md, the licenses or rustfmt.toml.

Downstream Sync

Beet has downstream repos (separate git repos building on beet via a path dependency). Each inherits beet's conventions rather than fracturing into its own: a verbatim copy of beet's AGENTS.md lives inside a marker block at the bottom of the downstream AGENTS.md, and beet's licenses and shared config files are copied as-is. This skill refreshes all of that; downstream-create scaffolds a new repo and registers it here.

Downstream repos

  • /home/pete/me/beet_atproto
  • /home/pete/me/beet_connect
  • /home/pete/me/beet_egress
  • /home/pete/me/beet_esp
  • /home/pete/me/beet_eval

downstream-create adds a new repo to this list and to the DOWNSTREAM array below.

What is synced

  1. rustfmt.toml, LICENSE-MIT.txt, LICENSE-APACHE.txt: verbatim copies of beet's, so every downstream formats like beet and is dual licensed MIT OR Apache-2.0 like beet.
  2. AGENTS.md inherited block: everything between the markers is replaced with beet's current AGENTS.md (the working tree version, so in-flight edits propagate):
md
<!-- beet:sync:begin, beet's AGENTS.md refreshed by the downstream-sync skill, do not hand-edit -->
<!-- beet:sync:end -->
  1. CLAUDE.md -> AGENTS.md symlink.

Skills are not synced

No skill is copied into a downstream. A skill an agent working on a crate built on beet would invoke lives in the shared user-level ~/.agents/skills (stowed from /home/pete/me/arch-config/stow/agents/.agents/skills), so every repo already sees it: the generic ones under their own names (docs-diataxis, release, phased-plan, ..), the beet-specific ones prefixed beet- (beet-rendering, beet-create-cli, beet-audit-free-fns).

Beet-repo procedures stay in $BEET/.agents/skills, since they name beet's justfile recipes, worktrees, example set, site and deploy; they are reachable at that path like every other beet-relative path in the block. A downstream's own equivalents (its test command, its deploy entry) belong in its AGENTS.md header, and its .agents/skills holds only its own skills (beet_egress keeps download-takeout there), never named like a shared one.

Show full SKILL.md (184 more words)Show less

The contract

  • A downstream AGENTS.md is its repo-specific header followed by the synced block. Where the header conflicts with the block, the header wins; downstream deltas (target quirks, path-dep notes, test attribute spellings) belong in the header, never as edits inside the block.
  • Never hand-edit inside the markers; the next sync clobbers it.
  • Leave all changes unstaged in every repo, including this one. Never commit.
  • A downstream AGENTS.md missing the markers is malformed, and a missing AGENTS.md is the same case: the script warns and skips it. Write the header by hand with the markers at the end (downstream-create's template is the shape), never append a second copy of anything, then rerun.

Run it

sh
BEET=/home/pete/me/beet
DOWNSTREAM=(/home/pete/me/beet_atproto /home/pete/me/beet_connect /home/pete/me/beet_egress /home/pete/me/beet_esp /home/pete/me/beet_eval)

for repo in "${DOWNSTREAM[@]}"; do
	for file in rustfmt.toml LICENSE-MIT.txt LICENSE-APACHE.txt; do
		cp "$BEET/$file" "$repo/$file"
	done
	if grep -q '<!-- beet:sync:begin' "$repo/AGENTS.md" 2>/dev/null; then
		awk -v src="$BEET/AGENTS.md" '
			/<!-- beet:sync:begin/ { print; while ((getline line < src) > 0) print line; close(src); skip=1; next }
			/<!-- beet:sync:end/ { skip=0 }
			!skip { print }
		' "$repo/AGENTS.md" > "$repo/AGENTS.md.tmp" && mv "$repo/AGENTS.md.tmp" "$repo/AGENTS.md"
		ln -sf AGENTS.md "$repo/CLAUDE.md"
	else
		echo "$repo/AGENTS.md: missing or no sync markers, write the header by hand" >&2
	fi
done

Afterwards spot-check one downstream repo: AGENTS.md header intact, exactly one block with beet's current text inside it, and both license files present.

Candidates deliberately not synced

  • justfile, .cargo/config.toml, .gitignore: repo-shaped, they drift for real reasons; downstream-create writes their initial shape.
  • Cargo.toml: repo-shaped; its license = "MIT OR Apache-2.0" (on the package, or [workspace.package] in a workspace) is set once, and downstream-create's template carries it.
  • .github/workflows/test.yml: revisit when a downstream gains CI.

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

Files

Just SKILL.md in .agents/skills/downstream-sync of mrchantey/beet.

Open the folder on GitHubat commit 75be3c1

Compare with similar skills

Downstream 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.

Downstream Sync compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Downstream Sync this skillmrchantey/beet135—~1.1kAutomated safety check: PassApache-2.0
Using Agent Skillsaddyosmani/agent-skills102k4 repos~2.4kAutomated safety check: PassMIT
Claude ReflectBayramAnnakov/claude-reflect1.7k2 repos~627Automated safety check: PassMIT
Neat-Freak Knowledge CloseoutKKKKhazix/khazix-skills21k—~1.9kAutomated safety check: PassMIT
Task Observerrebelytics/one-skill-to-rule-them-all3.2k1 repos~12kAutomated safety check: PassCC-BY-4.0
Writing For Agentsbestofjs/bestofjs3.1k17 repos~2.7kAutomated safety check: PassMIT

Similar skills

  • Using Agent Skills

    addyosmani/agent-skills

    Meta-skill for choosing which workflow skill fits the task at hand, plus always-on habits: surface assumptions, stop on confusion, push back, keep it simple and stay in scope.

    102k GitHub starsUsed in 4 repos~2.4k tokens
    Agent WorkflowsAuto-check passed
  • Claude Reflect

    BayramAnnakov/claude-reflect

    Self-learning system that captures corrections during sessions and reminds users to run /reflect to update CLAUDE.md.

    1.7k GitHub starsUsed in 2 repos~627 tokens
    Agent WorkflowsAuto-check passed
  • Neat-Freak Knowledge Closeout

    KKKKhazix/khazix-skills

    Brings project docs, agent rule files, authorized memory and leftover workspace files back in line with what the code and runtime actually do at the end of a work session.

    21k GitHub stars~1.9k tokensUpdated 6 days ago
    Agent WorkflowsAuto-check passed
  • Task Observer

    rebelytics/one-skill-to-rule-them-all

    Monitors task execution for skill improvement opportunities.

    3.2k GitHub starsUsed in 1 repo~12k tokens
    Agent WorkflowsAuto-check passed
  • Writing For Agents

    bestofjs/bestofjs

    Writing documents for agents. An agent skill from bestofjs/bestofjs.

    3.1k GitHub starsUsed in 17 repos~2.7k tokens
    Agent WorkflowsAuto-check passed
  • SkillOpt Sleep Cycle

    microsoft/SkillOpt

    Official

    Runs an on-demand or nightly sleep cycle that reviews past Claude Code sessions and proposes validated updates to CLAUDE.md and skills.

    18k GitHub stars~2.3k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

More from mrchantey/beet

All 11 skills in this repo
  • Downstream Create

    mrchantey/beet

    Scaffold a new beet downstream repo (beet<name, a sibling of this checkout depending on the beet facade by path) from the template, register it with downstream-sync and run the first sync.

    135 GitHub stars~709 tokensUpdated today
    Auto-check passed
  • Test Examples

    mrchantey/beet

    Run the workspace example smoke set to catch regressions unit tests miss, covering every feature gate combination with self-terminating examples and curl-probed servers.

    135 GitHub stars~2.8k tokensUpdated today
    Auto-check passed
  • Test The Works

    mrchantey/beet

    Maximal project health pass. An agent skill from mrchantey/beet.

    135 GitHub stars~382 tokensUpdated today
    Auto-check passed
  • Docs Rust Sweep

    mrchantey/beet

    Comprehensive public-api quality pass over the core crates, reducing pub visibility and documenting every public item to a deny(missingdocs) standard.

    135 GitHub stars~590 tokensUpdated today
    Auto-check passed
  • Infra Deploy

    mrchantey/beet

    The release process for the beet website. An agent skill from mrchantey/beet.

    135 GitHub stars~16k tokensUpdated today
    Auto-check: warnings
  • Docs Site

    mrchantey/beet

    Write and edit the public website docs in site/routes/docs (beet.org/docs).

    135 GitHub stars~672 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Downstream Sync

What does Downstream Sync do?

Refresh every downstream repo (beetatproto, beetconnect, beetegress, beetesp, beeteval) with beet's AGENTS.md marker block, its MIT/Apache licenses and shared config files. Downstream Sync is an agent skill from mrchantey/beet.md marker block, its MIT/Apache licenses and shared config files.

When should I use Downstream Sync?

Downstream Sync fits situations like: tasks that involve Agent instruction files.

How do I install Downstream Sync in Claude Code?

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

How do I install Downstream Sync in Codex?

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

Can I use Downstream 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 mrchantey/beet --skill downstream-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/downstream-sync, .gemini/skills/downstream-sync, .github/skills/downstream-sync and .opencode/skills/downstream-sync in your project.

What does Downstream Sync need to run?

SKILL.md names no scripts, command-line tools or credentials: Downstream Sync is instructions for the agent only.

Does Downstream Sync access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Downstream Sync safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Downstream Sync use?

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

How many tokens does Downstream Sync use?

About 1.1k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Downstream Sync?

Skills that share tags, products or a category with Downstream Sync: Using Agent Skills (addyosmani/agent-skills, 102k stars), Claude Reflect (BayramAnnakov/claude-reflect, 1.7k stars), Neat-Freak Knowledge Closeout (KKKKhazix/khazix-skills, 21k stars) and Task Observer (rebelytics/one-skill-to-rule-them-all, 3.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Downstream Sync?

mrchantey (a GitHub user) maintains it in mrchantey/beet, which has 135 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 7, 2026.

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