repo-harness-capability

Add explicit capability boundaries to existing repo-harness repositories.

407|29|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/Ancienttwo/repo-harness --skill repo-harness-capability
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-harness-capability
Source: https://github.com/Ancienttwo/repo-harness/tree/main/assets/skill-commands/repo-harness-capability
Command: npx skills add https://github.com/Ancienttwo/repo-harness --skill repo-harness-capability

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of defining and adding explicit capabilities to a repository, without the need to re-run the entire repo-harness initialization process.

Core Features & Use Cases

  • Selective Capability Management: Add or synchronize specific capability boundaries in a repository.
  • Enhanced Configuration: Add subfolders for AGENTS.md and CLAUDE.md for more granular capability definitions.
  • Use Case: If you want to define new capabilities for your project without re-initializing the entire repo-harness, use this skill to add just the necessary capability boundaries.

Quick Start

Use the repo-harness-capability skill to add the 'build' capability to your repository: repo-harness-capability add capability --repo <path> --prefix build

Frequently Asked Questions about repo-harness-capability

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

FAQPage Schema
How do I add new capabilities to an existing repo-harness without re-running the full initialization?

Selective capability management lets you add or synchronize specific capability boundaries in a repository without re-running the entire repo-harness initialization, ideal for defining new project capabilities incrementally without disrupting existing configurations.

Can I define granular capability configurations using AGENTS.md and CLAUDE.md subfolders?

Granular capability configuration is achieved by adding subfolders for AGENTS.md and CLAUDE.md, enabling precise and localized capability definitions within your repository's explicit boundaries without full harness migration.

What is the best way to set up repo-local capability boundaries for a specific build prefix?

Use the command `repo-harness-capability add capability --repo <path> --prefix build` to selectively add explicit capability boundaries to your repository path without full harness initialization.

Do I need to run a full repo-harness migration just to add a single capability boundary?

No, you do not need a full repo-harness migration to add a single capability boundary. This skill is optimized for selective capability setup, allowing you to add explicit boundaries without running init, migrate, or upgrade processes.

When should I avoid using selective capability management and opt for a full harness re-run instead?

Avoid selective capability management and choose a full harness re-run when your repository requires comprehensive initialization, migration, or upgrade, rather than just defining or synchronizing specific explicit capability boundaries.