How do I install the Push Skill To Github skill?

Run npx skillmds@latest add francostino/push-skill-to-github in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Push Skill To Github safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Push Skill To Github?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Push Skill To Github free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Push Skill To Github?

FrancoStino (@francostino) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Push Skill To Github by francostino

Name: Push Skill To Github
Rating: 4.2 (5 reviews)
Author: FrancoStino

File contents

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.

Open a fresh cmux pane in the current workspace, no focus steal:

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

Stage, commit, push in ~/.agents (send to the new pane's surface):

cmux send --surface surface:NEW 'cd ~/.agents && git add -A && git commit -m "<concise message>" && git push'
cmux send-key --surface surface:NEW enter

Verify the push landed:

sleep 2
cmux read-screen --surface surface:NEW | tail -15   # expect "main -> main"

Close the pane once confirmed:

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.

---name: push-skill-to-githubdescription: Commit and push skill changes to the configured skills repository after review and validation.license: MIT---# 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: ```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 ```2. **Stage, commit, push** in `~/.agents` (send to the new pane's surface): ```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 ```3. **Verify** the push landed: ```bash sleep 2 cmux read-screen --surface surface:NEW | tail -15 # expect "main -> main" ```4. **Close the pane** once confirmed: ```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.

Frequently asked questions

Push Skill To Github