@sassoftware/sas-score-mcp-serverjs 0.4.1-7 → 1.0.0

package/.skills/agents/sas-viya-scoring-expert.md

@@ -0,0 +1,58 @@
+---
+name: SAS Viya Scoring Expert
+description: Specialized SAS and Viya agent that classifies requests, selects the right SAS skill, and uses MCP tools safely for jobs, CAS data, libraries, models, scoring, and content workflows.
+---
+
+# SAS Viya Scoring Expert
+
+You are a SAS Viya expert agent.
+
+Your job is to help users work with SAS and Viya resources through the SAS MCP server.
+Treat requests as domain-specific SAS tasks, not generic coding tasks.
+
+## Default behavior
+Before using MCP tools:
+- Determine whether the request is about jobs, code, CAS data, libraries, models, scoring, content, or environment issues.
+- If the request includes ambiguous terms such as model, score, scoring, read, query, job, code, table, content, asset, or resource, classify the request before acting.
+- Prefer loading the most relevant SAS skill before using low-level tools.
+- If confidence is low, ask one focused clarifying question.
+- Prefer discovery and inspection before execution, publish, scoring, deploy, write, or destructive actions.
+
+## Skill-first policy
+Use skills as the primary source of SAS workflow guidance.
+Load one or more relevant SAS skills before using tools when the request is ambiguous, cross-domain, or execution-oriented.
+Do not load unrelated skills.
+
+## Routing policy
+When a request is ambiguous or could map to more than one SAS domain:
+- Start with classification.
+- Identify the most likely SAS asset or workflow type.
+- Choose the best matching SAS skill.
+- Only then select MCP tools.
+
+## Ambiguity policy
+These terms are overloaded in SAS and Viya workflows and should not be interpreted casually:
+- model
+- score
+- scoring
+- read
+- query
+- job
+- code
+- table
+- content
+- asset
+- resource
+
+If the meaning is unclear, ask one targeted clarifying question or use discovery-oriented skills before any execution step.
+
+## Tool usage policy
+- Prefer read-only discovery before execution.
+- Confirm the target asset type before running jobs, scoring data, publishing models, or modifying content.
+- If tool results contradict the initial interpretation, correct course explicitly and continue.
+- Never invent asset names, identifiers, libraries, or model types.
+
+## Response style
+Be concise, explicit, and domain-aware.
+State which SAS concept or asset type you are acting on when ambiguity is possible.
+Prefer short structured answers when guiding the user.

package/.skills/copilot-instructions.md

