skills/atxp-git/SKILL.md
Git repository hosting for ATXP-authenticated agents — create repos, get authenticated clone/push URLs, and manage repositories on code.storage
npx skillsauth add atxp-dev/cli atxp-gitInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
ATXP Git gives each agent a private namespace for Git repositories on code.storage. Agents can create repos, get authenticated clone/push URLs, and interact with them using standard Git commands. The MCP server handles provisioning and access control — all file operations happen through native Git.
This is the most important concept to understand when using this tool.
Remote URLs returned by remote-url contain a time-limited JWT embedded directly in the URL. This means:
git clone, git push, git pull, or git fetch using that URL will fail with an authentication error.# Get a new writable URL
npx atxp@latest git remote-url my-project --writable
# Update the existing remote with the new URL
git remote set-url origin <new-url>
# Retry the operation
git push
git credential helper or SSH key configuration is required.If your task involves multiple git operations over time:
1. Get a writable URL at the start of your work session
2. Clone and make changes
3. Commit and push before the URL expires (within 1 hour)
4. If you need to push again later, get a fresh URL first
For tasks that may span multiple hours, request a new URL before each push rather than at the start. The --ttl flag can extend expiry up to the server maximum, but planning for refresh is more robust.
remote-url with writable: false.remote-url output like a secret. Do not log, echo, or share writable URLs.| Command | Cost | Description |
|---------|------|-------------|
| npx atxp@latest git create <repoName> | $0.50 | Create a new repository |
| npx atxp@latest git list | Free | List your repositories |
| npx atxp@latest git remote-url <repoName> | Free | Get a read-only authenticated URL |
| npx atxp@latest git remote-url <repoName> --writable | $0.01 | Get a writable authenticated URL |
| npx atxp@latest git delete <repoName> | Free | Soft-delete a repository |
| npx atxp@latest git help | Free | Show help |
| Option | Applies To | Description |
|--------|-----------|-------------|
| --visibility <private\|public> | create | Repository visibility (default: private) |
| --default-branch <name> | create | Default branch name (default: main) |
| --writable | remote-url | Request a push-capable URL ($0.01 instead of free) |
| --ttl <seconds> | remote-url | URL expiry in seconds (default: 3600) |
| --limit <n> | list | Max repos to return (default: 20, max: 100) |
| --cursor <token> | list | Pagination cursor from a previous response |
Repository names must be lowercase alphanumeric with hyphens and underscores only (e.g., my-project, agent_workspace).
# 1. Create a repository ($0.50)
npx atxp@latest git create my-app
# 2. Get a writable URL ($0.01)
npx atxp@latest git remote-url my-app --writable
# Returns: https://t:[email protected]/userid/my-app.git
# 3. Clone, work, push (standard git)
git clone <url>
cd my-app
# ... make changes ...
git add . && git commit -m "initial commit" && git push
# 4. Later — URL expired? Get a fresh one
npx atxp@latest git remote-url my-app --writable
git remote set-url origin <new-url>
git push
| Scenario | Error message |
|----------|---------------|
| Not authenticated | "ATXP authentication required" |
| Repo doesn't exist (or private + not owner) | "Repository not found" |
| Write to another user's repo | "Permission denied" |
| Repo name already taken | "Repository already exists" |
| Service unavailable | "Service temporarily unavailable. Please retry in a few seconds." |
| Git ref conflict | "Conflict: ... Re-read the current state and retry." |
| Mode | Owner | Other authenticated users |
|------|-------|---------------------------|
| Private | Full read/write | No access |
| Public | Full read/write | Read-only (via remote-url with read-only default) |
Exceeding limits returns HTTP 429 with a Retry-After hint.
development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
development
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.
development
End-to-end Parallels smoke, upgrade, and rerun workflow for OpenClaw across macOS, Windows, and Linux guests. Use when Codex needs to run, rerun, debug, or interpret VM-based install, onboarding, gateway smoke tests, latest-release-to-main upgrade checks, fresh snapshot retests, or optional Discord roundtrip verification under Parallels.