How do I install the Pterodactyl Ops skill?

Run npx skillmds@latest add teddy563/pterodactyl-ops 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 Pterodactyl Ops safe to use?

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

Which AI agents work with Pterodactyl Ops?

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 Pterodactyl Ops free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Pterodactyl Ops?

Teddy563 (@teddy563) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pterodactyl Ops by teddy563 — Agent Skill

Name: Pterodactyl Ops
Author: Teddy563

Pterodactyl Ops

Operates Minecraft servers on the Pterodactyl Panel and its fork Pelican Panel. Use whenever the user mentions Pterodactyl, Pelican, "the panel", Wings, a game panel, eggs, allocations, "secondary port", RCON on a panel, SFTP to my server, "/home/container", egg variables, startup command, panel backups, "container out of memory", "Cannot allocate memory", or running Minecraft in Docker on a host panel. Covers RCON setup (secondary allocation), egg variables & the startup command, the AlwaysPreTouch/Xmx container-OOM footgun, panel backups (non-atomic), the client API (files/command/power), and Pelican-vs-Pterodactyl differences. Confirm before exposing RCON or deleting server files.

Teddy563 d57a251 4 files · 9.2 KB Updated Sep 17, 2026

File contents

Pterodactyl / Pelican Ops

Run and configure Minecraft servers on Pterodactyl Panel and Pelican Panel (a fork by the former Pterodactyl team, mid-2024; still beta as of 2026-06, relicensed AGPLv3). Pelican imports Pterodactyl eggs unmodified and keeps the API backward-compatible, so this skill applies to both — note the few differences in references/panel-footguns.md.

Architecture (one-screen model)

Panel (web UI) + Wings (daemon, one per node). Each server is an isolated Docker container; files live at /home/container (host bind-mount under /var/lib/pterodactyl/volumes/<uuid>).
The STARTUP command substitutes egg variables ({{SERVER_JARFILE}}, {{SERVER_MEMORY}}, …) from environment variables at boot. Console/stats stream to the panel.
Allocations: the primary allocation is the game port. Anything else (RCON, query, Geyser, Dynmap) needs a secondary allocation added in the Network tab.

Tasks

RCON → references/rcon-setup.md. Key point: add a secondary allocation first, then set enable-rcon=true / rcon.port=<that port> / a strong rcon.password in server.properties. Confirm with the user before enabling RCON, and never expose the port publicly.
Memory / OOM → if the container dies with "Cannot allocate memory" or the cgroup OOM-kills it: the JVM heap + -XX:+AlwaysPreTouch is claiming the full container limit at boot. Set Xmx below the panel's allocated memory (leave ~1–1.5 GB / 10–15% headroom for JVM native memory) and/or drop AlwaysPreTouch. The panel {{SERVER_MEMORY}} value is the container limit, not a safe heap size. (See performance-tuning for the full flag discussion.)
Backups → references/backup-strategies.md. Panel/Wings backups archive the live filesystem and are NOT atomic — quiesce writes (/save-off then /save-all flush via console or the /command API) before taking one, or stop the server.
Editing config → edit while stopped (a running server can overwrite files on shutdown), then start. Use SFTP for large/bulk file transfers the web file manager handles poorly.
Automation → the client API (below) for scripted file edits, commands, and power actions.

Client API (Pterodactyl + Pelican, backward-compatible)

Auth: Authorization: Bearer ptlc_<key> (Account → API Credentials), Accept: application/json. Rate limit ~240 req/min per key.

