← Back to Skills Marketplace
gora050

Search Api

by Vlad Ursul · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
107
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install search-api
Description
Search API integration. Manage Deals, Persons, Organizations, Leads, Projects, Pipelines and more. Use when the user wants to interact with Search API data.
Usage Guidance
This skill appears to be an instruction-only wrapper around the Membrane CLI, but it has three things you should consider before installing/using it: (1) Documentation mismatch — the top-level description mentions CRM entities while the SKILL.md links to Google Custom Search; confirm with the skill author which API/connector this actually targets. (2) Supply-chain risk — the instructions use npx @membranehq/cli@latest which downloads and runs the current npm package every time; prefer a pinned version (e.g., @membranehq/[email protected]) or an audited install to reduce risk. (3) Credential handling — the CLI will store credentials at ~/.membrane/credentials.json and will proxy requests through Membrane; verify you trust Membrane and understand which connectors/tokens will be granted. If you plan to use this skill, ask the publisher to (a) clarify the intended API and correct the docs, (b) pin the CLI version, and (c) document what tokens are stored and which endpoints receive proxied requests. If you cannot validate those, treat the skill with caution.
Capability Analysis
Type: OpenClaw Skill Name: search-api Version: 1.0.0 The skill bundle provides instructions for an AI agent to interact with the Search API using the Membrane CLI (@membranehq/cli). While the SKILL.md description contains mismatched references to CRM entities (Deals, Persons, Leads) likely copied from a template, the core logic focuses on legitimate API interaction, authentication via OAuth, and action discovery. No evidence of data exfiltration, malicious execution, or harmful prompt injection was found.
Capability Assessment
Purpose & Capability
The skill name/description mention managing 'Deals, Persons, Organizations, Leads, Projects, Pipelines' (CRM-like entities), but the SKILL.md links to Google Custom Search docs and otherwise describes a generic 'Search API' connector via Membrane. That mismatch between stated entities and referenced API docs is ambiguous and suggests the documentation may be copy-pasted or inaccurate.
Instruction Scope
Instructions are narrowly focused on using the Membrane CLI (npx @membranehq/cli@latest) to create connections, list actions, run actions, and proxy requests. They reference storing credentials at ~/.membrane/credentials.json (credential persistence) and instruct opening a browser for interactive login. The instructions do not request unrelated files or environment variables, but they do cause credentials and proxied requests to be managed by Membrane — meaning API calls and tokens will transit through/are stored by the Membrane tool/service.
Install Mechanism
There is no install spec in the skill bundle, but the runtime instructions call npx @membranehq/cli@latest. That fetches and executes the latest package from npm at runtime (supply-chain risk), and the command is unpinned (uses 'latest'), making behavior changeable by upstream package updates. This is moderate risk compared with a pinned or vetted release.
Credentials
The skill declares no required env vars, which aligns with being a Membrane-driven connector. However, the CLI stores credentials locally in ~/.membrane/credentials.json and uses them to proxy requests; those credentials could grant access to connected services. The skill's documentation explicitly tells users to let Membrane handle credentials rather than storing API keys locally, which is reasonable, but users should be aware these tokens reside on-disk and are used by the CLI.
Persistence & Privilege
The skill is not marked always:true and does not request elevated platform privileges. The only persistent artifact described is the credentials file (~/.membrane/credentials.json) created by the Membrane CLI; that is normal for CLI auth but is a persistent local secret that merits review.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install search-api
  3. After installation, invoke the skill by name or use /search-api
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Auto sync from membranedev/application-skills
Metadata
Slug search-api
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Search Api?

Search API integration. Manage Deals, Persons, Organizations, Leads, Projects, Pipelines and more. Use when the user wants to interact with Search API data. It is an AI Agent Skill for Claude Code / OpenClaw, with 107 downloads so far.

How do I install Search Api?

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

Is Search Api free?

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

Which platforms does Search Api support?

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

Who created Search Api?

It is built and maintained by Vlad Ursul (@gora050); the current version is v1.0.0.

💬 Comments