OKSign

Operate OKSign through your OOMOL-connected account. This skill calls the oksign connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Category: Productivity, Security & Identity. Exposes 5 action(s).

Running an action

Assume the user has already installed the oo CLI, signed in, and connected OKSign. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.

1. Inspect the contract to get the authoritative input/output schema before building a payload:

oo connector schema "oksign" --action "\x3Caction_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "oksign" --action "\x3Caction_name>" --data '\x3Cjson>' --json

• --data takes a JSON object string or @path/to/file.json; omit it to send {}.
• The response is { "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.

Each action below links to a reference file with its purpose and exact commands. Read the linked file, then fetch the live schema with oo connector schema before constructing --data.

Available actions

• get_credits — Get OKSign credits balance, expiry, and account storage details.
• get_document_metadata — Get OKSign metadata v2 for a signed document by signed_docid.
• get_linked_document — Resolve the corresponding source_docid and signed_docid pair for an OKSign document identifier.
• list_active_documents — List active OKSign documents visible in the current account.
• list_users — List the users configured in the current OKSign account.

Safety

• Read actions (get / list / search) are safe to run directly.
• Create, update, send, or post actions change OKSign state — confirm the exact payload and effect with the user before running.
• Delete or remove actions are destructive — always confirm the target and get explicit approval first.

First-time setup

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

• oo: command not found — install the oo CLI (other platforms: \x3Chttps://cli.oomol.com/install-guide.md>):

  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux
  

  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell
  

• Not signed in / authentication error — sign in to your OOMOL account once:

  oo auth login
  

• scope_missing / credential_expired / app_not_ready / app_not_found — OKSign is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:

  https://console.oomol.com/app-connections?provider=oksign
  

• HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources

• OKSign homepage: https://www.oksign.be/en/