@hybridlabor-api/aos 4.2.0-beta.0 → 4.3.0

package/skills/global_config/openwiki-skill/scripts/install_daemon.sh

@@ -39,14 +39,57 @@ if [ ! -f "$SCRIPT_PATH" ]; then
 fi
 SCRIPTS_DIR="$(dirname "$SCRIPT_PATH")"
 
-# 2. Install Python dependency
-echo "Installing google-genai SDK..."
-if command -v pip3 >/dev/null 2>&1; then
-    pip3 install --quiet google-genai 2>/dev/null || {
-        echo "Warning: pip3 install failed. You may need to install google-genai manually."
-    }
+# 2. Install Python dependency into a dedicated venv.
+#
+# Two bugs this replaces, both of which made the daemon unable to ever start:
+#   1. `pip3 install google-genai` fails on any PEP 668 "externally managed"
+#      interpreter (Homebrew/Debian python3) with externally-managed-environment,
+#      and the old `2>/dev/null` swallowed that message, so the log said only
+#      "pip3 install failed" with no cause.
+#   2. Even when it succeeded, it installed into whichever python3 was on PATH
+#      (e.g. Homebrew 3.14) while the macOS launcher ran the daemon under
+#      /usr/bin/python3 (Apple CommandLineTools 3.9) — a different interpreter
+#      that never saw the package.
+# A venv fixes both: it is immune to PEP 668, and DAEMON_PYTHON below pins the
+# launcher to the exact interpreter the package was installed into.
+VENV_DIR="$DAEMON_LOG_DIR/venv"
+DAEMON_PYTHON=""
+
+echo "Installing google-genai SDK into $VENV_DIR ..."
+mkdir -p "$DAEMON_LOG_DIR"
+
+if command -v uv >/dev/null 2>&1; then
+    # uv pip install --python <venv> never needs pip inside the venv, which is
+    # the failure memB hit when `uv venv --seed` silently under-delivered pip.
+    uv venv "$VENV_DIR" >/dev/null 2>&1 || true
+    if [ -x "$VENV_DIR/bin/python" ] && uv pip install --python "$VENV_DIR/bin/python" --quiet google-genai; then
+        DAEMON_PYTHON="$VENV_DIR/bin/python"
+    fi
+fi
+
+if [ -z "$DAEMON_PYTHON" ] && command -v python3 >/dev/null 2>&1; then
+    python3 -m venv "$VENV_DIR" >/dev/null 2>&1 || true
+    if [ -x "$VENV_DIR/bin/python" ] && "$VENV_DIR/bin/python" -m pip install --quiet google-genai; then
+        DAEMON_PYTHON="$VENV_DIR/bin/python"
+    fi
+fi
+
+if [ -z "$DAEMON_PYTHON" ]; then
+    # Do not hide the reason this time — print what actually failed.
+    echo "Warning: could not install google-genai into $VENV_DIR."
+    echo "         Reason (last attempt):"
+    if command -v python3 >/dev/null 2>&1; then
+        python3 -m venv "$VENV_DIR" 2>&1 | sed 's/^/           /' | head -5
+        "$VENV_DIR/bin/python" -m pip install google-genai 2>&1 | sed 's/^/           /' | head -8
+    else
+        echo "           python3 not found on PATH."
+    fi
+    echo "         The daemon will run in collect-only mode until this is resolved."
+    # Fall back to a bare interpreter so the launcher is still written; the
+    # daemon degrades to collect-only rather than not existing at all.
+    DAEMON_PYTHON="$(command -v python3 || echo /usr/bin/python3)"
 else
-    echo "Warning: pip3 not found. Install google-genai manually."
+    echo " -> google-genai installed; daemon will run under $DAEMON_PYTHON"
 fi
 
 # 3. Resolve API key
@@ -60,7 +103,7 @@ fi
 if [ -n "$GEMINI_KEY" ]; then
     export GEMINI_API_KEY="$GEMINI_KEY"
     echo "Verifying API key..."
-    VERIFY_OUTPUT=$(python3 "$SCRIPTS_DIR/verify_api_key.py" 2>&1)
+    VERIFY_OUTPUT=$("$DAEMON_PYTHON" "$SCRIPTS_DIR/verify_api_key.py" 2>&1)
     VERIFY_CODE=$?
     if [ $VERIFY_CODE -eq 0 ] && echo "$VERIFY_OUTPUT" | grep -q "VERIFIED_OK"; then
         echo " -> API key verified successfully."
