Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
An operational reference library spanning infrastructure, security, and compliance. Task-specific skills cover both routine operations and the surrounding concerns, including identity, observability, AI infrastructure, and policy checks.
WHO IT'S FOR
Platform / DevEx teams
building agentic AI workflows for infrastructure
Security engineers
implementing centralized audit logging and SIEM
Compliance officers
mapping technical controls to regulatory frameworks
SRE / Infrastructure engineers
developing business continuity and resilience plans
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
Installs: Complete DevOps & Security Agent Skills repository at .skills/devops-security in the containing repository; listed paths are a bounded selection.
Before you start
An existing Git repository to contain the submodule.
Run from: The containing Git repository.
Run this command in a terminal from the containing Git repository.
GitHub repository with write access and basic YAML familiarity.
Repository branch names.
A Node.js project with an npm lockfile and a working npm test script.
Use the github-actions skill to draft a minimal CI workflow for my Node.js repository. Use Node.js 20, npm caching, npm ci, and npm test, with push and pull-request triggers appropriate to my branches. Show the YAML and where it belongs; do not commit or publish it.
The Dockerfile and current container runtime configuration.
Required application ports and writable directories.
Use the container-hardening skill to review my Dockerfile and container runtime configuration. Identify the three most useful improvements involving a non-root user, a read-only filesystem, Linux capabilities, or no-new-privileges. Show proposed configuration changes and explain any writable-directory requirements; do not build or run the container.
Host operating system and OpenClaw deployment layout.
Current endpoint exposure, authentication, proxy, firewall, and remote-admin arrangements.
Descriptions of credential storage and log retention, without actual secret values.
Use the openclaw-security-hardening skill to create a short threat model for my self-hosted OpenClaw setup. Cover admin/API endpoints, provider credentials, prompt/response logs, and host access. Prioritize three controls to reduce credential theft, remote code execution blast radius, or data exfiltration before I share access. Base this on my deployment details and do not change the system.