oci-functions-troubleshoot

Diagnose OCI Functions setup, control-plane, deployment, invocation, and observability issues using a deterministic triage workflow. Use when asked to classify Fn CLI errors, deploy or invoke failures, OCIR auth and registry issues, app-limit symptoms, logs, tracing, metrics, or limits. Diagnose first, prefer read-only checks, and do not execute fixes unless the user explicitly asks.

Try your first task

Triage an OCI Functions failure

Start a fresh conversation.

Use the oci-functions-troubleshoot skill to diagnose the OCI Functions error and failed command I provide. Return the stage, concrete evidence, most likely cause, confidence, one best read-only confirming check, smallest safe remediation, and follow-up validation. Keep this first pass diagnosis-only.

Required inputs

Exact error text and HTTP status, if present.
The command or action that failed.
Region, compartment/profile, application name, and function name, if known.
Whether the failure occurred locally, during deployment, during invocation, or was discovered through telemetry.

Suggested template by Skill Leaderboard, grounded in the linked source. Task evidence ↗

Inside SKILL.md

167 lines

Section content has not been verified for this skill yet.

Full source remains withheld under the current source-display policy. Read the author’s source ↗