@@ -170,7 +213,7 @@ if [ "$OS" = "macos" ]; then
     fi
 
     MACOS_PATH="/opt/homebrew/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin"
-    write_launcher "/usr/bin/python3" "$MACOS_PATH"
+    write_launcher "$DAEMON_PYTHON" "$MACOS_PATH"
     echo " -> Launcher written to $LAUNCHER_PATH (mode 700; holds the API key, if any)."
 
     cat <<EOF > "$PLIST_PATH"
@@ -220,7 +263,7 @@ elif [ "$OS" = "linux" ]; then
         echo "Linux detected, but no usable systemd user session was found."
         echo "Skipping automatic daemon installation (no false success)."
         echo "Run it manually instead, e.g. via cron (every 2 hours):"
-        echo "  0 */2 * * *  python3 \"$SCRIPT_PATH\" --one-shot"
+        echo "  0 */2 * * *  $DAEMON_PYTHON \"$SCRIPT_PATH\" --one-shot"
         echo ""
         exit 1
     fi
@@ -228,7 +271,7 @@ elif [ "$OS" = "linux" ]; then
     mkdir -p "$SYSTEMD_DIR"
 
     LINUX_PATH="/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin"
-    write_launcher "python3" "$LINUX_PATH"
+    write_launcher "$DAEMON_PYTHON" "$LINUX_PATH"
     echo " -> Launcher written to $LAUNCHER_PATH (mode 700; holds the API key, if any)."
 
     cat > "$SYSTEMD_SERVICE" <<EOF
@@ -279,7 +322,7 @@ else
     echo "Unsupported OS: $OS"
     echo "Skipping automatic daemon installation (no false success)."
     echo "Run it manually via cron / task scheduler:"
-    echo "  python3 \"$SCRIPT_PATH\" --one-shot"
+    echo "  $DAEMON_PYTHON \"$SCRIPT_PATH\" --one-shot"
     exit 1
 fi
 

package/skills/global_config/playwright-skill/SKILL.md

@@ -3,7 +3,7 @@ name: playwright-skill
 description: General-purpose browser automation skill. Use when a task needs custom Playwright code — end-to-end testing, scraping a JS-rendered page, or driving a browser interactively — executed via this skill's universal executor rather than a one-off script.
 category: library
 risk: unknown
-source: community
+source: lackeyjb (MIT)
 date_added: "2026-02-27"
 plugin:
   setup:

package/skills/global_config/posix-shell-pro/SKILL.md

@@ -22,7 +22,6 @@ date_added: '2026-02-27'
 - Clarify goals, constraints, and required inputs.
 - Apply relevant best practices and validate outcomes.
 - Provide actionable steps and verification.
-- If detailed examples are required, open `resources/implementation-playbook.md`.
 
 ## Focus Areas
 

package/skills/global_config/postgres-best-practices/SKILL.md

@@ -3,7 +3,7 @@ name: postgres-best-practices
 description: "Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations."
 category: library
 risk: safe
-source: community
+source: Supabase
 date_added: "2026-02-27"
 ---
 

package/skills/global_config/prompt-engineering-patterns/SKILL.md

@@ -21,7 +21,6 @@ Master advanced prompt engineering techniques to maximize LLM performance, relia
 - Clarify goals, constraints, and required inputs.
 - Apply relevant best practices and validate outcomes.
 - Provide actionable steps and verification.
-- If detailed examples are required, open `resources/implementation-playbook.md`.
 
 ## Use this skill when
 

package/skills/global_config/rag-engineer/SKILL.md

@@ -1,9 +1,10 @@
 ---
 name: rag-engineer
-description: Expert in building Retrieval-Augmented Generation systems. Masters
+description: >-
+  Expert in building Retrieval-Augmented Generation systems. Masters embedding
+  models, vector databases, chunking strategies, and retrieval optimization for
+  LLM applications.
 category: library
-  embedding models, vector databases, chunking strategies, and retrieval
-  optimization for LLM applications.
 risk: unknown
 source: vibeship-spawner-skills (Apache 2.0)
 date_added: 2026-02-27