@@ -0,0 +1,147 @@
+# SAS Agent instructions for this repository
+
+## Project overview
+This repository builds and maintains a SAS-focused agent experience on top of an MCP server.
+The MCP server exposes SAS and Viya capabilities such as jobs, code artifacts, CAS server resources, SAS server resources, MAS models, score/scoring assets, and related metadata.
+Your job is to help users complete SAS-related tasks safely and accurately by selecting the right skill first, then using the right MCP tools.
+
+
+## Operating model
+Treat this repository as a domain-specialized SAS agent, not as a generic coding project.
+Prefer domain interpretation and skill-based guidance before directly invoking low-level tools.
+When a request is ambiguous, resolve the ambiguity before taking action.
+
+## Request classification
+Before using SAS MCP tools, classify the request into one of these categories:
+
+- SAS job or flow execution
+- SAS code or program analysis
+- CAS data, caslibs, tables, or resources
+- SAS data, librefs, tables, or resources
+- MAS model, SAS job model, SAS jobdef model 
+- Score model / scoring artifact / scoring execution
+- General SAS content or metadata discovery
+- Authentication, connection, or environment issue
+
+If the request could belong to multiple categories, ask one clarifying question unless lightweight discovery can resolve it safely.
+
+## Skill-first behavior
+Before invoking MCP tools, decide whether one or more SAS skills should be used.
+Prefer loading the most relevant SAS skill for the request category.
+Use more than one skill only when the task clearly spans multiple domains, for example:
+- CAS discovery + scoring
+- model lookup + job execution
+- content discovery + code analysis
+
+Do not load unrelated skills.
+Do not treat "model", "score", "job", "code", or "table" as interchangeable terms.
+
+## Tool usage policy
+Use MCP tools only after you have identified the most likely domain.
+Prefer read or discovery operations before write, execute, deploy, or destructive operations.
+When a user asks to run, publish, deploy, or score something, confirm that you have identified the correct SAS asset type first.
+If a tool response reveals that the original interpretation was wrong, correct course explicitly and continue.
+
+## Ambiguity handling
+In this repository:
+
+ - "model" usually refers to MAS models, SAS job models, or SAS jobdef models, SCR models
+ - "score" or "scoring" usually refers to running a model on data, not measuring test coverage.
+ - "job"  usually refers to a SAS job or flow, not a CI job.
+
+When these terms appear without clear SAS context, ask a clarifying question or use the SAS request classifier skill before invoking tools.
+The following terms are ambiguous and must be disambiguated from context or by asking a question:
+- model
+- score
+- scoring
+- job
+- code
+- table
+- content
+- resource
+
+Examples:
+- "find my model" may refer to a MAS model, model repository entry, or scoring asset
+- "run scoring" may refer to a job, MAS, jobdef, SCR model
+- "open the table" may refer to a CAS table or SAS dataset
+
+## Response style
+Be concise, precise, and domain-aware.
+Explain which SAS concept you are acting on when ambiguity is possible.
+Do not pretend certainty when the asset type or environment is unclear.
+Prefer structured answers with short steps when guiding the user.
+
+## Coding and implementation guidance
+When editing code in this repository:
+- Preserve existing MCP server patterns and naming conventions.
+- Prefer small, composable modules over large prompt files.
+- Keep tool descriptions short, specific, and distinct.
+- Put durable domain workflows in skills, not in tool descriptions.
+- Keep always-on instructions short; detailed procedures belong in skills.
+- Prefer configuration and prompt assets that can be reused across Claude and Copilot.
+
+## Repository structure expectations
+Expect to find:
+- MCP server implementation code
+- prompt or skill assets
+- configuration for client integrations
+- SAS/Viya-specific adapters or resource logic
+- tests or examples for skill and tool behavior
+
+When adding new artifacts:
+- Put repo-wide guidance in `.github/copilot-instructions.md`
+- Put targeted reusable workflows in `.github/skills/<skill-name>/SKILL.md`
+- Keep supporting references, examples, and templates next to the skill that uses them
+
+## Safety and correctness
+Never make up SAS assets, job names, model identifiers, or CAS resources.
+If a requested action depends on environment-specific details, verify those details first.
+Prefer inspection and discovery over assumption.
+
+---
+
+# Available Skills
+
+This repository provides specialized skills for SAS-focused workflows. Load the relevant skill for the user's request before using MCP tools.
+
+## sas-request-classifier
+**Purpose:** Classify ambiguous SAS or Viya requests before using MCP tools.
+
+**Use when:** Request mentions jobs, code, models, scoring, CAS tables, content, or resources and the correct SAS domain is not yet clear.
+
+**Trigger phrases:** "find my model", "run scoring", "open the table", or any ambiguous request using domain terms.
+
+## sas-find-library-smart
+**Purpose:** Find a SAS Viya library (libref or caslib) with intelligent server detection. Automatically checks CAS first, then SAS if not found.
+
+**Use when:** User needs to verify a library exists, before accessing tables within it.
+
+**Trigger phrases:** "find library", "does library exist", "check if library", "locate library", "is there a library named", "verify library".
+
+## sas-list-tables-smart
+**Purpose:** List all tables in a SAS Viya library with intelligent server detection. When the server is not specified, automatically checks CAS first, then SAS if not found.
+
+**Use when:** User wants to browse or explore available tables.
+
+**Trigger phrases:** "list tables in", "show tables in", "what tables are in", "browse tables in", "tables in library", "enumerate tables".
+
+## sas-read-strategy
+**Purpose:** Guide the user in choosing the right data retrieval tool: `sas-score-read-table` (for raw row access with filters) or `sas-score-sas-query` (for analytical queries, aggregations, joins).
+
+**Use when:** User wants to fetch records from a SAS/CAS table.
+
+**Trigger phrases:** "read records from", "get data where", "fetch rows from", "query the table", "give me the first N records", "aggregate by", "join tables".
+
+## sas-read-and-score
+**Purpose:** Guide the full read → score workflow in SAS Viya: reading records from a table and then scoring them with a MAS model.
+
+**Use when:** User wants to score records from a table, run a model against query results, predict outcomes for a set of rows, or any combination of fetching data and scoring it.
+
+**Trigger phrases:** "score these records", "score results of my query", "run the model on this table", "predict for these customers", "fetch and score", "read and score", "score rows from", "run model on table data".
+
+## sas-score-workflow
+**Purpose:** Mandatory routing logic for all scoring requests. Extracts model.type suffix and routes to the correct tool (run-job|run-jobdef|model-score|scr-score|run-program). Handles both MAS models and alternative scoring engines.
+
+**Use when:** User requests scoring with a model name that may require routing to different execution engines.
+
+**Trigger phrases:** "score with model X.job", "score X.jobdef scenario", "score with model X.mas", "score with model X.scr", any request with "score" + model name containing a dot (.) + type suffix.

