About infrahub-common
infrahub-common is a shared reference collection for other Infrahub skills and is not intended for direct invocation. It gathers query syntax, configuration details, Marketplace guidance, migration notes, and cross-skill practices.
Key features
- 01Infrahub GraphQL query reference
- 02`.infrahub.yml` configuration field guide
- 03Marketplace discovery and reuse guidance
- 04NetBox migration comparison reference
- 05Metadata and template documentation
- 06Shared practices and troubleshooting guidance
Use cases
- 01Look up shared rules for other Infrahub skills
- 02Build and validate GraphQL queries
- 03Reuse Marketplace schemas and collections
- 04Migrate NetBox queries or templates
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ opsmill/ infrahub-skills --skill infrahub-commonAfter installing, type/infrahub-commonin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
graphql-queries.mdinfrahub-yml-reference.mdmarketplace-reference.mdmetadata-lineage.mdnetbox-vs-infrahub.mdprofiles-and-templates.mdrules/_sections.md_template.mdcaching-display-label.mdconnectivity-python-environment.mdconnectivity-server-check.mddeployment-git-integration.mddeployment-gql-dry-run.mddeployment-partial-sync-recovery.mdprotocols-adopt-typed-kinds.mdprotocols-generated.mdtesting-resource-framework.mdworkflow-branch-for-crud.mdworkflow-information-priority.mdDetails
From the project READMEInfrahub Common References
This skill contains shared resources referenced by all other Infrahub skills. It is not meant to be invoked directly.
Contents
graphql-queries.md— Infrahub GraphQL query syntax, filters, nested queries, and pagination patternsinfrahub-yml-reference.md—.infrahub.ymlconfiguration file format and field referencemarketplace-reference.md— Infrahub Marketplace: reusing published schemas and collections viainfrahubctl marketplace get, discovery withinfrahubctl marketplace list/search/show, and airgap fallback. Reuse before modelling from scratch.netbox-vs-infrahub.md— Field-by-field migration appendix for engineers porting NetBox queries, templates, or overlay datametadata-lineage.md— Value metadata (source,owner,is_protected): what each field means, how to set it in object files, and whysourcedoes not control edit accessprofiles-and-templates.md— The Profiles vs Object Templates distinction and mechanicsrules/— Cross-cutting rules shared across skills:- Branch-first data CRUD (default to a branch, not the default branch)
- Caching display labels in queries
- Python environment and connectivity checks
- Git integration and deployment patterns
- Dry-running a changed
.gqlquery against the live schema before merge, and whichinfrahubctlcommand does it for a transform, check or generator - Recovery from partial repository syncs
- Generated file protocol conventions
schema.graphqlasinfrahubctl graphql export-schemaoutput — re-exported, never hand-edited- Adopting generated protocols for typed SDK calls
- Information-source priority (skill content first,
with a concrete last-resort procedure for consulting
docs.infrahub.appon a genuine gap)
Comments
Markdown supported