Skill: ogment-agentic-cli

Owner: asoviche

Summary: Access business integrations (SaaS, APIs, data) securely through Ogment. Use when the user asks to query, create, update, or manage data in external systems...

Tags: latest:1.0.1

Version history:

v1.0.1 | 2026-02-26T20:50:33.927Z | user

Skill updated for the new CLI version v0.5.0

v1.0.0 | 2026-02-11T14:45:50.451Z | user

Ogment 1.0.0 – Initial Release

• Securely access and manage business integrations (SaaS tools, APIs, databases) via the Ogment CLI.
• Easily discover servers and available tools with JSON-based commands.
• Query, create, update, and manage external system data using simple CLI workflows.
• Supports per-tool permissions, human approval flows, and never exposes credentials.
• Clear guidance for installation, login, usage, and common error handling.

Archive index:

Archive v1.0.1: 2 files, 1859 bytes

Files: SKILL.md (3038b), _meta.json (137b)

File v1.0.1:SKILL.md

Ogment CLI Skill

Securely invoke MCP tools via the Ogment CLI. Use for accessing user's connected SaaS tools (Linear, Notion, Gmail, PostHog, etc.) through Ogment's governance layer.

When to Use

• User asks to interact with their connected services (issues, docs, emails, analytics)
• You need to call MCP tools that require auth/credentials
• Discovering what integrations the user has available

Core Workflow

status → catalog → catalog <server> → catalog <server> <tool> → invoke

1. Check connectivity (if issues suspected)

ogment status

Returns auth state, connectivity, and available servers. Check summary.status for quick health.

2. Discover servers

ogment catalog

Returns list of servers with serverId and toolCount. Use serverId in subsequent calls.

3. List tools on a server

ogment catalog <serverId>

Returns all tools with name and description. Scan descriptions to find the right tool.

4. Inspect tool schema

ogment catalog <serverId> <toolName>

Returns inputSchema with properties, types, required fields, and descriptions.

5. Invoke a tool

ogment invoke <serverId>/<toolName> --input '<json>'

Input can be:

• Inline JSON: --input '{"query": "test"}'
• File: --input @path/to/input.json
• Stdin: echo '{}' | ogment invoke ... --input -

Output Format

All commands return structured JSON with ok, data, error, meta, and next_actions fields.

• Check ok first — boolean success indicator
• next_actions — suggested follow-up commands
• error.category — validation, not_found, remote, auth, internal
• error.retryable — whether retry might help

Common Patterns

Find a tool by intent

ogment catalog <serverId> | jq '.data.tools[] | select(.name + .description | test("email"; "i"))'

List issues assigned to user

ogment invoke openclaw/Linear_list_issues --input '{"assignee": "me"}'

Search Notion

ogment invoke openclaw/Notion_notion-search --input '{"query": "quarterly review", "query_type": "internal"}'

Get Gmail messages

ogment invoke openclaw/gmail_listMessages --input '{"q": "is:unread", "maxResults": 10}'

Gotchas & Workarounds

1. Opaque server errors - Re-check schema, verify required fields and types
2. Example placeholders are broken - Ignore exampleInput, construct your own
3. Server/tool IDs are case-sensitive - Use exact casing from catalog
4. Empty strings cause 502s - Validate inputs before calling
5. --quiet suppresses everything - Don't use it
6. No tool search/filter - Pipe to jq and filter locally

Error Recovery

TOOL_NOT_FOUND → Run ogment catalog to rediscover VALIDATION_INVALID_INPUT → Check JSON syntax TRANSPORT_REQUEST_FAILED → Check schema, required fields, types AUTH_INVALID_CREDENTIALS → Run ogment auth login HTTP_502 → Retry after delay

Pre-flight Checklist

Before invoking a tool:

1. Confirmed server exists (catalog)
2. Confirmed tool exists (catalog <server>)
3. Checked required fields in schema
4. Matched types exactly (number vs string)
5. Used exact casing for IDs

File v1.0.1:_meta.json

{ "ownerId": "kn7ay3vv2tg97we8zqr45jg46180zck9", "slug": "ogment-agentic-cli", "version": "1.0.1", "publishedAt": 1772139033927 }

Archive v1.0.0: 2 files, 1852 bytes

Files: SKILL.md (3237b), _meta.json (137b)

File v1.0.0:SKILL.md

---

name: ogment description: Access business integrations (SaaS, APIs, data) securely through Ogment. Use when the user asks to query, create, update, or manage data in external systems like Salesforce, Notion, Slack, databases, or any connected service. metadata: {"openclaw":{"emoji":"🦞","requires":{"bins":["ogment"]},"install":[{"id":"npm","kind":"node","package":"ogment","bins":["ogment"],"label":"Install Ogment CLI (npm)"}]}}

Ogment

Ogment gives you secure access to business integrations — SaaS tools, internal APIs, and data — through a single CLI. Credentials never leave Ogment. You get scoped, revocable tokens with per-tool permissions and human approval flows.

Setup (one-time)

If ogment is not installed or any command fails with "not logged in":

1. Install: npm install -g ogment
2. Ask the user to run ogment login in their terminal (opens browser for OAuth — zero arguments needed)
3. Login is a one-time step. After authenticating, all servers and tools are available automatically.

Commands

Discover servers:

ogment servers --json

Returns all available servers across all organizations.

Inspect a server's tools:

ogment servers <server-path> --json

Returns the full list of tools with names, descriptions, and input schemas.

Call a tool:

ogment call <server-path> <tool-name> '<json-args>'

Returns JSON. Arguments must be a single JSON string. Omit args for tools that take no parameters.

Workflow

Follow these steps in order:

1. Run ogment servers --json to discover available servers
2. Pick the server relevant to the user's request
3. Run ogment servers <path> --json to see that server's tools
4. Call the appropriate tool with ogment call <server> <tool> '<args>'
5. Parse the JSON response and present results to the user
6. If the user needs a different integration, go back to step 1

Examples

# Discover all servers
ogment servers --json

# Inspect tools on a server
ogment servers salesforce --json

# Query data
ogment call salesforce query_accounts '{"limit":5}'
ogment call notion search '{"query":"Q1 roadmap"}'
ogment call data-warehouse run_query '{"sql":"SELECT * FROM orders LIMIT 10"}'

# Create records
ogment call salesforce create_record '{"type":"Contact","fields":{"Name":"Jane Doe","Email":"jane@example.com"}}'

# Health check (no args)
ogment call my-api get__health

Handling Errors

• "not logged in" — ask the user to run ogment login in their terminal
• "server not found" — run ogment servers --json to see available servers
• approval link returned — the tool requires human approval. Show the approval URL to the user and ask them to approve. Then retry the same tool call.
• 401 / authentication error — the token may be expired. Ask the user to run ogment logout then ogment login

Important

• Always use --json when discovering servers and tools
• ogment call returns JSON by default — no --json flag needed
• Arguments to ogment call must be a single JSON string
• Do not store or log tokens — Ogment handles all credentials server-side
• Each tool call is authenticated, permission-checked, and logged by Ogment

File v1.0.0:_meta.json

{ "ownerId": "kn7ay3vv2tg97we8zqr45jg46180zck9", "slug": "ogment-agentic-cli", "version": "1.0.0", "publishedAt": 1770821150451 }