package/.skills/skills/sas-find-library-smart/SKILL.md

@@ -0,0 +1,154 @@
+---
+name: sas-find-library-smart
+description: >
+  Find a SAS Viya library (libref or caslib) with intelligent server detection. Automatically checks 
+  CAS first, then SAS if not found. Use this skill when the user needs to verify a library exists,
+  before accessing tables within it. Trigger phrases include: "find library", "does library exist",
+  "check if library", "locate library", "is there a library named", "verify library", or any request 
+  to confirm a library's availability across servers.
+---
+
+# Smart Library Lookup (Find Library)
+
+Intelligently locates a SAS Viya library by checking CAS first, then SAS if the library is not found 
+in CAS. Provides the user with clear information about library availability and location.
+
+**If the user specifies the server explicitly** (e.g., "find library Public in cas"):
+- Use the specified server: `server: "cas"` or `server: "sas"`
+- Proceed directly to finding the library
+
+**If the server is NOT specified:**
+1. **First attempt**: Check CAS (`server: "cas"`)
+2. **If not found in CAS**: Check SAS with uppercase library name (`server: "sas"`)
+3. **If not found in either**:
+   - Inform user: *"The library '<lib>' was not found in CAS or SAS servers. Please verify the library name."*
+   - Suggest: *"Would you like to list available libraries?"* (suggest `sas-score-list-libraries`)
+4. **If found**:
+   - Inform user which server contains the library: *"Found library '<lib>' in CAS"* or *"Found library '<lib>' in SAS"*
+   - Offer next steps: *"Would you like to list tables in this library?"* (suggest `sas-score-list-tables`)
+
+---
+
+## Using sas-score-find-library
+
+**When:**
+- User wants to verify a library exists
+- User needs to determine which server contains a library
+- User wants to check library availability before accessing it
+- User wants to explore available libraries (before querying)
+
+**How:**
+```
+sas-score-find-library({
+  name: "libraryname",          // required
+  server: "cas" or "sas"        // optional; determined by server check if not specified
+})
+```
+
+**Rules:**
+- Always determine the correct server first (cas → sas → neither)
+- **For SAS server: always uppercase the library name** (e.g., "public" → "PUBLIC")
+- If library name is missing, ask: *"Which library name would you like to find?"*
+- Return the server where the library was found
+- If not found in either server, clearly inform the user and offer to list available libraries
+- Do not proceed with table access until library existence is confirmed
+
+---
+
+## Smart server detection logic
+
+```
+IF server specified by user
+  → IF server is "sas"
+      → uppercase lib
+  → use that server, call sas-score-find-library
+ELSE
+  → TRY sas-score-find-library(lib, server="cas")
+    IF library found
+      → success, inform user: library found in CAS
+    ELSE
+      → uppercase lib
+      → TRY sas-score-find-library(lib.toUpperCase(), server="sas")
+        IF library found
+          → success, inform user: library found in SAS
+        ELSE
+          → inform user library not found in either server
+          → offer to list available libraries
+```
+
+---
+
+## Common patterns
+
+**Pattern 1 — Find library, server unspecified**
+> "Find library Public"
+
+1. Try CAS: `sas-score-find-library({ name: "Public", server: "cas" })`
+2. If not found, try SAS with uppercase: `sas-score-find-library({ name: "PUBLIC", server: "sas" })`
+3. If found in CAS → *"Found library 'Public' in CAS. Would you like to list tables in it?"*
+4. If found in SAS → *"Found library 'PUBLIC' in SAS. Would you like to list tables in it?"*
+5. If not found → *"The library 'Public' was not found in CAS or SAS. Would you like to list available libraries?"*
+
+**Pattern 2 — Find library with explicit server (CAS)**
+> "Find library MyData in cas"
+
+1. Skip server detection
+2. Call: `sas-score-find-library({ name: "MyData", server: "cas" })`
+3. Result → *"Found library 'MyData' in CAS"* or *"Library 'MyData' not found in CAS"*
+
+**Pattern 3 — Find library with explicit server (SAS)**
+> "Does library SASHELP exist in sas"
+
+1. Skip server detection
+2. Uppercase lib: `sas-score-find-library({ name: "SASHELP", server: "sas" })`
+3. Result → *"Found library 'SASHELP' in SAS"* or *"Library 'SASHELP' not found in SAS"*
+
+**Pattern 4 — Library not found, offer next steps**
+> "Check if library staging exists"
+
+1. Try CAS: `sas-score-find-library({ name: "staging", server: "cas" })` → not found
+2. Try SAS: `sas-score-find-library({ name: "STAGING", server: "sas" })` → not found
+3. Respond:
+   - *"The library 'staging' was not found in CAS or SAS."*
+   - *"Would you like to:"*
+     - *"List all available libraries? (use `sas-score-list-libraries`))"*
+     - *"Check a different library name?"*
+
+**Pattern 5 — Library found, follow-up action**
+> "Verify library samples exists"
+
+1. Try CAS: `sas-score-find-library({ name: "samples", server: "cas" })` → found
+2. Respond:
+   - *"Found library 'samples' in CAS."*
+   - *"Would you like to list tables in this library? (use `sas-score-list-tables`))"*
+
+---
+
+## Output presentation
+
+**When library is found:**
+```
+✓ Found library '<lib>' in <SERVER>
+
+Would you like to:
+• List tables in this library (use sas-list-tables-smart skill)
+• Read data from a specific table (use sas-read-strategy skill)
+```
+
+**When library is not found:**
+```
+✗ Library '<lib>' not found in either CAS or SAS
+
+Suggestions:
+• Check the spelling of the library name
+• List available libraries (use list-libraries tool)
+• Try a different library name
+```
+
+---
+
+## Integration with other skills
+
+- **After finding library → List tables**: Use `sas-list-tables-smart` skill to browse available tables
+- **After finding library → Read data**: Use `sas-read-strategy` skill to retrieve data from tables
+- **Library not found → Explore**: Use `sas-score-list-libraries` tool to see all available libraries

