self-validation

Validate Pact syntax, TypeScript types, gas limits, and cross-module consistency.

1|1|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/Pact-Community-Organization/github-marketplace --skill self-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: self-validation
Source: https://github.com/Pact-Community-Organization/github-marketplace/tree/main/skills/self-validation
Command: npx skills add https://github.com/Pact-Community-Organization/github-marketplace --skill self-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-output validation is essential to ensure all agent outputs meet correctness standards before submission. It checks Pact syntax integrity, TypeScript type conformance, gas usage ceilings, and cross-module consistency.

Core Features & Use Cases

  • Validate Pact contracts for syntax correctness and safety.
  • Validate TypeScript code for type safety and alignment with Pact modalities.
  • Ensure cross-module consistency before agents release outputs.

Quick Start

Run the self-validation checklist on all agent outputs prior to submission.

Frequently Asked Questions about self-validation

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

FAQPage Schema
How do I validate Pact contract syntax before agent output submission?

Validate Pact contract syntax by applying a pre-output validation checklist that checks syntax integrity, TypeScript type conformance, gas usage ceilings, and cross-module consistency before deployment.

What is pre-output validation for Pact and TypeScript agent workflows?

Pre-output validation is a deterministic checking process that identifies and prevents incorrect agent outputs by verifying Pact syntax, TypeScript types, gas limits, and cross-module consistency in Kadena workflows.

Can I use self-validation to check cross-module consistency in Kadena workflows?

Yes, you can use self-validation to check cross-module consistency in Kadena workflows by running the defined validation checklist on all Pact and TypeScript agent outputs prior to release.

What's the best way to ensure TypeScript type safety alignment with Pact modalities?

The best way to ensure TypeScript type safety alignment with Pact modalities is to run a pre-output validation checklist that verifies type conformance alongside Pact syntax and gas limits.

Why does my agent output fail gas limit checks during pre-output validation?

Agent output fails gas limit checks during pre-output validation when the defined checklist detects usage exceeding the allowed gas ceilings, preventing deployment of incorrect outputs.