Menu
Troubleshoot synchronization issues with the Stigix Registry (Cloudflare Worker). Use this when autodiscovery is failing or peers are not appearing in the dashboard.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Bump version, commit code changes, and push a GitHub tag for the stigix project. Use whenever making code changes that should trigger a Docker image rebuild via GitHub Actions CI.
Audit and synchronize the Stigix MCP server tools with the stigix-cli. Use this whenever stigix-cli.py changes (new commands, bug fixes, new API parameters) to ensure Claude's MCP tools stay in sync. Also use when MCP tools have bugs that were already fixed in the CLI.
Language policy for the Stigix repository. Use this skill whenever writing or editing any file that will be committed to the GitHub repository (docs/, mcp-server/Exemple/, README, CHANGELOG, code comments, docstrings, tool descriptions, etc.). Conversation with the user may remain in French, but all repo-facing content must be in English.
Evaluate whether a new feature or change warrants a documentation update in the Stigix docs. Use after adding new features (not bug fixes). Decides which docs to update, writes the content, and proposes the update to the user when the value is uncertain.
Pre-push security checklist to prevent leaking Palo Alto SASE credentials and other secrets into the Stigix GitHub repository. Use this skill BEFORE any git commit or push, and whenever modifying files that could contain credentials (.env, credentials.json, *.old, *.bak, etc.)
Cross-platform awareness guide for commands targeting external hosts. Use this skill whenever you are about to generate a shell command, script, or file path intended for a host whose OS is unknown or could be Windows, Linux, or macOS.
| name | stigix-registry-debug |
| description | Troubleshoot synchronization issues with the Stigix Registry (Cloudflare Worker). Use this when autodiscovery is failing or peers are not appearing in the dashboard. |
Use this skill to diagnose why instances are not discovering each other.
Run this command on the local instance (replace JWT_TOKEN with a valid session token, or check status via the CLI connect command):
curl -s -H "Authorization: Bearer $JWT_TOKEN" http://localhost:8080/api/registry/status | jq .
Verify:
is_registered: must be true.poc_id: must match the PRISMA_SDWAN_TSGID.poc_key: verify if the hash is present.Verify if the agent can reach the Cloudflare Worker:
STIGIX_URL=$(grep STIGIX_REGISTRY_URL .env | cut -d'=' -f2)
curl -I $STIGIX_URL/instances
A 403 Forbidden is expected without headers, but a 521 or 404 indicates a connectivity or URL issue.
If you have access to the Cloudflare dashboard:
[AUTH] Refused heartbeat: Invalid PoC Key (Hash mismatch).[AUTH] Refused registration: Invalid Global API Key.CLIENT_ID, you must wait for the 48h expiration or manually flush the KV key auth:poc:<TSG_ID>.STIGIX_REGISTRY_ENABLED=true is set.