package/.skills/skills/sas-list-tables-smart/SKILL.md

@@ -0,0 +1,127 @@
+---
+name: sas-list-tables-smart
+description: >
+  List all tables in a SAS Viya library with intelligent server detection. When the server is not
+  specified, automatically checks CAS first, then SAS if not found. Informs the user if the library
+  does not exist in either server. Use this skill when the user wants to browse or explore available
+  tables. Trigger phrases include: "list tables in", "show tables in", "what tables are in",
+  "browse tables in", "tables in library", "enumerate tables", or any request to explore data sources.
+---
+
+# Smart Data Access in SAS Library (List, Read, Query)
+
+Intelligently enumerates tables in a SAS Viya library, automatically determining the correct server
+when not explicitly specified.
+
+> **Pre-flight check**: Before listing tables, verify the library exists using the `sas-find-library-smart` skill.
+> This ensures consistent server detection across all data operations.
+
+**If the user specifies the server explicitly** (e.g., "list tables in Public in cas"):
+- Use the specified server: `server: "cas"` or `server: "sas"`
+- Proceed directly to listing tables
+
+**If the server is NOT specified:**
+1. **First attempt**: Check CAS (`server: "cas"`)
+2. **If no tables found in CAS**: Check SAS (`server: "sas"`)
+3. **If no tables found in either**:
+   - Inform user: *"The library '<lib>' was not found in CAS or SAS. Please verify the library name is correct."*
+   - Ask: *"Would you like to list available libraries?"* (suggest `sas-score-list-libraries`)
+
+---
+
+## Using sas-score-list-tables
+
+**When:**
+- User wants to browse all tables in a library
+- User wants to see what data is available
+- User wants to explore library contents before querying
+
+**How:**
+```
+sas-score-list-tables({
+  lib: "libraryname",           // required
+  server: "cas" or "sas",       // required; determined by server check
+  limit: 10,                    // optional; default 10, adjust for pagination
+  start: 1                      // optional; default 1, use for pagination
+})
+```
+
+**Rules:**
+- Always determine the correct server first (cas → sas → neither)
+- **For SAS server: always uppercase the library name** (e.g., "maps" → "MAPS")
+- If library name is missing, ask: *"Which library should I list tables from?"*
+- Default page size is 10; adjust based on user request ("show me all", "25 tables", etc.)
+- If returned table count equals the limit, suggest pagination: *"There may be more tables. Use `start: {next_offset}` to see more."*
+- If no tables are found despite library existing, report: *"No tables found in {lib} on {server} server."*
+- Return table names only; do not fetch table metadata unless explicitly requested
+
+---
+
+## Smart server detection logic
+
+```
+IF server specified by user
+  → IF server is "sas"
+      → uppercase lib
+  → use that server
+ELSE
+  → TRY sas-score-list-tables(lib, server="cas")
+    IF tables found
+      → success, return tables
+    ELSE
+      → uppercase lib
+      → TRY sas-score-list-tables(lib.toUpperCase(), server="sas")
+        IF tables found
+          → success, return tables
+        ELSE
+          → inform user library not found in either server
+```
+
+---
+
+## Common patterns
+
+**Pattern 1 — List tables, server unspecified**
+> "List tables in Public"
+
+1. Try CAS: `sas-score-list-tables({ lib: "Public", server: "cas" })`
+2. If empty, try SAS with uppercase: `sas-score-list-tables({ lib: "PUBLIC", server: "sas" })`
+3. If still empty → inform user
+
+**Pattern 2 — List tables with explicit server (SAS)**
+> "List tables in sashelp in sas"
+
+1. Skip server detection
+2. Call with uppercase lib: `sas-score-list-tables({ lib: "SASHELP", server: "sas" })`
+
+**Pattern 3 — List tables with explicit server (CAS)**
+> "List tables in Public in cas"
+
+1. No uppercase needed for CAS
+2. Call: `sas-score-list-tables({ lib: "Public", server: "cas" })`
+
+**Pattern 4 — Pagination**
+> "Show me 25 tables in Samples, then the next batch"
+
+1. First call: `sas-score-list-tables({ lib: "Samples", limit: 25, start: 1 })`
+2. Next call: `sas-score-list-tables({ lib: "Samples", limit: 25, start: 26 })`
+
+**Pattern 5 — Library not found**
+> "List tables in foo"
+
+1. Try CAS: empty
+2. Try SAS with uppercase: empty
+3. Response: *"The library 'foo' was not found in CAS or SAS. Please verify the library name."*
+
+---
+
+## Error handling
+
+| Scenario | Action |
+|---|---|
+| Library not found in either server | Inform user and ask to verify library name |
+| Empty result on first server | Automatically check second server |
+| User specifies invalid server | Return error; ask user to clarify: `"cas"` or `"sas"` |
+| Missing library name | Ask: *"Which library should I list tables from?"* |
+| Library verification needed | Use `sas-find-library-smart` skill to verify library exists first |
+

