Read, create, update or rotate a single secret value held in a secrets-management platform.
Reads, creates, updates, or rotates a secret's value on one of the supported secrets-management
platforms, following that platform's own documented API shape and access-control model
(references/<platform>/procedure.md).
certificate-management. Not for
enabling a secrets engine, creating a vault/Key Vault instance, writing a Conjur policy, or any
other one-time setup that makes a place for a secret to live — that's platform configuration,
not secret retrieval, and is out of scope here.procedure.md for exactly what it supports.There is no single wire-level standard (no RFC) governing secrets-management APIs the way DNS has RFC 1035 — each platform below defines its own request/response shape, so "universal concepts" here are behavioral guarantees observed to hold across all seven, not a shared protocol.
platform argument. If it
isn't one of the seven platforms in references/INDEX.md, stop: this skill doesn't cover it, and
does not improvise a generic procedure for an unsupported platform.references/<platform>/procedure.md and follow it exactly — it holds that platform's
full operational procedure, error handling, patterns, known limitations, tools, and verification
checklist. This file is intentionally just the router; the real steps live per platform because
authentication, addressing, and versioning genuinely differ across all seven (see
references/INDEX.md for why).certificate-management) or any
secrets-engine/vault/mount configuration step — every platform procedure here assumes the target
secret already has a place to be stored (an existing KV mount/path, vault, safe, or resource) and
the caller already has a scoped, authenticated credential for it.references/INDEX.md — a platform not listed
there needs a new references/<platform>/procedure.md before this skill can be used for it.SKILL.md itself should only ever change for two reasons: a bug in the universal concepts/router
logic above, or adding a pointer to a newly-supported platform. Platform-specific procedure
changes — a new error code, a corrected field name, a changed API path — belong in that platform's
own references/<platform>/procedure.md and endpoints.md, never here. If you're about to add
vendor-specific detail to this file, put it in the platform's reference file instead.
Each platform assumes its own authenticated client (a Vault token, a 1Password Connect token, a
Conjur access token, a Privilege Cloud session token, an AWS SigV4-signed client, an Azure AD
OAuth token, or a Secret Server access token) — see references/INDEX.md for which, and that platform's procedure.md for the
specific operations/mechanisms.
references/INDEX.md before proceedingprocedure.md was followed, including its own confirmation gates and
error handling — not a generic/improvised sequence