harness-skill

Name: harness-skill
Availability: InStock
Author: wild

Automate skill creation and management across Claude Code, Codex, and Copilot.

12|Updated Feb 6, 2026

Search Tags:#automation #workflow #documentation #scaffold #skill #harness #provider-artifacts

Ready to run

npx skills add https://github.com/madebywild/agent-harness --skill harness-skill

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: harness-skill
Source: https://github.com/madebywild/agent-harness/tree/main/.claude/skills/harness-skill
Command: npx skills add https://github.com/madebywild/agent-harness --skill harness-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation and management of skill entities across Claude Code, Codex, and Copilot.

Core Features & Use Cases

Central source of truth for skills under .harness/src/skills/<skill-id> and SKILL.md.
Generate provider artifacts with harness apply.
Supports optional files (reference.md, examples/, scripts/, references/, assets/) to enrich the skill.
Reuse across providers to ensure consistency and rapid iteration.

Quick Start

Scaffold the skill, edit SKILL.md, and run harness apply to generate provider-ready artifacts.

Frequently Asked Questions about harness-skill

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

FAQPage Schema

How do I create and manage skills across multiple AI coding assistants?▼

You can define skills once in a central source of truth under .harness/src/skills and run harness apply to generate provider-ready artifacts for Claude Code, Codex, and Copilot, ensuring consistency across providers.

What is the best way to scaffold a skill and generate provider artifacts?▼

Scaffold the skill entity, edit the SKILL.md file with required frontmatter schema including name and description, then execute harness apply to generate provider-ready artifacts for your target platforms.

Does this skill management approach work with Claude Code, Codex, and Copilot?▼

Yes, the harness apply command generates provider-ready artifacts specifically designed for integration with Claude Code, Codex, and Copilot outputs, allowing you to reuse skill definitions across all supported providers.

Can I include optional scripts and reference files when defining a skill?▼

Yes, you can enrich a skill by adding optional files such as reference.md, examples/, scripts/, references/, and assets/ alongside the required SKILL.md file within the skill directory structure.

What frontmatter schema is required for a valid SKILL.md file?▼

The frontmatter schema enforces name and description as required fields in the SKILL.md file, ensuring each skill entity has proper identification and documentation before generating provider artifacts.

Why do I need a central source of truth for skill definitions instead of editing provider files directly?▼

Maintaining a central source of truth under .harness/src/skills prevents provider-specific drift, enables rapid iteration, and ensures consistency by generating provider-ready artifacts from a single defined skill entity.