AgentOps / Harness Governance

Harness Skill Proposal

Propose new or revised harness skills and policy text from recurring failure patterns while keeping scope limited to harness assets.

DocumentationAgent instructionsRequirements & limits

Use when repeated harness failures justify drafting new or revised harness skills and policy text.

Inputs

  • reflection findings
  • current harness policies
  • current skills affected by the failure pattern

Outputs

  • Proposed skill changes
  • Boundary notes
  • Rationale summary

Before you begin

  • Reading and copying the procedure require no terminal setup. Check requirements for any packaged programs separately.

Try this first

Read the procedure and supply its documented inputs. Use the full text in an agent app or chat that supports pasted instructions, following that host's guidance.

Limits for this step
  • Instruction package only; it does not provide or authorize an executable runtime capability.
  • Safe for proposal drafting inside harness-owned assets; require human approval before any change outside harness scope.
Read full instructionsHide full instructionsSKILL.md · v0.1.0

Harness Skill Proposal

When to use

  • Use after run reflection identifies repeated harness failures.
  • Use when a new harness rule or skill is needed.
  • Use before creating a harness-only PR.

Inputs required

  • reflection findings
  • current harness policies
  • current skills affected by the failure pattern

Workflow

  1. Read the reflection evidence and isolate a recurring pattern.
  2. Decide whether the fix belongs in a skill, a policy file, or a benchmark.
  3. Draft the proposed change in a structured, reviewable format.
  4. Confirm the target stays within harness-owned paths.

Output format

  • Problem Statement
  • Proposed Harness Change
  • Target Artifacts
  • Expected Improvement
  • Approval Notes

Guardrails

  • Only target harness-owned artifacts by default.
  • Do not propose edits to production code or deployment config.
  • Tie every proposal to concrete run evidence.
  • Escalate if the best fix would require protected-path changes.

Failure modes

  • If evidence is too thin, recommend more benchmarks instead of a change.
  • If multiple fixes are plausible, present the smallest safe proposal first.
  • If scope expands beyond harness paths, stop and require approval.
View file metadata
---
name: harness-skill-proposal
description: Turn recurring harness failures into candidate skill or policy
  updates while keeping proposals limited to harness-owned artifacts.
---

Summary sources · Catalogue metadata, skill.yaml, SKILL.md, examples/input.json, examples/output.json · v0.1.0 · Release package

Install instruction files

These commands copy guidance into the selected runtime directories. Confirm that your agent app discovers it. Any packaged programs need separate setup and verification.

Install (Codex)

./bin/skills-hub install agentops/[email protected] --runtime codex

Install (Claude)

./bin/skills-hub install agentops/[email protected] --runtime claude

Install (Generic)

./bin/skills-hub install agentops/[email protected] --runtime generic --target ./my-agent/skills

How You Can Use This

Documentation

Resource form: Agent instructions

Read or copy the guidance. Any packaged programs have separate execution requirements and evidence.

First run: Read SKILL.md and follow the documented workflow.

Current limits

  • Instruction package only; it does not provide or authorize an executable runtime capability.
What installation and verification mean
File installation
Places package files and generated configuration in the selected directories.
Native discovery
Your agent app finds and accepts the instructions, tools or plugin registrations.
Mock execution
Exercises sample fixtures. Connected data and provider effects need a separate check.
Connected operation
Requires current configuration, provider authentication, scoped permissions and a successful operation in your intended environment.

Declared compatibility

Compatibility unknown: versions and capabilities have not been declared.

Classification: declared

Technical details and release files

Operational Summary

Execution mode: analysis-only

Approval boundary: Safe for proposal drafting inside harness-owned assets; require human approval before any change outside harness scope.

Review and lifecycle

Review maturity: Experimental

Security review declaration: Not declared

Lifecycle: Active

These release declarations are separate from evidence that a workflow operates in your environment.

Runtime & Dependencies

ID: agentops/harness-skill-proposal

Tags: proposal, harness, governance, skills

Runtimes: codex, claude, generic

Tool dependencies: 0

API dependencies: 0

Dependencies

Tools: Not documented

APIs: Not documented

Outputs

  • Proposed skill changes
  • Boundary notes
  • Rationale summary