infra-agent-skills

Contribute

Share what your team knows.

Anyone can contribute, in one of two ways.

This page is the short version. The contributing guide has the full process and the review checklist.

AAdd to the repositoryContribute a new skill, add a vendor to an existing one, or fix a step. Your work becomes part ofinfra-agent-skills and is reviewed like any other change.BList your own skillAlready publish a skill in your own public repo? Add one entry to CATALOG.yaml. It stays in your repo, under your license, and the directory links to it.

AAdd to the repository

For a new skill, a new vendor under an existing skill, or a fix to something that is wrong or out of date.

  1. 1Fork and branch

    Branch from main with a prefix such as feature/ or fix/.

  2. 2Write it

    Keep SKILL.md short and put each vendor’s steps under references/<vendor>/.

  3. 3Check it

    Verify every call against vendor docs, and update the skill’s index and CATALOG.yaml.

  4. 4Open a PR

    Sign the CLA. A maintainer reviews every change before it merges.

What makes a good contribution

  • It is an infrastructure operation. A procedure that carries judgment an agent lacks, not a tool manual, a command wrapper, or developer tooling.
  • It is checked against the source. Every endpoint, field, and step matches the vendor’s current published documentation.
  • It stays in its lane. Vendor-specific content goes in that vendor’s folder. Change the shared SKILL.md only to fix the shared part.
  • The PR explains itself. Say what it does, which skills and vendors it touches, which docs you used, and what you left out on purpose.
  • It is clean. No credentials, customer data, or internal hostnames. Use placeholders.

Not ready to write it yourself? Open an issue to report a problem or propose a new skill or vendor. Full process.

BList your own skill

For a skill you or your organization publish in your own public repository. The listing is a pull request that changes only CATALOG.yaml. Nothing is copied.

  1. 1Fork and branch

    Fork infra-agent-skills and branch from main.

  2. 2Add one entry

    Add your skill to CATALOG.yaml: title, one-line summary, link, category, tags, and vendors.

  3. 3Run the check

    The catalog check confirms the required fields, unique links, and https URLs.

  4. 4Open a PR

    Sign the CLA, and say what the skill does and how it differs from similar ones.

What a listing needs

  • Public and open source. The link loads without signing in, and the repo shows an open-source license.
  • Infrastructure work. The skill covers an infrastructure operation, not general developer tooling.
  • A neutral summary. One accurate sentence, with no marketing claims, links, or instructions to an agent.
  • The real publisher. You publish the skill or are authorized to list it.

Maintainers check that a listing is complete and its links work. They do not review the skill’s content, and a listing is not an endorsement. Listing guidelines.

Ready to contribute?

The full guide covers branch names, PR labels, the catalog format, and how review works.

Add a skill or list your own. Every change is reviewed.

Read the contributing guideView the repository