@recapt/mcp 0.0.42 → 0.0.43

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@recapt/mcp",
-  "version": "0.0.42",
+  "version": "0.0.43",
   "description": "MCP exposing recapt behavioral intelligence to AI coding agents",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",

package/skills/regression-hunt.md

@@ -47,7 +47,7 @@ Investigate the specific issue:
 
 - Search: "console errors" → `get_console_errors` (often the culprit)
 - Search: "dead clicks" → `get_dead_clicks` (broken interactions)
-- Search: "investigate issue" → `investigate_issue`
+- Search: "investigate issue" to discover available investigation tools
 
 ### 5. Examine Sessions
 
@@ -114,7 +114,7 @@ Once you've identified the cause:
 | Scope      | "element friction"  | `get_element_friction`                   |
 | Root cause | "console errors"    | `get_console_errors`                     |
 | Root cause | "dead clicks"       | `get_dead_clicks`                        |
-| Root cause | "investigate issue" | `investigate_issue`                      |
+| Root cause | "investigate issue" | Use `search_tools` to discover investigation tools |
 | Sessions   | "session details"   | `search_sessions`, `get_session_details` |
 | Fix        | "propose fix"       | `propose_fix`                            |
 | Track      | "deployment"        | `confirm_deployment`, `evaluate_fix`     |

package/skills/self-improvement.md

@@ -301,7 +301,7 @@ The organization will review issues in their dashboard and manually:
 
 For each high-priority issue or opportunity, search for investigation tools:
 
-- Search: "investigate issue" → `investigate_issue`, `validate_issue`
+- Search: "investigate issue" to discover available investigation and validation tools
 - This provides detailed context: affected sessions, element interactions, timing patterns
 
 For flow opportunities, also consider:
@@ -383,11 +383,7 @@ You are running in Fix Mode with GitHub connected. Use the organization's GitHub
 
 #### 1. Investigate the Issue
 
-Get detailed context about the issue:
-
-```
-investigate_issue({ issue_id: "<issue_id>" })
-```
+Use `search_tools` to find relevant investigation tools and perform a thorough investigation of the issue.
 
 This provides:
 
@@ -398,24 +394,13 @@ This provides:
 
 #### 2. Check Similar Fixes
 
-Before implementing, check if similar issues have been fixed before:
-
-```
-get_similar_fixes({
-  page_path: "<page_path>",
-  category: "<issue_category>"
-})
-```
+Before implementing, use `search_tools` to find remediation history tools and check if similar issues have been fixed before.
 
 Learn from past attempts - what worked, what didn't.
 
 #### 3. Validate the Issue
 
-Confirm the issue is still occurring and worth fixing:
-
-```
-validate_issue({ issue_id: "<issue_id>" })
-```
+Use `search_tools` to find validation tools and confirm the issue is still occurring and worth fixing.
 
 If the issue has resolved itself or has very low occurrence, you may skip fixing it.
 
@@ -605,8 +590,8 @@ If the user agrees:
 | Flows         | "analyze flow"       | `analyze_flow`, `get_flow_friction`                                                                     |
 | Personas      | "personas"           | `discover_personas`                                                                                     |
 | Compare       | "compare cohorts"    | `compare_cohorts`                                                                                       |
-| Investigate   | "investigate issue"  | `investigate_issue`, `validate_issue`                                                                   |
+| Investigate   | "investigate issue"  | Use `search_tools` to discover available investigation and validation tools                              |
 | Triage        | "dismiss issue"      | `dismiss_issue`, `mark_intended_behavior`                                                               |
-| Fix           | "propose fix"        | `propose_fix`, `get_similar_fixes`, `get_fix_history`                                                   |
+| Fix           | "propose fix"        | `propose_fix`                                                                                           |
 | Track         | "deployment"         | `confirm_deployment`, `evaluate_fix`, `list_pending_fixes`                                              |
 | Learn         | "site knowledge"     | `get_site_knowledge`, `add_site_knowledge`                                                              |