skills.rest
gapfDev
gapfDevCOMMUNITY
Explore all skills by this author →
GitHub

contract-profiles

Validate B2A to B2B contract handoffs against the L88_PROFILES_PAYLOAD schema.

Updated Aug 27, 2026
Search Tags:#compliance#handoff#validate#contracts#profiles#b2b#l88
One-click install
npx skills add https://github.com/gapfDev/workflow --skill contract-profiles
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: contract-profiles
Source: https://github.com/gapfDev/workflow/tree/main/c1.5/.claude/skills/contract-profiles
Command: npx skills add https://github.com/gapfDev/workflow --skill contract-profiles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

L88_PROFILES_PAYLOAD validation ensures B2A → B2B contract handoffs carry complete and verifiable profile data, preventing incomplete or inconsistent handoffs.

Core Features & Use Cases

  • Validates that a profile is non-empty and selected from available options
  • Validates that a profile mechanism is non-empty and describes the core strategy
  • Requires at least one Files Touched entry and ensures AC coverage for Block 1
  • Provides a mapped root-cause reference to L88_DIAGNOSTIC for issue tracing

Quick Start

Execute the L88_PROFILES_PAYLOAD validator against the target B2A/B2B handoff bundle.

Frequently Asked Questions about contract-profiles

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

FAQPage Schema
How do I validate B2A to B2B contract handoffs?▼

Validate B2A to B2B contract handoffs by executing the L88_PROFILES_PAYLOAD validator against the target handoff bundle to ensure payloads meet the required schema.

What is L88_PROFILES_PAYLOAD schema validation?▼

L88_PROFILES_PAYLOAD schema validation ensures B2A to B2B contract handoffs carry complete and verifiable profile data, preventing incomplete or inconsistent contract transfers.

What does a B2B contract handoff payload require?▼

A B2B contract handoff payload requires a non-empty chosen profile, a defined profile mechanism, at least one touched file, full Block 1 AC coverage, and a linked L88_DIAGNOSTIC root-cause reference.

How do I trace root causes for failed contract handoff profiles?▼

Trace root causes for failed contract handoff profiles by checking the mapped L88_DIAGNOSTIC reference, which enforces root-cause alignment for verifiable issue tracing.

Why does my contract handoff validation fail on AC coverage?▼

Contract handoff validation fails on AC coverage when the payload does not include complete Block 1 AC coverage, which is strictly enforced alongside requiring at least one touched file entry.

Does contract handoff validation work without a profile mechanism?▼

Contract handoff validation does not work without a profile mechanism, as the L88_PROFILES_PAYLOAD schema strictly enforces a non-empty profile mechanism describing the core strategy.

Related Skills

Explore More Legal & Compliance Skills→
TrevorEdrisTrevorEdris
2

session-handoff

Generate structured handoff documents to preserve context between AI agent sessions.

Community
Advanced
tangzheng202202tangzheng202202
1

systematic-debugging

Guide engineers through a four-phase root-cause investigation to diagnose bugs.

Community
Advanced
TruCol270TruCol270
1

systematic-debugging

Trace bugs through data flow to identify root causes before proposing fixes.

Community
Advanced
gitgoodordietryinggitgoodordietrying
1

data-validation

Validate data structures and API payloads against JSON Schema, Zod, and Pydantic schemas.

Community
Advanced