@opscompass/skills 0.1.0 → 0.2.0

package/skills/opscompass-resources/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: opscompass-resources
-description: Analyze Oracle and SQL Server workloads across cloud and on-prem infrastructure using `opscompass resources list` plus list-follow-up actions `get-latest-configuration` and `get-compliance`. Use when users need to identify licensing risk, sprawl, misconfiguration, and workload hosting context for Oracle, SQL Server, Azure SQL, AWS RDS, AWS EC2, VMware vCenter, or Nutanix resources.
+description: Analyze Oracle and SQL Server workloads across cloud and on-prem infrastructure using `opscompass resources list` plus list-follow-up actions `get-latest-configuration`, `get-compliance`, and read-only `get-drift`. Use when users need to identify licensing risk, sprawl, misconfiguration, drift, and workload hosting context for Oracle, SQL Server, Azure SQL, AWS RDS, AWS EC2, VMware vCenter, or Nutanix resources.
 ---
 
 # OpsCompass Resources
@@ -10,24 +10,29 @@ description: Analyze Oracle and SQL Server workloads across cloud and on-prem in
 ## Overview
 
 Use this skill for a narrow workflow centered on Oracle and SQL Server risk analysis across cloud and on-prem infrastructure:
+
 - `opscompass resources list` to find matching resources
 - `opscompass resources get-latest-configuration` to inspect full configuration for resource `--id` values from the list results
 - `opscompass resources get-compliance` to inspect compliance findings for resource `--id` values from the list results (with `--status`) when that resource type actually has compliance coverage
+- `opscompass resources get-drift` to inspect drift/change records for resource `--id` values from the list results (with optional `--status`, `--concern`, and `--type` filters)
 
 Translate user intent into exact commands, run them, and return concise risk-oriented summaries.
 
 This skill is primarily for:
+
 - Oracle license risk analysis
 - SQL Server and Oracle sprawl analysis
 - tracing workloads to AWS, Azure, VMware, or Nutanix infrastructure
 - identifying misconfiguration and placement context from latest configuration data
 
 For Oracle licensing and sprawl work, date-bounded inventory is a standard workflow. The model should remember it can start with `resources list` filtered by:
+
 - `--resource-creation-date-beginning` for "created on or after" questions
 - `--resource-creation-date-end` for "created before" questions
 - both flags together for date-range questions
 
 For Oracle specifically, licensing risk is a workload-plus-infrastructure problem, not just a database-config problem. The answer is stronger when it establishes:
+
 - the Oracle workload identity
 - where it is hosted
 - the underlying compute or core exposure
@@ -52,9 +57,10 @@ Standalone dev defaults inspection: `opscompassdev defaults list-defaults`. For
 3. If filtering is needed, add only the `list` filters needed (start minimal, then refine).
 4. Build and run `opscompass resources list`.
 5. Read the list output and collect the numeric resource `id` values.
-6. Iterate the ids needed for the user's objective and run one or both follow-up actions:
+6. Iterate the ids needed for the user's objective and run relevant follow-up actions:
    - `opscompass resources get-latest-configuration --company ... --id ...`
    - `opscompass resources get-compliance --company ... --id ... --status ...`
+   - `opscompass resources get-drift --company ... --id ... --status new`
 7. When the question is about Oracle license risk, SQL Server/Oracle sprawl, or hosting context, continue correlating the workload to infrastructure rather than stopping at the workload resource alone.
 8. Summarize the result(s) and include the exact command(s).
 
@@ -70,29 +76,33 @@ When the user says `Oracle` in this skill, interpret it as Oracle database workl
 
 ## Filter Selection
 
-Use `references/resources-commands.md` for the supported `list` filters and the `get-latest-configuration` follow-up action.
+Use `references/resources-commands.md` for the supported `list` filters and follow-up actions.
 Use `scripts/build_resources_command.js` to generate valid commands for:
+
 - `list`
 - `get-latest-configuration` (by numeric `--id`)
 - `get-compliance` (by numeric `--id` plus `--status`)
