request-routing

name	request-routing
description	Canonical, compact request-routing strategy for SAS Viya requests.

Request Routing — Canonical SKILL

Purpose: single source-of-truth for routing SAS Viya actions (read, query, score, describe, list).

Quick workflow

• Verify — confirm resources exist (use find-*).
• Execute — run the mapped execution tool (read, query, score, describe, list).
• Format — return results and append a short Strategy Summary.

Important Reminder: If the category is "Find resource" do not use the list-* rules below, use the specific find-* tool for that resource type. The list-* tools are for discovery when the user does not have a specific resource in mind.

Classification

Category	Triggers	Primary Action	Primary Tool(s)
Find resource	"find", "does X exist", "locate", "verify"	Verify resource	sas-score-find-library, sas-score-find-table, sas-score-find-mas, sas-score-find-job, sas-score-find-jobdef
Read / Query	"read", "show rows", "how many", "count", "average", "query"	Read / aggregate	sas-score-read-table, sas-score-sas-query
Score	"score", "predict", "run model"	Score inputs	sas-score-mas-score, sas-score-run-job, sas-score-run-jobdef, sas-score-scr-score
List / Discover	"list", "show all", "browse"	List resources	list-* tools (e.g., list-mas, list-jobs)
Describe	"describe", "what inputs", "metadata"	Return metadata	sas-score-*-info (mas/job/jobdef/scr), sas-score-table-info

Verification rules

• Always verify resources using the appropriate find-* tool before executing actions

Execution rules

• Execute only after verification; choose the execution tool per the Execute mapping section.
• Scoring flows:
  • Inline scenario: verify model → call scoring tool.
  • Table rows: verify model + table → read rows → map columns to model inputs → score → merge predictions with rows.
• Read/query flows:
  • Use sas-score-sas-query for aggregations and groupings.
  • Use sas-score-read-table for row reads.
  • When mapping between table columns and model inputs is ambiguous, ask the user for explicit mapping.

Defaults & exceptions

• Default model type: MAS unless the user specifies otherwise.
• Skip find-* verification for SCR models; SCR endpoints may be scored directly.
• If server determination is ambiguous, prompt the user for clarification.

Execute mapping (concise)

• Read rows: sas-score-read-table (lib, table, server)
• Aggregation/query: sas-score-sas-query (lib.table, query)
• MAS scoring: sas-score-mas-score (mas, scenario)
• Job scoring: sas-score-run-job (job, scenario)
• JobDef scoring: sas-score-run-jobdef (jobdef, scenario)
• SCR scoring: sas-score-scr-score (url, scenario)
• Describe: sas-score-*-info, sas-score-table-info

Combined Read + Score (short)

1. Verify: find table (server) and find the model (mas,job,jobdef,scr). If table/model not found, ask user to clarify resource and server.
2. Read: fetch rows (read-table or sas-query).
3. Map: ensure table columns match model inputs; ask for mapping if needed.
4. Score: call the appropriate scoring tool.
5. Merge: attach predictions to rows and return.

Strategy Summary (append to responses)

Strategy Summary:

• Classification: [Find / Read / Score / List / Describe]
• Verification: [Resources verified / skipped]
• Tool(s): [Primary tool(s) invoked]
• Decision: [Server chosen, model type, mapping]
• Next steps: [Follow-ups or clarifications]

---

Error handling (short)

• Resource not found → ask for exact resource name and server (for tables).
• Column/input mismatch → request mapping from user.
• Empty result → ask to relax filters or confirm criteria.
• Execution error → return tool error verbatim.

Examples (minimal)

• Read: "read customers in Public" → find Public (CAS) → read-table → return rows.
• Score inline: "score a=1,b=2 with job simplejob" → find job → run-job → return merged result.
• Score table: "score Public.customers with model risk" → find table (CAS) & model (MAS) → read rows → score → return merged.

Notes: Keep this SKILL as the canonical, compact router; agent wrappers should be short and reference this document for details and examples.