Devops Engineer
Yikai-Liao/symusic
Creates Dockerfiles, configures CI/CD pipelines, writes Kubernetes manifests, and generates Terraform/Pulumi infrastructure templates.
Infrastructure as code, CI/CD, container orchestration, service networking — methodology and reference patterns for building and operating internal developer platforms.
Install Platform Engineering
$ npx skills add magnus919/hermes-profiles --skill platform-engineering -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install magnus919/hermes-profiles 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/hermes-profiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/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/hermes-profiles/tree/main/skills/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/hermes-profiles/tree/main/skills/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/hermes-profiles --skill platform-engineering -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install magnus919/hermes-profiles platform-engineering --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/hermes-profiles.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/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/hermes-profiles/tree/main/skills/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/hermes-profiles --skill platform-engineering -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install magnus919/hermes-profiles platform-engineering --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/hermes-profiles.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/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/hermes-profiles/tree/main/skills/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/hermes-profiles.git --path skills/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/hermes-profiles --skill platform-engineering -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install magnus919/hermes-profiles 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/hermes-profiles.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/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/hermes-profiles/tree/main/skills/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/hermes-profiles 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/hermes-profiles --skill platform-engineering -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/magnus919/hermes-profiles.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/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/hermes-profiles/tree/main/skills/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/hermes-profiles --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/hermes-profiles platform-engineering --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/hermes-profiles.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/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/hermes-profiles/tree/main/skills/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
- 282
- Token cost
- ~1.4k tokens
- SKILL.md length
- 519 words
- Files
- 10 (incl. references)
- Skills in repo
- 31
- Repo updated
- First seen
- Licence
- MIT
At a glance
Infrastructure as code, CI/CD, container orchestration, service networking — methodology and reference patterns for building and operating internal developer platforms.
- Works in 9 steps: The platform is a product. Internal… → Golden paths, not golden cages. Provide… → Reduce cognitive load. Abstract… → …
- Tasks that involve Platform engineering
- SKILL.md covers When to Load, Loading Order, Reference Files and Output Contract, plus 2 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/hermes-profiles. Infrastructure as code, CI/CD, container orchestration, service networking — methodology and reference patterns for building and operating internal developer platforms.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including reference files (for example `references/automation-languages.md`, `references/ci-cd-pipelines.md` and `references/cloud-platforms.md`).
It sits in DevOps & Cloud, covering Platform engineering, Infrastructure as code and Container orchestration. It works with Terraform. The repository describes itself as: Curated Hermes Agent profiles for specialist swarms — opinionated, Hermes-optimized, artifact-pyramid native. The licence is MIT.
When your agent uses it
- Tasks that involve Platform engineering
- Tasks that involve Infrastructure as code
- Tasks that involve Container orchestration
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 867a555. 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 1.4k tokens when it runs, and up to ~8.2k if it reads all its reference files. Until then it costs about 47 tokens; SKILL.md has 519 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/hermes-profiles at commit 867a555, republished under its MIT licence (© magnus919). 519 words, ~1,397 tokens.
Download SKILL.mdSave it as
.claude/skills/platform-engineering/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.- name
- platform-engineering
- description
- Infrastructure as code, CI/CD, container orchestration, service networking — methodology and reference patterns for building and operating internal developer platforms.
- author
- Hermes Profiles
- license
- MIT
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 |
| Service networking / mesh | Traefik/nginx/Caddy config, Tailscale/Headscale ACL, WireGuard, service mesh |
| Observability strategy | Prometheus rules, Grafana dashboards-as-code, Loki logging, tracing |
| Secret management design | Vault, SOPS, External Secrets Operator patterns |
| Cloud architecture assessment | Multi-cloud patterns, provider foundations, cost governance |
| Deployment pipeline review | End-to-end delivery pipeline audit, release engineering patterns |
Loading Order
skill_view('platform-engineering') # This — methodology index
skill_view('artifact-pyramids') # Output contract
skill_view('docker-management') # Container lifecycle (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/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 |
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 (238 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-management— container lifecycle and Composetraefik— reverse proxy and ingress configurationtailscale— mesh networking and ACL policiesimplementation-planning— work breakdown and dependency orderingmermaid-diagrams— architecture diagram generationsite-reliability-engineering— sister domain (post-deployment reliability)
© 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 9 other files (references) in skills/platform-engineering of magnus919/hermes-profiles.
- SKILL.md
- 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/release-engineering.md
- references/secret-management.md
- references/service-networking.md
Open the folder on GitHubat commit 867a555
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/hermes-profiles | 282 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Devops EngineerYikai-Liao/symusic | 189 | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| Platform Engineeringmagnus919/agent-skills | 116 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Eks Best Practicesaws-samples/appmod-blueprints | 115 | — | ~5k | Automated safety check: Pass | MIT-0 | |
| Eks Reconaws-samples/appmod-blueprints | 115 | — | ~4.7k | Automated safety check: Warn | MIT-0 | |
| Cloud Devopsdavila7/claude-code-templates | 32k | 4 repos | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
Platform Engineering
magnus919/agent-skills
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…
- Official
Eks Best Practices
aws-samples/appmod-blueprints
Advisory guidance for Amazon EKS architecture and configuration decisions — compute strategy, networking, security, reliability, cost, autoscaling, observability, multi-tenancy, and upgrade planning.
- Official
Eks Recon
aws-samples/appmod-blueprints
EKS cluster reconnaissance and environment discovery. An agent skill from aws-samples/appmod-blueprints.
Cloud Devops
davila7/claude-code-templates
Cloud infrastructure and DevOps workflow covering AWS, Azure, GCP, Kubernetes, Terraform, CI/CD, monitoring, and cloud-native development.
Devops Iac Engineer
davila7/claude-code-templates
Implements infrastructure as code using Terraform, Kubernetes, and cloud platforms.
More from magnus919/hermes-profiles
All 31 skills in this repoData Scientist
magnus919/hermes-profiles
PhD-level expertise in data science, statistics, and machine learning.
Brand Designer
magnus919/hermes-profiles
Create comprehensive brand identity documentation for any brand.
Sdd Authoring
magnus919/hermes-profiles
Specification authoring for AI-native SDD — writes formal specifications in structured formats (Gherkin, user stories, acceptance criteria), enforces spec quality gates, and produces…
Sdd Verification
magnus919/hermes-profiles
SDD acceptance criteria verification — maps specification acceptance criteria to tests, validates implementation output against spec requirements, and produces artifact-pyramid-compliant…
Sdd Work Decomposition
magnus919/hermes-profiles
SDD work decomposition — translates formal specifications into dependency-aware task plans with per-task acceptance criteria.
Artifact Pyramids
magnus919/hermes-profiles
Progressive disclosure for what AI agents produce. An agent skill from magnus919/hermes-profiles.
Related
Works with
Categories
Questions about Platform Engineering
What does Platform Engineering do?
Infrastructure as code, CI/CD, container orchestration, service networking — methodology and reference patterns for building and operating internal developer platforms. Platform Engineering is an agent skill from magnus919/hermes-profiles. Infrastructure as code, CI/CD, container orchestration, service networking — methodology and reference patterns for building and operating internal developer platforms.
When should I use Platform Engineering?
Platform Engineering fits situations like: tasks that involve Platform engineering; tasks that involve Infrastructure as code; tasks that involve Container orchestration.
How do I install Platform Engineering in Claude Code?
Run `npx skills add magnus919/hermes-profiles --skill platform-engineering -a claude-code`. Or copy the skill folder (skills/platform-engineering in magnus919/hermes-profiles) 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/hermes-profiles --skill platform-engineering -a codex`. Or copy the skill folder (skills/platform-engineering in magnus919/hermes-profiles) 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/hermes-profiles --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 1.4k tokens (SKILL.md is roughly 5.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 6.8k 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), Platform Engineering (magnus919/agent-skills, 116 stars), Eks Best Practices (aws-samples/appmod-blueprints, 115 stars) and Eks Recon (aws-samples/appmod-blueprints, 115 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/hermes-profiles, which has 282 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on June 27, 2026.
Source: magnus919/hermes-profiles on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.