Explore, create, and troubleshoot Oracle Cloud Infrastructure Internet of Things Platform resources, including domains, digital twin models, adapters, instances, relationships, and device publish flows.
SkillScore78Maintained
Automatic
◆DevOps & SRE pack
Last verified 9/26/2026
What it changes
Passed 18 of 23 test cases with the skill, and 9 of 23 without it.
Without skill39%
With skill78%
Checks it passed that the model alone missed
Specifies the telemetry-template command parameter.
Recommends filtering output by specific active status.
Executes a read-only state query prior to instance creation.
and 11 more in the full report
9 fixed9 passed either way5 still failing0 broke
Pass-rate lift
+39 pp
Tokens
+41%
Agent turns
0%
Response time
-29%
Model gemini-3.6-flashMeasured 9/26/2026v118 of 23 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 9
Prompt
Before distributing our team's OCI IoT automation package publicly, which reference document should be checked to validate package readiness?
What was checked, without and with the skill
Checked
Without skill
With skill
Refers to release-validation.md for final package verification.
Missed
Passed
Requires ensuring all tenant IDs and credentials in examples are redacted.
Missed
Passed
case-20 · gemini-3.6-flash · 9/26/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md95 lines14 filesincludes scripts
OCI IoT Platform
Quick Start
Confirm the user is working with Oracle Cloud Infrastructure Internet of Things Platform.
Ask for the minimum context needed before giving commands:
IOT_DOMAIN_ID when available
OCI_CLI_PROFILE
OCI_CLI_AUTH when the selected profile needs it, such as security_token
OCI_REGION if it cannot be derived from the domain
intended operation: inspect, create, update, delete, or publish test telemetry
Prefer this execution order:
discover the domain and current state
inspect the relevant model, adapter, or twin
check local CLI capability with oci ... --help when using newer filters or gateway/raw-command options
make the smallest required change
verify the result with a fresh read
Default Workflow
Start with read-only OCI CLI discovery.
Use scripts/derive_domain_context.sh when the user only has IOT_DOMAIN_ID.
Use references/platform-surface.md when the task needs orientation on OCI IoT resource families, data flow, connectivity types, or which surface to use.
Use references/cli-workflows.md for control-plane actions:
domains and domain groups
digital twin models
adapters
instances
relationships
work requests
HTTPS publish examples
Use references/mcp-optional-use.md only when an OCI IoT MCP server is already available in the user's environment. Keep CLI as the fallback and never require MCP for public workflows.
Deploy and troubleshoot multihome networking on OCI Kubernetes Engine using existing GVA secondary VNIC node pools, Multus thick plugin, OCI CNI/IPAM, NetworkAttachmentDefinitions, and test pods. Use when the user asks to auto-discover OKE cluster subnets or node pools for multihome, create OKE multihome pod manifests, configure Multus NADs for secondary VNIC interfaces, validate multihomed pod connectivity, inspect OCI CNI IPAM allocation on OKE nodes, or package repeatable OKE GVA multihome de