-When using `scripts/build_resources_command.js` for compliance, pass the compliance status as `--param status=...` to the builder. The final printed `opscompass resources get-compliance ...` command will use `--status ...`.
-In embedded use, use the approved `opscompass_resources_defaults` tool to inspect defaults or preview requested setup/set commands with `dryRun: true`; only execute defaults changes when the user asks.
-Use `scripts/summarize_resources_list.js` to summarize large `resources list` JSON output.
-Use `scripts/summarize_latest_configuration.js` to summarize one or many `get-latest-configuration` JSON results into model-friendly summaries across resource types.
-Use `scripts/list_and_fetch_latest_configs.js` to automate the full paired workflow (`list` -> iterate ids -> `get-latest-configuration` and/or `get-compliance` -> summary) when the user wants details for many resources.
-When `scripts/list_and_fetch_latest_configs.js` collects mixed Oracle plus Nutanix or VMware VM configurations, it will also emit the Oracle workload to platform vCPU summary automatically.
+- `get-drift` (by numeric `--id` plus optional `--status`, `--concern`, and `--type`)
+  When using `scripts/build_resources_command.js` for compliance or drift, pass follow-up filters as `--param key=value`. The final printed commands use native flags such as `--status ...`, `--concern ...`, and `--type ...`.
+  In embedded use, use the approved `opscompass_resources_defaults` tool to inspect defaults or preview requested setup/set commands with `dryRun: true`; only execute defaults changes when the user asks.
+  Use `scripts/summarize_resources_list.js` to summarize large `resources list` JSON output.
+  Use `scripts/summarize_latest_configuration.js` to summarize one or many `get-latest-configuration` JSON results into model-friendly summaries across resource types.
+  Use `scripts/list_and_fetch_latest_configs.js` to automate the full paired workflow (`list` -> iterate ids -> `get-latest-configuration` and/or `get-compliance` -> summary) when the user wants details for many resources.
+  When `scripts/list_and_fetch_latest_configs.js` collects mixed Oracle plus Nutanix or VMware VM configurations, it will also emit the Oracle workload to platform vCPU summary automatically.
 
 Prefer tools/scripts this way:
+
 - embedded host with approved resource/default tools -> use those tools with the host context rather than substituting standalone shell commands
 - standalone, one or a few resources -> `scripts/build_resources_command.js` plus actual execution of the generated command
 - standalone, many matching resources -> `scripts/list_and_fetch_latest_configs.js`
 - many raw list rows already collected -> `scripts/summarize_resources_list.js`
 - many config payloads already collected -> `scripts/summarize_latest_configuration.js`
 
-Important: in this skill, `get-latest-configuration` and `get-compliance` are follow-up actions after `list`.
+Important: in this skill, `get-latest-configuration`, `get-compliance`, and `get-drift` are follow-up actions after `list`.
 The `id` for follow-up actions should come from the `list` results in the same workflow.
-Use the numeric OpsCompass resource `--id` for follow-up actions. Do not use `--resource-id` or `--resource-ids` for `get-latest-configuration` or `get-compliance`; those represent cloud platform resource identifiers such as ARNs or Azure resource ids and are not the same thing.
+Use the numeric OpsCompass resource `--id` for follow-up actions. Do not use `--resource-id` or `--resource-ids` for `get-latest-configuration`, `get-compliance`, or `get-drift`; those represent cloud platform resource identifiers such as ARNs or Azure resource ids and are not the same thing.
 Do not use `opscompass resources show` in this skill.
+For drift workflows, start with `resources list --unacknowledged-changes true`, page with `--skip` when needed, then inspect selected resources with `get-drift --status new` or another user-requested status. The CLI supports resource-scoped drift retrieval with statuses `new`, `inprogress`, `acknowledged`, and `resolved`, but it does not expose a company-wide drift listing, created/deleted drift classification, deleted-resource enumeration, or any action to acknowledge, resolve, or clear drift from the Dashboard.
 For Oracle resources, version/edition are available in `get-latest-configuration` output under `document.version` and `document.edition`.
 If the user asks "Do I have any Oracle?" or "Show me my Oracle," default to `--resource-types databases/oracle`.
 For Oracle resources, `get-compliance` should usually be interpreted as Oracle license compliance rather than generic infrastructure/security compliance.
