Deploy To Temps
gotempsh/temps
Deploy applications to the Temps platform with automatic framework detection, Dockerfile generation, and container orchestration.
Provides project infrastructure conventions and review criteria for local setup, Docker, Git hooks, CI/CD, service delivery, release artifacts, monitoring, backups, and operations.
Install Infrastructure Setup
$ npx skills add pavel-molyanov/molyanov-ai-dev --skill infrastructure-setup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pavel-molyanov/molyanov-ai-dev infrastructure-setup --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/pavel-molyanov/molyanov-ai-dev.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/infrastructure-setup .claude/skills/infrastructure-setup && 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 "infrastructure-setup" agent skill from https://github.com/pavel-molyanov/molyanov-ai-dev/tree/main/skills/infrastructure-setup into .claude/skills/infrastructure-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infrastructure-setup", 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/pavel-molyanov/molyanov-ai-dev/tree/main/skills/infrastructure-setupType 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 pavel-molyanov/molyanov-ai-dev --skill infrastructure-setup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pavel-molyanov/molyanov-ai-dev infrastructure-setup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pavel-molyanov/molyanov-ai-dev.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/infrastructure-setup .agents/skills/infrastructure-setup && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "infrastructure-setup" agent skill from https://github.com/pavel-molyanov/molyanov-ai-dev/tree/main/skills/infrastructure-setup into .agents/skills/infrastructure-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infrastructure-setup", 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 pavel-molyanov/molyanov-ai-dev --skill infrastructure-setup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pavel-molyanov/molyanov-ai-dev infrastructure-setup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pavel-molyanov/molyanov-ai-dev.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/infrastructure-setup .cursor/skills/infrastructure-setup && 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 "infrastructure-setup" agent skill from https://github.com/pavel-molyanov/molyanov-ai-dev/tree/main/skills/infrastructure-setup into .cursor/skills/infrastructure-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infrastructure-setup", 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/pavel-molyanov/molyanov-ai-dev.git --path skills/infrastructure-setup--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 pavel-molyanov/molyanov-ai-dev --skill infrastructure-setup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pavel-molyanov/molyanov-ai-dev infrastructure-setup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pavel-molyanov/molyanov-ai-dev.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/infrastructure-setup .gemini/skills/infrastructure-setup && 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 "infrastructure-setup" agent skill from https://github.com/pavel-molyanov/molyanov-ai-dev/tree/main/skills/infrastructure-setup into .gemini/skills/infrastructure-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infrastructure-setup", 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 pavel-molyanov/molyanov-ai-dev infrastructure-setupInstalls 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 pavel-molyanov/molyanov-ai-dev --skill infrastructure-setup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pavel-molyanov/molyanov-ai-dev.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/infrastructure-setup .github/skills/infrastructure-setup && 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 "infrastructure-setup" agent skill from https://github.com/pavel-molyanov/molyanov-ai-dev/tree/main/skills/infrastructure-setup into .github/skills/infrastructure-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infrastructure-setup", 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 pavel-molyanov/molyanov-ai-dev --skill infrastructure-setup -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pavel-molyanov/molyanov-ai-dev infrastructure-setup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pavel-molyanov/molyanov-ai-dev.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/infrastructure-setup .opencode/skills/infrastructure-setup && 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 "infrastructure-setup" agent skill from https://github.com/pavel-molyanov/molyanov-ai-dev/tree/main/skills/infrastructure-setup into .opencode/skills/infrastructure-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infrastructure-setup", 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
infrastructure-setup- GitHub stars
- 297
- Token cost
- ~1.9k tokens
- SKILL.md length
- 929 words
- Files
- 4 (incl. references)
- Skills in repo
- 13
- Repo updated
- First seen
- Licence
- MIT
At a glance
Provides project infrastructure conventions and review criteria for local setup, Docker, Git hooks, CI/CD, service delivery, release artifacts, monitoring, backups, and operations.
- : настрой инфраструктуру
- SKILL.md covers Manual Claude-to-Codex Sync, Scope and Judgment, Project-Specific Ownership and Repository and Runtime Rules, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Подготовь деплой
What it does
Infrastructure Setup is an agent skill from pavel-molyanov/molyanov-ai-dev. Provides project infrastructure conventions and review criteria for local setup, Docker, Git hooks, CI/CD, service delivery, release artifacts, monitoring, backups, and operations. Use when: "настрой инфраструктуру", "измени CI/CD", "подготовь деплой", "настрой Docker", "собери release artifact", "настрой мониторинг", "проверь инфраструктуру", "оцени деплой", "setup infrastructure", "review infrastructure" Do NOT use for: choosing or writing application tests without an infrastructure change.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/deployment.md`, `references/monitoring-and-alerting.md` and `references/release-artifacts.md`).
It sits in DevOps & Cloud, covering Backup and disaster recovery, CI/CD and Containers. It works with Docker and Git. The repository describes itself as: Intent-driven AI-First development methodology for Claude Code and Codex — Project Knowledge, user-spec planning, focused execution, and evidence-gated reviews. The licence is MIT.
When your agent uses it
- : настрой инфраструктуру
- Подготовь деплой
- Собери release artifact
- Настрой мониторинг
Example prompts
- “измени CI/CD”
- “настрой Docker”
- “собери release artifact”
- “/infrastructure-setup”
Requirements
- Docker
What it can do on your machine
Read from SKILL.md and the folder at commit b5db526. 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 (its code samples are bash).
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
Infrastructure Setup loads about 1.9k tokens when it runs, and up to ~3.8k if it reads all its reference files. Until then it costs about 130 tokens; SKILL.md has 929 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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:73
output. Local values belong in ignored `.env` or protected
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 pavel-molyanov/molyanov-ai-dev at commit b5db526, republished under its MIT licence (© pavel-molyanov). 929 words, ~1,946 tokens.
Download SKILL.mdSave it as
.claude/skills/infrastructure-setup/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- infrastructure-setup
- description
- Provides project infrastructure conventions and review criteria for local setup, Docker, Git hooks, CI/CD, service delivery, release artifacts, monitoring, backups, and operations. Use when: "настрой инфраструктуру", "измени CI/CD", "подготовь деплой", "настрой Docker", "собери release artifact", "настрой мониторинг", "проверь инфраструктуру", "оцени деплой", "setup infrastructure", "review infrastructure" Do NOT use for: choosing or writing application tests without an infrastructure change.
Infrastructure Conventions
Manual Claude-to-Codex Sync
Claude-side is the source of truth for the converter's allowlist: global skills/**,
agents/*.md, and commands/*.md; or project CLAUDE.md, .claude/skills/**,
.claude/agents/*.md, and .claude/commands/*.md. Codex-side outputs are generated runtime. No scheduled job performs this
conversion. After editing an allowlisted source, run the matching command and review the generated
result before finishing:
~/.claude/scripts/sync-to-codex.sh --apply # global ~/.claude/**
~/.claude/scripts/sync-to-codex.sh --project "$PWD" --apply # project .claude/**For a project, commit generated .codex/** and AGENTS.md changes with their Claude sources,
except host-local .codex/.sync/**. Global ~/.codex/** is runtime state outside the
~/.claude repository: run the global command explicitly on every affected host and do not add
it to the Claude-source commit. If sync reports a conflict or validation error, stop and report
it.
Scope and Judgment
- Project Knowledge is required infrastructure context. If it is absent, stop and ask the user to create or fill it before continuing.
- The user's request defines which changes are authorized. A request to inspect, review, or assess current infrastructure authorizes diagnosis and recommendations, not implementation.
- Existing architecture and Project Knowledge are the current contract, not proof that the setup is good. Report demonstrated defects, unnecessary complexity, unsafe behavior, operational risks, and worthwhile improvements instead of silently accepting them.
- Do not implement an improvement outside the user's request merely because it is beneficial. Explain the evidence, impact, and proposed direction, then obtain agreement before changing it.
- Discuss the situation with the user when material information is missing or contradictory, an action can affect production, users, data, secrets, or neighboring projects, the safe result is uncertain, the current setup appears wrong, or the intended response expands the request.
- Treat a rare or unagreed operational scenario as a user decision even when its correction looks local. Ask before adding or changing delivery, recovery, monitoring, isolation, persistent state, infrastructure entities, dependencies, architecture, or material complexity.
- Apply only the topic rules relevant to the request; these are conventions, not a required setup sequence.
Project-Specific Ownership
- Concrete hosts, platforms, users, paths, ports, service names, deployment triggers, direct-access policy, agent or operations host, monitoring location, notification route, backup destinations, and emergency recovery facts belong in Project Knowledge's deployment owner.
- Keep those facts current through
documentation-writingwhen an infrastructure change alters them. Do not copy private project facts into this global skill or another public methodology file. - Project-specific decisions override the generic patterns here. If a documented choice is risky or no longer fits reality, report it and discuss a change rather than overriding it silently.
Repository and Runtime Rules
- Do not introduce Docker, a server, a hook, or an environment merely because the skill covers it.
- Git pre-commit uses gitleaks for secret scanning and may add only fast staged-file lint or format checks. Full test suites and builds belong in CI. Test a secret-like fixture only in a disposable repository so it never enters the project's index, history, or reflog.
- When Docker is used, exclude secrets from the build context and image layers and give the final container only the privileges it needs.
- Keep secrets out of Git and command output. Local values belong in ignored
.envor protected config files; CI values belong in its secret store; runtime-only values belong in a protected target-side file or secret store. Keep a value-free.env.examplewhen configuration names need documenting. - Give project-owned ephemeral resources such as logs, caches, obsolete images, deployment bundles, temporary builds, and CI artifacts a bounded retention or size policy. Backups need retention that preserves current recovery needs and a verified restore path. Do not invent an expiry for persistent application data or clean another project's resources.
Show full SKILL.md (346 more words)Show less
Topic Rules
For a persistent service or deployment assessment, apply deployment.md — delivery model, shared-host placement, environments, production safety, rollback, and runtime verification.
For downloadable builds, browser extensions, packages, or CLIs, apply release-artifacts.md — verified artifacts, retention, and the manual Chrome Web Store boundary.
For health checks, timers, alerts, or monitoring assessment, apply monitoring-and-alerting.md — control-host placement, incident behavior, notification routing, installation, and drills.
Verification and Review
- Match implementation verification to the changed boundary: container, workflow, artifact, timer, recovery path, or user-facing service behavior. Do not replay unrelated checks.
- Use a fresh
infrastructure-reviewerfor an explicit review of current infrastructure or a change that materially affects production delivery, secrets, environment isolation, release publication, recovery, retention, monitoring, or shared-host boundaries. A trivial local or formatting-only change whose result is fully established by direct verification does not need a dedicated review. Supply the requested review boundary, relevant existing infrastructure, Project Knowledge, applicable topic references, and available runtime evidence. - When a dedicated review is required, run no more than two review waves. Wave 1 reviews the
requested current-infrastructure or completed-change boundary. After an authorized correction
changes the reviewed result, re-verify the affected boundary, refresh durable Project Knowledge
facts, and run wave 2 with a fresh
infrastructure-reviewer. Stop after a clean wave or when no authorized correction changes the result. Include reviewers required by other active skills in these same waves instead of starting a separate wave sequence. - Review findings are diagnoses, not a work queue. Check the evidence and exact correction. Apply
only an authorized local correction to agreed normal operation. If the scenario is rare or
unagreed, or the correction adds delivery, recovery, monitoring, isolation, persistent state,
infrastructure entities, dependencies, architecture, or material complexity, reject it with a
short reason or ask the user before editing.
user_decision_required: falsedoes not replace this check. Report unsupported or unrelated findings without acting on them. - After wave 2, do not launch another reviewer automatically. If a remaining local correction is made inside the agreed change, verify its affected boundary directly and refresh durable Project Knowledge facts. Report any remaining risks or required user decisions.
© pavel-molyanov, 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 3 other files (references) in skills/infrastructure-setup of pavel-molyanov/molyanov-ai-dev.
- SKILL.md
- references/deployment.md
- references/monitoring-and-alerting.md
- references/release-artifacts.md
Open the folder on GitHubat commit b5db526
Compare with similar skills
Infrastructure Setup 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 |
|---|---|---|---|---|---|---|
| Infrastructure Setup this skillpavel-molyanov/molyanov-ai-dev | 297 | — | ~1.9k | Automated safety check: Notes | MIT | |
| Deploy To Tempsgotempsh/temps | 831 | — | ~1.3k | Automated safety check: Notes | Apache-2.0 | |
| Scanning Containers With Trivy In Cicdmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.7k | Automated safety check: Pass | Apache-2.0 | |
| Performing Container Security Scanning With Trivymukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~818 | Automated safety check: Pass | Apache-2.0 | |
| Devops Automationrohitg00/awesome-claude-code-toolkit | 2.7k | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit | 260 | 6 repos | ~1.1k | Automated safety check: Notes | Custom licence |
Similar skills
Scanning Containers With Trivy In Cicd
mukul975/Anthropic-Cybersecurity-Skills
Integrates Aqua Security's Trivy scanner into CI/CD pipelines to detect OS package and application dependency CVEs, Dockerfile misconfigurations, and issues in filesystems or git repositories, and…
Performing Container Security Scanning With Trivy
mukul975/Anthropic-Cybersecurity-Skills
Runs Trivy across every target type it supports - container images, filesystems, Git repositories, and Kubernetes clusters - for OS and dependency vulnerabilities, IaC misconfiguration, exposed…
Devops Automation
rohitg00/awesome-claude-code-toolkit
CI/CD pipeline design with GitHub Actions, Docker, Kubernetes, Helm, and GitOps patterns
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…
Ssh Skill
badseal/ssh-skill
A skill your agent uses when a task requires SSH or SCP/SFTP behavior, a remote server, server alias/IP/hostname/user@host, bastion or jump-host access, remote command execution, upload/download…
More from pavel-molyanov/molyanov-ai-dev
All 13 skills in this repoDocumentation Writing
pavel-molyanov/molyanov-ai-dev
Creates and maintains project documentation in .claude/skills/project-knowledge/: interview, initial Project Knowledge, audit, edit, consistency, and feature finalization.
User Spec Planning
pavel-molyanov/molyanov-ai-dev
Creates user-spec.md through adaptive interview, codebase research, and three-lane validation.
Layout Writing
pavel-molyanov/molyanov-ai-dev
Reproduces and adjusts web layouts from Figma, Claude Design exports, screenshots, or an existing project style with high visual fidelity and proportional verification.
Skill Master
pavel-molyanov/molyanov-ai-dev
Guides skill creation and updates with specialized knowledge and workflows.
Project Initialization
pavel-molyanov/molyanov-ai-dev
Initializes a project from the standard dual-runtime template, preserves existing files, configures Git hooks, and creates or connects a private GitHub repository with main and dev branches.
Methodology
pavel-molyanov/molyanov-ai-dev
Explains the current AI-First development methodology: skill routing, Project Knowledge, user-spec planning and execution, evidence-gated reviews, feature finalization, and the Claude/Codex dual…
Related
Categories
Questions about Infrastructure Setup
What does Infrastructure Setup do?
Provides project infrastructure conventions and review criteria for local setup, Docker, Git hooks, CI/CD, service delivery, release artifacts, monitoring, backups, and operations. Infrastructure Setup is an agent skill from pavel-molyanov/molyanov-ai-dev. Provides project infrastructure conventions and review criteria for local setup, Docker, Git hooks, CI/CD, service delivery, release artifacts, monitoring, backups, and operations.
When should I use Infrastructure Setup?
Infrastructure Setup fits situations like: : настрой инфраструктуру; Подготовь деплой; Собери release artifact; Настрой мониторинг.
How do I install Infrastructure Setup in Claude Code?
Run `npx skills add pavel-molyanov/molyanov-ai-dev --skill infrastructure-setup -a claude-code`. Or copy the skill folder (skills/infrastructure-setup in pavel-molyanov/molyanov-ai-dev) into .claude/skills/infrastructure-setup in your project. Claude Code loads it when a task matches its description.
How do I install Infrastructure Setup in Codex?
Run `npx skills add pavel-molyanov/molyanov-ai-dev --skill infrastructure-setup -a codex`. Or copy the skill folder (skills/infrastructure-setup in pavel-molyanov/molyanov-ai-dev) into .agents/skills/infrastructure-setup in your project. Codex loads it when a task matches its description.
Can I use Infrastructure Setup 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 pavel-molyanov/molyanov-ai-dev --skill infrastructure-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/infrastructure-setup, .gemini/skills/infrastructure-setup, .github/skills/infrastructure-setup and .opencode/skills/infrastructure-setup in your project.
What does Infrastructure Setup need to run?
SKILL.md names no scripts, command-line tools or credentials: Infrastructure Setup is instructions for the agent only. Our summary lists: Docker.
Does Infrastructure Setup 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 Infrastructure Setup safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Infrastructure Setup use?
Infrastructure Setup is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Infrastructure Setup use?
About 1.9k tokens (SKILL.md is roughly 7.8k 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 1.8k tokens, read only when the agent opens those files.
What are the alternatives to Infrastructure Setup?
Skills that share tags, products or a category with Infrastructure Setup: Deploy To Temps (gotempsh/temps, 831 stars), Scanning Containers With Trivy In Cicd (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Performing Container Security Scanning With Trivy (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Devops Automation (rohitg00/awesome-claude-code-toolkit, 2.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Infrastructure Setup?
pavel-molyanov (a GitHub user) maintains it in pavel-molyanov/molyanov-ai-dev, which has 297 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on August 23, 2026.
Source: pavel-molyanov/molyanov-ai-dev on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.