domain-routing

Route knowledge cards to major domains and subdomains using routing guides.

9|2|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/zfy465914233/scholar-agent --skill domain-routing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: domain-routing
Source: https://github.com/zfy465914233/scholar-agent/tree/main/.github/skills/domain-routing
Command: npx skills add https://github.com/zfy465914233/scholar-agent --skill domain-routing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decide the correct major domain and subdomain for knowledge cards to keep the knowledge tree organized and consistent, reducing misrouting and manual rework.

Core Features & Use Cases

  • Read repository routing guides and policies to determine where a card should live.
  • Decide major domain and subdomain for new cards and audit existing routings for correctness.
  • Provide concise justification to support routing decisions and facilitate review.

Quick Start

Review a knowledge card and let the AI determine its domain and subdomain routing.

Frequently Asked Questions about domain-routing

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

FAQPage Schema
How do I route knowledge cards to the correct domain and subdomain?

Domain routing for knowledge cards works by reading canonical routing guides and policy files to output a major domain, an optional subdomain, and a justification for precise card placement.

How do I audit existing knowledge card routing decisions in my repository?

You can audit existing knowledge card routing decisions by applying the skill to review current placements against the domain routing policy, ensuring cards live in the correct domain and subdomain.

What is the best way to organize a knowledge tree and reduce card misrouting?

The best way to organize a knowledge tree and reduce misrouting is to apply routing policies that determine the correct major domain and subdomain for new cards while providing justifications for review.

Do I need a specific routing policy file to determine knowledge card placement?

Yes, you need the canonical source files domain_routing_guide.md and domain_routing_policy.json in your repository to determine accurate knowledge card placement and generate routing justifications.

Why does my knowledge card need a justification when assigning it to a domain?

Your knowledge card needs a concise justification to support the routing decision, facilitate manual review, and maintain consistency across the knowledge tree when adding new cards or auditing existing ones.