Agent skill

Push Skills

by davidondrej in davidondrej/skills

Push skills and global AGENTS.md to the private repo and verify the public mirror.

MITAuto-check passedAgent Workflows

Install Push Skills

skills CLI
$ npx skills add davidondrej/skills --skill push-skills -a claude-code

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

GitHub CLI
$ gh skill install davidondrej/skills push-skills --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/davidondrej/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/skill-authoring/push-skills .claude/skills/push-skills && 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
push-skills
GitHub stars
4.1k
Token cost
~1.3k tokens
SKILL.md length
617 words
Files
2
Skills in repo
51
Repo updated
First seen
Licence
MIT

At a glance

Push skills and global AGENTS.md to the private repo and verify the public mirror.

  • Explicitly invokes /push-skills
  • SKILL.md covers Always include global…, Choose the source file, Prepare without disturbing… and Commit and push, plus 1 more section
  • Calls git and gh
  • Tasks that involve Agent instruction files

What it does

Push Skills is an agent skill from davidondrej/skills. Push skills and global AGENTS.md to the private repo and verify the public mirror. Use only when the user explicitly invokes /push-skills.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Agent Workflows, covering Agent instruction files and Skill authoring. The repository describes itself as: access to david ondrej's personal agent skills. The licence is MIT.

When your agent uses it

  • Explicitly invokes /push-skills
  • Tasks that involve Agent instruction files
  • Tasks that involve Skill authoring

Example prompts

  • “/push-skills”

What it can do on your machine

Read from SKILL.md and the folder at commit 7874889. 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
    • gh

    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 gh, 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

Push Skills loads about 1.3k tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 617 words of instructions outside code blocks.

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

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 davidondrej/skills at commit 7874889, republished under its MIT licence (© davidondrej). 617 words, ~1,346 tokens.

Download SKILL.mdSave it as .claude/skills/push-skills/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
push-skills
description
Push skills and global AGENTS.md to the private repo and verify the public mirror. Use only when the user explicitly invokes /push-skills.
disable-model-invocation
true

Push Skills

Canonical repo: <skills-repo>. Private remote: OWNER/PRIVATE_REPO. Pushing main triggers the sanitized mirror at davidondrej/skills; only the configured publishing process pushes there.

Only commit or push when the user requests it. Editing this skill is not permission to publish it. For distributed skill edits, follow distribute-skill-to-all-agents before pushing.

Always include global instructions

The user's standing scope for an authorized /push-skills run includes saved changes to <workspace>/AGENTS.md, unless they explicitly exclude that file. Check it on every run, even when the latest message names a skill. Preserve the conversation's original publishing objective through skill edits, renames, and other follow-up requests.

After fetching, compare saved global/AGENTS.md with origin/main:global/AGENTS.md. Local dirt may already be published; Git status alone cannot tell. Transfer new edits while preserving upstream changes.

Verify saved global instructions are committed privately and substantive updates appear in public root AGENTS.md. Report this separately; successful skill publication does not complete an AGENTS.md request.

Choose the source file

  • <workspace>/AGENTS.md should link to <skills-repo>/global/AGENTS.md. Save the editor buffer and verify the link. If it differs, inspect both files before choosing; do not replace the link or overwrite either file. Public destination: root AGENTS.md.
  • <skills-repo>/AGENTS.md is a separate, private repo-instruction file and stays excluded.
  • Updating global instructions needs no copy, skill allowlisting, or policy version bump.
  • Skills live under skills/<skill-name>/. Use publish-skill for newly public skills; include policy changes in the same commit.

Prepare without disturbing other work

Run Git in <skills-repo> or the temporary worktree below. Check staged and unstaged changes:

bash
git status --short
git diff --cached --stat
git diff HEAD -- global/AGENTS.md
git remote -v
git fetch origin main

For skills, substitute the intended paths. Confirm origin is private. Review outgoing commits as well as files: every commit ahead of origin/main will push.

  • Clean checkout: fast-forward main with git merge --ff-only origin/main.
  • Only intended edits pending: commit, then rebase those commits onto origin/main.
  • Unrelated edits, staged files, or local commits: use git worktree add --detach <temporary-path> origin/main. Preserve the original checkout and index. Transfer approved changes as a patch against their original base, using three-way application when needed; copy approved new files separately. Preserve newer upstream edits instead of overwriting with an old copy. Resolve conflicts from both versions; ask only when intent is ambiguous.

Do not stash, reset, unstage, or commit someone else's work.

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

Commit and push

Stage only intended paths. Plain git commit includes all staged files regardless of the preceding git add; use an explicit path list:

bash
git add -- global/AGENTS.md
git commit --only -m "Update global agent instructions" -- global/AGENTS.md

Adapt paths and message for skills. Review git show --stat HEAD and git diff origin/main..HEAD before pushing. If nothing needs committing, check whether the intended state is already pushed, then verify it.

bash
git push origin HEAD:main
source_sha=$(git rev-parse HEAD)

If main advanced, fetch, rebase the isolated intended commits, review, and retry. Never force-push. Verify the remote contains the commit instead of relying on push-output labels. Report when a temporary worktree kept the original checkout untouched.

Verify public publication

Find the publication workflow for the pushed commit; a private push alone does not prove publication:

bash
gh run list --repo "$PRIVATE_REPO" --workflow "$PUBLISH_WORKFLOW" \\
  --commit "$source_sha" --json databaseId,headSha,status,conclusion,url
gh run watch <run-id> --repo "$PRIVATE_REPO" --exit-status

Wait for the matching run. If superseded, verify the newer source contains your change. The publishing process may add an automated sync commit, so public Source: can name a descendant of your commit. For failure, cancellation without replacement, or a stall, inspect status/logs and report incomplete publication with the run link. Do not rerun indefinitely.

