felo-ai 0.2.32 → 0.2.34

package/README.md

@@ -116,7 +116,7 @@ felo livedoc retrieve SHORT_ID --query "search query"
 
 ## Skills Overview
 
-5 skills across search, content generation, web scraping, and social media:
+7 skills across search, content generation, web scraping, social media, knowledge base, and shopping advice:
 
 | Skill                       | Description                                                   | Docs                            |
 | --------------------------- | ------------------------------------------------------------- | ------------------------------- |
@@ -126,6 +126,7 @@ felo livedoc retrieve SHORT_ID --query "search query"
 | **felo-youtube-subtitling** | Fetch YouTube video subtitles                                 | [→](./felo-youtube-subtitling/) |
 | **felo-x-search**           | Search X (Twitter) tweets, users, replies                     | [→](./felo-x-search/SKILL.md)   |
 | **felo-livedoc**            | Manage knowledge bases and semantic retrieval                 | [→](./felo-livedoc/)            |
+| **apple-buy-advisor**       | Research and compare Apple products before you buy            | [→](./apple-buy-advisor/)       |
 
 ---
 
@@ -144,6 +145,7 @@ felo livedoc retrieve SHORT_ID --query "search query"
 /plugin install felo-youtube-subtitling@felo-ai
 /plugin install felo-x-search@felo-ai
 /plugin install felo-livedoc@felo-ai
+/plugin install apple-buy-advisor@felo-ai
 ```
 
 ### ClawHub
@@ -157,6 +159,7 @@ clawhub install felo-web-fetch
 clawhub install felo-youtube-subtitling
 clawhub install felo-x-search
 clawhub install felo-livedoc
+clawhub install apple-buy-advisor
 ```
 
 ### Gemini CLI
@@ -168,6 +171,7 @@ cd felo-skills
 # Copy skill folders to Gemini CLI skills directory
 cp -r felo-search ~/.gemini/skills/
 cp -r felo-slides ~/.gemini/skills/
+cp -r apple-buy-advisor ~/.gemini/skills/
 ```
 
 ### OpenAI Codex
@@ -176,6 +180,7 @@ cp -r felo-slides ~/.gemini/skills/
 git clone https://github.com/Felo-Inc/felo-skills.git
 # Copy any skill folder to ~/.codex/skills/
 cp -r felo-search ~/.codex/skills/
+cp -r apple-buy-advisor ~/.codex/skills/
 ```
 
 ### OpenClaw
@@ -193,6 +198,7 @@ git clone https://github.com/Felo-Inc/felo-skills.git
 # Gemini CLI:  ~/.gemini/skills/
 # Codex:       ~/.codex/skills/
 cp -r felo-search ~/.claude/skills/
