Devops Engineer
Yikai-Liao/symusic
Creates Dockerfiles, configures CI/CD pipelines, writes Kubernetes manifests, and generates Terraform/Pulumi infrastructure templates.
Elite DevOps Engineer skill with mastery of CI/CD pipelines, Kubernetes operations, Infrastructure as Code (Terraform/Pulumi), GitOps (ArgoCD), observability systems, and cloud-native architecture.
Install Devops Engineer
$ npx skills add theneoai/awesome-skills --skill devops-engineer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install theneoai/awesome-skills devops-engineer --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/theneoai/awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/persona/software/devops-engineer .claude/skills/devops-engineer && 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 "devops-engineer" agent skill from https://github.com/theneoai/awesome-skills/tree/main/skills/persona/software/devops-engineer into .claude/skills/devops-engineer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "devops-engineer", 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/theneoai/awesome-skills/tree/main/skills/persona/software/devops-engineerType 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 theneoai/awesome-skills --skill devops-engineer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install theneoai/awesome-skills devops-engineer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/theneoai/awesome-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/persona/software/devops-engineer .agents/skills/devops-engineer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "devops-engineer" agent skill from https://github.com/theneoai/awesome-skills/tree/main/skills/persona/software/devops-engineer into .agents/skills/devops-engineer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "devops-engineer", 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 theneoai/awesome-skills --skill devops-engineer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install theneoai/awesome-skills devops-engineer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/theneoai/awesome-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/persona/software/devops-engineer .cursor/skills/devops-engineer && 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 "devops-engineer" agent skill from https://github.com/theneoai/awesome-skills/tree/main/skills/persona/software/devops-engineer into .cursor/skills/devops-engineer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "devops-engineer", 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/theneoai/awesome-skills.git --path skills/persona/software/devops-engineer--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 theneoai/awesome-skills --skill devops-engineer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install theneoai/awesome-skills devops-engineer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/theneoai/awesome-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/persona/software/devops-engineer .gemini/skills/devops-engineer && 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 "devops-engineer" agent skill from https://github.com/theneoai/awesome-skills/tree/main/skills/persona/software/devops-engineer into .gemini/skills/devops-engineer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "devops-engineer", 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 theneoai/awesome-skills devops-engineerInstalls 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 theneoai/awesome-skills --skill devops-engineer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/theneoai/awesome-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/persona/software/devops-engineer .github/skills/devops-engineer && 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 "devops-engineer" agent skill from https://github.com/theneoai/awesome-skills/tree/main/skills/persona/software/devops-engineer into .github/skills/devops-engineer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "devops-engineer", 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 theneoai/awesome-skills --skill devops-engineer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install theneoai/awesome-skills devops-engineer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/theneoai/awesome-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/persona/software/devops-engineer .opencode/skills/devops-engineer && 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 "devops-engineer" agent skill from https://github.com/theneoai/awesome-skills/tree/main/skills/persona/software/devops-engineer into .opencode/skills/devops-engineer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "devops-engineer", 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
devops-engineer- GitHub stars
- 183
- Token cost
- ~2.1k tokens
- SKILL.md length
- 555 words
- Files
- 11 (incl. references)
- Skills in repo
- 550
- Repo updated
- First seen
- Licence
- MIT
At a glance
Elite DevOps Engineer skill with mastery of CI/CD pipelines, Kubernetes operations, Infrastructure as Code (Terraform/Pulumi), GitOps (ArgoCD), observability systems, and cloud-native architecture.
- Works in 4 steps: Requirements → Design → Implementation → …
- Tasks that involve Infrastructure as code
- SKILL.md covers One-Liner, § 1 · System Prompt, § 10 · Scope & Limitations and § 11 · References, plus 4 more sections
- Calls git
What it does
Devops Engineer is an agent skill from theneoai/awesome-skills. Elite DevOps Engineer skill with mastery of CI/CD pipelines, Kubernetes operations, Infrastructure as Code (Terraform/Pulumi), GitOps (ArgoCD), observability systems, and cloud-native architecture. Transforms AI into a principal platform engineer who designs reliable, scalable, cost-optimized infrastructure at enterprise scale. Use when: devops, kubernetes, terraform, cicd, sre, gitops,
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including reference files (for example `EVALUATION_REPORT.md`, `references/domain.md` and `references/overview.md`).
It sits in DevOps & Cloud, covering Infrastructure as code, Container orchestration and CI/CD. It works with Kubernetes, Terraform, Argo CD and Pulumi. The repository describes itself as: 🌟1000+ Expert AI Skills | CEO, Doctor, Engineer, Scientist & more | Transform AI into any professional | Powered by https://theneoai.github.io/skill-writer/. The licence is MIT.
When your agent uses it
- Tasks that involve Infrastructure as code
- Tasks that involve Container orchestration
- Tasks that involve CI/CD
Example prompts
- “/devops-engineer”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 61fe4f2. 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
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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
Devops Engineer loads about 2.1k tokens when it runs, and up to ~7.2k if it reads all its reference files. Until then it costs about 101 tokens; SKILL.md has 555 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 theneoai/awesome-skills at commit 61fe4f2, republished under its MIT licence (© theneoai). 555 words, ~2,110 tokens.
Download SKILL.mdSave it as
.claude/skills/devops-engineer/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.- name
- devops-engineer
- description
- Elite DevOps Engineer skill with mastery of CI/CD pipelines, Kubernetes operations, Infrastructure as Code (Terraform/Pulumi), GitOps (ArgoCD), observability systems, and cloud-native architecture. Transforms AI into a principal platform engineer who designs reliable, scalable, cost-optimized infrastructure at enterprise scale. Use when: devops, kubernetes, terraform, cicd, sre, gitops,
- kind
- persona
- version
- 1.0.0
- license
- MIT
- metadata.author
- theNeoAI <lucas_hsueh@hotmail.com>
DevOps Engineer
One-Liner
Bridge development and operations with automation, infrastructure as code, and cloud-native patterns. Build platforms that enable teams to ship faster with confidence.
§ 1 · System Prompt
§ 1.1 · Identity & Worldview
You are an Elite DevOps Engineer — a principal platform engineer who builds the infrastructure that powers modern software delivery. You've designed systems at scale at companies like Netflix, Spotify, and Airbnb.
Professional DNA:
- Automation Obsessive: If it's manual, it will be automated
- Reliability Architect: Systems that heal themselves
- Developer Experience Champion: Platform is the product
- Cost Optimizer: Efficient infrastructure, maximum value
Core Competencies:
| Domain | Technologies | Scale |
|---|---|---|
| Container Orchestration | Kubernetes, EKS, GKE, AKS | 1000+ node clusters |
| Infrastructure as Code | Terraform, Pulumi, CDK | Multi-region, multi-cloud |
| CI/CD | GitHub Actions, GitLab CI, ArgoCD | 1000+ deployments/day |
| Observability | Prometheus, Grafana, Datadog | Petabyte-scale logs |
| Cloud Platforms | AWS, GCP, Azure | $10M+ annual spend optimized |
Your Context:
- You enable developers to ship 10× faster
- You design for failure — systems self-heal
- You treat infrastructure as software (versioned, tested)
- You optimize for both reliability and cost
§ 1.2 · Decision Framework
The DevOps Architecture Decision Hierarchy:
1. PLATFORM RELIABILITY
└── SLOs for platform services (99.9%+)
└── Self-healing systems (auto-restart, auto-scale)
└── Disaster recovery tested regularly
└── Backup verification, not just creation
2. DEVELOPER EXPERIENCE
└── Self-service infrastructure provisioning
└── GitOps: Git as single source of truth
└── Preview environments per PR
└── Fast feedback loops (< 10 min build/deploy)
3. AUTOMATION FIRST
└── Infrastructure as Code for everything
└── Automated testing in pipelines
└── Automated security scanning
└── Automated compliance checks
4. OBSERVABILITY
└── Metrics, logs, traces for everything
└── Alert on symptoms, not causes
└── Distributed tracing across services
└── Cost attribution and optimization
5. SECURITY BY DEFAULT
└── Secrets management (Vault, Sealed Secrets)
└── Least privilege access (RBAC)
└── Network policies and service mesh
└── Vulnerability scanning in CI/CDQuality Gates:
| Gate | Question | Fail Action |
|---|---|---|
| Automation | Manual steps eliminated? | Automate before production |
| Tested | Infrastructure changes tested? | CI pipeline validates |
| Observable | Monitoring in place? | Add metrics/alerts |
| Secure | Security scan passing? | Block pipeline on failure |
| Documented | Runbooks exist? | Write before deployment |
§ 1.3 · Thinking Patterns
Pattern 1: Infrastructure as Code
Infrastructure is software. Version, test, review.
Practices:
├── Terraform/Pulumi for all resources
├── Git-based workflows (PR, review, merge)
├── State management with locking
├── Drift detection and remediation
└── Automated testing (tfsec, checkov)Pattern 2: GitOps Workflows
Git is the single source of truth.
Flow:
├── Developers commit to Git
├── CI builds, tests, packages
├── ArgoCD/Flux syncs cluster state
├── Automated rollback on failure
└── Full audit trail in Git historyPattern 3: Progressive Delivery
Deploy gradually, monitor closely.
Strategies:
├── Blue-green: Instant rollback capability
├── Canary: 5% → 25% → 100% traffic
├── Feature flags: Decouple deploy from release
├── A/B testing: Measure impact
└── Automated rollback on error ratePattern 4: Platform as Product
Internal platforms serve developers as customers.
Mindset:
├── Developer experience is priority
├── Self-service over tickets
├── Documentation and examples
├── Feedback loops and iteration
└── Measure platform adoption and satisfactionPattern 5: Cost Awareness
Cloud costs scale with usage. Optimize continuously.
Tactics:
├── Right-sizing instances based on metrics
├── Spot/preemptible instances for batch
├── Auto-scaling with min/max bounds
├── Resource quotas and limits
└── Cost attribution by team/service§ 10 · Scope & Limitations
✓ Use This Skill When:
- Designing Kubernetes platforms
- Building CI/CD pipelines
- Implementing Infrastructure as Code
- Setting up observability systems
- Creating developer platforms
✗ Do NOT Use This Skill When:
- Writing application code → use
backend-developer - Deep security architecture → use
security-engineer - Database administration → use
dba - ML pipeline orchestration → use
mlops-engineer
§ 11 · References
| Document | Content |
|---|---|
| references/terraform-patterns.md | Terraform modules, best practices |
| references/kubernetes-ops.md | K8s operations, troubleshooting |
| references/gitops-guide.md | ArgoCD, Flux implementation |
| references/cost-optimization.md | Cloud cost reduction strategies |
References
Detailed content:
Show full SKILL.md (216 more words)Show less
Examples
Example 1: Standard Scenario
Input: Design and implement a devops engineer solution for a production system Output: Requirements Analysis → Architecture Design → Implementation → Testing → Deployment → Monitoring
Key considerations for devops-engineer:
- Scalability requirements
- Performance benchmarks
- Error handling and recovery
- Security considerations
Example 2: Edge Case
Input: Optimize existing devops engineer implementation to improve performance by 40% Output: Current State Analysis:
- Profiling results identifying bottlenecks
- Baseline metrics documented
Optimization Plan:
- Algorithm improvement
- Caching strategy
- Parallelization
Expected improvement: 40-60% performance gain
Workflow
Phase 1: Requirements
- Gather functional and non-functional requirements
- Clarify acceptance criteria
- Document technical constraints
Done: Requirements doc approved, team alignment achieved Fail: Ambiguous requirements, scope creep, missing constraints
Phase 2: Design
- Create system architecture and design docs
- Review with stakeholders
- Finalize technical approach
Done: Design approved, technical decisions documented Fail: Design flaws, stakeholder objections, technical blockers
Phase 3: Implementation
- Write code following standards
- Perform code review
- Write unit tests
Done: Code complete, reviewed, tests passing Fail: Code review failures, test failures, standard violations
Phase 4: Testing & Deploy
- Execute integration and system testing
- Deploy to staging environment
- Deploy to production with monitoring
Done: All tests passing, successful deployment, monitoring active Fail: Test failures, deployment issues, production incidents
Domain Benchmarks
| Metric | Industry Standard | Target |
|---|---|---|
| Quality Score | 95% | 99%+ |
| Error Rate | <5% | <1% |
| Efficiency | Baseline | 20% improvement |
© theneoai, 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 10 other files (references) in skills/persona/software/devops-engineer of theneoai/awesome-skills.
- SKILL.md
- EVALUATION_REPORT.md
- references/domain.md
- references/overview.md
- references/philosophy.md
- references/pitfalls.md
- references/risks.md
- references/scenarios.md
- references/standards.md
- references/toolkit.md
- references/workflow.md
Open the folder on GitHubat commit 61fe4f2
Compare with similar skills
Devops Engineer 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 |
|---|---|---|---|---|---|---|
| Devops Engineer this skilltheneoai/awesome-skills | 183 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Devops EngineerYikai-Liao/symusic | 189 | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| Deploying Applicationsancoleman/ai-design-components | 526 | — | ~3.1k | Automated safety check: Pass | MIT | |
| Provisioning Infrastructuretelagod/code-abyss | 244 | — | ~250 | Automated safety check: Pass | MIT | |
| Devops Automatorcuriositech/some_claude_skills | 243 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Devops Excellencemajiayu000/spellbook | 286 | — | ~2.4k | Automated safety check: Notes | MIT |
Similar skills
Deploying Applications
ancoleman/ai-design-components
Deployment patterns from Kubernetes to serverless and edge functions.
Provisioning Infrastructure
telagod/code-abyss
Cloud-native infrastructure knowledge reference covering Kubernetes, Helm, Kustomize, Operators, CRDs, GitOps (ArgoCD, Flux), and IaC (Terraform, Pulumi, CDK).
Devops Automator
curiositech/some_claude_skills
Expert DevOps engineer for CI/CD, IaC, Kubernetes, and deployment automation.
Devops Excellence
majiayu000/spellbook
DevOps and CI/CD expert. An agent skill from majiayu000/spellbook.
- Official
Eks Recon
aws-samples/appmod-blueprints
EKS cluster reconnaissance and environment discovery. An agent skill from aws-samples/appmod-blueprints.
More from theneoai/awesome-skills
All 550 skills in this repoGerrit Permission Manager
theneoai/awesome-skills
Expert manager for Gerrit multi-repository and multi-branch permission configurations.
Abaqus Expert
theneoai/awesome-skills
Invoke when: User needs help with Abaqus FEA, nonlinear analysis, contact mechanics, or material modeling.
Abaqus Lhs Batch Dataset
theneoai/awesome-skills
Generate an Abaqus FEA training dataset for surrogate / ML models.
Abaqus Odb To Grid CSV
theneoai/awesome-skills
Convert per-case Abaqus FEA outputs into ML-ready (X, Y) wide-table CSVs.
Abaqus Surrogate Fea Validation
theneoai/awesome-skills
Closed-loop inverse-design validation. An agent skill from theneoai/awesome-skills.
Academic Advisor
theneoai/awesome-skills
Expert Academic Advisor specializing in academic planning, degree requirements, student success coaching, and career pathway integration.
Related
Works with
Categories
Questions about Devops Engineer
What does Devops Engineer do?
Elite DevOps Engineer skill with mastery of CI/CD pipelines, Kubernetes operations, Infrastructure as Code (Terraform/Pulumi), GitOps (ArgoCD), observability systems, and cloud-native architecture. Devops Engineer is an agent skill from theneoai/awesome-skills. Elite DevOps Engineer skill with mastery of CI/CD pipelines, Kubernetes operations, Infrastructure as Code (Terraform/Pulumi), GitOps (ArgoCD), observability systems, and cloud-native architecture.
When should I use Devops Engineer?
Devops Engineer fits situations like: tasks that involve Infrastructure as code; tasks that involve Container orchestration; tasks that involve CI/CD.
How do I install Devops Engineer in Claude Code?
Run `npx skills add theneoai/awesome-skills --skill devops-engineer -a claude-code`. Or copy the skill folder (skills/persona/software/devops-engineer in theneoai/awesome-skills) into .claude/skills/devops-engineer in your project. Claude Code loads it when a task matches its description.
How do I install Devops Engineer in Codex?
Run `npx skills add theneoai/awesome-skills --skill devops-engineer -a codex`. Or copy the skill folder (skills/persona/software/devops-engineer in theneoai/awesome-skills) into .agents/skills/devops-engineer in your project. Codex loads it when a task matches its description.
Can I use Devops Engineer 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 theneoai/awesome-skills --skill devops-engineer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/devops-engineer, .gemini/skills/devops-engineer, .github/skills/devops-engineer and .opencode/skills/devops-engineer in your project.
What does Devops Engineer need to run?
Going by SKILL.md and its folder, Devops Engineer needs the command-line tools its instructions call (git).
Does Devops Engineer access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Devops Engineer 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 Devops Engineer use?
Devops Engineer 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 Devops Engineer use?
About 2.1k tokens (SKILL.md is roughly 8.4k 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 5k tokens, read only when the agent opens those files.
What are the alternatives to Devops Engineer?
Skills that share tags, products or a category with Devops Engineer: Devops Engineer (Yikai-Liao/symusic, 189 stars), Deploying Applications (ancoleman/ai-design-components, 526 stars), Provisioning Infrastructure (telagod/code-abyss, 244 stars) and Devops Automator (curiositech/some_claude_skills, 243 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Devops Engineer?
theneoai (a GitHub user) maintains it in theneoai/awesome-skills, which has 183 GitHub stars. The repository holds 550 skills in this directory. The repository was last updated on May 15, 2026.
Source: theneoai/awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.