package/skills/global_config/react-best-practices/SKILL.md

@@ -3,7 +3,7 @@ name: react-best-practices
 description: "Comprehensive performance optimization guide for React and Next.js applications, maintained by Vercel. Use when writing new React components or Next.js pages, implementing data fetching (client or server-side), or reviewing code for performance issues."
 category: library
 risk: safe
-source: community
+source: Vercel Engineering
 date_added: "2026-02-27"
 ---
 

package/skills/global_config/remotion/SKILL.md

@@ -192,7 +192,6 @@ Create the video components following Remotion best practices:
 
 **Reference Resources:**
 - Use `resources/screen-slide-template.tsx` as starting point
-- Follow `resources/composition-checklist.md` for completeness
 - Review examples in `examples/walkthrough/` directory
 
 ### Step 3: Preview and Refine

package/skills/global_config/seo/SKILL.md

@@ -12,8 +12,7 @@ argument-hint: "[command] [url]"
 # SEO: Universal SEO Analysis Skill
 
 Comprehensive SEO analysis across all industries (SaaS, local services,
-e-commerce, publishers, agencies). Orchestrates 12 specialized sub-skills and 7 subagents
-(+ optional extension sub-skills like seo-dataforseo).
+e-commerce, publishers, agencies). Orchestrates 2 specialized sub-skills.
 
 ## When to Use
 - Use when the user asks for a full SEO audit or broad SEO strategy.
@@ -25,30 +24,16 @@ e-commerce, publishers, agencies). Orchestrates 12 specialized sub-skills and 7
 | Command | What it does |
 |---------|-------------|
 | `/seo audit <url>` | Full website audit with parallel subagent delegation |
-| `/seo page <url>` | Deep single-page analysis |
-| `/seo sitemap <url or generate>` | Analyze or generate XML sitemaps |
-| `/seo schema <url>` | Detect, validate, and generate Schema.org markup |
-| `/seo images <url>` | Image optimization analysis |
 | `/seo technical <url>` | Technical SEO audit (9 categories) |
-| `/seo content <url>` | E-E-A-T and content quality analysis |
-| `/seo geo <url>` | AI Overviews / Generative Engine Optimization |
-| `/seo plan <business-type>` | Strategic SEO planning |
-| `/seo programmatic [url\|plan]` | Programmatic SEO analysis and planning |
-| `/seo competitor-pages [url\|generate]` | Competitor comparison page generation |
-| `/seo hreflang [url]` | Hreflang/i18n SEO audit and generation |
-| `/seo dataforseo [command]` | Live SEO data via DataForSEO (extension) |
-| `/seo image-gen [use-case] <description>` | AI image generation for SEO assets (extension) |
 
 ## Orchestration Logic
 
-When the user invokes `/seo audit`, delegate to subagents in parallel:
+When the user invokes `/seo audit`, delegate to subagents:
 1. Detect business type (SaaS, local, ecommerce, publisher, agency, other)
-2. Spawn subagents: seo-technical, seo-content, seo-schema, seo-sitemap, seo-performance, seo-visual, seo-geo
+2. Spawn subagent: seo-technical for technical SEO analysis
 3. Collect results and generate unified report with SEO Health Score (0-100)
 4. Create prioritized action plan (Critical -> High -> Medium -> Low)
 
-For individual commands, load the relevant sub-skill directly.
-
 ## Industry Detection
 
 Detect business type from homepage signals:
@@ -99,35 +84,15 @@ Weighted aggregate of all categories:
 
 ## Sub-Skills
 
-This skill orchestrates 12 specialized sub-skills (+ 2 extensions):
+This skill orchestrates 2 specialized sub-skills:
 
 1. **seo-audit** -- Full website audit with parallel delegation
-2. **seo-page** -- Deep single-page analysis
-3. **seo-technical** -- Technical SEO (9 categories)
-4. **seo-content** -- E-E-A-T and content quality
-5. **seo-schema** -- Schema markup detection and generation
-6. **seo-images** -- Image optimization
-7. **seo-sitemap** -- Sitemap analysis and generation
-8. **seo-geo** -- AI Overviews / GEO optimization
-9. **seo-plan** -- Strategic planning with templates
-10. **seo-programmatic** -- Programmatic SEO analysis and planning
-11. **seo-competitor-pages** -- Competitor comparison page generation
-12. **seo-hreflang** -- Hreflang/i18n SEO audit and generation
-13. **seo-dataforseo** -- Live SEO data via DataForSEO MCP (extension)
-14. **seo-image-gen** -- AI image generation for SEO assets via Gemini (extension)
+2. **seo-technical** -- Technical SEO (9 categories)
 
 ## Subagents
 
