smaqit.infrastructure-repo-config

Automate GitHub repository CI/CD secret and variable configuration via Vault.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ruifrvaz/local-image-generator --skill smaqit-infrastructure-repo-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smaqit.infrastructure-repo-config
Source: https://github.com/ruifrvaz/local-image-generator/tree/main/.github/skills/smaqit.infrastructure-repo-config
Command: npx skills add https://github.com/ruifrvaz/local-image-generator --skill smaqit-infrastructure-repo-config

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, vault, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Streamlines the setup of GitHub repository configurations required for CI/CD workflows, securely managing secrets and variables, and preventing common pitfalls like SSH key issues and reserved variable collisions.

Core Features & Use Cases

  • GitHub Repository Secrets & Variables Configuration: Automates the setting of critical repository secrets such as SSH keys, Terraform backend credentials, cloud provider credentials, and GitHub Terraform token.
  • Vault-Based Secret Management: Integrates with a Vault to source truth for secrets, ensuring security and consistency across deployments.
  • CI/CD Workflow Configuration: Supports setup for new repositories, rotation of CI/CD credentials, and verification of all required secrets and variables.

Quick Start

Use the smaqit.infrastructure-repo-config skill to set up secrets and variables for a GitHub repository, starting a ComfyUI server for interaction: ``` smaqit.infrastructure-repo-config <repository> start

Frequently Asked Questions about smaqit.infrastructure-repo-config

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub repository secrets configuration using Vault?

You can automate GitHub repository secrets configuration by sourcing truth from Vault, setting SSH keys, Terraform backend credentials, and cloud provider credentials directly into the repository to secure CI/CD workflows.

What is the best way to prevent SSH key collisions in CI/CD repository setup?

Preventing SSH key collisions in CI/CD repository setup involves utilizing a Vault system for secret management to safely handle deployment credentials and avoid reserved variable conflicts during configuration.

How do I rotate CI/CD credentials for a GitHub repository?

Rotating CI/CD credentials involves updating the repository secrets and variables by fetching newly rotated values from Vault and applying them to the target GitHub repository to maintain secure deployments.

Do I need Vault and gh installed to manage repository secrets?

Yes, you need both Vault and gh installed, as Vault sources the secret values and gh interacts with the GitHub repository API to apply the CI/CD configurations and required credentials.

Can I verify required GitHub secrets and variables are set correctly for CI/CD?

Yes, you can verify required GitHub secrets and variables by running a configuration check that validates all necessary CI/CD credentials, such as SSH keys and Terraform tokens, are present and correctly configured.