agentsclimarketplace

Integration checker

Skill lteawoo/skills/skills/integration-checker

A collection of practical AI agent skills for app development and code workflows.

Install
npx -y skills add lteawoo/skills --skill integration-checker

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Inspect the integration points between frontend, backend, database, and external APIs. Use it to detect contract mismatches, missing environment variables, broken assumptions, or setup-order issues.

SKILL.md

2.4 KB, as published. Nobody here has run it

Integration Checker

Purpose

Catch errors and omissions at system integration boundaries rather than focusing on isolated features.

Core Principles

  1. Check the input and output contract expected by each layer first.
  2. Prioritize mismatches in field names, types, status codes, and exception flow.
  3. Review environment variables, auth data, initialization order, and network routes together.
  4. Validate failure paths and empty-data cases, not just the success path.
  5. Separate local behavior from deployed-environment behavior.
  6. Judge integration by whether it honors the intended contract, not whether it merely "connects."

Inputs

  • List of modules or systems involved
  • API specs, type definitions, schemas, or environment variables
  • Relevant code or config files
  • Current error symptoms or concerns, if available

Workflow

  1. Identify the connected systems and the boundaries between them.
  2. Document request or response, event, and state-transfer contracts.
  3. Compare types, fields, status codes, error handling, and authentication flow.
  4. Check environment variables, config values, URLs, and secret injection points.
  5. Inspect initialization order, async handling, loading states, and retry behavior.
  6. Summarize the highest-risk integration points and how to validate them.

Output Format

Integration Summary

  • Connected systems
  • Boundaries under review

Contract Review Results

  • Request or response interfaces
  • Type or schema alignment
  • Authentication and authorization flow
  • Error-handling flow

Configuration and Environment Review

  • Required environment variables
  • Config files or runtime dependencies
  • Environment-specific differences

Key Risks

  • Likely mismatch points
  • Items that could cause real incidents
  • Areas that need more validation

Validation Plan

  • Items to confirm via automated tests
  • Items that need manual inspection
  • Reproduction steps or logs to inspect

When Information Is Missing

  • If no spec exists, separate code-based facts from inferences.
  • If a contract mismatch is suspected, state which side should be treated as the source of truth.
  • If the scope is too broad, prioritize from the outermost boundary inward.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.