skills.rest
endorlabs
endorlabsOFFICIAL
Explore all skills by this author →
Website𝕏@EndorLabsGitHub

endor-model-sync-drift

Diagnose and repair OpenAPI and model-sync drift in the Endor Labs SDK.

4|Updated Oct 18, 2025
Search Tags:#openapi#provenance#drift#ci#regeneration#model sync
One-click install
npx skills add https://github.com/endorlabs/endorlabs-sdk --skill endor-model-sync-drift
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: endor-model-sync-drift
Source: https://github.com/endorlabs/endorlabs-sdk/tree/main/agent-knowledge/skills/endor-model-sync-drift
Command: npx skills add https://github.com/endorlabs/endorlabs-sdk --skill endor-model-sync-drift

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you diagnose and resolve OpenAPI and model-sync drift when committed SDK artifacts no longer match the upstream Endor Labs specification, causing CI or pre-push validation to fail.

Core Features & Use Cases

  • Upstream Drift Triage: Verify whether the committed registry contract, generated models, and reference docs match the live upstream spec.
  • Regeneration Workflow: Regenerate stubs, contract files, and generated documentation when upstream changes are detected.
  • Release Readiness Checks: Review provenance, compare published endorctl versions, and validate generated diffs before pushing changes.
  • Use Case: A contributor sees verify-upstream-only fail in CI and uses this Skill to confirm the mismatch, regenerate artifacts, inspect the diff, and prepare a clean patch.

Quick Start

Ask the assistant to verify upstream drift for the Endor Labs SDK and regenerate the generated model artifacts if the committed provenance is stale.

Frequently Asked Questions about endor-model-sync-drift

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

FAQPage Schema
Why does OpenAPI model sync drift fail CI validation?▼

OpenAPI model sync drift fails CI when committed generated artifacts no longer match the upstream Endor Labs specification provenance. This mismatch causes pre-push and verify-upstream-only checks to break.

How do I fix generated SDK stubs that diverged from upstream provenance?▼

Fix divergent SDK stubs by verifying the registry contract, regenerating stale models and reference docs, inspecting the generated diff, and committing the updated provenance hashes.

What causes endorctl published version checks to fail during release?▼

Published endorctl version checks fail during release when committed generated artifacts lack matching upstream provenance hashes. Validate the registry contracts and regenerate stale stubs before pushing.

Can I use this to regenerate OpenAPI reference docs before a pre-push check?▼

Yes, you can regenerate OpenAPI reference docs and contract files before a pre-push check. The workflow verifies upstream changes, regenerates artifacts, and inspects diffs to ensure release readiness.

What is the best way to verify upstream drift in the Endor Labs SDK?▼

The best way to verify upstream drift is to compare committed generated models and reference docs against the live upstream specification, then review provenance hashes and generated diffs before committing updates.

When should I not use automated model sync regeneration?▼

Avoid automated model sync regeneration when you cannot review the generated diff or verify registry contracts beforehand, as unreviewed stubs may introduce breaking changes or invalid provenance.

Related Skills

Explore More Software Engineering Skills→
matt-rileymatt-riley
1

code-generation

Detect stale code-generation outputs and refresh them via the repo's generator workflow.

Community
Intermediate
Utchash007Utchash007

commit

Stage git changes and generate conventional commit messages with confirmation.

Community
Advanced
OpenSenseNovaOpenSenseNova
4.9k

sn-update

Synchronize installed SenseNova sn-* skills with upstream GitHub commits.

Official
Intermediate
tsuna44tsuna44

xddp.feedback

Synchronize manually edited project artifacts back into the Change Requirements Specification.

Community
Advanced