-For parallel analysis during audits:
+For analysis during audits:
 - `seo-technical` -- Crawlability, indexability, security, CWV
-- `seo-content` -- E-E-A-T, readability, thin content
-- `seo-schema` -- Detection, validation, generation
-- `seo-sitemap` -- Structure, coverage, quality gates
-- `seo-performance` -- Core Web Vitals measurement
-- `seo-visual` -- Screenshots, mobile testing, above-fold
-- `seo-geo` -- AI crawler access, llms.txt, citability, brand mention signals
-- `seo-dataforseo` -- Live SERP, keyword, backlink, local SEO data (extension, optional)
-- `seo-image-gen` -- SEO image audit and generation plan (extension, optional)
 
 ## Error Handling
 

package/skills/global_config/systematic-debugging/CREATION-LOG.md

@@ -4,7 +4,7 @@ Reference example of extracting, structuring, and bulletproofing a critical skil
 
 ## Source Material
 
-Extracted debugging framework from `/Users/jesse/.claude/CLAUDE.md`:
+Extracted debugging framework from `~/.claude/CLAUDE.md`:
 - 4-phase systematic process (Investigation → Pattern Analysis → Hypothesis → Implementation)
 - Core mandate: ALWAYS find root cause, NEVER fix symptoms
 - Rules designed to resist time pressure and rationalization

package/skills/global_config/systematic-debugging/root-cause-tracing.md

