skills.rest
equaltoai
equaltoaiOFFICIAL
Explore all skills by this author →
GitHub

coordinate-with-lesser

Audit body changes for lesser integration contract impact and coordination needs.

3|1|Updated Feb 21, 2026
Search Tags:#deployment#integration#jwt#dynamodb#cdk#ssm#lesser
One-click install
npx skills add https://github.com/equaltoai/lesser-body --skill coordinate-with-lesser
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coordinate-with-lesser
Source: https://github.com/equaltoai/lesser-body/tree/main/.agents/skills/coordinate-with-lesser
Command: npx skills add https://github.com/equaltoai/lesser-body --skill coordinate-with-lesser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you avoid breaking the body↔lesser integration by checking whether a proposed change affects shared auth, shared data access, API consumption, SSM exports, or the first-deploy wiring order.

Core Features & Use Cases

  • Integration contract review: Confirms whether a change touches JWT validation, DynamoDB reads, lesser REST API calls, SSM export names, or soul-enabled CDK behavior.
  • Cross-repo coordination planning: Produces a clear coordination plan for changes that require the lesser steward to update the other side first or in parallel.
  • Safe deployment sequencing: Helps preserve the required first-time deploy order and prevent accidental contract drift between services.
  • Use case: Before changing the MCP endpoint wiring or the Lesser API client, use this Skill to verify the impact and decide whether lesser-side coordination is required.

Quick Start

Ask for a lesser-integration audit of your concrete change and include the affected files, endpoints, or exports so the Skill can produce a coordination plan.

Frequently Asked Questions about coordinate-with-lesser

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

FAQPage Schema
How do I check if a body change breaks the lesser integration contract?▼

You can check if a body change breaks the lesser integration contract by auditing modifications for impacts on shared JWT secret handling, DynamoDB reads, lesser REST API consumption, SSM export publication, and soulEnabled deployment sequencing.

What is cross-repo coordination planning for shared JWT and DynamoDB integrations?▼

Cross-repo coordination planning for shared JWT and DynamoDB integrations produces a clear plan dictating whether the lesser steward must update the other side first or in parallel to prevent accidental contract drift between services.

How do I safely sequence deployments for soulEnabled CDK changes?▼

To safely sequence deployments for soulEnabled CDK changes, verify the required first-time deploy order and ensure the change does not disrupt the body-to-lesser dependencies before implementation proceeds.

When do I need to audit SSM export publication before updating an API client?▼

You need to audit SSM export publication before updating an API client when your proposed change touches SSM export names or lesser REST API calls, ensuring cross-repo coordination is required before proceeding.

Can I modify lesser REST API consumption without coordinating with the lesser steward?▼

Modifying lesser REST API consumption without coordinating with the lesser steward risks breaking the integration contract, so you must audit the change first to decide whether lesser-side coordination is required.

Related Skills

Explore More Software Engineering Skills→
equaltoaiequaltoai
3

deploy-body

Orchestrates staged AWS CDK deployments of merged lesser-body changes.

Official
Advanced
usuroborusurobor
8

handoff

Standardize inter-agent handoffs with a canonical wire-format contract.

Community
Advanced
MybonoMybono
100

aws-cloud-patterns

Automate AWS Lambda, DynamoDB, and API Gateway deployment with CDK or Terraform.

Community
Advanced
whritwhrit

github-multi-repo

Coordinate cross-repository development and synchronization across multiple GitHub repositories.

Community
Advanced