How do I install the Techtide Oci Certificates Issuer Review skill?

Run npx skillmds@latest add techtideohio/techtide-oci-certificates-issuer-review in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Techtide Oci Certificates Issuer Review safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Techtide Oci Certificates Issuer Review?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Techtide Oci Certificates Issuer Review free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Techtide Oci Certificates Issuer Review?

TechTideOhio (@techtideohio) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Techtide Oci Certificates Issuer Review by techtideohio

Name: Techtide Oci Certificates Issuer Review
Author: TechTideOhio

Techtide Oci Certificates Issuer Review

Use this skill when reviewing OCI Certificates Service issuer configurations for cert-manager on OKE. Trigger on any request to audit OCI CA hierarchy, issuance rules, OKE Workload Identity vs Instance Principal auth, IAM policy scope, OCSP reachability, or certificate version management.

TechTideOhio Updated Sep 17, 2026

File contents

OCI Certificates Issuer Review

Purpose

Review Oracle Cloud Infrastructure (OCI) Certificates Service configurations used as cert-manager issuers on OKE (Oracle Kubernetes Engine). Identify CA hierarchy misconfigurations (root vs subordinate), missing issuance rules, overly broad IAM policies, Instance Principal authentication scope risks, OCSP reachability gaps, and certificate version accumulation. Output severity-labeled findings with evidence and remediation steps.

Lean operating rules

Flag any OCI issuer that references a ROOT CA directly as CRITICAL - only a SUBORDINATE CA should be used for cert-manager issuance. The ROOT CA must be offline (disabled after subordinate creation) or kept entirely out of the Certificates Service.
Check whether OCI issuance rules are configured on the subordinate CA: flag missing validity caps (>90d) and missing key algorithm restrictions (RSA <2048 or EC <P-256) as MEDIUM.
Identify the authentication method used by cert-manager to call OCI APIs: flag Instance Principal auth as HIGH - any pod on the OKE node can call the OCI Certificates API via instance metadata. Correct method is OKE Workload Identity (SA-bound, pod-level).
Review the OCI IAM policy for cert-manager: flag manage certificate-authorities (grants delete/update CA) as HIGH. Minimum required: use certificate-authorities with request.permission='CREATE_CERTIFICATE_REQUEST'.
Check OCSP reachability from OKE worker nodes to ocsp.pki.oraclecloud.com. Flag unreachable OCSP endpoint as MEDIUM (soft-fail revocation = revoked certs accepted by most TLS stacks).
Review certificate version count; flag high version accumulation (> 10 versions per cert) as LOW (storage cost and management overhead).
Label all findings as live evidence, documentation-based, or inference.

References

Load these only when needed:

Workflow and output contract

Response minimum

Severity-labeled findings list (CRITICAL / HIGH / MEDIUM / LOW)
Evidence source for each finding
Specific resource name, CA OCID, or IAM policy statement that caused the finding
Recommended remediation with example OCI CLI command or IAM policy snippet
Overall OCI PKI trust posture verdict

---name: techtide-oci-certificates-issuer-reviewdescription: Use this skill when reviewing OCI Certificates Service issuer configurations for cert-manager on OKE. Trigger on any request to audit OCI CA hierarchy, issuance rules, OKE Workload Identity vs Instance Principal auth, IAM policy scope, OCSP reachability, or certificate version management.---# OCI Certificates Issuer Review## PurposeReview Oracle Cloud Infrastructure (OCI) Certificates Service configurations used as cert-manager issuers on OKE (Oracle Kubernetes Engine). Identify CA hierarchy misconfigurations (root vs subordinate), missing issuance rules, overly broad IAM policies, Instance Principal authentication scope risks, OCSP reachability gaps, and certificate version accumulation. Output severity-labeled findings with evidence and remediation steps.## Lean operating rules- Flag any OCI issuer that references a ROOT CA directly as CRITICAL - only a SUBORDINATE CA should be used for cert-manager issuance. The ROOT CA must be offline (disabled after subordinate creation) or kept entirely out of the Certificates Service.- Check whether OCI issuance rules are configured on the subordinate CA: flag missing validity caps (>90d) and missing key algorithm restrictions (RSA <2048 or EC <P-256) as MEDIUM.- Identify the authentication method used by cert-manager to call OCI APIs: flag Instance Principal auth as HIGH - any pod on the OKE node can call the OCI Certificates API via instance metadata. Correct method is OKE Workload Identity (SA-bound, pod-level).- Review the OCI IAM policy for cert-manager: flag `manage certificate-authorities` (grants delete/update CA) as HIGH. Minimum required: `use certificate-authorities` with `request.permission='CREATE_CERTIFICATE_REQUEST'`.- Check OCSP reachability from OKE worker nodes to `ocsp.pki.oraclecloud.com`. Flag unreachable OCSP endpoint as MEDIUM (soft-fail revocation = revoked certs accepted by most TLS stacks).- Review certificate version count; flag high version accumulation (> 10 versions per cert) as LOW (storage cost and management overhead).- Label all findings as live evidence, documentation-based, or inference.## ReferencesLoad these only when needed:- [Workflow and output contract](references/workflow-and-output.md)## Response minimum- Severity-labeled findings list (CRITICAL / HIGH / MEDIUM / LOW)- Evidence source for each finding- Specific resource name, CA OCID, or IAM policy statement that caused the finding- Recommended remediation with example OCI CLI command or IAM policy snippet- Overall OCI PKI trust posture verdict

Frequently asked questions