openclaw - 💡(How to fix) Fix CLI search --limit accepts partially numeric values [3 pull requests]

Problem

openclaw plugins search and openclaw skills search parse --limit with Number.parseInt, so partially numeric values are accepted instead of rejected. That can turn typos such as 1abc into 1, or let non-positive values fall through to a default/remote behavior instead of telling the user the option is invalid.

Current behavior on upstream main

Checked on origin/main at 67c12e036802224e76547092938e3b9759846956.

$ pnpm openclaw skills search calendar --limit 1abc --json
{
  "results": [
    {
      "score": 4.39479889756764,
      "slug": "calendar",
      "displayName": "Calendar",
      "summary": "Calendar management and scheduling. Create events, manage meetings, and sync across calendar providers.",
      "version": null,
      "updatedAt": 1778491574637,
      "ownerHandle": "ndcccccc",
      "owner": {
        "handle": "ndcccccc",
        "displayName": "NDCCCCCC",
        "image": "https://avatars.githubusercontent.com/u/63100268?v=4"
      }
    }
  ]
}

$ pnpm openclaw plugins search calendar --limit 1abc --json
{
  "results": []
}

Both commands accept the invalid option and continue.

Expected behavior

--limit should require a whole positive integer and fail fast for values such as 1abc, 5.5, 0, or -1, before calling ClawHub.

Duplicate/collision checks

I searched current open/closed issues and open PRs for:

• "plugins search" "--limit"
• "skills search" "--limit"
• "plugins search" "1abc"
• "skills search" "1abc"
• open PRs touching plugins-cli.ts or skills-cli.ts

No exact issue or open PR was found for this CLI search limit parser behavior.