@@ -111,6 +121,7 @@ For Nutanix vCPU mapping, inspect `document.numSockets`, `document.numCoresPerSo
 Naming conventions can provide strong supporting evidence for correlating Oracle or SQL Server workloads to Nutanix infrastructure when they align, but naming overlap is not required and its absence should not be treated as evidence that no relationship exists.
 
 For `--resource-types`, this skill is intentionally limited to these OpsCompass-formatted values:
+
 - `AWS::EC2::Instance`
 - `Microsoft.Sql/servers`
 - `AWS::RDS::DBInstance`
@@ -130,6 +141,7 @@ For `--resource-types`, this skill is intentionally limited to these OpsCompass-
 - `vcenter/virtualMachine`
 
 Common user intents this skill should handle:
+
 - "What Oracle licensing risk do I have?" -> treat as Oracle workload plus infrastructure analysis; use Oracle compliance/config plus hosting context
 - "Which Oracle databases were created on or after X?" -> use `resources list` with `--resource-creation-date-beginning`, usually together with `--resource-types databases/oracle`
 - "Which Oracle databases were created between X and Y?" -> use `resources list` with both `--resource-creation-date-beginning` and `--resource-creation-date-end`, usually together with `--resource-types databases/oracle`
@@ -147,6 +159,8 @@ Common user intents this skill should handle:
 - "List resources for account/provider/region" -> `--accounts`, `--cloud-providers`, `--region-ids`
 - "List resources with open compliance issues" -> `--open-compliance-issues true`
 - "List resources with unacknowledged changes" -> `--unacknowledged-changes true`
+- "Show the unacknowledged drift for those resources" -> iterate returned ids with `resources get-drift --status new`
+- "Acknowledge or clear drift from the Dashboard" -> explain that the current CLI exposes read-only drift retrieval but no acknowledge/resolve mutation action
 - "List resources by tag or type" -> `--tags`, `--resource-types` (restricted to the approved set above)
 - "List EC2 instances" -> `resources list ... --resource-types AWS::EC2::Instance`
 - "List Nutanix clusters" -> `resources list ... --resource-types Nutanix/Cluster`
@@ -177,8 +191,10 @@ Common user intents this skill should handle:
   - `opscompass resources list`
   - `opscompass resources get-latest-configuration`
   - `opscompass resources get-compliance`
+  - `opscompass resources get-drift`
 - Choose follow-up actions with this priority:
   - Oracle license/compliance question -> `get-compliance` plus `get-latest-configuration`, then correlate to infrastructure when possible
+  - drift/change question -> `list --unacknowledged-changes true`, then `get-drift --status new` or the requested status for selected resource ids; do not claim the CLI can acknowledge or clear drift
   - Oracle or SQL Server hosting/sprawl/misconfiguration question -> `get-latest-configuration` first, then correlate to infrastructure
   - VMware or Nutanix question -> `get-latest-configuration`, not `get-compliance`
   - generic inventory question -> `list`, then only fetch follow-up data if needed to answer the question
@@ -235,6 +251,8 @@ Common user intents this skill should handle:
 - For Oracle compliance answers, do not lead with "N databases have compliance problems" unless the user asked for counts; lead with the actual license-relevant findings.
 - Do not claim the Opscompass CLI lacks resource-level compliance detail unless an actual `get-compliance` command failed and the failure output supports that conclusion.
 - If `get-compliance` fails, report the real command failure or stderr and state that the detailed compliance answer is partial because retrieval failed.
+- For `get-drift`, report finding count and key fields per change record, including id, status, concern, type, `changeTime`, `changeUrl`, and `userDetected` when present. If the output omits before/after values or created/deleted classification, state that the CLI result does not expose those details.
+- If the user asks to acknowledge, resolve, clear, or remove drift from the Dashboard, state that the current CLI supports resource-scoped `get-drift` retrieval and drift-status filtering only; do not invent a mutation command. If the user asks for dashboard totals such as deleted-resource drift, state that `resources list` only returns current resource rows and the CLI does not expose deleted-resource drift enumeration.
 - For Oracle license-risk answers, explicitly state whether hosting/platform evidence and underlying compute context were established. If not, say the conclusion is partial and identify what infrastructure evidence is still missing.
 - For VMware and Nutanix resource types, do not frame the answer around compliance findings; frame the answer around latest configuration structure, relationships, placement, changes, and supporting infrastructure context.
 - For Oracle workload-to-vCPU mapping answers, report the Oracle workload, matched VM, platform, provisioned vCPU count, and the CPU fields used to derive that count.
@@ -286,6 +304,10 @@ opscompass resources list --company acme --resource-creation-date-beginning "202
 opscompass resources list --company acme --accounts 406219038857 --unacknowledged-changes true
 ```
 
+```bash
+opscompass resources get-drift --company acme --id 9403537 --status new
+```
+
 ```bash
 node scripts/build_resources_command.js --company acme --param resource-creation-date-beginning="2025-01-01 00:00:00.000" --param resource-types=databases/oracle
 ```
