Agent skill · software engineering · jeremylongshore
hex-ci-integration
Configure Hex CI/CD integration with GitHub Actions and testing.
Why this skill is useful
Adds a GitHub Actions CI/CD workflow and integration testing patterns specific to Hex that the AI wouldn't reliably generate on its own.
What it needs
Requires node installed locally. Requires hex account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Hex CI Integration Overview Set up CI/CD for Hex data analytics integrations: run unit tests with mocked project run and connection responses on every PR, trigger live Hex project runs and validate outputs on merge to main. Hex provides collaborative data notebooks with scheduled runs and API-triggered execution, so CI pipelines verify data transform logic, trigger post-deploy dashboard refreshes, and monitor run status. GitHub Actions Workflow Mock-Based Unit Tests Integration Tests Error Handling CI Issue Cause Fix ---------- ------- ----- 401 Unauthorized Invalid or expired API token Regenerate at app.hex.tech account settings 404 Project not found Wrong project ID Verify HEXPROJECTID matches the Hex dashboard URL Run status stuck on running Long-running query or connection issue Set timeout and poll interval (max 5 min) inputParams rejected Parameter name mismatch Match param names exactly to Hex project input cells Rate limit (429) Too many run triggers Deduplicate CI triggers and add cooldown between runs Prerequisites CI secret references, a sandbox project/destination, fixtures with no production output, protected branches, and a rollback mechanism. Instructions 1. Run mocked tests first, including malformed parameter, denied access, quota, cancellation, and output-assertion cases. 2. Run a bounded sandbox integration with idempotency and prohibit production projects/destinations in CI configuration. 3. Emit aggregate counts, opaque IDs, and policy revisions only; fail for unexpected scope, unredacted output, or expanded access. 4. Canary after protected review, verify assertions, and restore the last-known-good revision on failure. Output Publish a CI receipt with commit SHA, fixture revision, sandbox project, test totals, policy checks, canary outcome, and rollback reference. Exclude SQL, output, and secrets. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/hex-ci-integration