Add official HarnessRouter skill - #1
Draft
kuanzema wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
harnessrouterAgent SkillWhy
Coding agents need a stable, purpose-built workflow for identifying agent-powered product features, configuring one or more HarnessRouter Harnesses, and connecting them securely to the host product without rebuilding a parallel agent layer.
Developer impact
Developers can load
$harnessrouterfrom this repository and receive only the references required for the current integration task. The Skill requires a transcript-safe API-key modal at the start and preserves server-side authorization, tenancy, Streaming, Session, File, and Artifact boundaries.Manual review gate
Richard Song must review this Skill against HarnessRouter's currently deployed and verifiable product capabilities before this Draft PR becomes ready or merges. Valid evidence is the deployed API schema, capability metadata, official product surfaces, and accepted runtime behavior. Roadmap items, internal candidates, and unaccepted Payments, Deployment, or Database capabilities must not be presented as currently available.
Validation
quick_validate.py harnessroutergit diff --cached --check