swagger-api

Automate TTT API endpoint validation across environments via Swagger MCP tools or curl.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/midas44/ttt-expert-v2 --skill swagger-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swagger-api
Source: https://github.com/midas44/ttt-expert-v2/tree/main/.claude/skills/swagger-api
Command: npx skills add https://github.com/midas44/ttt-expert-v2 --skill swagger-api

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates calling TTT endpoints through Swagger MCP tools or curl to validate APIs across environments.

Core Features & Use Cases

  • Supports a wide range of TTT endpoints across clocks, employees, projects, notifications, and more, in qa1, timemachine, and stage environments.
  • Provides MCP naming conventions and practical examples for GET, PATCH, POST calls, easing integration into CI pipelines.
  • Ideal for software engineers and QA analysts validating API behavior, performance, and reliability.

Quick Start

Use the mcp__swagger-qa1-ttt-api__get-using-get-5 command to verify baseline API availability in the QA environment.

Frequently Asked Questions about swagger-api

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

FAQPage Schema
How do I automate API testing for endpoints across multiple environments?

Automating API testing across environments is achieved by calling TTT endpoints through Swagger MCP tools or curl to validate API behavior in qa1, timemachine, and stage environments. The Skill enforces API key usage and environment-specific naming conventions for reproducible integration tests.

What's the best way to validate TTT API endpoints using Swagger MCP tools?

Validating TTT API endpoints with Swagger MCP tools involves using structured GET, PATCH, and POST examples that follow MCP naming conventions. You can verify baseline API availability in the QA environment using the mcp__swagger-qa1-ttt-api__get-using-get-5 command.

Can I use curl to test clock, employees, projects, and notifications endpoints?

Testing clock, employees, projects, and notifications endpoints with curl is fully supported alongside Swagger MCP tools. The Skill provides practical curl examples for these TTT endpoints across qa1, timemachine, and stage environments to ensure reliable integration testing.

How do I configure environment-specific naming conventions for reproducible API tests?

Configuring environment-specific naming conventions for reproducible API tests requires using the predefined MCP naming patterns for qa1, timemachine, and stage. The Skill enforces API key usage and environment configuration to maintain test consistency across different TTT endpoints.

Does this approach integrate well with CI pipelines for endpoint validation?

Integration into CI pipelines for endpoint validation is ideal because the Skill provides MCP naming conventions and practical GET, PATCH, POST examples. Software engineers and QA analysts can automate calling TTT endpoints to validate API behavior, performance, and reliability across environments.

What do I need to start automating TTT endpoint calls for integration testing?

To start automating TTT endpoint calls for integration testing, you need API keys and correct environment configuration for qa1, timemachine, or stage. The Skill guides you through structured GET, PATCH, and POST calls to validate APIs reliably across these environments.