@agentrhq/webcmd 0.2.0 → 0.2.2

package/skills/smart-search/references/sources-other.md

@@ -0,0 +1,32 @@
+# Other Vertical Sources
+
+Use for jobs, finance, books, dictionaries, and other cases that do not fit the earlier categories.
+
+## Sites
+
+### linkedin
+
+- Use for: global jobs, English-language job listings, and multinational-company hiring
+- Before use, run: `webcmd linkedin -h`
+
+### yahoo
+
+- Use for: finance, market data, stock quotes, and company finance pages
+- Before use, run: `webcmd yahoo -h`
+
+### github
+
+- Use for: open-source project discovery, repository signals, issues, pull requests, and releases
+- Before use, run: `webcmd github -h`
+
+### dictionary
+
+- Use for: English word meanings and basic dictionary lookup
+- Before use, run: `webcmd dictionary -h`
+
+## Routing Hints
+
+- For jobs, prefer `linkedin`
+- For finance and market data, prefer `yahoo`
+- For open-source project signals, prefer `github`
+- For English word definitions, prefer `dictionary`

package/skills/smart-search/references/sources-shopping.md

@@ -0,0 +1,21 @@
+# Shopping
+
+Use for product search, prices, deals, reputation, and regional e-commerce results.
+
+## Sites
+
+### amazon
+
+- Use for: global product search, price references, and English-language e-commerce
+- Before use, run: `webcmd amazon -h`
+
+### coupang
+
+- Use for: Korean e-commerce product search
+- Before use, run: `webcmd coupang -h`
+
+## Routing Hints
+
+- If the user names a platform, use that platform directly
+- If no platform is named, prefer `amazon` for global products and `coupang` for Korean e-commerce
+- If product research starts with an AI source, add an e-commerce site afterward for actual product results

package/skills/smart-search/references/sources-social.md

@@ -0,0 +1,36 @@
+# Social Media
+
+Use when raw posts, raw user results, or community discussions are needed.
+
+## Sites
+
+### twitter
+
+- Use for: Twitter/X posts, authors, real-time discussion, and public reactions
+- Before use, run: `webcmd twitter -h`
+
+### reddit
+
+- Use for: community Q&A, experience posts, recommendations, comparisons, and subreddit discussions
+- Before use, run: `webcmd reddit -h`
+
+### instagram
+
+- Use for: account search, image-first social signals, creators, and profile clues
+- Before use, run: `webcmd instagram -h`
+
+### facebook
+
+- Use for: pages, people, post clues, and public social presence
+- Before use, run: `webcmd facebook -h`
+
+### bluesky
+
+- Use for: Bluesky users and account search
+- Before use, run: `webcmd bluesky -h`
+
+## Routing Hints
+
+- If the user explicitly names a platform, use that platform directly
+- If the user only asks what people are saying on social media, start with `grok`
+- If an AI answer only summarizes and does not provide raw posts, switch to the relevant social site

package/skills/smart-search/references/sources-tech.md

@@ -0,0 +1,38 @@
+# Technology And Research
+
+Use for technical questions, research papers, developer discussion, and open-source community information.
+
+## Sites
+
+### arxiv
+
+- Use for: papers, research, models, algorithms, and academic background
+- Before use, run: `webcmd arxiv -h`
+
+### stackoverflow
+
+- Use for: specific errors, API usage, code patterns, and implementation details
+- Before use, run: `webcmd stackoverflow -h`
+
+### hackernews
+
+- Use for: technical community discussion, developer opinions, startup topics, and product discussion
+- Before use, run: `webcmd hackernews -h`
+
+### reddit
+
+- Use for: community Q&A, experience posts, recommendations, and comparison discussions
+- Before use, run: `webcmd reddit -h`
+
+### github
+
+- Use for: repositories, issues, pull requests, releases, code search, and open-source project signals
+- Before use, run: `webcmd github -h`
+
+## Routing Hints
+
+- If the user explicitly asks for papers or research, prefer `arxiv`
+- If the user asks about an error or API usage, prefer `stackoverflow`
+- If the user wants community discussion or developer viewpoints, prefer `hackernews` or `reddit`
+- If the user wants open-source project evidence, prefer `github`
+- If the user did not name a site, start with `gemini` or `grok`, then add these specialized sources when needed

package/skills/smart-search/references/sources-travel.md

