github-sync-agent SKILL.md skillA
github-sync-agent from alamoooooooo/alamo_hub is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add alamoooooooo/alamo_hub/github-sync-agent@git:20260721.a03daa2Pins git:20260721.a03daa2 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- alamoooooooo/alamo_hub
- Path
packages/github_sync_workflow_kernel/github-sync-agent/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260721.a03daa2, committed Jul 21, 2026
- Size
- 4,704 bytes
- Repository stars
- 5
- License
- Apache-2.0
Coordinate an end-to-end GitHub synchronization workflow over a target repository by discovering the real repo root, inspecting auth and remotes, classifying local changes, preparing the right commit scope, pushing the chosen remote, and verifying final state. Use when a user wants one reusable skill for GitHub setup, search, sync, commit, and push instead of ad hoc terminal steps.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# GitHub Sync Agent Act like a dedicated mini-agent that coordinates repository discovery, GitHub auth inspection, commit-scope review, commit creation, push, and verification. This skill is the workflow and host-adapter layer. Keep reusable Git/GitHub policy in the `references/` files, not in one-off chat explanations. ## Core Policy - Treat the current directory as a router until the real repository is identified. - Inspect before mutating: branch, remotes, worktree, and tracking must be known first. - Separate auth setup from repository changes. - Preserve the user's remote strategy when possible. - Prefer explicit push targets over guessing. - Exclude whitespace-only noise and obvious generated-output noise unless the user explicitly wants them committed. ## Default Workflow 1. Identify the actual target repository. 2. Inspect: - current branch - upstream tracking - remotes - worktree state 3. Inspect the auth path: - SSH vs HTTPS - credential or SSH readiness - WSL-specific GitHub SSH routing when relevant 4. Decide which path applies: - push existing commits only - stage and create a new commit first …
Read the whole file at its exact version.
How to install
mdr add alamoooooooo/alamo_hub/github-sync-agent@sha256:3edd71d801b11624The line at the top of this page pins the label git:20260721.a03daa2, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_5jnbio5nskqhadjt)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 21, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4704 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
alamoooooooo/alamo_hub · 5 stars · license Apache-2.0 · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5jnbio5nskqhadjt GET https://markdownregistry.com/api/v1/resolve?ref=alamoooooooo/alamo_hub/github-sync-agent GET https://markdownregistry.com/api/v1/blob/3edd71d801b1162454f66364b4441c09ff6e62ecea93f6162424ec7933f30bc6
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.