local

Run end-to-end tests for Kagenti in Kind and HyperShift environments.

292|103|Updated Mar 27, 2025
One-click install
npx skills add https://github.com/kagenti/kagenti --skill local-kagenti
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: local
Source: https://github.com/kagenti/kagenti/tree/main/.claude/skills/local
Command: npx skills add https://github.com/kagenti/kagenti --skill local-kagenti

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of setting up, running, and testing Kagenti in a local development environment, ensuring smooth workflows and rapid iteration.

Core Features & Use Cases

  • Local Testing Suites: Provides comprehensive test suites for both Kind (local Docker) and HyperShift (AWS) environments.
  • Development Workflow: Guides users through the typical development cycle, from making code changes to checking logs and accessing services.
  • Use Case: A developer needs to quickly test a new agent deployment locally. They can use the local:full-test skill to spin up a test environment, run the agent, and verify its functionality without complex manual setup.

Quick Start

Run the full end-to-end test workflow for Kind by executing the command ./.github/scripts/local-setup/kind-full-test.sh.

Frequently Asked Questions about local

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

FAQPage Schema
How do I run local development and end-to-end testing for Kagenti?

Local development and end-to-end testing for Kagenti is facilitated by executing the `kind-full-test.sh` script, which spins up a containerized environment to verify platform functionality.

Can I test Kagenti deployments using HyperShift and Kind environments?

Yes, Kagenti testing supports both Kind for local Docker environments and HyperShift for AWS, allowing you to validate agent deployments across different containerized platforms.

What is the typical development workflow for testing a new agent locally?

The local testing workflow involves spinning up a test environment using automated scripts, running the agent, checking logs, and inspecting deployed services to verify functionality without manual setup.

Do I need Docker to run local Kagenti testing suites?

Yes, Docker is required for the Kind (Kubernetes in Docker) local testing environment, which provides the containerized infrastructure needed to run and test Kagenti platform components.

How do I inspect deployed services during local Kubernetes testing?

Inspecting deployed services during local Kubernetes testing is supported through built-in utilities that allow you to check logs and access services for verifying agent functionality.