Skip to content

rlaope/oh-my-hermes / .claude/agent-skills/omh-provider-profile-posture

omh-provider-profile-posture

Verified

[omh] Provider credentials without exposure.

Provider Profile Posture

This is an OMH provider-profile-posture workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

Why This Exists

provider-profile-posture exists so a profile's required secret names and capabilities are recorded as present, missing, or unknown without any secret value being read or any provider being called.

Do Not Use When

  • Choosing or adopting a connector; use omh-external-connector-readiness.
  • Listing every tool and credential a workflow needs; use omh-toolbelt-readiness.
  • Connecting a model provider or its login.

Examples

Good example:

  • Prompt: Prepare provider profile posture for this connector using metadata-only secret presence.
  • Expected behavior: Produce prepare_provider_profile_posture with required context, wrapper actions, and not-evidence boundaries.
  • Why: The card records which key names are present, missing, or unknown, and never reads a value.

Bad example:

  • Prompt: Read the secret, validate the credential, call the provider, or create a payment route.
  • Expected behavior: Report the missing observed evidence or authority instead of claiming the external step happened.
  • Why: Prepared OMH guidance is not platform, runtime, connector, file, memory, or delivery evidence.

Completion Checklist

  • Provider ID, profile ID, requested capabilities (chat, embedding, tool_call, image), and secret presence are explicit, and omh ops provider-profile-posture --input <file> made the record from JSON with schema_version provider_profile_posture_input/v1, provider_id, profile_id, requested_capabilities, secret_requirements as {name, present: true|false|"unknown"}, optional host_observations.
  • No secret value, credential validation, provider call, model route, wallet, or payment action is claimed.
  • Any host observation reference remains supplied metadata, not a live connector check.

Recovery Notes

  • If provider ID or profile ID is missing, retain the supplied capability requirements, mark provider_profile_posture/v1 unresolved, and hand back a request for the missing ID without reading any secret.
  • If secret-presence metadata is absent, retain the named provider, profile, and requested capabilities, mark secret presence not_observed, and hand back metadata-only secret requirements plus allowed and prohibited actions.
  • If only a host observation reference is supplied, retain it as metadata, mark provider connectivity not_observed, and hand back provider_profile_posture/v1 without claiming credential validation or making a provider call.

When to Use

Use for provider/profile capability and secret-presence preparation before connector or credential action.

Strong routing signals: `provider-profile-posture`, `provider profile posture`, `provider profile readiness`, `secret presence confirmation`, `connector profile posture`, `공급자 프로필 상태`, `시크릿 존재 확인`, `커넥터 준비 상태`

Catalog Metadata

Category: operations Phase: provider-profile-posture Quality tier: workflow-surface-gated Reasoning demand: light

Quality bar:

  • Name the user-facing workflow objective, required context, next action, and stop condition.
  • Separate prepared guidance from observed platform, runtime, connector, file, memory, or delivery evidence.
  • Expose missing tools, credentials, targets, or observations as user-visible gaps.

Required inputs:

  • user request
  • target context
  • delivery or status expectation
  • known missing evidence

Expected outputs:

  • provider_profile_posture/v1
  • metadata-only secret requirements
  • allowed and prohibited actions

Artifact expectations:

  • provider_profile_posture/v1 metadata-only preparation record

Safety rules:

  • Provider/profile posture is OMH-local preparation metadata; it is not credential validation, provider connectivity, model routing, payment/wallet, or host execution evidence.
  • Do not claim connector, gateway, runtime, file generation, memory mutation, or host automation evidence from prepared guidance.

Runtime Evidence

Use the current host's own tools and subagent/task mechanism when available; otherwise run the same lanes sequentially or name the unavailable capability. A prepared plan, handoff, checklist, or skill installation is not execution, review, CI, merge-readiness, or merge evidence. Record actual tool results, or not_observed / not_available, in the record; never invent dispatch or host accounting. Treat supplied context as advisory, not proof of hidden memory reads or writes. State scope, constraints, verification, and the stop condition before work. Reply in the user's own words and the host's own voice: the host's persona owns reply language, tone, speech level, and sentence endings, progress updates included (where it sets no language, use the one the user wrote in), and OMH shapes structure and content only; OMH's record terms (surface, lane, wrapper, handoff, evidence boundary, not_observed) stay in records and tool calls, never in the sentence the user reads unless they ask about one; and when a real unresolved user decision or a useful briefing discussion remains, offer one specific, content-linked question. Completed work needs no question; omit unrelated non-action footers and generic offers to continue. Supporting paths are relative to this skill directory; sibling skill paths are relative to its parent. Resolve them from the host-provided skill base directory ({baseDir} on hosts that provide it), never a hardcoded install location. A named workflow not installed here is unavailable, not permission to emulate its host-specific capabilities. Verify through the real surface before done.

slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall