api-execution-trace

Document API calls with fully resolved URLs in api_info.md.

1|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/Saurav-snapwork/NewAppTemplate --skill api-execution-trace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-execution-trace
Source: https://github.com/Saurav-snapwork/NewAppTemplate/tree/main/.github/skills/api-execution-trace
Command: npx skills add https://github.com/Saurav-snapwork/NewAppTemplate --skill api-execution-trace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Document all API calls with fully resolved URLs for reliable debugging and QA.

Core Features & Use Cases

  • Cross-verify API surface between apiOutput and dataLayerOutput to ensure documented endpoints match implemented calls.
  • Resolve final URLs for each endpoint by composing baseURL, path parameters, and query parameters, producing finalResolvedUrl and finalRequestUrl.
  • Generate a production-ready api_info.md that enumerates APIs with headers, request bodies, and warnings for dynamic placeholders.
  • Halt on fatal discrepancies while surfacing warning annotations for non-fatal issues to aid QA and debugging.
  • Provide a structured artifact that can be consumed by downstream tooling and audits.

Quick Start

Run this skill after API Integration and Data Layer Builder to generate a complete api_info.md with final URLs for your feature.

Frequently Asked Questions about api-execution-trace

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

FAQPage Schema
How do I document API calls with fully resolved URLs for QA debugging?

To document API calls with resolved URLs, cross-verify declared endpoints against implemented calls and generate a markdown file enumerating final URLs, headers, and request bodies for debugging.

What is deterministic URL construction for API execution traces?

Deterministic URL construction resolves final endpoint URLs by composing the baseURL with path and query parameters, producing a reliable execution trace that validates inputs and ensures documented APIs match implemented calls.

How do I cross-verify documented API endpoints against implemented calls?

Cross-verify API endpoints by comparing the declared API surface against the data layer output, enforcing deterministic URL construction, and halting the process when fatal discrepancies are detected.

Why does my API documentation show unresolved dynamic placeholders?

Dynamic placeholders appear in API documentation when non-fatal issues are detected during URL resolution; the tool surfaces these as warning annotations in the output file to aid debugging without halting.

When do I need to generate an api_info.md file for API audits?

Generate an API documentation file after completing API integration and data layer building, producing a structured artifact with final request URLs and warnings that can be consumed by downstream tooling and audits.

Can I use execution trace data for downstream tooling and audits?

Yes, execution traces produce a structured markdown artifact enumerating APIs with headers and request bodies, providing a production-ready output that downstream tooling and audit processes can directly consume.