Complete AI Training
Sign inBecome a member

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Skill · Development

Push skill to github

Commit and push skill changes to the configured skills repository after review and validation.

Agentic Awesome SkillsLicense: MITAdded Sep 5, 2026
Use it in my AI

How to use it

  1. Start your plan and connect your AI once
  2. Add the skill to your AI, one time only: press Copy skill and paste it into your AI's instructions: a project in ChatGPT, Claude or Grok, a Gem in Gemini, an agent in Microsoft 365 Copilot, or a rule in Cursor. It stays there for every new chat. In Kimi, paste it at the start of a new chat.
  3. Ask for the task in your own words, or say it directly:
Use the Push skill to github skill to help me with this.
SKILL.md

Push Skills to GitHub

When to Use

  • Use when skill changes are ready to commit and push to the configured skills repo.
  • Use when the user asks to save or publish skill updates after validation.

For committing any skill change to the user's private skills repo, git root ~/.agents (this is also the canonical skill folder; .claude and .pi/agent/skills symlink to ~/.agents/skills). Pushes here auto-publish a sanitized public mirror to davidondrej/skills — never push directly to that public repo.

Use this after creating or editing a skill. If the skill is distributed to all agents, do that first (distribute-skill-to-all-agents), then run this to push the canonical copy.

Steps

Not in cmux? (no $CMUX_WORKSPACE_ID): skip the cmux pane steps — just run the git commands from step 2 directly in any available terminal, then verify the push output.

  1. Open a fresh cmux pane in the current workspace, no focus steal:
  2. ``bash cmux new-pane --type terminal --direction right --workspace "$CMUX_WORKSPACE_ID" --focus false cmux list-panes --workspace "$CMUX_WORKSPACE_ID" # note the NEW pane + its surface ref ``

  3. Stage, commit, push in ~/.agents (send to the new pane's surface):
  4. ``bash cmux send --surface surface:NEW 'cd ~/.agents && git add -A && git commit -m "<concise message>" && git push' cmux send-key --surface surface:NEW enter ``

  5. Verify the push landed:
  6. ``bash sleep 2 cmux read-screen --surface surface:NEW | tail -15 # expect "main -> main" ``

  7. Close the pane once confirmed:
  8. ``bash cmux close-surface --surface surface:NEW cmux list-panes --workspace "$CMUX_WORKSPACE_ID" # confirm the pane is gone ``

Notes

  • Always run git from ~/.agents (the repo root), not ~/.agents/skills.
  • Write a concise, specific commit message describing the skill change.
  • Only push to GitHub when the user asks. Don't push speculatively.

Example

User request:

Validate the changed skills, review the diff, commit them with a focused message, and push the topic branch.

Limitations

  • Adapted from davidondrej/skills; verify local paths, tools, credentials, and agent features before acting.
  • For commands, remote access, scheduling, browser automation, or file-changing workflows, get explicit user approval and confirm the target environment first.