Read the published file and confirm the intended update:

bash
gh api repos/davidondrej/skills/contents/AGENTS.md \\
  -H 'Accept: application/vnd.github.raw'

Find skill categories from the committed policy and published tree, then check skills/<category>/<skill-name>/SKILL.md. Private-only skills need only private push verification.

The mirror may rewrite or omit content; green CI and file existence do not prove correctness. For missing or unexpected content, inspect the matching publication report artifact and the mirror tooling documentation in <skills-repo>/tools/. Report exclusions/failures accurately. Never bypass the sanitizer or add manual approval gates. Finish with the private commit, workflow result, and published file link.

© davidondrej, 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 1 other file in skills/skill-authoring/push-skills of davidondrej/skills.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 7874889

Compare with similar skills

Push Skills 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.

Push Skills compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Push Skills this skilldavidondrej/skills4.1k—~1.3kAutomated safety check: PassMIT
Harness Agent Team Designerrevfactory/harness9.1k—~4.5kAutomated safety check: PassApache-2.0
Harness Evolution Feedback Looprevfactory/harness9.1k—~855Automated safety check: PassApache-2.0
Skill Creatorccusage/ccusage19k—~1.1kAutomated safety check: PassCustom licence
ShellLM Skill Authorlaude-institute/headlong1.2k—~1.3kAutomated safety check: PassApache-2.0
Authoring Skillsvercel/next.js143k—~1kAutomated safety check: PassMIT

Similar skills

  • Harness Agent Team Designer

    revfactory/harness

    Designs a project-specific agent harness: defines specialist agents, writes the skills they follow, picks an execution mode and model for each, and keeps the setup maintained.

    9.1k GitHub stars~4.5k tokensUpdated 12 days ago
    Agent WorkflowsAuto-check passed
  • Collects feedback on how an agent harness performed, generalizes it, and updates the harness agents, skills and orchestrator along with a change-history table.

    9.1k GitHub stars~855 tokensUpdated 12 days ago
    Agent WorkflowsAuto-check passed
  • Skill Creator

    ccusage/ccusage

    Guides repo-local skill creation and updates. An agent skill from ccusage/ccusage.

    19k GitHub stars~1.1k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • ShellLM Skill Author

    laude-institute/headlong

    Scaffolds new ShellLM skills with the right frontmatter, directory layout and agent-facing writing style, so an agent can extend its own capabilities.

    1.2k GitHub stars~1.3k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Authoring Skills

    vercel/next.js

    Official

    How to create and maintain agent skills in .agents/skills/. An agent skill from vercel/next.js.

    143k GitHub stars~1k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Skill Creator

    Gentleman-Programming/gentle-ai

    Guides writing a new agent skill: when one is warranted, the required folder layout and frontmatter, section order and size limits, with a bundled style guide.

    7.6k GitHub stars~998 tokensUpdated today
    Agent WorkflowsAuto-check passed

More from davidondrej/skills

All 51 skills in this repo
  • Nagent

    davidondrej/skills

    Launch a new bb worker thread with the right project, model, worktree, and task brief.

    4.1k GitHub stars~1.7k tokensUpdated 2 days ago
    Auto-check: notes
  • Browser Harness

    davidondrej/skills

    Direct browser control via CDP. An agent skill from davidondrej/skills.

    4.1k GitHub starsUsed in 2 repos~3k tokens
    Auto-check passed
  • Persistent Localhost

    davidondrej/skills

    Manage persistent dev servers, APIs, and other local processes on a port using macOS LaunchAgents.

    4.1k GitHub stars~618 tokensUpdated 2 days ago
    Auto-check passed
  • Reset Cursor Acp

    davidondrej/skills

    Reset a stuck Cursor ACP thread in <chat-system and reload its configuration.

    4.1k GitHub stars~728 tokensUpdated 2 days ago
    Auto-check passed
  • Anti Sleep

    davidondrej/skills

    Keep a Mac awake for a set duration or while a process runs.

    4.1k GitHub stars~640 tokensUpdated 2 days ago
    Auto-check: warnings
  • Bb CLI

    davidondrej/skills

    Use this when controlling bb. An agent skill from davidondrej/skills.

    4.1k GitHub stars~823 tokensUpdated 2 days ago
    Auto-check passed

Categories

Questions about Push Skills

What does Push Skills do?

Push skills and global AGENTS.md to the private repo and verify the public mirror. Push Skills is an agent skill from davidondrej/skills.md to the private repo and verify the public mirror.

When should I use Push Skills?

Push Skills fits situations like: explicitly invokes /push-skills; tasks that involve Agent instruction files; tasks that involve Skill authoring.

How do I install Push Skills in Claude Code?

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

How do I install Push Skills in Codex?

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

Can I use Push Skills 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 davidondrej/skills --skill push-skills -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/push-skills, .gemini/skills/push-skills, .github/skills/push-skills and .opencode/skills/push-skills in your project.

What does Push Skills need to run?

Going by SKILL.md and its folder, Push Skills needs the command-line tools its instructions call (git and gh).

Does Push Skills access the network?

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

Is Push Skills 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 Push Skills use?

Push Skills 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 Push Skills use?

About 1.3k tokens (SKILL.md is roughly 5.4k 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 Push Skills?

Skills that share tags, products or a category with Push Skills: Harness Agent Team Designer (revfactory/harness, 9.1k stars), Harness Evolution Feedback Loop (revfactory/harness, 9.1k stars), Skill Creator (ccusage/ccusage, 19k stars) and ShellLM Skill Author (laude-institute/headlong, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Push Skills?

davidondrej (a GitHub user) maintains it in davidondrej/skills, which has 4,112 GitHub stars. The repository holds 51 skills in this directory. The repository was last updated on October 8, 2026.

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