searching-packages
Finds Robomotion packages, nodes, and templates via the `robomotion` CLI, which is backed by Bleve full-text search with fuzzy matching and semantic expansion. Use when the user asks to find a package, explore templates, discover what nodes exist for a task, or check exact property names before writing a flow.
How do I install this agent skill?
npx skills add https://github.com/robomotionio/agent-skills --skill searching-packagesIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill provides commands to search and browse Robomotion automation packages, nodes, and templates using the vendor's own command-line interface.
- Socketpass
No alerts
- Snykwarn
Risk: MEDIUM · 1 issue
- ZeroLeakspass
Score: 93/100 · 2 sections analyzed
What does this agent skill do?
Searching Robomotion Packages
Discover Robomotion packages, nodes, and templates. All lookups go through the robomotion CLI — no separate MCP client required.
Four verbs cover every lookup
robomotion search <query> # cross-source fuzzy+semantic search
robomotion get <resource> [query] [flags] # list or filter a resource
robomotion describe <resource> <name> # full detail of one thing
robomotion docs <namespace> # read a package's llms.txt
Resources for get: packages | nodes | templates | categories | tags (plus vaults | vault-items | robots for runtime data).
Resources for describe: node | package | template.
Typical workflow when authoring a flow
-
Find what's available — if you don't know the package/node yet:
robomotion search "http request" # mixed results across sources robomotion get nodes click # nodes with "click" in the name robomotion get nodes --in Core.Browser # every node in one package robomotion get templates bmi # match by slug/name/summary robomotion get templates --category "Web Scraping" robomotion get templates --tag api robomotion get categories # vocabulary robomotion get tags # vocabulary -
Verify properties before writing:
robomotion describe node Core.Net.HttpRequest robomotion describe node Core.Net.HttpRequest,Core.Flow.GoTo # batchReturns the full card: property names, types, descriptions, enums, defaults, and common properties (
delayBefore,continueOnError, …). -
Read package docs when wiring a non-
Core.*package:robomotion docs Robomotion.WordPress # compact (first 100 lines) robomotion docs Robomotion.WordPress --full # whole llms.txt robomotion docs Robomotion.WordPress --grep auth # line-filtered robomotion docs Robomotion.WordPress --section CreatePostdocscarries auth patterns and package-level gotchas that aren't in node schemas. Run it for every non-Core.*package you use. Many packages have no llms.txt (for exampleRobomotion.HermesAgent): thendocsanswers"available":false, and the package's own descriptions are the documentation — readrobomotion describe package <ns>for its nodes and versions, androbomotion describe node <type>for each node you wire (every property carries a description).
Search engine capabilities
Under the hood robomotion search uses Bleve full-text search with:
| Feature | Behavior |
|---|---|
| Full-text | BM25 ranking across title, name, description, content, keywords |
| Fuzzy | Levenshtein ≤ 2 — tolerates typos (browsr → browser, wordpres → wordpress) |
| Semantic | Synonym expansion — browser also matches chrome, firefox, web, scraping |
| Multi-source | Package docs (llms.txt) and templates in one call |
Built-in synonym families:
browser ↔ chrome · firefox · web · scrapingautomation ↔ robot · flow · workflow · processwordpress ↔ blog · cms · post · articledatabase ↔ sql · sqlite · query · tableemail ↔ mail · smtp · send · messagefile ↔ filesystem · directory · folder · path
Filter flags
robomotion search "automation" --limit 5
robomotion get nodes "click" --package Core.Browser
robomotion get templates --tag api --limit 10
robomotion describe node Core.Browser.ClickElement --json # raw MCP response
First-call warm-up
robomotion search spawns robomotion-sdk-mcp under the hood; its Bleve index takes ~3–6 s to build on cold start. The CLI retries automatically on "Search index not ready", so you'll see one slow search per session, then near-instant afterward.
Quick reference
| I want to… | Command |
|---|---|
| Find anything by keyword | robomotion search <query> |
| List all packages | robomotion get packages |
| Find a package | robomotion get packages <keyword> |
| List nodes in a package | robomotion get nodes --in <namespace> |
| Find nodes by keyword | robomotion get nodes <keyword> |
| Get full node schema | robomotion describe node <type> |
| Read package docs | robomotion docs <namespace> |
| Grep package docs | robomotion docs <namespace> --grep <pattern> |
| List available vaults | robomotion get vaults |
| List robots | robomotion get robots |
Related Skills
creating-flow— generate a flow from the nodes you foundvalidating-flow— pspec-check the resultrunning-flow— submit + stream agent events
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/robomotionio/agent-skills/searching-packages">View searching-packages on skillZs</a>