+cp -r apple-buy-advisor ~/.claude/skills/
 ```
 
 ---

package/apple-buy-advisor/README.md

@@ -0,0 +1,283 @@
+# Apple Buy Advisor Skill
+
+Research and compare Apple products to help users make informed buying decisions.
+
+## Directory Structure
+
+```
+apple-buy-advisor/
+├── SKILL.md          # Main skill definition
+└── README.md         # This file
+```
+
+## What It Does
+
+When a user asks about buying or comparing Apple products, this skill:
+
+1. **Fetches official specs** from Apple.com via `felo-web-fetch`
+2. **Searches user opinions** on X (Twitter) via `felo-x-search`
+3. **Researches community & professional reviews** via `felo-search`
+4. **Produces a structured report** — single product or head-to-head comparison
+5. **Saves the report automatically** to a local `.md` file and, when available, to Felo LiveDoc
+
+## Trigger Conditions
+
+Activates when users:
+- Mention an Apple product model by name (e.g. "iPhone 17", "MacBook Pro M4", "iPad Air 13")
+- Use a comparison pattern: `[Model A] vs [Model B]` (e.g. "iPhone 17 vs iPhone 17e")
+- Ask about buying, upgrading, or choosing between Apple products
+- Ask "Should I buy a MacBook Pro?", "Is iPhone 16 Pro worth it?", "Which Apple Watch should I get?"
+
+## Key Features
+
+✅ **Fresh data** — All specs fetched live from Apple.com via `felo-web-fetch`; never from training knowledge
+✅ **felo-web-fetch enforced** — All URL content retrieval goes through `felo-web-fetch` exclusively
+✅ **Multiple sources** — X, Reddit, MacRumors forums (personal) + 9to5Mac, The Verge, CNET (professional)
+✅ **Two report modes** — Single product analysis or A vs B head-to-head comparison
+✅ **Balanced** — Separates personal user feedback from professional reviews
+✅ **Clear recommendations** — Specific buying conditions with overall rating
+✅ **Multilingual** — Responds in the user's input language
+✅ **Auto-save workflow** — Always writes a local markdown report; also saves to Felo LiveDoc when configured
+
+## Report Formats
+
+**Single product:** Product Positioning → Specs Comparison → Real User Feedback → Professional Reviews → Buying Recommendation
+
+**A vs B comparison:** Head-to-Head Specs → User Feedback per product → Professional Verdict → Who Should Buy Which
+
+## Tools Used
+
+| Tool | Purpose |
+|------|---------|
+| `felo-web-fetch` | Fetch all URLs (Apple specs pages, review sites) |
+| `felo-x-search` | Real-time user reactions on X/Twitter |
+| `felo-search` | Reddit, MacRumors forums, professional review sites |
+| `felo-livedoc` | Create a LiveDoc and save the final report for sharing/reference |
+
+## Save Behavior
+
+After generating the report, the skill must complete a save step before ending:
+
+- Always save the full report to a local file named `apple-buy-advisor-<product-slug>-<YYYY-MM-DD>.md`
+- If `FELO_API_KEY` is configured, also create a Felo LiveDoc entry and save the report there
+- If LiveDoc save succeeds, the user is reminded they can open it at `https://felo.ai/livedoc/<short_id>`
+- If `FELO_API_KEY` is missing, LiveDoc save is skipped and the user is told why
+
+## Trusted Sources
+
+| Category | Sources |
+|----------|---------|
+| Personal reviews | X/Twitter, Reddit (r/apple, r/[product]), MacRumors Forums |
+| Professional reviews | 9to5Mac, The Verge, CNET, Tom's Guide, Engadget |
+
+## Quick Setup
+
+### Step 1: Install
+
+```bash
+npx skills add Felo-Inc/felo-skills --skill apple-buy-advisor
+```
+
+Or manually copy to your skills directory:
+
+```bash
+# Linux/macOS
+cp -r apple-buy-advisor ~/.claude/skills/
+
+# Windows (PowerShell)
+Copy-Item -Recurse apple-buy-advisor "$env:USERPROFILE\.claude\skills\"
+```
+
+### Step 2: Install required skills
+
+This skill depends on four other Felo skills. Install them all:
+
+```bash
+npx skills add Felo-Inc/felo-skills --skill felo-web-fetch
+npx skills add Felo-Inc/felo-skills --skill felo-search
+npx skills add Felo-Inc/felo-skills --skill felo-x-search
+npx skills add Felo-Inc/felo-skills --skill felo-livedoc
+```
+
+### Step 3: Get API Key
+
+1. Visit [felo.ai](https://felo.ai) and log in
+2. Click your avatar → **Settings** → **API Keys**
+3. Click **Create New Key** and copy it
+
+### Step 4: Configure
+
+```bash
+# Linux/macOS
+export FELO_API_KEY="your-api-key-here"
+
+# Make it permanent
+echo 'export FELO_API_KEY="your-api-key-here"' >> ~/.zshrc
+```
+
+```powershell
+# Windows PowerShell
+$env:FELO_API_KEY="your-api-key-here"
+```
+
+Restart Claude Code to load the environment variable.
+
+`FELO_API_KEY` is also used for the optional Felo LiveDoc auto-save step.
+
+### Step 5: Test
+
+```
+Should I buy the iPhone 17?
+```
+
+If you get a structured report with specs and reviews, plus a saved local `.md` file, you're all set.
+
+---
+
+## Usage Examples
+
+### Single Product
+
+**Is it worth buying?**
+```
+You: Is the iPhone 17e worth buying?
+Claude: ## iPhone 17e — Worth Buying?
+
+        ### Product Positioning
+        Apple's most affordable iPhone with A16 chip, targeting budget-conscious users.
+
+        ### Specs Comparison
+        | Spec       | iPhone 17e | iPhone 16  | Samsung S24 |
+        |------------|------------|------------|-------------|
+        | Processor  | A16 Bionic | A16 Bionic | Snapdragon 8 Gen 3 |
+        | RAM        | 6GB        | 6GB        | 12GB        |
+        | Capacity   | 128GB      | 128GB      | 128GB       |
+        | Battery    | 26h video  | 22h video  | 27h video   |
+        | Price      | $599       | $699       | $799        |
+
+        ### Real User Feedback
+        **Common Praise:**
+        - Performance: "Handles everything I throw at it" (Reddit r/apple)
+        - Value: "Best bang for buck in the iPhone lineup" (MacRumors forums)
+
+        **Common Complaints:**
+        - No ProMotion display: "60Hz feels dated at this price" (Reddit)
+        - Single camera: "Miss the ultrawide from my old phone" (X)
+
+        ### Buying Recommendation
+        **Buy if:** You want iPhone reliability without the Pro price tag
+        **Skip if:** You care about camera versatility or high refresh rate
+
+        **Overall Rating:** ⭐⭐⭐⭐☆ (4/5)
+```
+
+**Upgrade decision**
+```
+You: Should I upgrade from iPhone 14 to iPhone 17?
+Claude: For iPhone 14 → 17 upgrade:
+
+        Key gains: A18 chip (40% faster), 48MP camera, Action Button
+        Battery: +4h video playback
+        Price difference: ~$200 with trade-in
+
+        Worth it if: You use the camera heavily or notice slowdowns
+        Skip if: Your 14 still feels fast and camera is good enough
+
+        Verdict: Meaningful upgrade, but not urgent unless camera matters to you.
+```
+
+### Comparison (A vs B)
+
+**Model comparison**
+```
+You: iPhone 17 vs iPhone 17e
+Claude: ## iPhone 17 vs iPhone 17e — Which Should You Buy?
+
+        ### Head-to-Head Specs
+        | Spec      | iPhone 17   | iPhone 17e  | Winner     |
+        |-----------|-------------|-------------|------------|
+        | Processor | A18         | A16 Bionic  | iPhone 17  |
+        | RAM       | 8GB         | 6GB         | iPhone 17  |
+        | Display   | 6.1" OLED 60Hz | 6.1" OLED 60Hz | Tie   |
+        | Camera    | 48MP + 12MP | 48MP        | iPhone 17  |
+        | Battery   | 22h video   | 26h video   | iPhone 17e |
+        | Price     | $799        | $599        | iPhone 17e |
+
+        ### Who Should Buy Which
+        **Choose iPhone 17 if:** You want the latest chip and dual cameras
+        **Choose iPhone 17e if:** Budget is the priority and you don't need ultrawide
+
+        **Overall Verdict:** Pay the extra $200 for iPhone 17 if you use the camera daily.
+        Otherwise, 17e is excellent value.
+```
+
+**Mac comparison**
+```
+You: MacBook Air M3 vs MacBook Pro M4
+Claude: ## MacBook Air M3 vs MacBook Pro M4 — Which Should You Buy?
+
+        | Spec        | MacBook Air M3 | MacBook Pro M4 |
+        |-------------|----------------|----------------|
+        | Chip        | M3             | M4             |
+        | RAM (base)  | 8GB            | 16GB           |
+        | Display     | 13.6" Liquid Retina | 14.2" Liquid Retina XDR |
+        | Fan         | Fanless        | Active cooling |
+        | Battery     | 18h            | 24h            |
+        | Price       | $1,099         | $1,599         |
+
+        **Choose Air M3 if:** Light tasks, portability, budget-conscious
+        **Choose Pro M4 if:** Video editing, sustained workloads, need more RAM headroom
+```
+
+### Chinese input
+
+```
+You: iPhone 17 值得买吗？
+Claude: ## iPhone 17 — 值得购买吗？
+
+        ### 产品定位
+        苹果主力旗舰，搭载 A18 芯片，面向追求性能与相机体验的用户。
+
+        ### 规格对比
+        | 规格   | iPhone 17 | iPhone 16 | 三星 S25 |
+        |--------|-----------|-----------|---------|
+        | 处理器 | A18       | A16       | 骁龙 8 Elite |
+        | 内存   | 8GB       | 6GB       | 12GB    |
+        | 起售价 | ¥5,999    | ¥4,999    | ¥5,499  |
+
+        ### 购买建议
+        **适合购买：** 重度相机用户、从 iPhone 14 及更早机型升级
+        **不建议购买：** 已有 iPhone 16，提升有限
+
+        **综合评分：** ⭐⭐⭐⭐☆ (4/5)
+```
+
+### Common questions
+
+```
+You: Buy now or wait for iPhone 18?
+Claude: iPhone 18 is expected September 2026 (~6 months away.
+        Current deals on iPhone 17 are strong.
+
+        Buy now if: You need a phone today or find a good trade-in deal
+        Wait if: You can hold out 6 months and want the latest
+
+You: Is AirPods Pro 2 worth it over regular AirPods?
+Claude: AirPods Pro 2 vs AirPods 4:
+
+        ANC: Pro 2 significantly better (industry-leading)
+        Sound: Pro 2 wins, especially bass
+        Fit: Pro 2 with ear tips seals better
+        Price gap: ~$80
+
+        Worth it if: You commute, travel, or work in noisy environments
+        Skip if: You mostly use them at home or don't need ANC
+```
+
+---
+
+## Version
+
+- **Version:** 4.0
+- **Status:** Production Ready
+- **Last Updated:** March 2026

package/apple-buy-advisor/SKILL.md

@@ -0,0 +1,323 @@
+---
+name: apple-buy-advisor
+description: Research and compare Apple products to help decide if they're worth buying. Use when the user: (1) asks whether to buy a Mac, iPhone, iPad, Apple Watch, or AirPods; (2) wants to compare models; (3) seeks a buying recommendation; (4) mentions an Apple product model name or number (e.g. "iPhone 17", "MacBook Pro M4", "iPad Air 13"); (5) uses a comparison pattern like "X vs Y" where X or Y is an Apple product (e.g. "iPhone 17 vs iPhone 17e", "MacBook Air vs MacBook Pro"); (6) asks about upgrading, waiting, or which model to choose.
+allowed-tools: Bash(node:*) Bash(bash:*) Bash(curl:*) Bash(echo:*) Fetch(*) Write(*)
+metadata:
+  requires:
+    - felo-web-fetch
+    - felo-search
+    - felo-x-search
+    - felo-livedoc
+---
+
+# Apple Buy Advisor
+
+Research Apple products and produce a structured buying recommendation based on official specs, professional reviews, and real user feedback.
+
+**Language:** Detect the user's input language and respond entirely in that language. If the user writes in Chinese, respond in Chinese. If in English, respond in English. Apply this to all sections of the report.
+
+**Input Detection:** This skill activates when the user:
+
+- Mentions an Apple product model by name or number (e.g. "iPhone 17", "M4 MacBook Pro", "Apple Watch Series 10")
+- Uses a comparison pattern: `[Model A] vs [Model B]` (e.g. "iPhone 17 vs iPhone 17e")
+- Asks about buying, upgrading, or choosing between Apple products
+
+## Steps to Execute
+
+> **Completion rule:** The task is not complete after Step 5. You must execute Step 6 before ending the turn. Never stop at "I now have all the data needed. Let me compile the full report." or after showing the markdown report alone.
+
+### 0. Tool Usage Rule
+
+> **CRITICAL: Always use `felo-web-fetch` to retrieve any URL content.** Never use built-in WebFetch, curl, or any other tool to fetch web pages. All HTTP requests to external URLs — Apple specs pages, review sites, or any other URL — must go through `felo-web-fetch`.
+
+### 1. Fetch Official Specs
+
+Use `felo-web-fetch` in two steps:
+
+**Step 1a — Get model names from compare page** (to identify which models exist):
+
+- Mac: `https://www.apple.com/mac/compare/`
+- iPhone: `https://www.apple.com/iphone/compare/`
+- iPad: `https://www.apple.com/ipad/compare/`
+- Apple Watch: `https://www.apple.com/watch/compare/`
+- AirPods: `https://www.apple.com/airpods/compare/`
+
+Use this page only to identify the current model lineup. Do not extract specs from here.
+
+**Step 1b — Get full specs from the product specs page** (required for all spec values):
+
+- `https://www.apple.com/[product-model]/specs/`
+- Example: `https://www.apple.com/iphone-17e/specs/`, `https://www.apple.com/macbook-pro/specs/`
+
+Extract all specs exclusively from this page: processor, RAM, storage options (starting capacity), battery life, display specs, and pricing.
+
+> **CRITICAL:** Storage, RAM, and all other specs must come from the `/specs/` page only. Never use the compare page or training knowledge for spec values. If the specs page fails to load, explicitly state: "Unable to fetch current specs from Apple.com — specs may be inaccurate." Do not silently substitute any remembered values. **Always fetch via `felo-web-fetch`.**
+
+> **REQUIRED FIELDS for Mac / iPad / iPhone:** RAM (unified memory / memory) is a mandatory spec. It must always appear in the Specs Comparison table. If the `/specs/` page does not list RAM explicitly, state "RAM: not listed on specs page" — never omit the field or leave it blank.
+
+### 2. Search Personal User Reviews & Professional Reviews (run in parallel)
+
+Run all queries simultaneously to save time.
+
+**Personal user reviews** — `felo-x-search` (1 query):
+
+- `"[product]" review OR experience OR problem`
+
+**Personal user reviews** — `felo-search` (2 queries, run in parallel):
+
+- `site:reddit.com "[product]" review OR experience`
+- `site:forums.macrumors.com "[product]" review`
+
+**Professional reviews** — `felo-search` (1 query):
+
+- `site:9to5mac.com OR site:theverge.com OR site:cnet.com "[product]" review`
+
+> **Source filter — personal:** Only extract content from individual users (posts, comments, threads). Discard media articles.
+> **Source filter — professional:** Only extract editorial content. Discard user comments.
+
+### 3. Generate User Feedback Section (from personal sources in Step 2 only)
+
+Using **only** the personal user data from Step 2 (X, Reddit, MacRumors forums):
+
+- Extract recurring themes from individual user posts and comments
+- Group by sentiment: praise vs. complaints
+- Quote specific user language where possible
+- Apply frequency indicators based on how often a theme appears across sources
+- Attribute each point to its source platform
+
+### 4. Generate Professional Review Section (from professional sources in Step 2 only)
+
+Using **only** the professional review data from Step 2 (9to5Mac, The Verge, CNET):
+
+- Summarize each publication's key findings
+- Note where professional assessments agree or diverge
+- Highlight benchmark data or lab-tested metrics separately from subjective opinions
+
+### 5. Produce Report
+
+**If single product query:**
+
+```
+## [Product Name] — Worth Buying?
+
+### Product Positioning
+[One sentence: where this product sits in Apple's lineup]
+
+### Specs Comparison
+(Data source: Apple.com — Step 1)
+| Spec | This Product | Previous Gen | Competitor |
+|------|---|---|---|
+| Processor | ... | ... | ... |
+| RAM | ... | ... | ... |
+| Capacity | ... | ... | ... |
+| Battery | ... | ... | ... |
+| Price | ... | ... | ... |
+
+### Real User Feedback
+(Data source: X, Reddit, MacRumors forums — personal sources from Step 2)
+
+**Common Praise:**
+- [Theme]: [Specific quote or paraphrase — source: X / Reddit r/apple / MacRumors forums]
+
+**Common Complaints:**
+- [Theme]: [Specific quote or paraphrase — source: X / Reddit r/[product] / MacRumors forums]
+
+**Community Consensus:**
+[1-2 sentences synthesizing overall user sentiment, based on frequency across sources]
+
+### Professional Review Summary
+(Data source: 9to5Mac, The Verge, CNET — professional sources from Step 2)
+
+- **[Publication name]:** [Key finding or verdict]
+- **[Publication name]:** [Key finding or verdict]
+- **[Publication name]:** [Benchmark result or lab-tested metric]
+
+**Where pros agree:** [Common conclusion across publications]
+**Where pros diverge:** [Any notable disagreements, e.g. battery life estimates]
+
+### Buying Recommendation
+
+**Buy if:** [specific use case]
+**Skip if:** [specific concern]
+
+**Overall Rating:** ⭐⭐⭐⭐☆ (4/5)
+
+**Conclusion:** [Clear answer to user's question]
+```
+
+**If comparison query (A vs B):**
+
+```
+## [Product A] vs [Product B] — Which Should You Buy?
+
+### Head-to-Head Specs
+(Data source: Apple.com — Step 1)
+| Spec | [Product A] | [Product B] | Winner |
+|------|---|---|---|
+| Processor | ... | ... | ... |
+| RAM | ... | ... | ... |
+| Capacity | ... | ... | ... |
+| Battery | ... | ... | ... |
+| Price | ... | ... | ... |
+
+### Real User Feedback
+**[Product A] users say:**
+- Praise: ...
+- Complaints: ...
+
+**[Product B] users say:**
+- Praise: ...
+- Complaints: ...
+
+### Professional Review Summary
+- **[Publication]:** [Verdict on A vs B]
+
+### Who Should Buy Which
+
+**Choose [Product A] if:** [specific use case]
+**Choose [Product B] if:** [specific use case]
+
+**Overall Verdict:** [Clear recommendation with reasoning]
+```
+
+#### Key Principles
+
+- **Fresh data only** — Never rely on training knowledge for specs or prices
+- **Personal reviews first** — Show community feedback before professional reviews
+- **Source attribution** — Always cite where feedback comes from
+- **Frequency matters** — "Many users report..." vs "One user mentioned..."
+- **Balanced** — Include both praise and complaints
+- **User-focused** — Tailor to their specific needs
+
+#### Trusted Sources
+
+**Community (personal reviews):**
+
+- X/Twitter: Real-time reactions
+- Reddit: r/apple, r/[product]
+- MacRumors Forums: enthusiast depth
+
+**Professional reviews:**
+
+- Apple-focused: 9to5Mac, MacRumors
+- Tech media: The Verge, CNET, Tom's Guide, Engadget
+
+#### Display Strategy for Personal Reviews
+
+1. **Extract themes** from X, Reddit, MacRumors forums
+2. **Group by sentiment** — praise vs complaints
+3. **Quote specifically** — "Battery lasts 8-10 hours" beats "battery is good"
+4. **Show frequency** — note if an issue appears across multiple sources
+5. **Attribute sources** — "(Reddit, MacRumors forums)"
+
+Frequency language:
+
+- "Many users report..." (50%+)
+- "Some users report..." (20–50%)
+- "A few users report..." (5–20%)
+- "One user mentioned..." (<5%)
+
+#### Product Category Focus
+
+| Product     | Key Focus                            | Common Concerns                       |
+| ----------- | ------------------------------------ | ------------------------------------- |
+| Mac         | Performance, thermals, compatibility | Throttling, RAM/storage limits, ports |
+| iPhone      | Camera, battery, durability          | Battery degradation, heat             |
+| iPad        | Display, stylus, keyboard            | Software limits, value vs MacBook     |
+| Apple Watch | Battery, health tracking             | Battery claims vs reality             |
+| AirPods     | Sound, ANC, battery                  | Fit, durability, repairability        |
+
+#### Common User Questions
+
+**"Worth the upgrade?"** — Compare gains, cite user feedback on value, suggest who should/shouldn't upgrade.
+
+**"Buy now or wait?"** — Check upcoming releases, current deals, known issues with current gen.
+
+**"vs [competitor]?"** — Side-by-side table, user feedback on both, ecosystem considerations.
+
+**"Reliable/durable?"** — Search long-term reports, failure modes, user durability experiences.
+
+**"Good for [use case]?"** — Find users with same use case, highlight relevant specs and limitations.
+
+#### Handling Edge Cases
+
+**New product (<1 month):** Limited data — focus on early adopters, compare to previous gen, flag unknown long-term reliability.
+
+**Mature product (>1 year):** Rich data — look for retrospective reviews, known issues, upcoming replacements.
+
+**Discontinued:** Focus on retrospectives, compare to current alternatives, note support/repair considerations.
+
+**Conflicting sources:** Identify what they disagree on, look for patterns, present both sides with context (e.g. "Pro reviews show 12h; real-world Reddit reports 8–10h under typical load").
+
+## Step 6. Save Report (Mandatory)
+
+Step 6 is required. After generating the report in Step 5, immediately save it before ending the response. A report that is only displayed but not saved is incomplete. Execute the save steps sequentially.
+
+**6a — Save report to local `.md` file:**
+
+Write the full markdown report to a local file using the filename format:
+
+```
+apple-buy-advisor-<product-slug>-<YYYY-MM-DD>.md
+```
+
+Example: `apple-buy-advisor-iphone-17e-2026-03-20.md`
+
+Save the file in the current working directory. After writing, confirm to the user: "Report saved locally: `<filename>` ✓"
+
+> **Required behavior:** Do not ask the user whether to save. Perform the local save automatically every time. The final answer must not be sent until the file write succeeds or an explicit file-write failure is reported.
+
+**6b — Create a LiveDoc** (invoke `felo-livedoc` skill):
+
+```
+felo-livedoc create --name "Apple Buy Advisor" --description "Apple product research reports and buying recommendations"
+```
+
+Extract the `short_id` from the response.
+
+**6c — Add a text document** (invoke `felo-livedoc` skill with the `short_id` from 6b):
+
+```
+felo-livedoc add-doc <short_id> --title "<Product Name> — <YYYY-MM-DD>" --content "<full markdown report from Step 5>"
+```
+
+After success, confirm to the user:
+
+- "Report saved to Felo LiveDoc ✓"
+- "View it at: `https://felo.ai/livedoc/<short_id>`"
+
+> If `FELO_API_KEY` is not set, skip and inform the user: "Set FELO_API_KEY to enable auto-saving reports to LiveDoc."
+>
+> If LiveDoc save is skipped, local `.md` save is still mandatory and must already be completed.
+
+## Final Response Requirements
+
+- First show the full report from Step 5
+- Then confirm the local save result with the exact filename
+- Then confirm the LiveDoc save result, or explicitly state that it was skipped because `FELO_API_KEY` is missing
+- Never end with only the report body
+- Never claim completion unless Step 6 has been attempted
+
+## Checklist Before Delivery
+
+- [ ] Step 1: Specs fetched from Apple.com specs page (not from memory)
+- [ ] Step 1: RAM field included in Specs Comparison table for Mac / iPad / iPhone (mandatory)
+- [ ] Step 2: Personal user reviews collected from X + Reddit + forums (parallel queries)
+- [ ] Step 2: Professional reviews collected from 3+ media publications (parallel queries)
+- [ ] Step 3: User feedback section built exclusively from personal sources — no media mixed in
+- [ ] Step 4: Professional review section built exclusively from media sources — no user posts mixed in
+- [ ] Recurring themes identified and grouped by sentiment
+- [ ] Every claim attributed to its source
+- [ ] Frequency indicators used appropriately
+- [ ] User's specific needs addressed
+- [ ] Clear, direct answer to their question
+- [ ] Step 6: Report saved to local `.md` file in current working directory
+- [ ] Step 6: Report saved to Felo LiveDoc (or user notified if API key missing)
+
+## Do's and Don'ts
+
+✅ Always fetch fresh specs | ❌ Never use training knowledge for specs/prices
+✅ Multiple sources | ❌ Never rely on a single source
+✅ Cite sources | ❌ Never present opinions as facts
+✅ Show both sides | ❌ Never ignore negative feedback
+✅ Mention alternatives | ❌ Never over-weight isolated complaints

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "felo-ai",
-  "version": "0.2.32",
+  "version": "0.2.34",
   "description": "Felo AI CLI - real-time search, PPT generation, SuperAgent conversation, LiveDoc management, web fetch, YouTube subtitles, LiveDoc knowledge base, and X (Twitter) search from the terminal",
   "type": "module",
   "main": "src/cli.js",