harness-plugin-maintainer

Manages lifecycle, builds, and validates ai-agent-harness plugin for Codex and Claude Runtimes.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/hb9397/ai-agent-harness-docs --skill harness-plugin-maintainer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-plugin-maintainer
Source: https://github.com/hb9397/ai-agent-harness-docs/tree/main/maintainer/skills/harness-plugin-maintainer
Command: npx skills add https://github.com/hb9397/ai-agent-harness-docs --skill harness-plugin-maintainer

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a centralized management interface for maintaining the integrity, versioning, and deployment readiness of the ai-agent-harness plugin across Codex and Claude runtime environments.

Core Features & Use Cases

  • Deterministic Builds: Ensures consistent plugin tree generation, manifest creation, and archive hashing for reliable releases.
  • Automated Validation: Performs comprehensive smoke tests, inventory checks, and regression analysis to ensure plugin stability.
  • Use Case: A maintainer uses this Skill to build a new release candidate, verify that all user skills are correctly projected into the runtime, and confirm that the plugin passes CLI installation smoke tests before official distribution.

Quick Start

Call the harness-plugin-maintainer skill to build the plugin and run the full validation suite.

Frequently Asked Questions about harness-plugin-maintainer

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

FAQPage Schema
How do I automate plugin release validation for Codex and Claude Code runtimes?

You can automate plugin release validation by executing deterministic artifact generation, manifest verification, and CLI installation smoke tests. This Skill manages the full validation suite to ensure release readiness and stability for Codex and Claude Code runtimes.

What is deterministic plugin tree generation and why is it needed for releases?

Deterministic plugin tree generation creates consistent plugin archives, manifests, and hashes for reliable releases. It is needed to lock upstream dependencies and ensure predictable runtime environments across Codex and Claude Code installations.

Does this validation process enforce semantic versioning and upstream dependency locking?

Yes, the validation process enforces strict compliance with semantic versioning and upstream dependency locking. It verifies release candidates against these regression standards to prevent version conflicts and ensure plugin stability before official distribution.

How do I run a CLI installation smoke test for an AI agent harness plugin?

To run a CLI installation smoke test, invoke the validation suite to build the plugin and verify its installation. This Skill automates the process, checking that all user skills are correctly projected into the runtime environment and pass installation checks.

Can I use this to check if user skills are correctly projected into the runtime?

Yes, you can use this to verify that user skills are correctly projected into the runtime. The Skill performs comprehensive inventory checks and regression analysis to confirm accurate component projection before the plugin passes distribution validation.

What are the limitations when managing AI agent harness plugin releases?

The limitations include its strict scope restricted to Codex and Claude Code runtimes. It focuses exclusively on deterministic builds, semantic versioning compliance, and regression standards, meaning it does not handle arbitrary runtime environments or non-standard deployment workflows.