Action	Endpoint
Read file	`GET /api/client/servers/{id}/files/contents?file=/path`
Write file	`POST /api/client/servers/{id}/files/write?file=/path`
List files	`GET /api/client/servers/{id}/files/list`
Send command	`POST /api/client/servers/{id}/command` — body `{"command":"save-all flush"}`
Power signal	`POST /api/client/servers/{id}/power` — body `{"signal":"start

Output

Give exact panel steps (which tab, which field) and exact file/server.properties edits. For any destructive action (deleting server files, wiping a world, exposing RCON), state the risk and confirm first.

---name: pterodactyl-opsdescription: Operates Minecraft servers on the Pterodactyl Panel and its fork Pelican Panel. Use whenever the user mentions Pterodactyl, Pelican, "the panel", Wings, a game panel, eggs, allocations, "secondary port", RCON on a panel, SFTP to my server, "/home/container", egg variables, startup command, panel backups, "container out of memory", "Cannot allocate memory", or running Minecraft in Docker on a host panel. Covers RCON setup (secondary allocation), egg variables & the startup command, the AlwaysPreTouch/Xmx container-OOM footgun, panel backups (non-atomic), the client API (files/command/power), and Pelican-vs-Pterodactyl differences. Confirm before exposing RCON or deleting server files.license: MIT---# Pterodactyl / Pelican OpsRun and configure Minecraft servers on Pterodactyl Panel and **Pelican Panel** (a fork by theformer Pterodactyl team, mid-2024; still **beta** as of 2026-06, relicensed **AGPLv3**). Pelicanimports Pterodactyl **eggs unmodified** and keeps the **API backward-compatible**, so this skillapplies to both — note the few differences in `references/panel-footguns.md`.## Architecture (one-screen model)- **Panel** (web UI) + **Wings** (daemon, one per node). Each server is an isolated **Docker container**; files live at **`/home/container`** (host bind-mount under `/var/lib/pterodactyl/volumes/<uuid>`).- The **STARTUP** command substitutes egg variables (`{{SERVER_JARFILE}}`, `{{SERVER_MEMORY}}`, …) from environment variables at boot. Console/stats stream to the panel.- **Allocations**: the *primary* allocation is the game port. Anything else (RCON, query, Geyser, Dynmap) needs a **secondary allocation** added in the **Network** tab.## Tasks- **RCON** → `references/rcon-setup.md`. Key point: add a **secondary allocation** first, then set `enable-rcon=true` / `rcon.port=<that port>` / a strong `rcon.password` in `server.properties`. **Confirm with the user before enabling RCON**, and never expose the port publicly.- **Memory / OOM** → if the container dies with "Cannot allocate memory" or the cgroup OOM-kills it: the JVM heap + `-XX:+AlwaysPreTouch` is claiming the full container limit at boot. **Set `Xmx` below the panel's allocated memory** (leave ~1–1.5 GB / 10–15% headroom for JVM native memory) and/or drop `AlwaysPreTouch`. The panel `{{SERVER_MEMORY}}` value is the *container* limit, not a safe heap size. (See `performance-tuning` for the full flag discussion.)- **Backups** → `references/backup-strategies.md`. Panel/Wings backups archive the **live filesystem and are NOT atomic** — quiesce writes (`/save-off` then `/save-all flush` via console or the `/command` API) before taking one, or stop the server.- **Editing config** → edit while **stopped** (a running server can overwrite files on shutdown), then start. Use **SFTP** for large/bulk file transfers the web file manager handles poorly.- **Automation** → the client API (below) for scripted file edits, commands, and power actions.## Client API (Pterodactyl + Pelican, backward-compatible)Auth: `Authorization: Bearer ptlc_<key>` (Account → API Credentials), `Accept: application/json`.Rate limit ~240 req/min per key.| Action | Endpoint ||---|---|| Read file | `GET /api/client/servers/{id}/files/contents?file=/path` || Write file | `POST /api/client/servers/{id}/files/write?file=/path` || List files | `GET /api/client/servers/{id}/files/list` || Send command | `POST /api/client/servers/{id}/command` — body `{"command":"save-all flush"}` || Power signal | `POST /api/client/servers/{id}/power` — body `{"signal":"start|stop|restart|kill"}` |## OutputGive exact panel steps (which tab, which field) and exact file/`server.properties` edits. For anydestructive action (deleting server files, wiping a world, exposing RCON), state the risk andconfirm first.

Frequently asked questions