jackson2w/claude-code-skills / synced/cf97bcf7-64d2-4957-bae5-cb5fb135ae82_c88beb8d-59aa-4523-9d2c-7f1ba377a42d/abernathy-deploy
abernathy-deploy
UnverifiedDeploy the Abernathy Magazine static site to GitHub and Cloudflare Pages. Use this skill whenever the user says "deploy", "push", "publish", "go live", "push to GitHub", or "update the site" in the context of the Abernathy Magazine project. Also use it to set up GitHub credentials in the sandbox for the first time. Triggers on any mention of deploying, pushing, or publishing changes to abernathymagazine.com, the abernathymagazine GitHub repo, or Cloudflare Pages.
Abernathy Deploy Skill
Pushes changes in the local abernathymagazine.com project folder to
github.com/jackson2w/abernathymagazine,
which triggers an automatic Cloudflare Pages deployment.
Project details
| Local path | The user's mounted workspace folder (abernathymagazine.com) |
| GitHub repo | https://github.com/jackson2w/abernathymagazine |
| Branch | main |
| Cloudflare | Auto-deploys on every push to main via git integration |
Step 1 — Check credentials
Before pushing, verify the sandbox has GitHub credentials configured:
bash /sessions/gifted-intelligent-archimedes/mnt/.claude/skills/abernathy-deploy/scripts/check-credentials.sh
CREDENTIALS_OK→ skip to Step 3CREDENTIALS_MISSING→ follow Step 2
Step 2 — One-time credential setup (first time only)
The sandbox can't use the user's system keychain, so we embed a GitHub Personal
Access Token (PAT) directly into the local git remote URL. This is safe — the URL
lives only in .git/config, which is never committed.
Ask the user to create a PAT
Tell the user:
"I need a GitHub Personal Access Token to push from this sandbox. Please go to: github.com/settings/tokens/new (or use a fine-grained token at github.com/settings/personal-access-tokens/new) and create a token with Contents: Read and Write access (or
reposcope for classic tokens). Copy the token value and paste it here."
Important: Do NOT ask the user to paste the token in a way that would expose it in the conversation permanently. Accept it, use it immediately in the setup script, and do not log or repeat it.
Run the setup script
Once the user provides the token:
bash /sessions/gifted-intelligent-archimedes/mnt/.claude/skills/abernathy-deploy/scripts/setup-credentials.sh <PAT>
Confirm success with a test push (or git ls-remote origin if no new commits):
git -C /path/to/abernathymagazine.com ls-remote origin HEAD
Step 3 — Stage, commit, and push
cd /path/to/abernathymagazine.com
# Stage changed files (be specific — avoid git add -A)
git add <changed-files>
# Commit with a conventional message
git commit -m "style: describe what changed"
# Push to main — Cloudflare picks it up automatically
git push
Use conventional commit prefixes: feat:, fix:, style:, chore:, docs:
Step 4 — Confirm deployment
After a successful push, let the user know:
"Pushed to GitHub. Cloudflare Pages will deploy automatically — the live site at abernathymagazine.pages.dev (or the custom domain) should update within 30–60 seconds."
To verify the Cloudflare deployment from the terminal (if the user has wrangler):
npx wrangler pages deployment list abernathymagazine
Notes
- The PAT is stored in
.git/configas part of the remote URL — never in a committed file. It will persist across Cowork sessions as long as the user's folder remains mounted. - If a push fails with a 401/403 error, the token may have expired. Re-run Step 2 with a fresh token.
- The Cloudflare Pages build takes 20–60 seconds. No build command is needed — the repo root is the deploy directory.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 117k | Updated | Claude CodeCodex | Unverified | Install |