@@ -298,6 +320,10 @@ node scripts/build_resources_command.js --action get-latest-configuration --comp
 node scripts/build_resources_command.js --action get-compliance --company opscompassdemo --id 7180543 --param status=open
 ```
 
+```bash
+node scripts/build_resources_command.js --action get-drift --company opscompassdemo --id 9403537 --param status=new --param type=configuration_alert
+```
+
 ```bash
 opscompass resources list --company opscompassdemo --resource-types databases/oracle
 # then use returned ids (for example 9403537) with:

package/skills/opscompass-resources/references/resources-commands.md

@@ -1,14 +1,16 @@
 # OpsCompass Resources `list` + Follow-up Details Reference
 
-Use this file to map workload and infrastructure questions to `opscompass resources list` flags and then inspect selected resources by iterating their ids with follow-up actions like `get-latest-configuration` and `get-compliance`.
+Use this file to map workload and infrastructure questions to `opscompass resources list` flags and then inspect selected resources by iterating their ids with follow-up actions like `get-latest-configuration`, `get-compliance`, and read-only `get-drift`.
 
 This skill is primarily for:
+
 - Oracle license risk analysis
 - Oracle and SQL Server sprawl analysis
 - tracing workloads to AWS, Azure, VMware, or Nutanix infrastructure
 - identifying misconfiguration from latest configuration data
 
 For Oracle licensing and sprawl work, date-bounded inventory is a standard workflow. Use `resources list` with:
+
 - `--resource-creation-date-beginning` for created-on-or-after questions
 - `--resource-creation-date-end` for created-before questions
 - both flags together for date-range questions
@@ -44,6 +46,14 @@ For Oracle licensing and sprawl work, date-bounded inventory is a standard workf
 - Required for this skill: resolved `--company`, numeric `--id` (from `list` output), and `--status`.
 - Builder syntax note: when using `scripts/build_resources_command.js` for compliance, pass `--param status=...` to the builder. The final printed `opscompass resources get-compliance ...` command will use `--status ...`.
 - Allowed `get-compliance --status` values: `open`, `remediated`, `policy-exception`, `mitigation`.
+- `get-drift`: Drift/change records for one resource.
+- Required for this skill: resolved `--company` and numeric `--id` (from `list` output). The CLI rejects company-wide `get-drift` without an id.
+- Optional filters are `--status`, `--concern`, and `--type`.
+- Builder syntax note: when using `scripts/build_resources_command.js` for drift, pass filters as `--param status=new`, `--param concern=...`, or `--param type=configuration_alert`. The final printed `opscompass resources get-drift ...` command will use native flags.
+- Allowed `get-drift --status` values: `new`, `inprogress`, `acknowledged`, `resolved`.
+- Allowed `get-drift --type` values: `configuration_alert`, `security_alert`.
+- For drift summaries, focus on id, status, concern, type, `changeTime`, `changeUrl`, and `userDetected` when present. The current CLI output may not include before/after values or created/deleted classification.
+- The CLI exposes resource-scoped drift retrieval and drift-status filtering, but no company-wide drift listing, deleted-resource drift enumeration, or acknowledge/resolve/clear mutation action in this skill. If a user asks for Dashboard-only deleted-resource totals or clearing drift from the Dashboard, report that limitation instead of inventing a command.
 - For compliance summaries, focus on `checkName`, `checkSeverity`, `errorMessage`, `recommendedAction`, and framework/control names.
 - For Oracle DBs, interpret `get-compliance` results primarily as Oracle license compliance findings unless the user explicitly frames the request differently.
 - For Oracle DB compliance workflows, also inspect `document.version`, `document.edition`, `document.productUsageConcerns`, and concerning `document.parameters` from `get-latest-configuration` so the answer has license context and feature-usage evidence.
@@ -121,6 +131,8 @@ For Oracle licensing and sprawl work, date-bounded inventory is a standard workf
 - "Are these Oracle databases on Nutanix?" -> do not stop at `cloud_provider: "mlss"`; continue workload-to-infrastructure correlation through Nutanix resources
 - "resources with open compliance issues" -> `--open-compliance-issues true`
 - "resources with unacknowledged changes" -> `--unacknowledged-changes true`
+- "show unacknowledged drift details" -> list with `--unacknowledged-changes true`, then iterate selected ids with `get-drift --status new`
+- "acknowledge or clear drift" -> unsupported by the current CLI/skill; only drift retrieval/filtering is available
 
 ## Allowed `--resource-types` in this skill
 
