@opscompass/skills 0.1.0

package/README.md

@@ -0,0 +1,78 @@
+# OpsCompass Skills
+
+`@opscompass/skills` provides portable Skills for working with OpsCompass inventory, configuration, and Oracle licensing evidence. Each Skill includes instructions, references, and compiled Node.js helpers.
+
+## Install
+
+Requires Node.js `>=22.20.0 <25`.
+
+```sh
+npm install @opscompass/skills
+```
+
+The package contains these Skills:
+
+- [Resources](./skills/opscompass-resources/SKILL.md): discover resources and retrieve inventory and configuration evidence.
+- [Oracle Licensing](./skills/opscompass-oracle-licensing/SKILL.md): organize Oracle licensing assessments using workload, infrastructure, and entitlement evidence.
+
+Read the selected Skill's `SKILL.md` before use. To use a Skill with an agent, follow that agent's supported Skill installation or loading procedure and select the corresponding directory under `node_modules/@opscompass/skills/skills/`. Installing the npm package alone does not register Skills with an agent.
+
+## Package layout and exported paths
+
+```text
+@opscompass/skills/
+  README.md
+  package.json
+  manifest.json
+  skills/
+    opscompass-resources/
+    opscompass-oracle-licensing/
+```
+
+The package exports `@opscompass/skills/manifest.json` and paths beneath `@opscompass/skills/skills/*`. The manifest identifies the included Skills, their versions, runtime requirements, and packaged entry points.
+
+For an ESM application integrating the tool modules:
+
+```js
+import manifest from "@opscompass/skills/manifest.json" with { type: "json" };
+import { tools as resourceTools } from "@opscompass/skills/skills/opscompass-resources/scripts/tools.js";
+import { tools as oracleTools } from "@opscompass/skills/skills/opscompass-oracle-licensing/scripts/tools.js";
+
+console.log(manifest.skills.map((skill) => skill.id));
+console.log([...resourceTools, ...oracleTools].map((tool) => tool.name));
+```
+
+Importing a tool module does not run a live query. Follow the selected Skill's instructions and your host's tool-execution interface when invoking tools.
+
+## OpsCompass CLI and authentication
+
+Live resource queries require a separately installed OpsCompass CLI, an authenticated session in the selected environment, and permission to access the requested company. This package does not install the CLI, create an OpsCompass account, or provide credentials. Use the CLI setup instructions supplied for your OpsCompass environment.
+
+Use the `opscompass` CLI for standalone helpers. Its defaults and authentication state are stored under `~/.opscompass`. When you need to sign in, run `opscompass login`; use `opscompass login --use-device-code` for device-code authentication:
+
+```sh
+opscompass login
+opscompass defaults list-defaults
+```
+
+Keep login, defaults inspection, and helper execution in the same environment. `--company` selects company scope, not an environment. An explicit company takes precedence over that environment's defaults; credentials and defaults must not be borrowed from another environment.
+
+From the project where this package is installed, this command **previews** a production resource query without executing it. Replace `YOUR_COMPANY` with your company identifier:
+
+```sh
+node node_modules/@opscompass/skills/skills/opscompass-resources/scripts/build_resources_command.js --cli opscompass --company YOUR_COMPANY --param resource-types=databases/oracle
+```
+
+This command **executes** the resource/configuration workflow using the same selected environment:
+
+```sh
+node node_modules/@opscompass/skills/skills/opscompass-resources/scripts/list_and_fetch_latest_configs.js --cli opscompass --company YOUR_COMPANY --param resource-types=databases/oracle --max-resources 25
+```
+
+Hosts that supply an OpsCompass CLI context control the executable, environment, and session home. In that case, use the host's approved tools and authentication guidance rather than assuming a global CLI or production session. Standalone helpers do not require a host integration. See the [Resources Skill](./skills/opscompass-resources/SKILL.md) for custom executable overrides and additional command guidance.
+
+Report query errors as errors, not as an empty inventory. Authentication failures, missing scope, authorization denial, and network failures require different remedies; do not switch environments to work around a failure.
+
+## Oracle licensing evidence
+
+The Oracle Licensing Skill's included entitlement fixtures and `fake_entitlements_api.js` helper are synthetic examples for local testing. They do not query a live entitlement service, establish license ownership, or prove compliance. Use real customer-provided entitlement evidence for an assessment, and identify missing evidence explicitly. Follow the [Oracle Licensing Skill](./skills/opscompass-oracle-licensing/SKILL.md) for the assessment workflow.

