agentleFS
alanalvestechalanalvestech/hitank/skills/planetscale/SKILL.md

planetscale

Skill38 starsChanged 8 months agoMITView on GitHub

Manage PlanetScale databases, branches, deploy requests and backups via REST API

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the output is OK, proceed to the Flow section.

    line 36
  2. Very specific:

    If the output is SETUP_NEEDED, guide the user step by step.

    line 38
  3. Distinctive:

    If the script outputs an error, the credentials are invalid.

    line 63
  4. Very specific:

    Ask: "Do you want to create a new branch named BRANCH_NAME from PARENT_BRANCH?" Only execute after a "yes".

    line 109

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/planetscale

Connect to the PlanetScale REST API to manage databases, branches, deploy requests, backups and more. Pure Ruby, zero gems — stdlib only.

Structure

scripts/
├── auth.rb                # Basic auth + ps_request helper (required by all scripts)
├── check_setup.rb         # Check if credentials exist (outputs OK or SETUP_NEEDED)
├── save_token.rb          # Save and validate service token credentials
├── organizations.rb       # List organizations
├── databases.rb           # List databases for an organization
├── database.rb            # Get database details
├── branches.rb            # List branches for a database
├── branch.rb              # Get branch details
├── create_branch.rb       # Create a new branch
├── deploy_requests.rb     # List deploy requests for a database
├── create_deploy_request.rb # Create a deploy request
└── backups.rb             # List backups for a database

Setup (check before using)

ruby ~/.claude/skills/planetscale/scripts/check_setup.rb

If the output is OK, proceed to the Flow section.

If the output is SETUP_NEEDED, guide the user step by step. Present ONE step at a time, wait for the user to confirm before moving to the next.

Step 1 — Ask the user to create a service token:

You need a PlanetScale service token. Go to your PlanetScale organization settings:

  1. Open Settings → Service tokens in the PlanetScale dashboard
  2. Click New service token
  3. Name it (e.g. "hitank") and grant the desired database access permissions
  4. Copy both the Service token ID and the Service token value

https://app.planetscale.com

Paste the Service token ID first.

Step 2 — When the user pastes the token ID, ask for the token:

Now paste the Service token value.

Step 3 — When the user pastes the token, save both credentials:

ruby ~/.claude/skills/planetscale/scripts/save_token.rb 'PASTED_TOKEN_ID' 'PASTED_TOKEN'

If the script outputs an error, the credentials are invalid. Ask the user to double-check and try again.

If setup is not complete, DO NOT proceed to the Flow. Complete all steps first.

Flow

The argument $ARGUMENTS may contain a database name.

Step 1: List organizations

ruby ~/.claude/skills/planetscale/scripts/organizations.rb

Present the organizations to the user. If there is only one, use it automatically. Otherwise ask which org to work with.

Step 2: List databases

ruby ~/.claude/skills/planetscale/scripts/databases.rb ORG

Present the databases to the user. If $ARGUMENTS matches a database name, use that database. Otherwise ask which database to work with.

Step 3: Show database details

ruby ~/.claude/skills/planetscale/scripts/database.rb ORG DATABASE

Present the database info and ask what the user wants to do.

Step 4: Actions

List branches:

ruby ~/.claude/skills/planetscale/scripts/branches.rb ORG DATABASE

Get branch details:

ruby ~/.claude/skills/planetscale/scripts/branch.rb ORG DATABASE BRANCH

Create a branch (requires user confirmation):

Ask: "Do you want to create a new branch named BRANCH_NAME from PARENT_BRANCH?" Only execute after a "yes".

ruby ~/.claude/skills/planetscale/scripts/create_branch.rb ORG DATABASE BRANCH_NAME
ruby ~/.claude/skills/planetscale/scripts/create_branch.rb ORG DATABASE BRANCH_NAME PARENT_BRANCH

List deploy requests:

ruby ~/.claude/skills/planetscale/scripts/deploy_requests.rb ORG DATABASE

Create a deploy request (requires user confirmation):

Show current branches first, then ask: "Do you want to create a deploy request from BRANCH to DEPLOY_TO?" Only execute after a "yes".

ruby ~/.claude/skills/planetscale/scripts/create_deploy_request.rb ORG DATABASE BRANCH
ruby ~/.claude/skills/planetscale/scripts/create_deploy_request.rb ORG DATABASE BRANCH DEPLOY_TO

List backups:

ruby ~/.claude/skills/planetscale/scripts/backups.rb ORG DATABASE

Notes

  • Pure Ruby, zero gems — stdlib only (json, net/http, uri, fileutils)
  • Auth via service token: Authorization: {service_token_id}:{service_token}
  • Config files: ~/.config/planetscale/token_id and ~/.config/planetscale/token (outside the repo, never commit)
  • Creating branches and deploy requests require explicit user confirmation
  • Base URL: https://api.planetscale.com/v1

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.