@@ -150,12 +162,14 @@ For Oracle licensing and sprawl work, date-bounded inventory is a standard workf
 - For large result sets, page deliberately and summarize the aggregate result instead of inspecting one oversized raw response.
 - Choose follow-up actions with this priority:
   - Oracle license/compliance question -> `get-compliance` plus `get-latest-configuration`, then correlate to infrastructure when possible
+  - drift/change question -> `list --unacknowledged-changes true`, page with `--skip` as needed, then `get-drift --status new` or the requested status for selected resource ids; report that deleted-resource drift totals may be visible in the Dashboard without being enumerable through this CLI workflow
   - Oracle or SQL Server hosting/sprawl/misconfiguration question -> `get-latest-configuration` first, then correlate to infrastructure
   - VMware or Nutanix question -> `get-latest-configuration`, not `get-compliance`
   - generic inventory question -> `list`, then only fetch follow-up data if needed
 - For Oracle licensing or sprawl questions scoped to time, start with a date-bounded `resources list` rather than a broad list.
 - When the user wants full details, pick a resource `id` from the list output and run `get-latest-configuration`.
 - When the user wants compliance findings, pick a resource `id` from the list output and run `get-compliance --status ...`.
+- When the user wants drift/change records, pick a resource `id` from the list output and run `get-drift --status ...`; do not claim the CLI can acknowledge or clear the records.
 - If the conversation was previously focused on VMware or Nutanix and the user pivots to Oracle or SQL Server, re-evaluate intent from scratch and default to `databases/oracle` or `databases/mssqlserver` rather than continuing the prior infrastructure framing.
 - For multiple resources, iterate through the list ids and run `get-latest-configuration` per resource.
 - For multiple compliance checks, iterate through list ids and run `get-compliance --status ...` per resource.

package/skills/opscompass-resources/scripts/build-resources-command.tool.js

