TypingMindTypingMindThe best frontend for AI
Oci Lz Orchestrator Contract Advisor logo

Oci Lz Orchestrator Contract Advisor

Organization
oci-landing-zones
oci-lz-orchestrator-contract-advisor

Use only when verifying or troubleshooting OCI Landing Zone Orchestrator contract/runtime behavior such as rms-facade source settings, dependency and output files, stack sequencing, duplicate top-level configuration collisions, provider or Resource Manager failures, supported root variables, or version drift. Do not use for customer discovery, landing-zone design, config authoring, blueprint selection, or workload-extension generation.

Overview

Publisheroci-landing-zones
Repositoryoci-landing-zone-operating-entities
Skill nameoci-lz-orchestrator-contract-advisor
Stars
67
Forks
35
Bundled files
4
LicenseUPL-1.0
Links
Skill sourceRepositoryHomepage
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 4 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by oci-landing-zones on GitHub. Read the source before you install it.

Installation

Install the Oci Lz Orchestrator Contract Advisor AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/oci-landing-zones/oci-landing-zone-operating-entities/tree/master/.agents/skills/oci-lz-orchestrator-contract-advisor
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/oci-landing-zones/oci-landing-zone-operating-entities.git /tmp/oci-landing-zone-operating-entities
mkdir -p .claude/skills
cp -r /tmp/oci-landing-zone-operating-entities/.agents/skills/oci-lz-orchestrator-contract-advisor .claude/skills/oci-lz-orchestrator-contract-advisor
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Oci Lz Orchestrator Contract Advisor in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Oci Lz Orchestrator Contract Advisor on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Oci Lz Orchestrator Contract Advisor is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

OCI LZ Orchestrator Contract Advisor

Overview

Use this skill for contract/runtime troubleshooting around terraform-oci-modules-orchestrator and OCI Resource Manager rms-facade. It is a verifier, not a builder.

Use the existing repo workflows first when the request is about design or generation:

  • Customer discovery and deployment recommendations: use landing-zone-customer-guidance.
  • Config-mode authoring or review: use landing-zone-config.
  • Extension-specific Blueprint Factory semantics: use the relevant guide under gen/workload-extensions/<extension>/.

Do not use this skill for customer discovery, landing-zone design, config generation, ExaDB-C@C / ExaCC generation, or blueprint selection.

Workflow

  1. Classify the issue as one of: supported root family, dependency input, output file, rms-facade source setting, stack boundary, duplicate top-level config collision, provider/RMS failure, or version drift.
  2. Inspect the active source before answering. Prefer the pinned Orchestrator ref selected by the deployment; use a local checkout only for local configs, local changes, or failing local runs.
  3. Verify exact names from code, not memory: variables.tf, outputs.tf, rms-facade/variables.tf, rms-facade/get_configurations.tf, rms-facade/get_dependencies.tf, and rms-facade/schema.yml.
  4. Keep configuration files, dependency files, output files, and Resource Manager source fields separate in the answer.
  5. Report evidence by level: design coherence, JSON syntax, Orchestrator contract, Terraform validate, Terraform plan, apply/runtime.

References

  • Read references/orchestrator.md for root contract checks, output/dependency names, and version-drift handling.
  • Read references/rms-ui-and-sources.md for Resource Manager source settings and output persistence.
  • Read references/multistack-and-config-collisions.md for multi-stack boundaries and duplicate root-key behavior.

Guardrails

  • Do not invent root families such as native ExaCC or ExaCS families unless the active variables.tf proves they exist.
  • Do not imply duplicate top-level families across config files are deep-merged; verify CLI or rms-facade behavior.
  • Do not present custom manifest/profile files as Orchestrator inputs.
  • Do not recommend public raw URLs as a default deployment source for customer artifacts.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Oci Lz Orchestrator Contract Advisor AI skill do?

Use only when verifying or troubleshooting OCI Landing Zone Orchestrator contract/runtime behavior such as rms-facade source settings, dependency and output files, stack sequencing, duplicate top-level configuration collisions, provider or Resource Manager failures, supported root variables, or version drift. Do not use for customer discovery, landing-zone design, config authoring, blueprint selection, or workload-extension generation.

Why use Oci Lz Orchestrator Contract Advisor on TypingMind?

Because you install it once and use it with any model. Oci Lz Orchestrator Contract Advisor is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Oci Lz Orchestrator Contract Advisor in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/oci-landing-zones/oci-landing-zone-operating-entities/tree/master/.agents/skills/oci-lz-orchestrator-contract-advisor. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Oci Lz Orchestrator Contract Advisor?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Oci Lz Orchestrator Contract Advisor?

As many as you like. As long as a model supports skills, you can use Oci Lz Orchestrator Contract Advisor with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Oci Lz Orchestrator Contract Advisor AI skill free?

Yes. It is published on GitHub by oci-landing-zones under the UPL-1.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
affaan-m logo

Deployment Patterns

affaan-m
CommunityPopular

Flujos de trabajo de despliegue, patrones de pipeline CI/CD, contenedorización Docker, health checks, estrategias de rollback y listas de verificación de preparación para producción de aplicaciones…

39.1K
261.1K
Instructions
View
affaan-m logo

Docker Patterns

affaan-m
CommunityPopular

Patrones de Docker y Docker Compose para desarrollo local, seguridad de contenedores, networking, estrategias de volúmenes y orquestación de múltiples servicios.

39.1K
261.1K
Instructions
View
affaan-m logo

Architecture Decision Records

affaan-m
CommunityPopular

コーディングセッション中にアーキテクチャ決定を構造化ADRとして記録し、自動的に決定の瞬間を検出し、コンテキスト、検討された代替案、根拠を記録します。今後の開発者がコードベースの形成理由を理解するためのADRログを維持します。

39.1K
261.1K
Instructions
View
affaan-m logo

Automation Audit Ops

affaan-m
CommunityPopular

ECC用の証拠ベースの自動化インベントリとオーバーラップ監査ワークフロー。ユーザーがどのジョブ、フック、コネクタ、MCPサーバー、またはラッパーがライブか、壊れているか、冗長であるか、修正前に不足しているかを知りたい場合に使用します。

39.1K
261.1K
Instructions
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