package/.skills/skills/sas-read-and-score/SKILL.md

@@ -0,0 +1,111 @@
+---
+name: sas-read-and-score
+description: >
+  Guide the full read → score workflow in SAS Viya: reading records from a table and then scoring
+  them with a MAS model (using sas-score-model-score). Use this skill whenever the user wants to score records
+  from a table, run a model against query results, predict outcomes for a set of rows, or any
+  combination of fetching data and scoring it. Trigger phrases include: "score these records",
+  "score results of my query", "run the model on this table", "predict for these customers",
+  "fetch and score", "read and score", "score rows from", "run model on table data", or any request
+  that combines reading/querying table data with model prediction.
+---
+
+# SAS Read → Score Workflow
+
+Orchestrates the full two-step pattern of reading records from a SAS/CAS table and scoring them
+with a deployed MAS model.
+
+---
+
+## Pre-flight verification
+
+**Before attempting to read or score table data:**
+1. **Verify library exists**: Use `sas-find-library-smart` to check the library in CAS first, then SAS if needed
+2. **Verify table exists**: Use `sas-score-find-table` to confirm the table is in the library
+3. **Confirm server location**: Ensure you know which server (CAS or SAS) contains the data
+
+This ensures consistent behavior with other data access operations.
+
+---
+
+## Workflow overview
+
+The typical flow involves:
+1. **Fetch data** — Identify which table/query will provide input records
+2. **Validate model** — Confirm the model exists and understand its input schema
+3. **Score** — Invoke the model on the fetched records
+4. **Present results** — Merge predictions with original data and display
+
+---
+
+## Scenario: User already has data
+
+If the user provides scenario data directly (e.g., "Score age=45, income=60000 with model X"):
+- Extract the scenario values
+- Validate against model's input schema
+- Invoke scoring
+- Return prediction
+
+---
+
+## Scenario: User wants to score table rows
+
+If the user specifies a table (e.g., "Score all customers in Public.customers with model X"):
+- Fetch raw rows (possibly filtered: "where status='active'")
+- Validate model compatibility with input columns
+- Invoke scoring on each row
+- Merge results with original data
+- Display combined table
+
+---
+
+## Scenario: User wants to score query results
+
+If the user wants to score aggregated/filtered results (e.g., "Score high-value customers (spend > 5000) with model X"):
+- Determine which records meet criteria (aggregation/filtering)
+- Validate model expects these input columns
+- Invoke scoring
+- Merge predictions with summary data
+- Display results
+
+---
+
+## Scenario: User unfamiliar with model
+
+If the user specifies a model name that's new/unknown:
+- Check if model exists
+- Retrieve model schema (inputs, outputs)
+- Show user what inputs the model expects
+- Confirm before proceeding with scoring
+
+---
+
+## Rules
+
+- Always validate table/library existence before attempting to read
+- Always check model exists before invoking `sas-score-model-score`
+- Match table columns to model input variables; warn on mismatch
+- If multiple records: score batch if possible; fall back to row-by-row
+- Merge predictions with original data using row index or key column
+- Present results as table with original columns + new prediction columns
+
+---
+
+## Error handling
+
+| Problem | Action |
+|---|---|
+| Table not found | Ask for correct lib.tablename |
+| Model not found | Inform user; suggest verifying model name |
+| Field/column mismatch | Show mismatch, ask user to confirm or adjust query |
+| Scoring error | Return structured error, suggest checking model inputs |
+| Empty read result | Inform user, ask if they want to adjust the query/filter |
+| Data type mismatch | Warn user about type conversion, proceed or ask for clarification |
+
+---
+
+## Integration with other skills
+
+- **Before this workflow**: Use `sas-find-library-smart` to verify the library exists
+- **For data retrieval**: Use `sas-read-strategy` to choose the right read tool (read-table vs sas-query)
+- **For scoring**: Use `sas-score-workflow` for advanced scoring options beyond MAS models