package/manifest.json

@@ -0,0 +1,35 @@
+{
+  "schemaVersion": 1,
+  "scope": "public",
+  "name": "@opscompass/skills",
+  "version": "0.1.0",
+  "source": {
+    "repository": "https://gitlab.com/opscompass-hob/opscompass-ai/opscompassai.git",
+    "revision": "3a8fb700e740024080bfb4d2863784cca0254581",
+    "dirty": false
+  },
+  "skills": [
+    {
+      "id": "opscompass-resources",
+      "visibility": "public",
+      "version": "1.0.0",
+      "sourcePath": "skills/resources/opscompass-resources",
+      "root": "skills/opscompass-resources",
+      "toolModule": "skills/opscompass-resources/scripts/tools.js",
+      "requiredCli": ">=1.3.500 <2",
+      "requiredHarness": ">=0.1.0 <1",
+      "requiredNode": ">=22 <25"
+    },
+    {
+      "id": "opscompass-oracle-licensing",
+      "visibility": "public",
+      "version": "1.0.0",
+      "sourcePath": "skills/licensing/opscompass-oracle-licensing",
+      "root": "skills/opscompass-oracle-licensing",
+      "toolModule": "skills/opscompass-oracle-licensing/scripts/tools.js",
+      "requiredCli": ">=1.3.500 <2",
+      "requiredHarness": ">=0.1.0 <1",
+      "requiredNode": ">=22 <25"
+    }
+  ]
+}

package/package.json

@@ -0,0 +1,23 @@
+{
+  "name": "@opscompass/skills",
+  "version": "0.1.0",
+  "description": "Public OpsCompass Skills with portable compiled tools and runtime assets",
+  "license": "UNLICENSED",
+  "type": "module",
+  "engines": {
+    "node": ">=22.20.0 <25"
+  },
+  "files": [
+    "README.md",
+    "manifest.json",
+    "skills"
+  ],
+  "exports": {
+    "./manifest.json": "./manifest.json",
+    "./skills/*": "./skills/*"
+  },
+  "publishConfig": {
+    "access": "public",
+    "registry": "https://registry.npmjs.org/"
+  }
+}

package/skills/opscompass-oracle-licensing/.opscompass-runtime/tools/cli-entrypoint.js

@@ -0,0 +1,15 @@
+import { realpathSync, statSync } from "node:fs";
+import { fileURLToPath } from "node:url";
+export function isMainModule(moduleUrl) {
+    const entryPoint = process.argv[1];
+    if (!entryPoint)
+        return false;
+    try {
+        const entryPath = realpathSync.native(entryPoint);
+        return (entryPath === realpathSync.native(fileURLToPath(moduleUrl)) &&
+            statSync(entryPath).isFile());
+    }
+    catch {
+        return false;
+    }
+}

package/skills/opscompass-oracle-licensing/SKILL.md