@@ -0,0 +1,26 @@
+# Travel
+
+Use for destinations, attractions, hotel ideas, and travel leads.
+
+## Sites
+
+### google
+
+- Use for: broad destination, attraction, hotel, and itinerary discovery across the web
+- Before use, run: `webcmd google -h`
+
+### reddit
+
+- Use for: traveler experiences, local tips, itinerary comparisons, and community recommendations
+- Before use, run: `webcmd reddit -h`
+
+### youtube
+
+- Use for: destination walkthroughs, hotel reviews, travel vlogs, and visual checks
+- Before use, run: `webcmd youtube -h`
+
+## Routing Hints
+
+- If the user names a specific travel platform and it exists in the live registry, use that platform directly
+- If the user only asks about travel, destinations, attractions, or hotels, start with `google`
+- Add `reddit` for traveler experience and `youtube` for visual inspection

package/skills/webcmd-adapter-author/SKILL.md

@@ -244,6 +244,7 @@ Check these off step by step:
 - **Intermediate parsing object keys must not overlap any `columns` entry.** Otherwise silent-column-drop audits can misread the adapter. Use dedicated internal names and destructure with aliases when pushing rows.
 - **The `browser:` field determines the `func` signature:** `browser:false -> (args)`, `browser:true -> (page, args)`. If this is reversed, `args` may actually be a debug flag and all external parameters can silently fall back to defaults.
 - Throw the correct typed error for known failures according to [`references/typed-errors.md`](./references/typed-errors.md). **Do not** silently `return []`, **do not** silently `return [{sentinel}]`, and **do not** silently clamp external parameters with `Math.max/min`.
+- **Persistent sessions keep stale DOM between commands.** `siteSession: 'persistent'` shares one tab per site; leftover modals/drawers from the previous command leak into the next one. State-sensitive write commands (checkout flows) should add `freshPage: true` (new tab, same lease — cookies/login/location survive). Verify session-scoped context (login, selected city/date) *before* side effects, and embed such context in URLs/IDs your command emits for sibling commands. See `references/adapter-template.md` and "Persistent Sessions and State Hygiene" in `docs/authoring.mdx`.
 - For private adapters, write `~/.webcmd/clis/<site>/<name>.js` to avoid a build. Copy to `clis/<site>/<name>.js` only when preparing a PR.
 - Write site memory every round: no memory -> use skill -> produce memory -> next time becomes a five-minute task.
 - **Raw dumps, packet captures, and HTML samples from debugging may only be written to `~/.webcmd/sites/<site>/fixtures/` or `/tmp/`. Never leave `.dbg-*.html`, `raw-*.json`, `sample.*`, or similar temporary files in the repo root, `clis/<site>/`, or the current working directory.**

package/skills/webcmd-adapter-author/references/adapter-template.md

@@ -112,6 +112,8 @@ Rules:
 | `args` | Include type, default, and help for every external parameter. |
 | `columns` | Must exactly match row keys, including order. |
 | `pipeline` or `func` | Use the style already established by nearby adapters. |
+| `siteSession` | `'persistent'` shares one tab per site across commands (multi-step flows); `'ephemeral'` gets a fresh isolated tab per run. Persistent tabs keep leftover DOM (modals, drawers) between commands — see "Persistent Sessions and State Hygiene" in docs/authoring.mdx. |
+| `freshPage` | With `siteSession: 'persistent'`, set `true` to start the command on a newly created tab under the same lease: profile state (cookies, login, location) survives, stale DOM does not. Recommended for state-sensitive write commands such as checkout flows. |
 
 ## Strategy Enum Examples
 

package/skills/webcmd-autofix/SKILL.md

@@ -53,6 +53,14 @@ Use this skill when `webcmd <site> <command>` fails with repairable errors:
 
 Proceed only when the empty or missing-selector result is reproducible across retries and alternative entry points.
 
+## Before Repair: An Error Modal Is Not Always the Site's Verdict
+
+Persistent-session adapters (`siteSession: 'persistent'`) share one tab per site, so error text in the body may be inherited or context-scoped rather than real. Before patching code:
+
+- Check the trace screenshot and `location.href`: a modal over a blank page or the wrong URL means the tab carried stale DOM from a previous command, not that the site rejected this request.
+- Check session-scoped context: sites often scope results to a selected city, date, or account. A "closed" / "unavailable" verdict can simply mean the browser's selected context does not match the request (for example, a seat layout opened while the site's location cookie points at another city).
+- Reproduce in a clean tab (`webcmd browser open <url>`) before trusting the verdict. If it only fails in the adapter's persistent tab, fix state handling (`freshPage: true`, dismiss-and-renavigate, context preconditions) instead of selectors.
+
 ## Step 1: Collect Trace Context
 
 Run the failing command with retained trace:

package/skills/webcmd-sitemap-author/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: webcmd-sitemap-author
-description: Use when creating or maintaining Webcmd site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
+description: 'Use when creating or maintaining Webcmd site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.'
 allowed-tools: Bash(webcmd:*), Read, Edit, Write, Grep
 ---