How do I install the Pscale Service Token skill?

Run npx skillmds add vince-winkintel/pscale-service-token in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pscale Service Token safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pscale Service Token?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pscale Service Token free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pscale Service Token?

vince-winkintel (@vince-winkintel) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pscale Service Token by vince-winkintel

Name: Pscale Service Token
Rating: 4.5 (4 reviews)
Author: vince-winkintel

Pscale Service Token

Create, show, list, and manage service tokens for CI/CD authentication. Use when setting up automated deployments, configuring CI/CD pipelines (GitHub Actions, GitLab CI, CircleCI, etc.), creating non-interactive authentication, inspecting service token metadata, or rotating CI/CD credentials. Preferred over passwords for production automation. Triggers on service token, service-token show, CI/CD auth, automation token, pipeline authentication.

vince-winkintel 0f7c30a 2 files · 8.3 KB Updated Sep 10, 2026

File contents

pscale service-token

Create, list, and manage service tokens for CI/CD and automation.

Common Commands

# Create service token
pscale service-token create --org <org>

# List service tokens
pscale service-token list --org <org>

# Show safe metadata for one service token
pscale service-token show <token-id> --org <org> --format json

# Delete service token
pscale service-token delete <token-id> --org <org>

Workflows

CI/CD Setup (GitHub Actions)

# 1. Create service token
pscale service-token create --org my-org

# Returns:
#   TOKEN_ID: xxxxx
#   TOKEN: yyyyy

# 2. Add to GitHub Secrets
#   PLANETSCALE_SERVICE_TOKEN_ID = xxxxx
#   PLANETSCALE_SERVICE_TOKEN = yyyyy

# 3. Use in workflow
# .github/workflows/deploy.yml
# env:
#   PLANETSCALE_SERVICE_TOKEN_ID: ${{ secrets.PLANETSCALE_SERVICE_TOKEN_ID }}
#   PLANETSCALE_SERVICE_TOKEN: ${{ secrets.PLANETSCALE_SERVICE_TOKEN }}
# run: |
#   pscale deploy-request deploy my-db my-branch

CI/CD Pipeline Integration

# 1. Create service token
pscale service-token create --org my-org

# 2. Add to your CI/CD secrets/variables
#   PLANETSCALE_SERVICE_TOKEN_ID
#   PLANETSCALE_SERVICE_TOKEN

# 3. Use in your pipeline config (.github/workflows, .gitlab-ci.yml, etc.)
# deploy:
#   script:
#     - pscale deploy-request create $DATABASE $BRANCH_NAME

Token Rotation

# 1. List existing tokens
pscale service-token list --org my-org

# 2. Create new token
pscale service-token create --org my-org

# 3. Update CI/CD secrets

# 4. Delete old token
pscale service-token delete <old-token-id> --org my-org

Inspect a service token

pscale service-token show returns safe service-token metadata such as ID, name, creation time, and last-used time. It does not print the token secret and does not include access grants; use show-access when grants are needed.

pscale service-token show <token-id> --org <org> --format json
pscale service-token show-access <token-id> --org <org> --format json

Treat token IDs and grant details as sensitive operational metadata. Never ask the user to paste a service token secret into chat; use environment variables or a secrets manager.

Troubleshooting

Token authentication fails

Error: 401 Unauthorized

Solutions:

Verify both TOKEN_ID and TOKEN are set correctly
Check token hasn't been deleted: pscale service-token list
Ensure token has required permissions
Try creating new token (old may be expired)

Token not showing in list

Cause: Tokens are organization-scoped

Solution:

# Ensure correct org
pscale org show

# List tokens for specific org
pscale service-token list --org <correct-org>

Security Best Practices

Rotate tokens regularly (every 90 days recommended)
Use separate tokens for different CI/CD systems
Delete unused tokens immediately
Never commit tokens to version control
Use secrets management (GitHub Secrets, environment variables, vault systems)
Limit token scope if possible (coming in future PlanetScale updates)

Related Skills

