harness-distribution

Classify and route reusable harness artifacts for shared distribution.

Updated May 17, 2022
One-click install
npx skills add https://github.com/kanade0404/dotfiles --skill harness-distribution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-distribution
Source: https://github.com/kanade0404/dotfiles/tree/main/.opencode/skills/harness-distribution
Command: npx skills add https://github.com/kanade0404/dotfiles --skill harness-distribution

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents reusable rules, commands, hooks, and subagents from being stranded in local-only settings by helping you decide whether they should be shared through the canonical skills distribution path instead of kept on one machine.

Core Features & Use Cases

  • Distribution Judgment: Checks whether an artifact is safe to share, whether it is environment-dependent, and whether it belongs in a local config or a shared repository.
  • Canonical Placement: Maps each reusable harness artifact to the correct destination such as rules, commands, subagents, hooks, or skills-oriented handoff paths.
  • Release and Propagation Workflow: Supports the full path from repository placement and release tagging to downstream consumer regeneration so shared behavior reaches other repos and cloud executions.
  • Use Case: When a team wants the same guardrail or automation behavior to work across multiple repositories and cloud sessions, this Skill determines the proper publishing route and the follow-up steps.

Quick Start

Use the harness-distribution skill to decide where a reusable rule, command, hook, or subagent should live and how to publish it so it reaches every intended execution environment.

Frequently Asked Questions about harness-distribution

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

FAQPage Schema
How do I share reusable hooks and subagents across multiple repositories?

To distribute reusable hooks and subagents across multiple repositories, classify and route them through a canonical distribution path. This process enforces secrecy and environment-dependence checks before mapping artifacts to a shared repository for downstream propagation.

What is the best way to distribute slash commands and rules to cloud sessions?

Distributing slash commands and rules to cloud sessions requires canonical placement and release tagging. This workflow ensures shared behavior reaches intended execution environments by supporting downstream consumer regeneration across repos and cloud executions.

When should I keep reusable scripts in a local config instead of a shared repository?

Keep reusable scripts in a local config instead of a shared repository when they are environment-dependent or fail secrecy checks. Distribution judgment evaluates whether artifacts are safe to share or should remain locally stranded to prevent unsafe exposure.

How do I publish shared automation behavior so downstream consumers can regenerate it?

Publish shared automation behavior for downstream regeneration by applying release tagging to routed artifacts in the repository. This propagation workflow ensures shared rules and commands automatically reach other repos and cloud sessions after release.

Does rulesync help with routing repeatable scripts to canonical destinations?

Rulesync aligns with routing repeatable scripts to canonical destinations like rules, commands, subagents, and hooks. The distribution process maps these harness artifacts to the correct shared path, preventing them from remaining stranded in local-only settings.