Agent skill

Project Tooling

by alinaqi in alinaqi/maggy

gh, vercel, supabase, render CLI and deployment platform setup

MITAuto-check: notesDevOps & Cloud

Install Project Tooling

skills CLI
$ npx skills add alinaqi/maggy --skill project-tooling -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install alinaqi/maggy project-tooling --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/alinaqi/maggy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/project-tooling .claude/skills/project-tooling && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
project-tooling
GitHub stars
707
Token cost
~2.5k tokens
SKILL.md length
297 words
Files
1
Skills in repo
71
Repo updated
First seen
Licence
MIT

At a glance

gh, vercel, supabase, render CLI and deployment platform setup

  • Works in 4 steps: GitHub CLI (gh) → Vercel CLI → Supabase CLI → …
  • Tasks that involve Deployment
  • SKILL.md covers Required CLI Tools, Validation Script, GitHub Repository Setup and Vercel Deployment, plus 5 more sections
  • Calls supabase, vercel and gh; reaches api.render.com and github.com; needs RENDER_API_KEY and SUPABASE_ACCESS_TOKEN

What it does

Project Tooling is an agent skill from alinaqi/maggy. gh, vercel, supabase, render CLI and deployment platform setup

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering Deployment. It works with Vercel, Supabase, Git and Python. The repository describes itself as: What started as an opinionated Claude Code setup kit is now an autonomous AI engineering command center. The licence is MIT.

When your agent uses it

  • Tasks that involve Deployment

Example prompts

  • “/project-tooling”

Requirements

  • Python 3
  • Node.js
  • A credential in RENDER_API_KEY
  • A credential in ANTHROPIC_API_KEY

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. GitHub CLI (gh)
  2. Vercel CLI
  3. Supabase CLI
  4. Render CLI (optional - for Render deployments)

What it can do on your machine

Read from SKILL.md and the folder at commit 72a456e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • supabase
    • vercel
    • gh
    • curl
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • api.render.com
    • github.com
    • dashboard.render.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • RENDER_API_KEY
    • SUPABASE_ACCESS_TOKEN
    • SUPABASE_DB_PASSWORD
    • ANTHROPIC_API_KEY
    • VERCEL_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Project Tooling loads about 2.5k tokens when it runs. Until then it costs about 20 tokens; SKILL.md has 297 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~20
When it runs · the whole SKILL.md, loaded when a task matches
~2.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:175
    # Pull env vars to local .env
  • NoteMentions a .env fileSKILL.md:176
    vercel env pull .env.local
  • NoteMentions a .env fileSKILL.md:416
    echo "RENDER_API_KEY=<your-key>" >> .env

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from alinaqi/maggy at commit 72a456e, republished under its MIT licence (© alinaqi). 297 words, ~2,485 tokens.

