Devops Engineer
Yikai-Liao/symusic
Creates Dockerfiles, configures CI/CD pipelines, writes Kubernetes manifests, and generates Terraform/Pulumi infrastructure templates.
A skill your agent uses when building or operating internal developer platforms: infrastructure as code, CI/CD, container orchestration, service networking, secrets, and observability, or when…
Install Platform Engineering
$ npx skills add magnus919/agent-skills --skill platform-engineering -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install magnus919/agent-skills platform-engineering --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/platform-engineering .claude/skills/platform-engineering && rm -rf skills-srcUse ~/.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/
Install the "platform-engineering" agent skill from https://github.com/magnus919/agent-skills/tree/main/platform-engineering into .claude/skills/platform-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-engineering", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/magnus919/agent-skills/tree/main/platform-engineeringType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add magnus919/agent-skills --skill platform-engineering -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install magnus919/agent-skills platform-engineering --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/platform-engineering .agents/skills/platform-engineering && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "platform-engineering" agent skill from https://github.com/magnus919/agent-skills/tree/main/platform-engineering into .agents/skills/platform-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-engineering", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add magnus919/agent-skills --skill platform-engineering -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install magnus919/agent-skills platform-engineering --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/platform-engineering .cursor/skills/platform-engineering && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "platform-engineering" agent skill from https://github.com/magnus919/agent-skills/tree/main/platform-engineering into .cursor/skills/platform-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-engineering", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/magnus919/agent-skills.git --path platform-engineering--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add magnus919/agent-skills --skill platform-engineering -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install magnus919/agent-skills platform-engineering --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/platform-engineering .gemini/skills/platform-engineering && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "platform-engineering" agent skill from https://github.com/magnus919/agent-skills/tree/main/platform-engineering into .gemini/skills/platform-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-engineering", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install magnus919/agent-skills platform-engineeringInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add magnus919/agent-skills --skill platform-engineering -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/platform-engineering .github/skills/platform-engineering && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "platform-engineering" agent skill from https://github.com/magnus919/agent-skills/tree/main/platform-engineering into .github/skills/platform-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-engineering", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add magnus919/agent-skills --skill platform-engineering -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install magnus919/agent-skills platform-engineering --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/platform-engineering .opencode/skills/platform-engineering && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "platform-engineering" agent skill from https://github.com/magnus919/agent-skills/tree/main/platform-engineering into .opencode/skills/platform-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-engineering", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
platform-engineering- GitHub stars
- 113
- Token cost
- ~2.4k tokens
- SKILL.md length
- 832 words
- Files
- 19 (incl. references)
- Skills in repo
- 115
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when building or operating internal developer platforms: infrastructure as code, CI/CD, container orchestration, service networking, secrets, and observability, or when…
- Works in 9 steps: The platform is a product. Internal… → Golden paths, not golden cages. Provide… → Reduce cognitive load. Abstract… → …
- Operating internal developer platforms: infrastructure as code
- SKILL.md covers When to Load, When not to use, Loading Order and Reference Files, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Platform Engineering is an agent skill from magnus919/agent-skills. Use this skill when building or operating internal developer platforms: infrastructure as code, CI/CD, container orchestration, service networking, secrets, and observability, or when shaping platform products, self-service interfaces, adoption evidence, and policy guardrails. Do not use it to define release process, promotion, rollout, or rollback policy; use release-engineering for that delivery model. Route named-tool configuration and troubleshooting to the corresponding operational skill, such as kubernetes…
Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 21 other files, including reference files (for example `README.md`, `evals/evals.json` and `references/automation-languages.md`).
It sits in DevOps & Cloud, covering Platform engineering, Container orchestration and Infrastructure as code. It works with Kubernetes, Terraform, PostgreSQL and Grafana. The repository describes itself as: Curated collection of AI agent skills for Hermes and other agent frameworks. The licence is MIT.
When your agent uses it
- Operating internal developer platforms: infrastructure as code
- Container orchestration
- Service networking
- Shaping platform products
Example prompts
- “/platform-engineering”
Requirements
- Python 3
- Docker
Workflow steps
9 steps, taken from the first numbered list in SKILL.md.
- The platform is a product. Internal developers are your customers. Their productivity, satisfaction, and cognitive load are the primary…
- Golden paths, not golden cages. Provide paved roads for common workflows but allow escape hatches. Make the right thing easy, not the…
- Reduce cognitive load. Abstract infrastructure complexity. Developers should not need to understand Kubernetes internals or Terraform…
- Everything as code. Infrastructure, configuration, pipelines, and policies are version-controlled, reviewed, and reproducible. Git is the…
- Self-service over tickets. Every manual handoff between teams is a bottleneck. If a developer needs another team to deploy, the platform…
- Automation is the default. If a process can be automated, it must be. Manual operations are toil — tax on the organization.
- Observability is infrastructure. Logs, metrics, traces, and dashboards are platform contract, not optional extras. Every service gets them…
- Security is built in, not bolted on. Supply chain security, secret management, vulnerability scanning, and policy enforcement are platform…
- API-first design. Everything the platform does should be accessible via API — enabling automation, self-service portals, and CLI tools.
What it can do on your machine
Read from SKILL.md and the folder at commit 96fbe07. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Platform Engineering loads about 2.4k tokens when it runs, and up to ~13k if it reads all its reference files. Until then it costs about 147 tokens; SKILL.md has 832 words of instructions outside code blocks.
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 passed
The automated check found no risky patterns in SKILL.md.
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 magnus919/agent-skills at commit 96fbe07, republished under its MIT licence (© magnus919). 832 words, ~2,391 tokens.
Download SKILL.mdSave it as
.claude/skills/platform-engineering/SKILL.md (or your agent's skills folder). This skill also uses 18 other files; get the full folder from GitHub.- name
- platform-engineering
- description
- Use this skill when building or operating internal developer platforms: infrastructure as code, CI/CD, container orchestration, service networking, secrets, and observability, or when shaping platform products, self-service interfaces, adoption evidence, and policy guardrails. Do not use it to define release process, promotion, rollout, or rollback policy; use release-engineering for that delivery model. Route named-tool configuration and troubleshooting to the corresponding operational skill, such as kubernetes or traefik for ingress-controller configuration.
- license
- MIT
- metadata.source_repo
- https://github.com/magnus919/hermes-profiles
Platform Engineering
Core methodology and reference library for platform engineering work. This skill does not execute operations itself — it provides the frameworks, patterns, and reference material that a platform-engineer profile loads on demand.
When to Load
Load this skill when the task involves:
| Trigger | What's Needed |
|---|---|
| Design a CI/CD pipeline | Pipeline structure, GitOps sync strategies, release automation |
| Infrastructure as code plan | Terraform/OpenTofu module patterns, state management, Pulumi/Ansible patterns |
| Container orchestration design | K8s pod lifecycle, Helm chart conventions, Kustomize overlays, Docker Compose; operating a cluster (manifests, RBAC, workloads, upgrades) routes to kubernetes |
| Service networking / mesh | Traefik/nginx/Caddy config, Tailscale/Headscale ACL, WireGuard, service mesh |
| Observability strategy | Prometheus rules, Grafana dashboards-as-code, Loki logging, tracing; operating the Prometheus/OTel/Loki stack (scrape, rules, retention) routes to telemetry, Grafana product work routes to grafana |
| Infrastructure execution | Terraform/OpenTofu plan/apply workflow, state backends, drift detection, upgrades — route to terraform |
| PostgreSQL operations | Server config review, indexes and query plans, vacuum/bloat, backups/PITR, replication — route to postgres |
| Secret management design | Vault, SOPS, External Secrets Operator patterns |
| Cloud architecture assessment | Multi-cloud patterns, provider foundations, cost governance |
| Deployment pipeline review | Delivery-platform architecture; load release-engineering when defining the release model, promotion gates, rollout, or rollback policy |
| Platform product intake or value case | Applicability, internal-user discovery, outcome contracts, adoption/value evidence, and stop/escalation rules |
| Self-service contract or policy exception | API/outcome contract, guardrail evidence, exception ownership, and escape-hatch review |
| Platform observability ownership | Platform-customer adoption, SLI/SLO publication, response routing, and ownership handoffs |
When not to use
Use release-engineering to define release process, promotion, rollout, or rollback policy. This skill builds and operates the delivery platform that implements those decisions.
Loading Order
skill_view('platform-engineering') # This — methodology index
skill_view('artifact-pyramids') # Output contract
skill_view('docker-compose') # Container lifecycle and Compose (if needed)
skill_view('traefik') # Reverse proxy (if needed)
skill_view('tailscale') # Mesh networking (if needed)
skill_view('implementation-planning') # Work breakdown (if needed)Then load domain-specific references from this skill:
skill_view('platform-engineering', file_path='references/ci-cd-pipelines.md')
skill_view('platform-engineering', file_path='references/platform-product-evidence.md')
skill_view('platform-engineering', file_path='references/policy-and-observability-ownership.md')
skill_view('platform-engineering', file_path='references/infrastructure-as-code.md')
# ... etc per domainReference Files
| Reference | Purpose |
|---|---|
references/ci-cd-pipelines.md | GitHub Actions, GitLab CI, Forgejo CI, Jenkins, CircleCI; GitOps with ArgoCD/Flux; release automation |
references/container-orchestration.md | K8s/k3s, Helm chart conventions, Kustomize overlays, RBAC patterns, Docker Compose production patterns |
references/infrastructure-as-code.md | Terraform/OpenTofu module design, state backends, Pulumi project structure, Ansible roles, CloudFormation/CDK |
references/service-networking.md | Reverse proxy config (Traefik, nginx, Caddy), Tailscale/Headscale ACL, WireGuard topology, service mesh (Istio, Cilium) |
references/observability.md | Prometheus recording rules/alerting, Grafana dashboards-as-code, Loki log aggregation, OpenTelemetry tracing |
references/secret-management.md | HashiCorp Vault auth/policies, SOPS/age encryption in Git, External Secrets Operator, Sealed Secrets |
references/cloud-platforms.md | AWS/GCP/Azure foundational services, multi-cloud design, cost governance, provider abstraction |
references/automation-languages.md | Go CLI patterns, Python SDK integration, Bash bootstrap/conventions for platform tooling |
references/release-engineering.md | Container image lifecycle, artifact versioning strategies, release gate checklists, Helm chart promotion |
references/platform-product-evidence.md | Applicability/intake, platform domain boundaries, outcome/self-service contracts, adoption and value evidence |
references/policy-and-observability-ownership.md | Developer-owned delivery with reusable policy checks, exceptions, observability ownership, and response routing |
Templates
| Template | When to Use |
|---|---|
templates/golden-path-self-service-portal.md | Designing a golden path or self-service portal for a developer workflow (scoping, journey, guardrails, escape hatch, metrics) |
templates/iac-review-record.md | Recording a structured review of Terraform/OpenTofu/Pulumi/Ansible modules before they ship |
templates/observability-contract.md | Declaring the metrics/logs/traces contract a service must meet before production traffic |
templates/platform-value-record.md | Recording the platform problem, baseline, adoption assumptions, value model, and stop/escalation decision |
templates/platform-exception-record.md | Reviewing an escape-hatch or policy exception with scope, evidence, expiry, and accountable owner |
Output Contract
The profile using this skill produces artifact pyramids. The response to any caller is the absolute path to 00-index.md. See artifact-pyramids skill for the specification.
Show full SKILL.md (323 more words)Show less
Design Principles
- The platform is a product. Internal developers are your customers. Their productivity, satisfaction, and cognitive load are the primary metrics.
- Golden paths, not golden cages. Provide paved roads for common workflows but allow escape hatches. Make the right thing easy, not the wrong thing impossible.
- Reduce cognitive load. Abstract infrastructure complexity. Developers should not need to understand Kubernetes internals or Terraform state management to deploy their service.
- Everything as code. Infrastructure, configuration, pipelines, and policies are version-controlled, reviewed, and reproducible. Git is the single source of truth.
- Self-service over tickets. Every manual handoff between teams is a bottleneck. If a developer needs another team to deploy, the platform is incomplete.
- Automation is the default. If a process can be automated, it must be. Manual operations are toil — tax on the organization.
- Observability is infrastructure. Logs, metrics, traces, and dashboards are platform contract, not optional extras. Every service gets them by default.
- Security is built in, not bolted on. Supply chain security, secret management, vulnerability scanning, and policy enforcement are platform responsibilities.
- API-first design. Everything the platform does should be accessible via API — enabling automation, self-service portals, and CLI tools.
Related Skills
artifact-pyramids— output contract specificationdocker-compose— container lifecycle and multi-container Compose orchestrationkubernetes— cluster operations: manifests, RBAC, workloads, Helm, upgrades, troubleshootingterraform— Terraform/OpenTofu execution: plan/apply workflow, state backends and locking, drift detection, upgrades and refactorstelemetry— Prometheus/OpenTelemetry Collector/Loki stack operations: scrape configs, rules files, retention, HApostgres— PostgreSQL operations: configuration review, index and query-plan diagnosis, vacuum/bloat, backups/PITR, replication and failovergrafana— Grafana product work: dashboards, panels, data sources, alert rules, contact points, notification policiestraefik— reverse proxy and ingress configurationtailscale— mesh networking and ACL policiesimplementation-planning— work breakdown and dependency orderingmermaid-diagrams— architecture diagram generationsite-reliability-engineering— sister domain for post-deployment reliabilityrelease-engineering— release process, artifact promotion, readiness, rollout, and rollback policy; this skill owns the delivery platform that implements those decisions
© magnus919, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 18 other files (references) in platform-engineering of magnus919/agent-skills.
- SKILL.md
- README.md
- evals/evals.json
- references/automation-languages.md
- references/ci-cd-pipelines.md
- references/cloud-platforms.md
- references/container-orchestration.md
- references/infrastructure-as-code.md
- references/observability.md
- references/platform-product-evidence.md
- references/policy-and-observability-ownership.md
- references/release-engineering.md
- references/secret-management.md
- references/service-networking.md
- templates/golden-path-self-service-portal.md
- templates/iac-review-record.md
- templates/observability-contract.md
- templates/platform-exception-record.md
- … and 1 more
Open the folder on GitHubat commit 96fbe07
Compare with similar skills
Platform Engineering 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Platform Engineering this skillmagnus919/agent-skills | 113 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Devops EngineerYikai-Liao/symusic | 189 | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| Ocioracle/skills | 873 | — | ~2.4k | Automated safety check: Pass | UPL-1.0 | |
| Devops Excellencemajiayu000/spellbook | 286 | — | ~2.4k | Automated safety check: Notes | MIT | |
| Devops Deploymentyonatangross/orchestkit | 289 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Senior Devopsborghei/Claude-Skills | 881 | — | ~1.3k | Automated safety check: Pass | MIT |
Similar skills
- Official
Oci
oracle/skills
Oracle Cloud Infrastructure guidance for designing, operating, and troubleshooting OCI services, including OCI Kubernetes Engine (OKE), OCI Internet of Things Platform, OCI Functions deployment and…
Devops Excellence
majiayu000/spellbook
DevOps and CI/CD expert. An agent skill from majiayu000/spellbook.
Devops Deployment
yonatangross/orchestkit
A skill your agent uses when setting up CI/CD pipelines, containerizing applications, deploying to Kubernetes, or writing infrastructure as code.
Senior Devops
borghei/Claude-Skills
DevOps for CI/CD, containers, Kubernetes, and Terraform. An agent skill from borghei/Claude-Skills.
Senior DevOps Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
More from magnus919/agent-skills
All 115 skills in this repoArtifact Pyramids
magnus919/agent-skills
Organize durable agent research outputs as summaries, analysis, and evidence dossiers.
Ascii City Engine
magnus919/agent-skills
Build portable, first-person colored ASCII city engines and small GIS-derived city packs.
Color Management
magnus919/agent-skills
Manage color workflows with ICC profiles, working spaces, gamut mapping, and color science.
Data Scientist
magnus919/agent-skills
A skill your agent uses for PhD-level expertise in data science, statistics, and machine learning: rigorous statistical analysis, experimental design, causal inference, advanced modeling, research…
Docker Compose
magnus919/agent-skills
Use Docker Compose to define, run, debug, and harden multi-container applications.
Fpga Development
magnus919/agent-skills
Design, review, simulate, and verify FPGA logic using explicit RTL contracts, clock and reset models, CDC analysis, timing constraints, and reproducible implementation evidence.
Related
Works with
Categories
Questions about Platform Engineering
What does Platform Engineering do?
A skill your agent uses when building or operating internal developer platforms: infrastructure as code, CI/CD, container orchestration, service networking, secrets, and observability, or when…. Platform Engineering is an agent skill from magnus919/agent-skills. Use this skill when building or operating internal developer platforms: infrastructure as code, CI/CD, container orchestration, service networking, secrets, and observability, or when shaping platform products, self-service interfaces, adoption evidence, and policy guardrails.
When should I use Platform Engineering?
Platform Engineering fits situations like: operating internal developer platforms: infrastructure as code; container orchestration; service networking; shaping platform products.
How do I install Platform Engineering in Claude Code?
Run `npx skills add magnus919/agent-skills --skill platform-engineering -a claude-code`. Or copy the skill folder (platform-engineering in magnus919/agent-skills) into .claude/skills/platform-engineering in your project. Claude Code loads it when a task matches its description.
How do I install Platform Engineering in Codex?
Run `npx skills add magnus919/agent-skills --skill platform-engineering -a codex`. Or copy the skill folder (platform-engineering in magnus919/agent-skills) into .agents/skills/platform-engineering in your project. Codex loads it when a task matches its description.
Can I use Platform Engineering 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 magnus919/agent-skills --skill platform-engineering -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/platform-engineering, .gemini/skills/platform-engineering, .github/skills/platform-engineering and .opencode/skills/platform-engineering in your project.
What does Platform Engineering need to run?
SKILL.md names no scripts, command-line tools or credentials: Platform Engineering is instructions for the agent only. Our summary lists: Python 3; Docker.
Does Platform Engineering access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Platform Engineering safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Platform Engineering use?
Platform Engineering is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Platform Engineering use?
About 2.4k tokens (SKILL.md is roughly 9.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 11k tokens, read only when the agent opens those files.
What are the alternatives to Platform Engineering?
Skills that share tags, products or a category with Platform Engineering: Devops Engineer (Yikai-Liao/symusic, 189 stars), Oci (oracle/skills, 873 stars), Devops Excellence (majiayu000/spellbook, 286 stars) and Devops Deployment (yonatangross/orchestkit, 289 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Platform Engineering?
magnus919 (a GitHub user) maintains it in magnus919/agent-skills, which has 113 GitHub stars. The repository holds 115 skills in this directory. The repository was last updated on October 6, 2026.
Source: magnus919/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.