owner-routing
Internal process for the owner-router agent. Defines the step-by-step procedure for determining likely bug owners using strict 6-level routing precedence with staleness detection. Not user-invocable — loaded by the agent via its `skills: ["owner-routing"]` frontmatter property.
Best use case
owner-routing is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Internal process for the owner-router agent. Defines the step-by-step procedure for determining likely bug owners using strict 6-level routing precedence with staleness detection. Not user-invocable — loaded by the agent via its `skills: ["owner-routing"]` frontmatter property.
Teams using owner-routing should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/owner-routing/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How owner-routing Compares
| Feature / Agent | owner-routing | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Internal process for the owner-router agent. Defines the step-by-step procedure for determining likely bug owners using strict 6-level routing precedence with staleness detection. Not user-invocable — loaded by the agent via its `skills: ["owner-routing"]` frontmatter property.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# Owner Routing Process Step-by-step procedure for determining the most likely owner/team for each bug cluster using strict 6-level precedence with staleness detection and override memory. ## Instructions ### Step 1: Check Overrides First For each cluster, check if a routing_override exists from a prior run: - If found: use the override (confidence 1.0, source "routing_override"), skip precedence lookup - Log the override application to audit ### Step 2: Query Sources in Precedence Order For each cluster without an override, query sources strictly in order: | Level | Source | Tool | Base Confidence | |-------|--------|------|----------------| | 1 | Service owner | `mcp__triage__lookup_service_owner` | 1.0 | | 2 | Oncall | `mcp__triage__lookup_oncall` | 0.9 | | 3 | CODEOWNERS | `mcp__triage__parse_codeowners` | 0.8 | | 4 | Recent assignees (30d) | `mcp__triage__lookup_recent_assignees` | 0.6 | | 5 | Recent committers (14d) | `mcp__triage__lookup_recent_committers` | 0.5 | | 6 | Fallback mapping | Config lookup | 0.3 | Stop at the first level that returns a valid team or assignee. ### Step 3: Apply Confidence Modifiers Multiply each result's confidence by the precedence modifier from routing_config. ### Step 4: Detect Staleness Flag any routing signal older than the staleness threshold (default 30 days): - Mark the result as stale with the number of days - Reduce confidence accordingly - Stale signals are still usable but should be noted in output ### Step 5: Build Recommendation Using `lib.buildRoutingRecommendation()`: - Rank valid results by level (lowest level = highest priority) - Set top_recommendation to the best result - If no valid results: set uncertainty=true with reason "Routing: uncertain — no routing signals available. Manual assignment required." ## References Load routing precedence rules: ``` !cat skills/x-bug-triage/references/routing-rules.md ``` Load escalation trigger definitions: ``` !cat skills/x-bug-triage/references/escalation-rules.md ```
Related Skills
openrouter-routing-rules
Define custom routing rules for OpenRouter requests based on user tier, task type, cost budget, and availability. Triggers: 'openrouter rules', 'routing rules', 'custom routing openrouter', 'conditional model selection'.
openrouter-model-routing
Implement intelligent model routing to optimize cost, quality, and latency on OpenRouter. Use when building multi-model systems or optimizing spend across task types. Triggers: 'openrouter routing', 'model routing', 'route to model', 'model selection openrouter'.
routing-dex-trades
Route trades across multiple DEXs to find optimal prices with minimal slippage and gas costs. Use when comparing DEX prices, finding optimal swap routes, analyzing price impact, splitting large orders, or assessing MEV risk. Trigger with phrases like "find best swap", "compare DEX prices", "route trade", "optimal swap route", "split order", "DEX aggregator", "check slippage", or "MEV protection".
schema-optimization-orchestrator
Multi-phase schema optimization workflow orchestrator. Creates session directories, spawns phase agents sequentially, validates outputs, aggregates results. Trigger: "run schema optimization", "optimize schema workflow", "execute schema phases"
test-skill
Test skill for E2E validation. Trigger with "run test skill" or "execute test". Use this skill when testing skill activation and tool permissions.
example-skill
Brief description of what this skill does and when the model should activate it. Use when [describe the user's intent or situation]. Trigger with "example phrase", "another trigger", "/example-skill".
testing-visual-regression
Detect visual changes in UI components using screenshot comparison. Use when detecting unintended UI changes or pixel differences. Trigger with phrases like "test visual changes", "compare screenshots", or "detect UI regressions".
generating-unit-tests
Test automatically generate comprehensive unit tests from source code covering happy paths, edge cases, and error conditions. Use when creating test coverage for functions, classes, or modules. Trigger with phrases like "generate unit tests", "create tests for", or "add test coverage".
generating-test-reports
Generate comprehensive test reports with metrics, coverage, and visualizations. Use when performing specialized testing. Trigger with phrases like "generate test report", "create test documentation", or "show test metrics".
orchestrating-test-execution
Test coordinate parallel test execution across multiple environments and frameworks. Use when performing specialized testing. Trigger with phrases like "orchestrate tests", "run parallel tests", or "coordinate test execution".
managing-test-environments
Test provision and manage isolated test environments with configuration and data. Use when performing specialized testing. Trigger with phrases like "manage test environment", "provision test env", or "setup test infrastructure".
generating-test-doubles
Generate mocks, stubs, spies, and fakes for dependency isolation. Use when creating mocks, stubs, or test isolation fixtures. Trigger with phrases like "generate mocks", "create test doubles", or "setup stubs".