$npx -y skills add imsus/pi-extension-minimax-coding-plan-mcp --skill minimax-web-searchSearch the web for current information using the web_search tool
| 1 | # MiniMax Web Search Skill |
| 2 | |
| 3 | Use this skill when you need to find current, real-time, or authoritative information that may have changed since my knowledge cutoff. |
| 4 | |
| 5 | ## How to Use |
| 6 | |
| 7 | Call the `web_search` tool directly with a query: |
| 8 | |
| 9 | ``` |
| 10 | web_search({ query: "your search query" }) |
| 11 | ``` |
| 12 | |
| 13 | ## When to Use |
| 14 | |
| 15 | Use `web_search` when: |
| 16 | |
| 17 | - **Current events**: News, recent developments, latest releases |
| 18 | - **Fact verification**: Checking if information is still accurate |
| 19 | - **Technical updates**: New versions, patches, breaking changes |
| 20 | - **Dynamic content**: Prices, availability, schedules |
| 21 | - **Authoritative sources**: Official documentation, API references |
| 22 | |
| 23 | ## When NOT to Use |
| 24 | |
| 25 | Do NOT use `web_search` when: |
| 26 | |
| 27 | - **General knowledge** I likely know (historical facts, basic concepts) |
| 28 | - **Coding help** for common patterns (unless asking about latest practices) |
| 29 | - **Opinion-based questions** without specific recent information needs |
| 30 | - **Files already in context** or accessible via `read` tool |
| 31 | |
| 32 | ## Usage |
| 33 | |
| 34 | ``` |
| 35 | web_search({ |
| 36 | query: "your search query here" |
| 37 | }) |
| 38 | ``` |
| 39 | |
| 40 | ## API Details |
| 41 | |
| 42 | **Endpoint**: `POST {api_host}/v1/coding_plan/search` |
| 43 | |
| 44 | **Request Body**: |
| 45 | ```json |
| 46 | { |
| 47 | "q": "your search query" |
| 48 | } |
| 49 | ``` |
| 50 | |
| 51 | **Response Format**: |
| 52 | ```json |
| 53 | { |
| 54 | "organic": [ |
| 55 | { |
| 56 | "title": "Result Title", |
| 57 | "link": "https://example.com", |
| 58 | "snippet": "Brief description...", |
| 59 | "date": "2025-01-15" |
| 60 | } |
| 61 | ], |
| 62 | "related_searches": [ |
| 63 | {"query": "related query 1"}, |
| 64 | {"query": "related query 2"} |
| 65 | ], |
| 66 | "base_resp": { |
| 67 | "status_code": 0, |
| 68 | "status_msg": "success" |
| 69 | } |
| 70 | } |
| 71 | ``` |
| 72 | |
| 73 | ## Tips for Better Results |
| 74 | |
| 75 | 1. **Be specific**: "TypeScript 5.4 new features" vs "TypeScript updates" |
| 76 | 2. **Include context**: "React 19 server components vs client components" |
| 77 | 3. **Use recent keywords**: "2024" or "2025" when timing matters |
| 78 | 4. **Target authoritative sources**: Include product names, official sites |
| 79 | 5. **Use 3-5 keywords** for optimal results |
| 80 | |
| 81 | ## Examples |
| 82 | |
| 83 | ### Good Queries |
| 84 | - "Node.js 22 new features" |
| 85 | - "Claude Code vs pi coding agent 2025" |
| 86 | - "React 19 release date official" |
| 87 | - "Docker desktop alternatives 2024" |
| 88 | - "TypeScript 5.4 generics tutorial" |
| 89 | |
| 90 | ### Poor Queries |
| 91 | - "how to use TypeScript" (too general) |
| 92 | - "is Python popular" (opinion, not time-sensitive) |
| 93 | - "help me debug my code" (not a search task) |
| 94 | - "best programming language" (opinion-based) |
| 95 | |
| 96 | ## Response Format |
| 97 | |
| 98 | Results include: |
| 99 | - **Titles** and **URLs** for each result |
| 100 | - **Snippets** with relevant context |
| 101 | - **Dates** when available |
| 102 | - **Related searches** for follow-up queries |
| 103 | |
| 104 | You can use the suggestions to refine your search or ask the user which direction they'd like to explore. |
| 105 | |
| 106 | ## Error Handling |
| 107 | |
| 108 | - **Status code 1004**: Authentication error - check API key and region |
| 109 | - **Status code 2038**: Real-name verification required |
| 110 | - **Other errors**: Check Trace-Id in error message for support |