@@ -10,7 +10,12 @@ export const buildResourcesCommandTool = {
         properties: {
             action: {
                 type: "string",
-                enum: ["list", "get-latest-configuration", "get-compliance"],
+                enum: [
+                    "list",
+                    "get-latest-configuration",
+                    "get-compliance",
+                    "get-drift",
+                ],
             },
             company: { type: "string" },
             id: { type: "string" },

package/skills/opscompass-resources/scripts/build_resources_command.js

@@ -51,6 +51,7 @@ const ALLOWED_ACTIONS = new Set([
     "list",
     "get-latest-configuration",
     "get-compliance",
+    "get-drift",
 ]);
 const ALLOWED_COMPLIANCE_STATUSES = new Set([
     "open",
@@ -58,6 +59,21 @@ const ALLOWED_COMPLIANCE_STATUSES = new Set([
     "policy-exception",
     "mitigation",
 ]);
+const ALLOWED_DRIFT_STATUSES = {
+    new: true,
+    inprogress: true,
+    acknowledged: true,
+    resolved: true,
+};
+const ALLOWED_DRIFT_TYPES = {
+    configuration_alert: true,
+    security_alert: true,
+};
+const ALLOWED_DRIFT_PARAMS = {
+    status: true,
+    concern: true,
+    type: true,
+};
 const sorted = (values) => [...values].sort();
 const shellQuote = (value) => /^[A-Za-z0-9_./:-]+$/.test(value)
     ? value
@@ -121,6 +137,26 @@ export function validateArgs(args, paramMap) {
             throw new Error(`invalid value '${status}' for --param status=... (allowed: ${sorted(ALLOWED_COMPLIANCE_STATUSES).join(", ")}).`);
         return;
     }
+    if (args.action === "get-drift") {
+        if (!args.resourceNumericId)
+            throw new Error("resources get-drift requires --id.");
+        for (const key of mapEntries(paramMap).map(([key]) => key))
+            if (!Object.hasOwn(ALLOWED_DRIFT_PARAMS, key))
+                throw new Error("resources get-drift only supports --param status=..., --param concern=..., and --param type=....");
+        const statuses = mapGet(paramMap, "status") ?? [];
+        if (statuses.length > 1)
+            throw new Error("resources get-drift accepts at most one --param status=...");
+        const status = statuses[0]?.trim();
+        if (status && !Object.hasOwn(ALLOWED_DRIFT_STATUSES, status))
+            throw new Error(`invalid value '${status}' for --param status=... (allowed: ${Object.keys(ALLOWED_DRIFT_STATUSES).sort().join(", ")}).`);
+        const types = mapGet(paramMap, "type") ?? [];
+        if (types.length > 1)
+            throw new Error("resources get-drift accepts at most one --param type=...");
+        const type = types[0]?.trim();
+        if (type && !Object.hasOwn(ALLOWED_DRIFT_TYPES, type))
+            throw new Error(`invalid value '${type}' for --param type=... (allowed: ${Object.keys(ALLOWED_DRIFT_TYPES).sort().join(", ")}).`);
+        return;
+    }
     if (args.resourceNumericId)
         throw new Error("resources list does not support top-level --id.");
     for (const key of mapEntries(paramMap).map(([key]) => key))
@@ -160,9 +196,9 @@ export function buildCommand(args, paramMap, context = resolveCliContext()) {
         "--company",
         args.company,
     ];
-    if (["get-latest-configuration", "get-compliance"].includes(args.action)) {
+    if (["get-latest-configuration", "get-compliance", "get-drift"].includes(args.action)) {
         command.push("--id", args.resourceNumericId);
-        if (args.action === "get-compliance")
+        if (["get-compliance", "get-drift"].includes(args.action))
             for (const [key, values] of mapEntries(paramMap))
                 for (const value of values)
                     command.push(`--${key}`, value);
@@ -205,7 +241,7 @@ function parseArgs(argv) {
             args.param.push(argv[i]);
         }
         else if (flag === "--help" || flag === "-h") {
-            console.log("Build an opscompass resources list/get-latest-configuration/get-compliance command.");
+            console.log("Build an opscompass resources list/get-latest-configuration/get-compliance/get-drift command.");
             process.exit(0);
         }
         else

package/skills/opscompass-resources/scripts/opscompass-resources.tool.js

@@ -4,6 +4,7 @@ const ACTIONS = [
     "resources list",
     "resources get-latest-configuration",
     "resources get-compliance",
+    "resources get-drift",
 ];
 export const opscompassResourcesTool = {
     name: "opscompass_resources",

package/skills/opscompass-oracle-licensing/api/entitlement-compliance/entitlement-compliance.json

@@ -1,189 +0,0 @@
-[
-  {
-    "Product": "Oracle Active Data Guard",
-    "Metric": "Processor",
-    "Limitation": "Full Use",
-    "Limited To": "",
-    "Licensed": 0,
-    "Used": 16,
-    "Available": 0,
-    "Potential risk": "$0.00",
-    "Comments": "(GoldenGate)"
-  },
-  {
-    "Product": "Oracle Advanced Compression",
-    "Metric": "Named User Plus",
-    "Limitation": "Limited Use",
-    "Limited To": "Test / Dev",
-    "Licensed": 400,
-    "Used": 0,
-    "Available": 400,
-    "Potential risk": "$0.00",
-    "Comments": ""
-  },
-  {
-    "Product": "Oracle Advanced Compression",
-    "Metric": "Processor",
-    "Limitation": "Full Use",
-    "Limited To": "",
-    "Licensed": 16,
-    "Used": 16,
-    "Available": 0,
-    "Potential risk": "$0.00",
-    "Comments": ""
-  },
-  {
-    "Product": "Oracle Advanced Security",
-    "Metric": "Processor",
-    "Limitation": "Full Use",
-    "Limited To": "",
-    "Licensed": 16,
-    "Used": 32,
-    "Available": -16,
-    "Potential risk": "$292,800.00",
-    "Comments": ""
-  },
-  {
-    "Product": "Oracle Advanced Security",
-    "Metric": "Named User Plus",
-    "Limitation": "Limited Use",
-    "Limited To": "Test / Dev",
-    "Licensed": 400,
-    "Used": 400,
-    "Available": 0,
-    "Potential risk": "$0.00",
-    "Comments": ""
-  },
-  {
-    "Product": "Oracle Database Enterprise Edition",
-    "Metric": "Named User Plus",
-    "Limitation": "Limited Use",
-    "Limited To": "Test / Dev",
-    "Licensed": 400,
-    "Used": 400,
-    "Available": 0,
-    "Potential risk": "$0.00",
-    "Comments": ""
-  },
-  {
-    "Product": "Oracle Database Enterprise Edition",
-    "Metric": "Processor",
-    "Limitation": "Full Use",
-    "Limited To": "",
-    "Licensed": 16,
-    "Used": 32,
-    "Available": -16,
-    "Potential risk": "$927,200.00",
-    "Comments": ""
-  },
-  {
-    "Product": "Oracle Database Vault",
-    "Metric": "Processor",
-    "Limitation": "Full Use",
-    "Limited To": "",
-    "Licensed": 16,
-    "Used": 32,
-    "Available": -16,
-    "Potential risk": "$224,480.00",
-    "Comments": ""
-  },
-  {
-    "Product": "Oracle Database Vault",
-    "Metric": "Named User Plus",
-    "Limitation": "Limited Use",
-    "Limited To": "Test / Dev",
-    "Licensed": 400,
-    "Used": 400,
-    "Available": 0,
-    "Potential risk": "$0.00",
-    "Comments": ""
-  },
-  {
-    "Product": "Oracle Diagnostics Pack",
-    "Metric": "Named User Plus",
-    "Limitation": "Limited Use",
-    "Limited To": "Test / Dev",
-    "Licensed": 400,
-    "Used": 400,
-    "Available": 0,
-    "Potential risk": "$0.00",
-    "Comments": ""
-  },
-  {
-    "Product": "Oracle Diagnostics Pack",
-    "Metric": "Processor",
-    "Limitation": "Full Use",
-    "Limited To": "",
-    "Licensed": 16,
-    "Used": 16,
-    "Available": 0,
-    "Potential risk": "$0.00",
-    "Comments": ""
-  },
-  {
-    "Product": "Oracle GoldenGate",
-    "Metric": "Named User Plus",
-    "Limitation": "Limited Use",
-    "Limited To": "Test / Dev",
-    "Licensed": 400,
-    "Used": 400,
-    "Available": 0,
-    "Potential risk": "$0.00",
-    "Comments": ""
-  },
-  {
-    "Product": "Oracle GoldenGate",
-    "Metric": "Processor",
-    "Limitation": "Full Use",
-    "Limited To": "",
-    "Licensed": 16,
-    "Used": 16,
-    "Available": 0,
-    "Potential risk": "$0.00",
-    "Comments": ""
-  },
-  {
-    "Product": "Oracle Partitioning",
-    "Metric": "Processor",
-    "Limitation": "Full Use",
-    "Limited To": "",
-    "Licensed": 16,
-    "Used": 16,
-    "Available": 0,
-    "Potential risk": "$0.00",
-    "Comments": ""
-  },
-  {
-    "Product": "Oracle Partitioning",
-    "Metric": "Named User Plus",
-    "Limitation": "Limited Use",
-    "Limited To": "Test / Dev",
-    "Licensed": 400,
-    "Used": 400,
-    "Available": 0,
-    "Potential risk": "$0.00",
-    "Comments": ""
-  },
-  {
-    "Product": "Oracle Real Application Clusters",
-    "Metric": "Named User Plus",
-    "Limitation": "Limited Use",
-    "Limited To": "Test / Dev",
-    "Licensed": 400,
-    "Used": 400,
-    "Available": 0,
-    "Potential risk": "$0.00",
-    "Comments": ""
-  },
-  {
-    "Product": "Oracle Real Application Clusters",
-    "Metric": "Processor",
-    "Limitation": "Full Use",
-    "Limited To": "",
-    "Licensed": 16,
-    "Used": 32,
-    "Available": -16,
-    "Potential risk": "$448,960.00",
-    "Comments": ""
-  }
-]

package/skills/opscompass-oracle-licensing/api/entitlement-deployment/entitlement-deployment

@@ -1,26 +0,0 @@
-[
-  {"Server":"NTX3-HOST06-DC3","VM":"NTX-APPLICATIONPROD-LX02","Instance":"TRKP1","Edition":"Enterprise Edition","Version":"19.0.0.0.0","DB Created":"3/5/25"},
-  {"Server":"NTX5-HOST01-DC1","VM":"NTX-INTERFACEDEV-LX01","Instance":"INVD1","Edition":"Enterprise Edition","Version":"19.0.0.0.0","DB Created":"4/11/25"},
-  {"Server":"NTX5-HOST01-DC1","VM":"NTX-ARRAYDEV-LX01","Instance":"INVQ2","Edition":"Enterprise Edition","Version":"19.0.0.0.0","DB Created":"3/14/25"},
-  {"Server":"NTX5-HOST01-DC1","VM":"NTX-CAPACITORDEV-LX01","Instance":"DWHS01","Edition":"Enterprise Edition","Version":"19.0.0.0.0","DB Created":"4/11/25"},
-  {"Server":"NTX5-HOST01-DC1","VM":"NTX-MONITORDEV-LX01","Instance":"HISTDR2","Edition":"Enterprise Edition","Version":"19.0.0.0.0","DB Created":"5/3/18"},
-  {"Server":"NTX5-HOST01-DC1","VM":"NTX-ALARMDEV-LX02","Instance":"INVT2","Edition":"Enterprise Edition","Version":"19.0.0.0.0","DB Created":"4/9/25"},
-  {"Server":"NTX5-HOST01-DC1","VM":"NTX-CARDDEV-LX01","Instance":"MEND2","Edition":"Enterprise Edition","Version":"19.0.0.0.0","DB Created":"1/1/25"},
-  {"Server":"NTX5-HOST01-DC1","VM":"NTX-DRIVERDEV-LX01","Instance":"HISTQA","Edition":"Enterprise Edition","Version":"19.0.0.0.0","DB Created":"2/26/25"},
-  {"Server":"NTX5-HOST01-DC1","VM":"NTX-CIRCUITDEV-LX01","Instance":"REPD1","Edition":"Enterprise Edition","Version":"19.0.0.0.0","DB Created":"2/24/25"},
-  {"Server":"NTX5-HOST01-DC1","VM":"NTX-BANDWIDTHDEV-LX01","Instance":"RMANCP1","Edition":"Enterprise Edition","Version":"19.0.0.0.0","DB Created":"3/3/25"},
-  {"Server":"NTX5-HOST01-DC1","VM":"NTX-MONITORDEV-LX01","Instance":"TRK2","Edition":"Enterprise Edition","Version":"19.0.0.0.0","DB Created":"2/13/25"},
-  {"Server":"NTX5-HOST01-DC1","VM":"NTX-ALARMDEV-LX02","Instance":"INVT1","Edition":"Enterprise Edition","Version":"19.0.0.0.0","DB Created":"4/9/25"},
-  {"Server":"NTX5-HOST01-DC1","VM":"NTX-MONITORDEV-LX01","Instance":"INVT2","Edition":"Enterprise Edition","Version":"19.0.0.0.0","DB Created":"4/9/25"},
-  {"Server":"NTX5-HOST02-DC1","VM":"NTX-APPLICATIONDEV-LX02","Instance":"DWHS02","Edition":"Enterprise Edition","Version":"19.0.0.0.0","DB Created":"4/11/25"},
-  {"Server":"NTX5-HOST02-DC1","VM":"NTX-PROGRAMDEV-LX02","Instance":"INVD2","Edition":"Enterprise Edition","Version":"19.0.0.0.0","DB Created":"4/11/25"},
-  {"Server":"NTX5-HOST02-DC1","VM":"NTX-FIREWALLDEV-LX02","Instance":"HISTDR1","Edition":"Enterprise Edition","Version":"19.0.0.0.0","DB Created":"5/3/18"},
-  {"Server":"NTX5-HOST02-DC1","VM":"NTX-CAPACITORDEV-LX02","Instance":"INVQ1","Edition":"Enterprise Edition","Version":"19.0.0.0.0","DB Created":"3/14/25"},
-  {"Server":"NTX5-HOST02-DC1","VM":"NTX-ALARMDEV-LX02","Instance":"MEND1","Edition":"Enterprise Edition","Version":"19.0.0.0.0","DB Created":"1/1/25"},
-  {"Server":"NTX5-HOST02-DC1","VM":"NTX-APPLICATIONDEV-LX02","Instance":"RMANCP2","Edition":"Enterprise Edition","Version":"19.0.0.0.0","DB Created":"3/3/25"},
-  {"Server":"NTX5-HOST02-DC1","VM":"NTX-CARDDEV-LX02","Instance":"TRK1","Edition":"Enterprise Edition","Version":"19.0.0.0.0","DB Created":"2/13/25"},
-  {"Server":"NTX5-HOST02-DC1","VM":"NTX-ARRAYDEV-LX02","Instance":"REPD2","Edition":"Enterprise Edition","Version":"19.0.0.0.0","DB Created":"2/23/25"},
-  {"Server":"NTX6-HOST01-DC1","VM":"NTX-FIREWALLPROD-LX01","Instance":"INVP2","Edition":"Enterprise Edition","Version":"19.0.0.0.0","DB Created":"2/2/13"},
-  {"Server":"NTX6-HOST01-DC1","VM":"NTX-PIXELPROD-LX01","Instance":"TRKP2","Edition":"Enterprise Edition","Version":"19.0.0.0.0","DB Created":"3/5/25"},
-  {"Server":"NTX6-HOST02-DC1","VM":"NTX-SYSTEMPROD-LX02","Instance":"INVP1","Edition":"Enterprise Edition","Version":"19.0.0.0.0","DB Created":"2/2/13"}
-]