@@ -33,7 +33,7 @@ digraph when_to_use {
 
 ### 1. Observe the Symptom
 ```
-Error: git init failed in /Users/jesse/project/packages/core
+Error: git init failed in ~/project/packages/core
 ```
 
 ### 2. Find Immediate Cause

package/skills/global_config/turborepo-caching/SKILL.md

@@ -21,7 +21,6 @@ Production patterns for Turborepo build optimization.
 - Clarify goals, constraints, and required inputs.
 - Apply relevant best practices and validate outcomes.
 - Provide actionable steps and verification.
-- If detailed examples are required, open `resources/implementation-playbook.md`.
 
 ## Use this skill when
 

package/skills/global_config/using-neon/SKILL.md

@@ -25,8 +25,6 @@ Use this skill when:
 
 Always reference the Neon documentation before making Neon-related claims. The documentation is the source of truth for all Neon-related information.
 
-Below you'll find a list of resources organized by area of concern. This is meant to support you find the right documentation pages to fetch and add a bit of additonal context.
-
 You can use the `curl` commands to fetch the documentation page as markdown:
 
 **Documentation:**
@@ -39,51 +37,7 @@ curl https://neon.com/llms.txt
 curl -H "Accept: text/markdown" https://neon.com/docs/<path>
 ```
 
-Don't guess docs pages. Use the `llms.txt` index to find the relevant URL or follow the links in the resources below.
-
-## Overview of Resources
-
-Reference the appropriate resource file based on the user's needs:
-
-### Core Guides
-
-| Area               | Resource                           | When to Use                                                    |
-| ------------------ | ---------------------------------- | -------------------------------------------------------------- |
-| What is Neon       | `references/what-is-neon.md`       | Understanding Neon concepts, architecture, core resources      |
-| Referencing Docs   | `references/referencing-docs.md`   | Looking up official documentation, verifying information       |
-| Features           | `references/features.md`           | Branching, autoscaling, scale-to-zero, instant restore         |
-| Getting Started    | `references/getting-started.md`    | Setting up a project, connection strings, dependencies, schema |
-| Connection Methods | `references/connection-methods.md` | Choosing drivers based on platform and runtime                 |
-| Developer Tools    | `references/devtools.md`           | VSCode extension, MCP server, Neon CLI (`neon init`)           |
-
-### Database Drivers & ORMs
-
-HTTP/WebSocket queries for serverless/edge functions.
-
-| Area              | Resource                        | When to Use                                         |
-| ----------------- | ------------------------------- | --------------------------------------------------- |
-| Serverless Driver | `references/neon-serverless.md` | `@neondatabase/serverless` - HTTP/WebSocket queries |
-| Drizzle ORM       | `references/neon-drizzle.md`    | Drizzle ORM integration with Neon                   |
-
-### Auth & Data API SDKs
-
-Authentication and PostgREST-style data API for Neon.
-
-| Area        | Resource                  | When to Use                                                         |
-| ----------- | ------------------------- | ------------------------------------------------------------------- |
-| Neon Auth   | `references/neon-auth.md` | `@neondatabase/auth` - Authentication only                          |
-| Neon JS SDK | `references/neon-js.md`   | `@neondatabase/neon-js` - Auth + Data API (PostgREST-style queries) |
-
-### Neon Platform API & CLI
-
-Managing Neon resources programmatically via REST API, SDKs, or CLI.
-
-| Area                  | Resource                            | When to Use                                  |
-| --------------------- | ----------------------------------- | -------------------------------------------- |
-| Platform API Overview | `references/neon-platform-api.md`   | Managing Neon resources via REST API         |
-| Neon CLI              | `references/neon-cli.md`            | Terminal workflows, scripts, CI/CD pipelines |
-| TypeScript SDK        | `references/neon-typescript-sdk.md` | `@neondatabase/api-client`                   |
-| Python SDK            | `references/neon-python-sdk.md`     | `neon-api` package                           |
+Don't guess docs pages. Use the `llms.txt` index to find the relevant URL.
 
 ## Limitations
 - Use this skill only when the task clearly matches the scope described above.

package/skills/global_config/vector-database-engineer/SKILL.md

@@ -21,7 +21,6 @@ Expert in vector databases, embedding strategies, and semantic search implementa
 - Clarify goals, constraints, and required inputs.
 - Apply relevant best practices and validate outcomes.
 - Provide actionable steps and verification.
-- If detailed examples are required, open `resources/implementation-playbook.md`.
 
 ## Capabilities
 

package/skills/global_config/web-artifacts-builder/LICENSE.txt

@@ -187,7 +187,7 @@
       same "printed page" as the copyright notice for easier
       identification within third-party archives.
 
-   Copyright [yyyy] [name of copyright owner]
+   Copyright 2026 Anthropic, PBC.
 
    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.

package/skills/global_config/web-artifacts-builder/SKILL.md

@@ -3,7 +3,7 @@ name: web-artifacts-builder
 description: "To build powerful frontend claude.ai artifacts, follow these steps:"
 category: library
 risk: unknown
-source: community
+source: anthropics/skills (Apache-2.0)
 date_added: "2026-02-27"
 ---
 

package/skills/global_config/webapp-testing/LICENSE.txt

@@ -187,7 +187,7 @@
       same "printed page" as the copyright notice for easier
       identification within third-party archives.
 
-   Copyright [yyyy] [name of copyright owner]
+   Copyright 2026 Anthropic, PBC.
 
    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.

package/skills/global_config/webapp-testing/SKILL.md

@@ -3,7 +3,7 @@ name: webapp-testing
 description: "To test local web applications, write native Python Playwright scripts."
 category: engineering-method
 risk: unknown
-source: community
+source: anthropics/skills (Apache-2.0)
 date_added: "2026-02-27"
 ---
 

package/.agents/skills/firecrawl/SKILL.md

@@ -1,149 +0,0 @@
----
-name: firecrawl
-description: |
-  Search, scrape, and interact with the web via the Firecrawl CLI. Use this skill whenever the user wants to search the web, find articles, research a topic, look something up online, scrape a webpage, grab content from a URL, get data from a website, crawl documentation, download a site, or interact with pages that need clicks or logins. Also use when they say "fetch this page", "pull the content from", "get the page at https://", or reference external websites. This provides real-time web search with full page content and interact capabilities — beyond what Claude can do natively with built-in tools. Do NOT trigger for local file operations, git commands, deployments, or code editing tasks.
-category: library
-allowed-tools:
-  - Bash(firecrawl *)
-  - Bash(npx firecrawl *)
----
-
-# Firecrawl CLI
-
-Search, scrape, and interact with the web. Returns clean markdown optimized for LLM context windows.
-
-Run `firecrawl --help` or `firecrawl <command> --help` for full option details.
-
-If the task is to integrate Firecrawl into an application, add `FIRECRAWL_API_KEY` to a project, or choose endpoint usage in product code, use the `firecrawl-build` skills. They are already installed alongside this CLI skill when you run `firecrawl init`.
-
-## Prerequisites
-
-Must be installed and authenticated. Check with `firecrawl --status`.
-
-```
-  🔥 firecrawl cli v1.8.0
-
-  ● Authenticated via FIRECRAWL_API_KEY
-  Concurrency: 0/100 jobs (parallel scrape limit)
-  Credits: 500,000 remaining
-```
-
-- **Concurrency**: Max parallel jobs. Run parallel operations up to this limit.
-- **Credits**: Remaining API credits. Each operation consumes credits.
-
-If not ready, see [rules/install.md](rules/install.md). For output handling guidelines, see [rules/security.md](rules/security.md).
-
-Before doing real work, verify the setup with one small request:
-
-```bash
-mkdir -p .firecrawl
-firecrawl scrape "https://firecrawl.dev" -o .firecrawl/install-check.md
-```
-
-```bash
-firecrawl search "query" --scrape --limit 3
-```
-
-## Workflow
-
-Follow this escalation pattern:
-
-1. **Search** - No specific URL yet. Find pages, answer questions, discover sources.
-2. **Scrape** - Have a URL. Extract its content directly.
-3. **Map + Scrape** - Large site or need a specific subpage. Use `map --search` to find the right URL, then scrape it.
-4. **Crawl** - Need bulk content from an entire site section (e.g., all /docs/).
-5. **Interact** - Scrape first, then interact with the page (pagination, modals, form submissions, multi-step navigation).
-
-| Need                        | Command               | When                                                      |
-| --------------------------- | --------------------- | --------------------------------------------------------- |
-| Find pages on a topic       | `search`              | No specific URL yet                                       |
-| Get a page's content        | `scrape`              | Have a URL, page is static or JS-rendered                 |
-| Find URLs within a site     | `map`                 | Need to locate a specific subpage                         |
-| Bulk extract a site section | `crawl`               | Need many pages (e.g., all /docs/)                        |
-| AI-powered data extraction  | `agent`               | Need structured data from complex sites                   |
-| Interact with a page        | `scrape` + `interact` | Content requires clicks, form fills, pagination, or login |
-| Download a site to files    | `download`            | Save an entire site as local files                        |
-
-For detailed command reference, run `firecrawl <command> --help`.
-
-**Scrape vs interact:**
-
-- Use `scrape` first. It handles static pages and JS-rendered SPAs.
-- Use `scrape` + `interact` when you need to interact with a page, such as clicking buttons, filling out forms, navigating through a complex site, infinite scroll, or when scrape fails to grab all the content you need.
-- Never use interact for web searches - use `search` instead.
-
-**Avoid redundant fetches:**
-
-- `search --scrape` already fetches full page content. Don't re-scrape those URLs.
-- Check `.firecrawl/` for existing data before fetching again.
-
-## When to Load References
-
-- **Searching the web or finding sources first** -> [firecrawl-search](../firecrawl-search/SKILL.md)
-- **Scraping a known URL** -> [firecrawl-scrape](../firecrawl-scrape/SKILL.md)
-- **Finding URLs on a known site** -> [firecrawl-map](../firecrawl-map/SKILL.md)
-- **Bulk extraction from a docs section or site** -> [firecrawl-crawl](../firecrawl-crawl/SKILL.md)
-- **AI-powered structured extraction from complex sites** -> [firecrawl-agent](../firecrawl-agent/SKILL.md)
-- **Clicks, forms, login, pagination, or post-scrape browser actions** -> [firecrawl-interact](../firecrawl-interact/SKILL.md)
-- **Downloading a site to local files** -> [firecrawl-download](../firecrawl-download/SKILL.md)
-- **Install, auth, or setup problems** -> [rules/install.md](rules/install.md)
-- **Output handling and safe file-reading patterns** -> [rules/security.md](rules/security.md)
-- **Integrating Firecrawl into an app, adding `FIRECRAWL_API_KEY` to `.env`, or choosing endpoint usage in product code** -> use the `firecrawl-build` skills (already installed alongside this CLI skill)
-
-## Output & Organization
-
-Unless the user specifies to return in context, write results to `.firecrawl/` with `-o`. Add `.firecrawl/` to `.gitignore`. Always quote URLs - shell interprets `?` and `&` as special characters.
-
-```bash
-firecrawl search "react hooks" -o .firecrawl/search-react-hooks.json --json
-firecrawl scrape "<url>" -o .firecrawl/page.md
-```
-
-Naming conventions:
-
-```
-.firecrawl/search-{query}.json
-.firecrawl/search-{query}-scraped.json
-.firecrawl/{site}-{path}.md
-```
-
-Never read entire output files at once. Use `grep`, `head`, or incremental reads:
-
-```bash
-wc -l .firecrawl/file.md && head -50 .firecrawl/file.md
-grep -n "keyword" .firecrawl/file.md
-```
-
-Single format outputs raw content. Multiple formats (e.g., `--format markdown,links`) output JSON.
-
-## Working with Results
-
-These patterns are useful when working with file-based output (`-o` flag) for complex tasks:
-
-```bash
-# Extract URLs from search
-jq -r '.data.web[].url' .firecrawl/search.json
-
-# Get titles and URLs
-jq -r '.data.web[] | "\(.title): \(.url)"' .firecrawl/search.json
-```
-
-## Parallelization
-
-Run independent operations in parallel. Check `firecrawl --status` for concurrency limit:
-
-```bash
-firecrawl scrape "<url-1>" -o .firecrawl/1.md &
-firecrawl scrape "<url-2>" -o .firecrawl/2.md &
-firecrawl scrape "<url-3>" -o .firecrawl/3.md &
-wait
-```
-
-For interact, scrape multiple pages and interact with each independently using their scrape IDs.
-
-## Credit Usage
-
-```bash
-firecrawl credit-usage
-firecrawl credit-usage --json --pretty -o .firecrawl/credits.json
-```

package/.agents/skills/firecrawl/rules/install.md

@@ -1,82 +0,0 @@
----
-name: firecrawl-cli-installation
-description: |
-  Install the official Firecrawl CLI and handle authentication.
-  Package: https://www.npmjs.com/package/firecrawl-cli
-  Source: https://github.com/firecrawl/cli
-  Docs: https://docs.firecrawl.dev/sdks/cli
----
-
-# Firecrawl CLI Installation
-
-## Quick Setup (Recommended)
-
-```bash
-npx -y firecrawl-cli@1.14.8 -y
-```
-
-This installs `firecrawl-cli` globally, authenticates via browser, and installs all skills.
-
-This setup is safe to re-run when the CLI is missing, stale, or only partially configured.
-
-If `firecrawl` is already installed and you want to update it first:
-
-```bash
-npm update -g firecrawl-cli
-```
-
-Skills are installed globally across all detected coding editors by default.
-
-To install skills manually:
-
-```bash
-firecrawl setup skills
-```
-
-## Manual Install
-
-```bash
-npm install -g firecrawl-cli@1.14.8
-```
-
-## Verify
-
-First check status:
-
-```bash
-firecrawl --status
-```
-
-Then run one small real request to prove install, auth, and output all work:
-
-```bash
-mkdir -p .firecrawl
-firecrawl scrape "https://firecrawl.dev" -o .firecrawl/install-check.md
-```
-
-The install is healthy when both commands succeed.
-
-## Authentication
-
-Authenticate using the built-in login flow:
-
-```bash
-firecrawl login --browser
-```
-
-This opens the browser for OAuth authentication. Credentials are stored securely by the CLI.
-
-### If authentication fails
-
-Ask the user how they'd like to authenticate:
-
-1. **Login with browser (Recommended)** - Run `firecrawl login --browser`
-2. **Enter API key manually** - Run `firecrawl login --api-key "<key>"` with a key from firecrawl.dev
-
-### Command not found
-
-If `firecrawl` is not found after installation:
-
-1. Ensure npm global bin is in PATH
-2. Try: `npx firecrawl-cli@1.14.8 --version`
-3. Reinstall: `npm install -g firecrawl-cli@1.14.8`