Pgyer Docs
CI/CD & Dev Tools

Pgyer Skill

PGYER Agent Skill integration guide: let Claude Code, Cursor, Windsurf, and 50+ AI agents handle Pgyer uploads, queries, and CI/CD setup automatically.

An Agent Skill is a capability bundle for AI agents — it tells the agent when to use Pgyer and what flow to follow. The PGYER Agent Skill ships upload decision logic, short-link / QR-code response templates, CI/CD scaffolds, and a troubleshooting checklist. Paired with the open skills CLI, you can install it on Claude Code, Cursor, Windsurf, Codex, OpenCode, Gemini, and 50+ other AI agents in one command.

Full source and latest release live in the GitHub repo: PGYER/pgyer-skill.

How it differs from Pgyer MCP: MCP exposes upload and query as tools for AI clients. The Skill sits on top and adds the "when to call, how to combine, how to wire CI/CD" know-how. You can install both — when the MCP server is present, the Skill prefers it.

Prerequisites

Install

# Install to the current project (commit alongside code, share with teammates)
npx skills add PGYER/pgyer-skill

# Install globally (available in every project for the current user)
npx skills add PGYER/pgyer-skill -g

# Target a specific agent (auto-detected if omitted)
npx skills add PGYER/pgyer-skill -g -a claude-code
npx skills add PGYER/pgyer-skill -g -a cursor
npx skills add PGYER/pgyer-skill -g -a codex

The skills CLI copies the skill files into each agent's skills directory — no manual config required.

Fallback: manual install

git clone https://github.com/PGYER/pgyer-skill.git
cd pgyer-skill
./install.sh

install.sh only handles Claude Code and installs to ~/.claude/skills/pgyer/. For other agents, use the skills CLI or copy the whole directory into the agent's skills path.

Configure your API Key

Choose either approach:

Best for CI/CD — pair with your secrets manager:

export PGYER_API_KEY=<your key>

Best for personal machines — no need to re-export each shell session:

mkdir -p ~/.pgyer && chmod 700 ~/.pgyer
echo 'api_key=<your key>' > ~/.pgyer/config
chmod 600 ~/.pgyer/config

Pair with the MCP Server

When pgyer-mcp-server is installed, the Skill prefers MCP — fewer round-trips and more structured errors. One-line setup for common agents:

# Claude Code
claude mcp add --transport stdio pgyer \
  --env PGYER_API_KEY=<your key> \
  -- npx -y pgyer-mcp-server

# Codex CLI
codex mcp add pgyer --env PGYER_API_KEY=<your key> -- npx -y pgyer-mcp-server

See Pgyer MCP for the full client matrix. If MCP isn't installed, the Skill falls back to Pgyer's official shell upload script automatically.

Usage

Once configured, describe the task in natural language:

Example prompt

Upload build/release/app.apk to Pgyer with install method password and password qa2026.

Other common requests:

  • List apps under the current account, or look up version history by short link.
  • Generate a GitHub Actions or GitLab CI workflow that publishes an Android / iOS / HarmonyOS build to Pgyer.
  • Diagnose an upload failure — the Skill maps Pgyer error codes back to signing, format, or quota issues.

The agent picks between MCP and the shell script automatically and reports back the short link, QR code, and install password.

Feedback

On this page