← Back to Skills Marketplace
🔌

GIPHY

by OOMOL · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
28
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install oo-giphy
Description
GIPHY (giphy.com). Use this skill for ANY GIPHY request — searching and reading data. Whenever a task involves GIPHY, use this skill instead of calling the A...
README (SKILL.md)

GIPHY

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

Category: Design & Media, Social. Exposes 15 action(s).

Running an action

Assume the user has already installed the oo CLI, signed in, and connected GIPHY. 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 "giphy" --action "\x3Caction_name>"

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

oo connector run "giphy" --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

Safety

  • Read actions (get / list / search) are safe to run directly.
  • Create, update, send, or post actions change GIPHY 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 — GIPHY 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=giphy
    
  • HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources

Usage Guidance
Install this only in a ClawHub/Convex maintenance context and treat it as a powerful operator aid. Confirm moderation, role, publish, deploy, and migration actions before running them, and use --no-yolo or AUTOREVIEW_YOLO=0 if you do not want autoreview to run nested Codex with full filesystem and command authority.
Capability Tags
requires-sensitive-credentials
Capability Assessment
Purpose & Capability
The artifact contains skills for ClawHub moderation, PR review, UI proof, autoreview, and Convex setup/auth/migration/performance work; the high-impact capabilities fit those stated purposes.
Instruction Scope
Sensitive workflows are mostly scoped by explicit targets, reasons, confirmation, dry runs, and verification; the autoreview helper defaults to full-access nested Codex review but documents the opt-out.
Install Mechanism
Files are plain skill markdown, references, icons, and one documented autoreview shell helper; no hidden postinstall, obfuscated payload, or automatic startup mechanism was evident.
Credentials
Use of GitHub CLI, Convex CLI, repo scripts, authenticated moderation commands, and network-backed proof publishing is proportionate to ClawHub maintainer and Convex development work.
Persistence & Privilege
No stealth persistence or privilege escalation was found; expected effects include local project edits, proof artifacts, optional long-running dev/proof processes, PR comments, and explicit moderation mutations.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install oo-giphy
  3. After installation, invoke the skill by name or use /oo-giphy
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial `oo-giphy` release for operating GIPHY through an OOMOL-connected account via the `oo` CLI. - Adds GIF and sticker discovery actions, including search, trending lists, random results, and phrase-to-best-match translation. - Supports metadata lookup for individual GIFs, multiple GIF IDs, content categories, trending tags, related tags, and tag autocomplete. - Uses server-side OOMOL credential injection, so raw GIPHY API tokens are not handled by the skill. - Includes per-action reference docs with schema inspection and execution commands for all 15 GIPHY actions.
Metadata
Slug oo-giphy
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is GIPHY?

GIPHY (giphy.com). Use this skill for ANY GIPHY request — searching and reading data. Whenever a task involves GIPHY, use this skill instead of calling the A... It is an AI Agent Skill for Claude Code / OpenClaw, with 28 downloads so far.

How do I install GIPHY?

Run "/install oo-giphy" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is GIPHY free?

Yes, GIPHY is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does GIPHY support?

GIPHY is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created GIPHY?

It is built and maintained by OOMOL (@oomol); the current version is v1.0.0.

💬 Comments