skills.rest
skmtc
skmtcOFFICIAL
Explore all skills by this author →
Website𝕏@BuiltWithSkmtcGitHub

skmtc-debug

Diagnose SKMTC code generation failures by inspecting manifests and reproducing reported behavior.

19|Updated Aug 27, 2025
Search Tags:#debugging#openapi#code generation#manifest analysis#skmtc#parse issues
One-click install
npx skills add https://github.com/skmtc/skmtc --skill skmtc-debug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skmtc-debug
Source: https://github.com/skmtc/skmtc/tree/main/deno/docs/skills/skmtc-debug
Command: npx skills add https://github.com/skmtc/skmtc --skill skmtc-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill diagnoses broken SKMTC generation sessions by gathering evidence before recommending fixes, helping identify whether failures originate in manifests, schemas, configuration, bundles, generators, or generated code.

Core Features & Use Cases

  • Verification-First Diagnosis: Reproduce failures and inspect the manifest, source code, parse issues, and exact error messages before proposing changes.
  • Symptom-Based Workflows: Investigate missing output, incorrect output, compilation failures, stale bundles, reference errors, definition collisions, module resolution failures, and configuration problems.
  • Root-Cause Analysis: Distinguish upstream schema errors from cascaded dependency failures and determine when to hand off to CLI configuration, generator authoring, or SKMTC core maintenance.
  • Use Case: When a SKMTC operation produces no generated file, use the manifest results and parse issues to determine whether it was unsupported, skipped, pruned during parsing, or failed inside the generator.

Quick Start

Ask the SKMTC debug skill to reproduce the failure, inspect the latest manifest and relevant source, and identify the evidence-backed root cause.

Frequently Asked Questions about skmtc-debug

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

FAQPage Schema
How do I diagnose stale bundles and reference cycles in OpenAPI manifests?▼

Diagnosing stale bundles and reference cycles requires inspecting the manifest results and parse issues to verify the observed run state. Reproducing the reported behavior isolates upstream schema errors from cascaded dependency failures.

What is the best way to find compilation errors caused by definition collisions?▼

Finding compilation errors from definition collisions involves inspecting generated files and exact error messages to separate root causes from downstream symptoms. Verification-first diagnosis identifies whether failures stem from configuration or generator authoring.

How do I resolve module resolution failures during code generation?▼

Resolving module resolution failures requires inspecting the generator source, configuration, and exact error messages to identify the root cause. Distinguishing upstream schema errors from cascaded dependency failures determines whether a CLI configuration fix is needed.

When should I inspect parse issues versus generator source for incorrect output?▼

Inspect parse issues first when generated output is incorrect, as this reveals parsing or schema problems before checking generator source. If parsing is clean, investigate the generator source and configuration to find the root cause.

Related Skills

Explore More Software Engineering Skills→
H2OSLabsH2OSLabs
1

schema-to-openapi

Converts Synnovator data schemas into OpenAPI 3.0 YAML or JSON specifications.

Official
Intermediate
drvossdrvoss
42

fix-build-errors

Diagnoses build, compilation, and type-check failures and generates minimal fixes.

Community
Intermediate
adamayoungadamayoung
1

build-package

Compile individual Swift packages with warnings as errors.

Community
Intermediate
cas-bigdatalabcas-bigdatalab
541

schema_validator

Validate structured data against JSON schemas with field and constraint checks.

Official
Intermediate