pscale-auth - Interactive authentication (development)
pscale-deploy-request - Automated deployments via tokens
gitlab-cli-skills - GitLab CI integration
github - GitHub Actions integration

References

See references/commands.md for complete command reference.

---name: pscale-service-tokendescription: Create, show, list, and manage service tokens for CI/CD authentication. Use when setting up automated deployments, configuring CI/CD pipelines (GitHub Actions, GitLab CI, CircleCI, etc.), creating non-interactive authentication, inspecting service token metadata, or rotating CI/CD credentials. Preferred over passwords for production automation. Triggers on service token, service-token show, CI/CD auth, automation token, pipeline authentication.---# pscale service-tokenCreate, list, and manage service tokens for CI/CD and automation.## Common Commands```bash# Create service tokenpscale service-token create --org <org># List service tokenspscale service-token list --org <org># Show safe metadata for one service tokenpscale service-token show <token-id> --org <org> --format json# Delete service tokenpscale service-token delete <token-id> --org <org>```## Workflows### CI/CD Setup (GitHub Actions)```bash# 1. Create service tokenpscale service-token create --org my-org# Returns:# TOKEN_ID: xxxxx# TOKEN: yyyyy# 2. Add to GitHub Secrets# PLANETSCALE_SERVICE_TOKEN_ID = xxxxx# PLANETSCALE_SERVICE_TOKEN = yyyyy# 3. Use in workflow# .github/workflows/deploy.yml# env:# PLANETSCALE_SERVICE_TOKEN_ID: ${{ secrets.PLANETSCALE_SERVICE_TOKEN_ID }}# PLANETSCALE_SERVICE_TOKEN: ${{ secrets.PLANETSCALE_SERVICE_TOKEN }}# run: |# pscale deploy-request deploy my-db my-branch```### CI/CD Pipeline Integration```bash# 1. Create service tokenpscale service-token create --org my-org# 2. Add to your CI/CD secrets/variables# PLANETSCALE_SERVICE_TOKEN_ID# PLANETSCALE_SERVICE_TOKEN# 3. Use in your pipeline config (.github/workflows, .gitlab-ci.yml, etc.)# deploy:# script:# - pscale deploy-request create $DATABASE $BRANCH_NAME```### Token Rotation```bash# 1. List existing tokenspscale service-token list --org my-org# 2. Create new tokenpscale service-token create --org my-org# 3. Update CI/CD secrets# 4. Delete old tokenpscale service-token delete <old-token-id> --org my-org```### Inspect a service token`pscale service-token show` returns safe service-token metadata such as ID, name, creation time, and last-used time. It does not print the token secret and does not include access grants; use `show-access` when grants are needed.```bashpscale service-token show <token-id> --org <org> --format jsonpscale service-token show-access <token-id> --org <org> --format json```Treat token IDs and grant details as sensitive operational metadata. Never ask the user to paste a service token secret into chat; use environment variables or a secrets manager.## Troubleshooting### Token authentication fails**Error:** `401 Unauthorized`**Solutions:**- Verify both TOKEN_ID and TOKEN are set correctly- Check token hasn't been deleted: `pscale service-token list`- Ensure token has required permissions- Try creating new token (old may be expired)### Token not showing in list**Cause:** Tokens are organization-scoped**Solution:**```bash# Ensure correct orgpscale org show# List tokens for specific orgpscale service-token list --org <correct-org>```## Security Best Practices1. **Rotate tokens regularly** (every 90 days recommended)2. **Use separate tokens** for different CI/CD systems3. **Delete unused tokens** immediately4. **Never commit tokens** to version control5. **Use secrets management** (GitHub Secrets, environment variables, vault systems)6. **Limit token scope** if possible (coming in future PlanetScale updates)## Related Skills- **pscale-auth** - Interactive authentication (development)- **pscale-deploy-request** - Automated deployments via tokens- **gitlab-cli-skills** - GitLab CI integration- **github** - GitHub Actions integration## ReferencesSee `references/commands.md` for complete command reference.

Frequently asked questions