Download SKILL.mdSave it as .claude/skills/project-tooling/SKILL.md (or your agent's skills folder).
name
project-tooling
description
gh, vercel, supabase, render CLI and deployment platform setup
when-to-use
When setting up deployment, CI/CD, or when CLI tools are needed
user-invocable
false
effort
low

Project Tooling Skill

Standard CLI tools for project infrastructure management.


Required CLI Tools

Before starting any project, verify these tools are installed and authenticated:

1. GitHub CLI (gh)
bash
# Verify installation
gh --version

# Verify authentication
gh auth status

# If not authenticated:
gh auth login
2. Vercel CLI
bash
# Verify installation
vercel --version

# Verify authentication
vercel whoami

# If not authenticated:
vercel login
3. Supabase CLI
bash
# Verify installation
supabase --version

# Verify authentication (check if linked to a project or logged in)
supabase projects list

# If not authenticated:
supabase login
4. Render CLI (optional - for Render deployments)
bash
# Verify installation
render --version

# If using Render API instead:
# Ensure RENDER_API_KEY is set in environment

Validation Script

Run this at project initialization to verify all tools:

bash
#!/bin/bash
# scripts/verify-tooling.sh

set -e

echo "Verifying project tooling..."

# GitHub CLI
if command -v gh &> /dev/null; then
  if gh auth status &> /dev/null; then
    echo "✓ GitHub CLI authenticated"
  else
    echo "✗ GitHub CLI not authenticated. Run: gh auth login"
    exit 1
  fi
else
  echo "✗ GitHub CLI not installed. Run: brew install gh"
  exit 1
fi

# Vercel CLI
if command -v vercel &> /dev/null; then
  if vercel whoami &> /dev/null; then
    echo "✓ Vercel CLI authenticated"
  else
    echo "✗ Vercel CLI not authenticated. Run: vercel login"
    exit 1
  fi
else
  echo "✗ Vercel CLI not installed. Run: npm i -g vercel"
  exit 1
fi

# Supabase CLI
if command -v supabase &> /dev/null; then
  if supabase projects list &> /dev/null; then
    echo "✓ Supabase CLI authenticated"
  else
    echo "✗ Supabase CLI not authenticated. Run: supabase login"
    exit 1
  fi
else
  echo "✗ Supabase CLI not installed. Run: brew install supabase/tap/supabase"
  exit 1
fi

echo ""
echo "All tools verified!"

GitHub Repository Setup

Create New Repository
bash
# Create and push in one command
gh repo create <repo-name> --private --source=. --remote=origin --push

# Or public:
gh repo create <repo-name> --public --source=. --remote=origin --push
Connect Existing Repository
bash
# If repo exists on GitHub but not linked locally
gh repo clone <owner>/<repo>

# Or add remote to existing local project
git remote add origin https://github.com/<owner>/<repo>.git
git push -u origin main
Repository Settings
bash
# Enable branch protection on main
gh api repos/{owner}/{repo}/branches/main/protection -X PUT \
  -F required_status_checks='{"strict":true,"contexts":["quality"]}' \
  -F enforce_admins=false \
  -F required_pull_request_reviews='{"required_approving_review_count":1}'

# Set default branch
gh repo edit --default-branch main

Vercel Deployment

bash
# Link current directory to Vercel project
vercel link

# Or create new project
vercel
Environment Variables
bash
# Add environment variable
vercel env add ANTHROPIC_API_KEY production

# Pull env vars to local .env
vercel env pull .env.local
Deploy
bash
# Deploy to preview
vercel

# Deploy to production
vercel --prod

Supabase Setup

Create New Project
bash
# Create project (interactive)
supabase projects create <project-name> --org-id <org-id>

# Link local to remote
supabase link --project-ref <project-ref>
Local Development
bash
# Start local Supabase
supabase start

# Stop local Supabase
supabase stop

# Reset database (apply all migrations fresh)
supabase db reset
Migrations
bash
# Create new migration
supabase migration new <migration-name>

# Apply migrations to remote
supabase db push

# Pull remote schema to local
supabase db pull
Generate Types
bash
# Generate TypeScript types from schema
supabase gen types typescript --local > src/types/database.ts

# Or from remote
supabase gen types typescript --project-id <ref> > src/types/database.ts

Render Setup (API-based)

Environment
bash
# Set API key
export RENDER_API_KEY=<your-api-key>
Common Operations via API
bash
# List services
curl -H "Authorization: Bearer $RENDER_API_KEY" \
  https://api.render.com/v1/services

# Trigger deploy
curl -X POST -H "Authorization: Bearer $RENDER_API_KEY" \
  https://api.render.com/v1/services/<service-id>/deploys

# Get deploy status
curl -H "Authorization: Bearer $RENDER_API_KEY" \
  https://api.render.com/v1/services/<service-id>/deploys/<deploy-id>

Package.json Scripts

Add these scripts for common operations:

json
{
  "scripts": {
    "verify-tools": "./scripts/verify-tooling.sh",
    "deploy:preview": "vercel",
    "deploy:prod": "vercel --prod",
    "db:start": "supabase start",
    "db:stop": "supabase stop",
    "db:reset": "supabase db reset",
    "db:migrate": "supabase db push",
    "db:types": "supabase gen types typescript --local > src/types/database.ts"
  }
}

CI/CD Integration

GitHub Actions with Vercel
yaml
# .github/workflows/deploy.yml
name: Deploy

on:
  push:
    branches: [main]
  pull_request:
    branches: [main]

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Deploy to Vercel
        uses: amondnet/vercel-action@v25
        with:
          vercel-token: ${{ secrets.VERCEL_TOKEN }}
          vercel-org-id: ${{ secrets.VERCEL_ORG_ID }}
          vercel-project-id: ${{ secrets.VERCEL_PROJECT_ID }}
          vercel-args: ${{ github.ref == 'refs/heads/main' && '--prod' || '' }}
GitHub Actions with Supabase
yaml
# .github/workflows/migrate.yml
name: Migrate Database

on:
  push:
    branches: [main]
    paths:
      - 'supabase/migrations/**'

jobs:
  migrate:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Setup Supabase CLI
        uses: supabase/setup-cli@v1
        with:
          version: latest

      - name: Push migrations
        run: supabase db push
        env:
          SUPABASE_ACCESS_TOKEN: ${{ secrets.SUPABASE_ACCESS_TOKEN }}
          SUPABASE_DB_PASSWORD: ${{ secrets.SUPABASE_DB_PASSWORD }}

Deployment Platform Setup

REQUIRED: When initializing a project, always create todos for deployment platform connection based on the stack.

Platform Selection by Stack
StackDefault PlatformAction Required
Next.js / Node.jsVercelConnect Git repo to Vercel
Python (FastAPI, Flask)RenderConnect Git repo to Render, get API key
Static sitesVercel or Cloudflare PagesConnect Git repo
Vercel: Connect Git Repository

When Vercel is the deployment platform, create this todo:

TODO: Connect Git repository to Vercel for automatic deployments

Steps:

bash
# Option 1: Via CLI
vercel link
vercel git connect

# Option 2: Via Dashboard (recommended for first setup)
# 1. Go to vercel.com/new
# 2. Import Git repository
# 3. Configure project settings
# 4. Deploy

After connecting:

  • Push to main → Production deploy
  • Push to other branches → Preview deploy
  • PRs get deploy previews automatically
Render: Connect Git Repository (Python)

When Render is the deployment platform for Python projects:

Step 1: Ask user for Render API key

Before proceeding, please provide your Render API key.
Get it from: https://dashboard.render.com/u/settings/api-keys

Store it securely - we'll add it to your environment.

Step 2: Create todos

TODO: Get Render API key from user
TODO: Connect Git repository to Render
TODO: Configure Render service (web service or background worker)
TODO: Set environment variables on Render

Step 3: Connect via Dashboard (recommended)

bash
# 1. Go to dashboard.render.com/create
# 2. Select "Web Service" for APIs, "Background Worker" for async
# 3. Connect your GitHub/GitLab repository
# 4. Configure:
#    - Name: <project-name>
#    - Runtime: Python 3
#    - Build Command: pip install -r requirements.txt
#    - Start Command: uvicorn main:app --host 0.0.0.0 --port $PORT

Step 4: Store API key for CI/CD

bash
# Add to GitHub secrets for CI/CD
gh secret set RENDER_API_KEY

# Or add to local env
echo "RENDER_API_KEY=<your-key>" >> .env

Step 5: Configure render.yaml (optional - Infrastructure as Code)

yaml
# render.yaml
services:
  - type: web
    name: <project-name>-api
    runtime: python
    buildCommand: pip install -r requirements.txt
    startCommand: uvicorn main:app --host 0.0.0.0 --port $PORT
    envVars:
      - key: PYTHON_VERSION
        value: "3.11"
      - key: DATABASE_URL
        fromDatabase:
          name: <project-name>-db
          property: connectionString

databases:
  - name: <project-name>-db
    plan: free
Deployment Checklist Template

Add to project todos when setting up deployment:

markdown
## Deployment Setup
- [ ] Create Git repository (gh repo create)
- [ ] Choose deployment platform (Vercel/Render/other)
- [ ] Connect Git to deployment platform
- [ ] Configure environment variables
- [ ] Set up CI/CD workflow
- [ ] Verify preview deployments work
- [ ] Configure production domain

Tooling Anti-Patterns

  • ❌ Hardcoded secrets - use CLI env management or GitHub secrets
  • ❌ Manual deployments - automate via CI/CD
  • ❌ Skipping local Supabase - always develop locally first
  • ❌ Direct production database changes - use migrations
  • ❌ No branch protection - require PR reviews and CI checks
  • ❌ Missing environment separation - keep dev/staging/prod separate

© alinaqi, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/project-tooling of alinaqi/maggy.

Open the folder on GitHubat commit 72a456e

Compare with similar skills

Project Tooling next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Project Tooling compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Project Tooling this skillalinaqi/maggy707—~2.5kAutomated safety check: NotesMIT
Deploy SiteJayFarei/opentraces100—~4.3kAutomated safety check: PassCustom licence
Deploy To Tempsgotempsh/temps831—~1.3kAutomated safety check: NotesApache-2.0
Memstack Deployment Railway Deploycwinvestments/memstack423—~2.1kAutomated safety check: PassProprietary
Vercel CI Integrationjeremylongshore/tons-of-skills-marketplace2.8k—~1.9kAutomated safety check: PassMIT
Vercel Deploy Integrationjeremylongshore/tons-of-skills-marketplace2.8k—~1.7kAutomated safety check: PassMIT

Similar skills

  • Deploy Site

    JayFarei/opentraces

    Land every site-related fix on main, deploy opentraces.ai to Vercel production, and verify it works across all pages (desktop + mobile) and the email-capture flow, fixing and re-deploying until green.

    100 GitHub stars~4.3k tokensUpdated 4 days ago
    DevOps & CloudAuto-check passed
  • Deploy To Temps

    gotempsh/temps

    Deploy applications to the Temps platform with automatic framework detection, Dockerfile generation, and container orchestration.

    831 GitHub stars~1.3k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • A skill your agent uses when the user says 'deploy to Railway', 'Railway setup', 'railway-deploy', or needs to deploy a Node.js, Python, or Docker application to Railway with environment variables…

    423 GitHub stars~2.1k tokensUpdated 13 days ago
    DevOps & CloudAuto-check passed
  • Vercel CI Integration

    jeremylongshore/tons-of-skills-marketplace

    Configure Vercel CI/CD with GitHub Actions, preview deployments, and automated testing.

    2.8k GitHub stars~1.9k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Vercel Deploy Integration

    jeremylongshore/tons-of-skills-marketplace

    Deploy and manage Vercel production deployments with promotion, rollback, and multi-region strategies.

    2.8k GitHub stars~1.7k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Deployment

    ericrisco/rsc-harness

    A skill your agent uses when taking an app from source to live: choosing the deploy target from requirements (Hetzner+Coolify vs Vercel vs a third), then wiring container → CI → registry → host with…

    180 GitHub stars~4.2k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes

More from alinaqi/maggy

All 71 skills in this repo
  • Aeo Optimization

    alinaqi/maggy

    AI Engine Optimization - semantic triples, page templates, content clusters for AI citations

    707 GitHub stars~3.7k tokensUpdated 16 days ago
    Auto-check passed
  • Agent Teams

    alinaqi/maggy

    Claude Code Agent Teams - default team-based development with strict TDD pipeline enforcement

    707 GitHub stars~5k tokensUpdated 16 days ago
    Auto-check: notes
  • AI Models

    alinaqi/maggy

    Latest AI models reference - Claude, OpenAI, Gemini, Eleven Labs, Replicate

    707 GitHub stars~4.1k tokensUpdated 16 days ago
    Auto-check passed
  • Android Java

    alinaqi/maggy

    Android Java development with MVVM, ViewBinding, and Espresso testing

    707 GitHub stars~3.9k tokensUpdated 16 days ago
    Auto-check: notes
  • Android Kotlin

    alinaqi/maggy

    Android Kotlin development with Coroutines, Jetpack Compose, Hilt, and MockK testing

    707 GitHub stars~3k tokensUpdated 16 days ago
    Auto-check passed
  • Autonomous Testing

    alinaqi/maggy

    AI-driven testing agent that auto-discovers, generates, executes, evaluates, and fixes tests for any project type

    707 GitHub stars~1.1k tokensUpdated 16 days ago
    Auto-check passed

Categories

Questions about Project Tooling

What does Project Tooling do?

gh, vercel, supabase, render CLI and deployment platform setup. Project Tooling is an agent skill from alinaqi/maggy.

When should I use Project Tooling?

Project Tooling fits situations like: tasks that involve Deployment.

How do I install Project Tooling in Claude Code?

Run `npx skills add alinaqi/maggy --skill project-tooling -a claude-code`. Or copy the skill folder (skills/project-tooling in alinaqi/maggy) into .claude/skills/project-tooling in your project. Claude Code loads it when a task matches its description.

How do I install Project Tooling in Codex?

Run `npx skills add alinaqi/maggy --skill project-tooling -a codex`. Or copy the skill folder (skills/project-tooling in alinaqi/maggy) into .agents/skills/project-tooling in your project. Codex loads it when a task matches its description.

Can I use Project Tooling in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add alinaqi/maggy --skill project-tooling -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/project-tooling, .gemini/skills/project-tooling, .github/skills/project-tooling and .opencode/skills/project-tooling in your project.

What does Project Tooling need to run?

Going by SKILL.md and its folder, Project Tooling needs the command-line tools its instructions call (supabase, vercel, gh, curl and git) and credentials named RENDER_API_KEY, SUPABASE_ACCESS_TOKEN, SUPABASE_DB_PASSWORD and ANTHROPIC_API_KEY. Our summary lists: Python 3; Node.js; A credential in RENDER_API_KEY; A credential in ANTHROPIC_API_KEY.

Does Project Tooling access the network?

SKILL.md names 3 domains. In commands or code: api.render.com, github.com and dashboard.render.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Project Tooling safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Project Tooling use?

Project Tooling is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Project Tooling use?

About 2.5k tokens (SKILL.md is roughly 9.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Project Tooling?

Skills that share tags, products or a category with Project Tooling: Deploy Site (JayFarei/opentraces, 100 stars), Deploy To Temps (gotempsh/temps, 831 stars), Memstack Deployment Railway Deploy (cwinvestments/memstack, 423 stars) and Vercel CI Integration (jeremylongshore/tons-of-skills-marketplace, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Project Tooling?

alinaqi (a GitHub user) maintains it in alinaqi/maggy, which has 707 GitHub stars. The repository holds 71 skills in this directory. The repository was last updated on September 24, 2026.

Source: alinaqi/maggy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.