stigg-product-catalog

Manage Stigg product catalogs via GraphQL across environments.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/stiggio/ai --skill stigg-product-catalog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stigg-product-catalog
Source: https://github.com/stiggio/ai/tree/main/skills/product-catalog-management
Command: npx skills add https://github.com/stiggio/ai --skill stigg-product-catalog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Teams often manage multiple Stigg product catalogs across environments and need a reliable, auditable workflow to view, export, compare, and apply changes via the GraphQL API.

Core Features & Use Cases

  • View environments and current catalogs to assess readiness and plan changes.
  • Dump/export complete catalogs for version control, offline analysis, or auditing.
  • Preview merges and apply changes, or create environments from JSON templates.

Quick Start

Set your STIGG_API_KEY and use the included scripts to dump a catalog or perform a merge.

Frequently Asked Questions about stigg-product-catalog

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

FAQPage Schema
How do I manage Stigg product catalogs across multiple environments?

Managing Stigg product catalogs across environments involves using GraphQL to view, export, compare, and merge catalogs. You must set a valid STIGG_API_KEY to enable safe, auditable workflows for applying changes.

Can I export a complete Stigg catalog for version control?

Yes, you can dump and export complete Stigg catalogs for version control, offline analysis, or auditing. The skill provides included scripts to extract catalog data via the GraphQL API.

What is the best way to compare Stigg catalogs before applying changes?

The best way to compare Stigg catalogs is to preview merges using the provided GraphQL scripts. This allows you to assess environment readiness and verify changes before applying them to your product catalogs.

Do I need an API key to merge Stigg product catalogs via GraphQL?

Yes, a valid STIGG_API_KEY is required to merge Stigg product catalogs via GraphQL. This key authenticates your scripts to safely preview and apply changes across your environments.

Can I create a new Stigg environment from a JSON template?

Yes, you can create new Stigg environments from JSON templates. The skill enables you to apply these templates via GraphQL to quickly replicate or initialize catalog structures.