endor-troubleshoot-sdk

Diagnose Endor Labs SDK failures by comparing client behavior with endorctl and OpenAPI contracts.

4|Updated Oct 18, 2025
One-click install
npx skills add https://github.com/endorlabs/endorlabs-sdk --skill endor-troubleshoot-sdk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: endor-troubleshoot-sdk
Source: https://github.com/endorlabs/endorlabs-sdk/tree/main/agent-knowledge/skills/endor-troubleshoot-sdk
Command: npx skills add https://github.com/endorlabs/endorlabs-sdk --skill endor-troubleshoot-sdk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you determine whether an Endor Labs SDK issue is caused by client usage, namespace scoping, contract mismatch, model-sync drift, or a platform-side behavior difference. It is designed to replace guesswork with a repeatable validation process.

Core Features & Use Cases

  • SDK vs endorctl comparison: Reproduce the same request in both tools to see whether the failure is specific to the SDK or shared by the platform.
  • Namespace and traversal debugging: Resolve common 404s, empty lists, and scope errors caused by parent vs child namespace selection or traversed resources.
  • Update and mask validation: Diagnose update_mask problems, list mask behavior, and resource-specific read-only or mutable field constraints.
  • Test and contract triage: Investigate unexpected test skips, server errors, and parsing issues by checking OpenAPI, contracts, and reference guidance.

Quick Start

Ask the Skill to diagnose the failing Endor Labs SDK call and compare it against endorctl output, the resource namespace, and the documented contracts.

Frequently Asked Questions about endor-troubleshoot-sdk

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

FAQPage Schema
Why does my Endor Labs SDK call return a 404 for a traversed resource?▼

A 404 on a traversed resource usually stems from namespace scoping errors. Diagnose the SDK failure by verifying parent versus child namespace selection and comparing the client behavior against endorctl to isolate scope misconfigurations.

How do I debug update_mask validation errors in the Endor Labs SDK?▼

Debug update_mask validation errors by checking resource-specific read-only and mutable field constraints. Compare the SDK request against documented OpenAPI contract rules to determine if the failure is a client usage error or model-sync drift.

What is the best way to tell if an SDK failure is a platform-side issue or a client bug?▼

The best way to distinguish an SDK bug from a platform-side failure is to reproduce the exact request using endorctl. If both tools fail, the issue is platform-side; if only the SDK fails, it indicates a client usage or model-sync drift problem.

How do I resolve empty list responses when using namespace scoping with the Endor Labs SDK?▼

Resolve empty list responses by validating your list mask parsing and namespace scoping. Compare the SDK list request against endorctl output and OpenAPI contracts to identify whether the empty result comes from scope errors or mask behavior.

Why are my Endor Labs integration tests unexpectedly skipping?▼

Unexpected test skips often result from contract mismatches or parsing issues. Investigate the skips by checking the OpenAPI contracts, validating the SDK behavior against endorctl, and reviewing reference guidance for known server errors.