@@ -0,0 +1,211 @@
+---
+name: opscompass-oracle-licensing
+description: Perform Oracle Optimized License Assessments using OpsCompass workload, configuration, compliance, entitlement, and infrastructure evidence. Use when users explicitly ask for an Oracle License Assessment, OLA, Oracle licensing report, entitlement-aware Oracle license analysis, Oracle licensing posture, or current-state versus AWS target-state Oracle licensing optimization. Use for AWS Oracle migration/license planning across Amazon RDS for Oracle and Oracle on Amazon EC2, including workloads currently hosted on VMware, Nutanix, Oracle Cloud, AWS, Azure, GCP, or other platforms. Prefer the general OpsCompass resources workflow when the task is only exploratory Oracle inventory, latest configuration, compliance, or hosting analysis without an OLA/license-assessment outcome.
+---
+
+# OpsCompass Oracle Licensing
+
+## Purpose
+
+Use this skill for Oracle Optimized License Assessment work. In this skill, OLA means Optimized License Assessment.
+
+The goal is to combine OpsCompass evidence, entitlement evidence, current hosting/core exposure, and AWS target-state assumptions to produce practical Oracle licensing findings and AWS optimization recommendations.
+
+Strong activation signals:
+- `/ola`
+- "OLA"
+- "Oracle License Assessment"
+- "Oracle licensing assessment"
+- "Oracle licensing report"
+- "entitlement-aware Oracle license analysis"
+- "optimize Oracle licensing for AWS"
+- "optimize Oracle licensing for RDS"
+- "compare Oracle on RDS and EC2"
+
+Use the general OpsCompass resources skill instead when the user only wants inventory, latest configuration, compliance details, or hosting correlation without an entitlement-aware assessment or AWS optimization outcome.
+
+Read [references/evidence-model.md](references/evidence-model.md) for detailed evidence categories.
+Read [references/report-structure.md](references/report-structure.md) when producing a written OLA-style report.
+
+## Critical Rules
+
+- This is a public catalog Skill at `skills/licensing/opscompass-oracle-licensing`; its licensing category does not make it internal. It runs without Studio, Electron, or a harness package. A host-supplied CLI context is optional integration, not a standalone prerequisite.
+- Entitlement truth comes from explicit user-provided entitlement records and evidence from sources the user authorizes for this assessment. Do not infer license ownership, quantity, contractual terms, or a definitive compliance position from usage signals alone. Static fixtures and example ids are illustrative, never customer entitlement evidence.
+
+- Evaluate both Amazon RDS for Oracle and Oracle on Amazon EC2 by default for AWS optimization unless the user explicitly scopes to one target or excludes one target.
+- Respect explicit scope such as "RDS only", "exclude EC2", "EC2 only", or "exclude RDS", and state the exclusion in the assessment.
+- Treat Oracle compliance as Oracle license compliance unless the user clearly asks for something else.
+- Treat Oracle compliance findings and Oracle latest-configuration feature signals as licensed feature, option, pack, or parameter usage evidence.
+- Do not say per-database Oracle feature usage is unavailable until both `get-compliance --status open` and `get-latest-configuration` have been checked for the database.
+- Do not conclude Oracle license risk from database configuration alone when hosting and host/core evidence can be obtained.
+- Current host hardware/core exposure is required evidence for strong OLA conclusions when Oracle runs on VMware, Nutanix, Oracle Cloud, EC2, or another infrastructure platform where host/core exposure affects licensing.
+- Surface Limited Use restrictions explicitly.
+- If entitlement, hosting, host hardware, compute, or target-state evidence is missing, label the conclusion partial and name the missing evidence.
+
+## AWS Target Rules
+
+- Prefer memory-optimized AWS shape candidates for Oracle when supported by evidence. R Series, X1, and Z1 instance families are common Oracle-friendly candidates, but validate platform availability, workload requirements, entitlement terms, tenancy, architecture, and cost.
+- Include EC2 Dedicated Hosts as a licensing-relevant EC2 option when EC2 is in scope. Dedicated Hosts can be licensing friendly because they may provide clearer host-level control and visibility, but they are not automatically optimal.
+- Validate Dedicated Host recommendations against entitlement terms, current and target core exposure, workload consolidation, HA/DR architecture, operational requirements, and cost.
+- Do not recommend Oracle Standard Edition when RAC usage is present unless the assessment explicitly assumes RAC removal. Oracle RAC is not included in Oracle SE.
+- Do not recommend Amazon RDS for Oracle for workloads that must retain RAC. Oracle RAC is not supported on RDS; RAC workloads must either move off RAC or redesign HA for RDS, or target EC2 to retain RAC.
+- Do not recommend Oracle Standard Edition when Oracle Partitioning usage is present unless the assessment explicitly assumes Partitioning removal. Oracle Partitioning requires Enterprise Edition.
+
+## Evidence Workflow
+
+1. Confirm assessment scope.
+Determine whether the user wants current-state assessment, AWS target-state planning, current-versus-target comparison, estate-wide review, a workload subset, RDS-only, EC2-only, both RDS and EC2, or an explicit exclusion.
+
+2. Gather Oracle workloads.
+Use the OpsCompass resources workflow to list `databases/oracle` resources in scope.
+Resolve company scope through the resources workflow. Prefer explicit `--company`; when absent, use the approved defaults tool or the selected CLI's `defaults list-defaults` to inspect `<selected-home>/defaults.json`, then include the resolved `--company` in every resources command. Never fall back to another environment's defaults or credentials.
+Use date-bounded inventory for sprawl, recently created databases, or defined assessment periods.
+
+3. Gather Oracle workload evidence.
+For each Oracle workload in scope, collect:
+- `get-latest-configuration`
+- `get-compliance --status open`
+- version and edition
+- feature, option, pack, and parameter usage signals
+- RAC or cluster indicators
+- Partitioning indicators
+
+In Oracle latest configuration, inspect:
+- `document.version`
+- `document.edition`
+- `document.productUsageConcerns`
+- `document.parameters` entries where `isConcerning` is `true`
+
+Treat non-empty `document.productUsageConcerns` as per-database licensed feature/option usage concern evidence.
+Treat concerning parameters as license-relevant evidence. Example: `CONTROL_MANAGEMENT_PACK_ACCESS=DIAGNOSTIC+TUNING` indicates Diagnostic Pack and Tuning Pack exposure.
+
+4. Gather hosting and compute evidence.
+Correlate Oracle workloads to the infrastructure they run on.
+For VMware and Nutanix, establish:
+- database workload -> VM
+- VM -> host
+- host -> cluster or broader platform context
+- host latest configuration -> CPU/core hardware evidence
+
+Use the resources workflow to fetch latest configuration for the infrastructure hosts supporting Oracle workloads, not just the Oracle database resources.
+
+5. Gather entitlement evidence.
+Review available entitlement evidence for:
+- license type and quantity
+- Limited Use constraints
+- assigned versus unassigned position
+- applicability to workloads in scope
+- missing or ambiguous entitlement records
+
+Only for illustrative local testing, not for a customer assessment, installed Skill fixture responses can be generated with:
+- `node scripts/fake_entitlements_api.js deployment-details`
+- `node scripts/fake_entitlements_api.js license-usage-map`
+- `node scripts/fake_entitlements_api.js overall-compliance`
+
+Those commands read static payloads from `api/entitlement-deployment/`, `api/entitlement-usage/`, and `api/entitlement-compliance/`. They do not query a live entitlement service and must never fill missing customer evidence or establish license ownership/compliance. From the Skills source repository root after building, use `.compiled/skills/licensing/opscompass-oracle-licensing/scripts/fake_entitlements_api.js` instead of the installed `scripts/` path.
+
+6. Analyze current-state exposure.
+Assess:
+- editions and versions in use
+- licensed features, options, packs, and concerning parameters in use
+- RAC usage and whether it affects edition or AWS target feasibility
+- Partitioning usage and whether it requires Enterprise Edition
+- where each workload is hosted today
+- supporting VM, host, and cluster context
+- current core/vCPU or host hardware exposure
+- likely deficiencies, over-allocation, Limited Use conflicts, and unclear cases
+
+7. Analyze AWS target-state options.
+For AWS planning, compare in-scope target options:
+- Amazon RDS for Oracle
+- Oracle on Amazon EC2
+- EC2 Dedicated Hosts when EC2 is in scope
+
+For each option, assess:
+- whether it increases or reduces license risk
+- shape, sizing, edition, tenancy, and architecture implications
+- memory-optimized candidate fit
+- whether RAC blocks RDS unless RAC removal or HA redesign is assumed
+- whether RAC retention requires EC2
+- whether Partitioning blocks Standard Edition
+- how target assumptions compare to current host/core exposure and entitlement posture
+
+8. Produce the assessment.
+Summarize findings, risks, evidence, assumptions, gaps, and recommendations.
+
+## Resource Collection Guidance
+
+Use the OpsCompass resources workflow to gather evidence. In embedded use, prefer approved resource tools and `opscompass_resources_defaults` with the host's authoritative `OpscompassCliContext` (`cliEntryPoint`, `cliCommand`, `opscompassHome`), which wins over ambient settings. Do not assume `opscompass` exists on global `PATH`, production login, or `~/.opscompass`.
+
+Standalone resource helpers `build_resources_command.js` and `list_and_fetch_latest_configs.js` in the Resources Skill accept `--cli opscompass|opscompassdev|opscompassdemo`. These select respectively `~/.opscompass`, `~/.opscompassdev`, and `~/.opscompassdemo`, with production the default. Pure summarizers process supplied JSON and do not accept `--cli`. Keep the selection consistent for defaults, resource queries, command previews, and login/setup guidance. A company name does not select an environment.
+
+`OPSCOMPASS_CLI_ENTRYPOINT` may override the standalone executable. A recognized bare command selects its matching identity/home when `--cli` is absent. An arbitrary executable path retains production identity unless paired with explicit `--cli`; its filename does not identify an environment. Explicit `--cli` wins over conflicting recognized ambient commands, while a custom executable path can pair with that explicit identity. Follow the installed Resources Skill's `SKILL.md` for command-builder examples; those helpers belong to that skill, not this one.
+
+Use the selected CLI's `defaults list-defaults` only to inspect defaults, for example `opscompassdev defaults list-defaults` for dev; use interactive `data-gathering setup` or direct defaults setters only when the user explicitly asks to configure/change them. Standalone instructions and helpers do not require an embedding host.
+
+Builder output and `execute: false` tool results are previews, not retrieved evidence. Obtain actual execution output before claiming a query ran or evidence was collected. Report the real failure if retrieval fails; distinguish authentication from missing scope/defaults, authorization denial, invalid arguments, and service/network errors. Recommend the selected environment's login only when authentication evidence supports it, never automatically for every query failure.
+
+Prefer:
+- Oracle resource inventory for workload discovery
+- Oracle `get-latest-configuration` for version, edition, configuration, product usage concerns, and concerning parameters
+- Oracle `get-compliance --status open` for license compliance findings
+- VMware, Nutanix, AWS, Azure, GCP, and Oracle Cloud infrastructure evidence for current-state hosting and compute context when available
+- infrastructure host `get-latest-configuration` for hardware/core evidence
+- date-bounded `resources list` for sprawl or defined assessment periods
+
+For Oracle on VMware or Nutanix, workload-to-infrastructure correlation is mandatory evidence for strong conclusions. If the chain cannot be established, say the Oracle licensing conclusion is partial.
+
+## Output Rules
+
+Lead with licensing risk and business-impacting recommendations, not raw inventory.
+
+Structure the final answer in this order when possible:
+
+1. Assessment summary
+2. Key findings
+3. Oracle workloads in scope
+4. Hosting and compute context
+5. Entitlement comparison
+6. Current-state deficiencies or risks
+7. AWS target-state findings
+8. AWS optimization recommendations
+9. Evidence gaps and assumptions
+
+For each major conclusion, indicate whether it is:
+- directly established from evidence
+- inferred from strong supporting signals
+- partial because key evidence is missing
+
+Prioritize findings in this order:
+- likely Oracle licensing deficiencies
+- Limited Use conflicts
+- feature, option, pack, or parameter usage that may expand license exposure
+- RAC constraints on Standard Edition and RDS feasibility
+- Partitioning constraints on Standard Edition
+- sprawl or excessive footprint
+- hosting or compute risks that affect licensing
+- missing host hardware/core evidence
+- AWS shape, tenancy, and architecture choices that improve or worsen licensing efficiency
+- evidence gaps that block a definitive conclusion
+
+When the assessment is incomplete, explicitly name missing evidence, such as:
+- entitlement records
+- VM-to-host mapping
+- host hardware/core evidence
+- AWS target-state sizing assumptions
+- RDS shape and architecture assumptions, if RDS is in scope
+- EC2 shape, tenancy, Dedicated Host, and architecture assumptions, if EC2 is in scope
+
+## Example Requests
+
+- "/ola"
+- "/ola assess these Oracle databases for licensing risk"
+- "Do an OLA for this environment."
+- "Optimize my Oracle licensing for AWS."
+- "Optimize my Oracle licensing for Amazon RDS."
+- "Compare RDS and EC2 for my Oracle migration."
+- "I am migrating Oracle from Nutanix to AWS. Give me an OLA."
+- "I am considering Oracle on EC2 Dedicated Hosts. Assess whether that is license-efficient."
+- "Compare current Oracle core exposure to the planned AWS environment."
+- "Develop an AWS Oracle license plan and identify deficiencies."
+- "Produce an Oracle licensing report with findings and recommendations."

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

@@ -0,0 +1,189 @@
+[
+  {
+    "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

@@ -0,0 +1,26 @@
+[
+  {"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"}
+]