si-provider-debug

Debug SI provider integrations with reproducible CLI checks and root-cause analysis.

Updated Dec 31, 2025
One-click install
npx skills add https://github.com/Aureuma/si --skill si-provider-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: si-provider-debug
Source: https://github.com/Aureuma/si/tree/main/tools/codex-skills/si-provider-debug
Command: npx skills add https://github.com/Aureuma/si --skill si-provider-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users quickly identify and resolve issues when integrating with various third-party providers by providing a structured debugging process.

Core Features & Use Cases

  • Reproducible CLI Checks: Run specific commands to test provider connectivity and functionality.
  • Root-Cause Analysis: Provides a checklist to systematically identify common integration problems.
  • Use Case: If your SI OpenAI integration is failing, you can use this skill to run a si openai models list --limit 1 command to verify authentication and connectivity before attempting more complex operations.

Quick Start

Use the si-provider-debug skill to run a self-doctor check on your SI setup.

Frequently Asked Questions about si-provider-debug

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

FAQPage Schema
How do I debug failing API integrations with OpenAI or AWS?

To debug API integrations with OpenAI or AWS, run reproducible CLI checks to test connectivity and perform root-cause analysis for authentication, configuration, and permission problems.

What is the best way to troubleshoot provider authentication and configuration errors?

Troubleshooting provider authentication and configuration errors involves running self-doctor CLI checks to verify connectivity, systematically identifying root causes using structured checklists, and enforcing least-privilege probes.

How do I run a connectivity test for my Stripe provider integration?

You can run a connectivity test for your Stripe provider integration by executing specific CLI commands, such as listing models with a limit, to verify authentication and functionality before attempting complex operations.

Does this debugging process support GCP and Cloudflare integrations?

Yes, the debugging process supports GCP and Cloudflare integrations, providing reproducible CLI checks and root-cause analysis to resolve issues across these specific cloud providers.

Why does my GitHub provider integration return a permission error?

Your GitHub provider integration might return a permission error due to misconfigured access controls; root-cause analysis checklists help identify these issues while enforcing sensitive data redaction during probes.

Can I safely debug sensitive data issues during provider integration checks?

Yes, you can safely debug sensitive data issues because the process enforces guardrails for least-privilege probes and applies sensitive data redaction during root-cause analysis and CLI checks.