@agentrhq/webcmd 0.2.5 → 0.3.0

package/skills/smart-search/SKILL.md

@@ -11,9 +11,19 @@ Route a query to the best webcmd search source based on the topic and context. T
 
 Before every use, do both of these steps:
 
-- Run `webcmd list -f yaml`
+- Run `webcmd list -f json`
 - Use the live registry to confirm that candidate sites exist, and inspect `strategy`, `browser`, and `domain`
 
+If the user explicitly names a site/source and it is missing from `webcmd list` or when none of the sites cover the query, check installable plugins before marking it unavailable:
+
+```bash
+webcmd plugin search <site-or-source-or-capability> -f json
+```
+
+Derive a short plugin query from the missing site or capability. Preserve the user's term when practical: `find flights` becomes `flight`.
+
+If plugin search finds a match, tell the user it is available as a plugin and offer `webcmd plugin install <source>`. If plugin search fails because catalog sources cannot be fetched, report that catalog/search error separately from no plugin match.
+
 After choosing a site, do both of these steps:
 
 - Run `webcmd <site> -h` to see the site's subcommands
@@ -42,7 +52,7 @@ First create a site-call ledger. After each real search command, update it immed
 
 Counting rules:
 
-- `webcmd list -f yaml`, `webcmd <site> -h`, and `webcmd <site> <command> -h` are preflight/help commands and do not count as searches.
+- `webcmd list -f json`, `webcmd plugin search <query> -f json`, `webcmd <site> -h`, and `webcmd <site> <command> -h` are preflight/help commands and do not count as searches.
 - One real `webcmd <site> ...` search/query execution counts as 1 call for that site.
 - A failed call caused by an error, timeout, CAPTCHA, anti-bot check, or broken login state still counts as 1 call for that site. Do not retry indefinitely.
 
@@ -134,9 +144,10 @@ Keep a typical query to 1 AI source plus 1-2 specialized sources to avoid result
 When a site is unavailable:
 
 - Do not stop the whole search because one source failed
+- For a missing site or capability, run `webcmd plugin search <query> -f json` before recording unavailable
 - Record: `Skipped: <site> unavailable`
 - Fall back to another site of the same type, or to one AI source
-- Always trust the actual output of `webcmd list -f yaml` and `webcmd <site> -h`
+- Always trust the actual output of `webcmd list -f json`, `webcmd plugin search -f json`, and `webcmd <site> -h`
 
 Do not assume any site is always available. Even for public sites, trust live help and execution results in the current environment.
 

package/skills/webcmd-usage/SKILL.md

@@ -44,21 +44,25 @@ npx tsx src/main.ts <command>
 
 Electron desktop app adapters route through CDP against the running app. Make sure the app is open before invoking those commands.
 
-## Discover Installed Commands
+## Discover Commands
 
 Run commands instead of reading static docs:
 
 ```bash
-webcmd list
+webcmd
 webcmd list -f json
-webcmd list | grep -i github
 webcmd <site> --help
 webcmd <site> <command> --help
 ```
 
-Do not hard-code adapter lists. `webcmd list -f json` is the source of truth and emits one entry per command with fields such as `{site, name, aliases, description, strategy, browser, args, columns}`.
+Run `webcmd` with no arguments to see all available functions and installed site adapters. Do not hard-code adapter lists: `webcmd list -f json` is the source of truth for installed commands and emits one entry per command with fields such as `{site, name, aliases, description, strategy, browser, args, columns}`.
 
-Before falling back to raw `webcmd browser` on high-change authenticated sites, check whether a site adapter already exposes the workflow.
+Use this fallback order:
+
+1. Run `webcmd list -f json` once.
+2. Check that result against the whole requested workflow, not only a named site. If one installed command covers it, use that command and stop discovery.
+3. If none covers it, derive a short plugin query from the missing site or capability and run `webcmd plugin search <query> -f json`. Preserve the user's term when practical: `find flights` becomes `flight`.
+4. If plugin search returns a match, offer `webcmd plugin install <installSource>`. If it returns no match and no error, raw `webcmd browser` is allowed. If it errors, report plugin discovery as unavailable and stop. If `fetch failed` appears in `errors[].message`, report plugin discovery as unavailable due to network/reachability and ask the user whether to rerun with network/escalated permissions. Do not retry unless they approve.
 
 ## Universal Flags
 
@@ -129,10 +133,13 @@ webcmd plugin list [-f json]
 webcmd plugin update [name] | --all
 webcmd plugin uninstall <name>
 webcmd plugin create <name>
-webcmd plugin search [query]
+webcmd plugin search [query] -f json
+webcmd plugin catalog list -f json
+webcmd plugin catalog add <source>
+webcmd plugin catalog remove <id>
 ```
 
-Plugins are installable extensions pulled from git or local paths. Main-repo community CLIs are exposed through the root plugin catalog manifest, not bundled into npm's `clis/` set.
+Plugins are installable extensions pulled from git or local paths. Use `plugin search` for marketplace discovery and `plugin list` for already-installed plugins. Main-repo community CLIs are exposed through the root plugin catalog manifest, not bundled into npm's `clis/` set.
 
 > **Note:** The repository's `plugins/` directory is not shipped in the npm package. Find the required plugin with `webcmd plugin search`, then install its `installSource` with `webcmd plugin install <installSource>`.
 

package/clis/antigravity/SKILL.md

@@ -1,38 +0,0 @@
----
-description: How to automate Antigravity using Webcmd
----
-
-# Antigravity Automation Skill
-
-This skill allows AI agents to control the [Antigravity](https://github.com/chengazhen/Antigravity) desktop app (and any Electron app with CDP enabled) programmatically via Webcmd.
-
-## Requirements
-webcmd automatically detects, launches (with `--remote-debugging-port=9234`), and connects to Antigravity.
-If Antigravity is already running without CDP, webcmd will prompt to restart it.
-
-If the endpoint exposes multiple inspectable targets, set:
-\`\`\`bash
-export WEBCMD_CDP_TARGET="antigravity"
-\`\`\`
-
-## High-Level Capabilities
-1. **Send Messages (`webcmd antigravity send <message>`)**: Type and send a message directly into the chat UI.
-2. **Read History (`webcmd antigravity read`)**: Scrape the raw chat transcript from the main UI container.
-3. **Extract Code (`webcmd antigravity extract-code`)**: Automatically isolate and extract source code text blocks from the AI's recent answers.
-4. **Switch Models (`webcmd antigravity model <name>`)**: Instantly toggle the active LLM (e.g., \`gemini\`, \`claude\`).
-5. **Clear Context (`webcmd antigravity new`)**: Start a fresh conversation.
-
-## Examples for Automated Workflows
-
-### Generating and Saving Code
-\`\`\`bash
-webcmd antigravity send "Write a python script to fetch HN top stories"
-# wait ~10-15 seconds for output to render
-webcmd antigravity extract-code > hn_fetcher.py
-\`\`\`
-
-### Reading Real-time Logs
-Agents can run long-running streaming watch instances:
-\`\`\`bash
-webcmd antigravity watch
-\`\`\`