Update to Openhandle

{
  "description": "Use when the user asks for public Instagram, TikTok, X (Twitter), or Reddit data (profiles, posts, comments, followers, search, trends), or about their Openhandle account (balance, usage, spend, request history, failed requests, API keys). Covers tool choice, Test versus Live, cost, paging, and errors for the openhandle MCP server.",
  "included_files": [],
  "name": "openhandle",
  "skill_md_contents": "---\nname: openhandle\ndescription: Use when the user asks for public Instagram, TikTok, X (Twitter), or Reddit data (profiles, posts, comments, followers, search, trends), or about their Openhandle account (balance, usage, spend, request history, failed requests, API keys). Covers tool choice, Test versus Live, cost, paging, and errors for the openhandle MCP server.\n---\n\n# Openhandle\n\nThe `openhandle` MCP server gives you two groups of tools.\n\n- **Platform tools** read public social data. Each name starts with the platform, for example `instagram_get_profile`, `tiktok_search_posts`, `twitter_list_followers`, and `reddit_profile_get`. Each tool is one REST endpoint with the same inputs and answers.\n- **Account tools** read the user's own Openhandle workspace: `account_get_balance`, `account_get_usage`, `account_list_requests`, `account_get_request`, and `account_list_api_keys`. They are free and never touch social platforms.\n\nIf no Openhandle tools are visible, tell the user to connect Openhandle and approve in the browser. In Claude Code they run `/mcp` and pick `openhandle`. In ChatGPT they open the Openhandle plugin and connect it.\n\n## Test or Live\n\nThe credential picks the environment. Never send an environment argument.\n\n- Every result has `environment` in its metadata. Tell the user which one you used when it matters.\n- **Test** returns synthetic data and costs nothing. Real handles return not found in Test. Call `find_test_data` first to get a working input, for example `{\"operation\": \"instagram.profile.get\", \"limit\": 1}`.\n- **Live** returns real public data and uses the user's balance.\n- To switch, the user disconnects Openhandle, connects again, and picks the other environment on the approval screen.\n\n## Inputs\n\n- Profiles take `identifier` as `@username` or the raw platform ID. Posts take the native post ID, or the shortcode on Instagram. Never pass a URL. Take the handle or ID out of a URL first.\n- `freshness` controls cache age: `live`, `24h` (default), `7d`, or `30d`. Older answers cost less and a `30d` cache hit is free. Use `live` only when the user needs data from this minute.\n- List tools return a cursor. Pass it back as `cursor` for the next page. Fetch more pages only when the user needs them, because each page is one billed call in Live.\n\n## Answers\n\n- `null` means the platform does not expose the value. It does not mean zero. Say \"not available\", never \"0\".\n- Error answers carry a stable `code`, such as `PROFILE_NOT_FOUND` or `PROFILE_PRIVATE`. Explain the code in plain words. These definitive answers are billed in Live. Provider failures and internal errors are free.\n- Result metadata has `requestId`, `actualCharge`, and `liveEquivalentPrice`. When the user asks what a call cost, read `actualCharge`.\n\n## Account questions\n\n- \"How much credit do I have left?\" → `account_get_balance`.\n- \"What did I spend this week?\" or \"Which endpoints do I use most?\" → `account_get_usage` with `from` and `to` as `YYYY-MM-DD`. Set `groupBy` to `operation`, `platform`, `api_key`, or `source`.\n- \"Why did my requests fail?\" → `account_list_requests` with `status` set to `client_error` or `server_error`, then `account_get_request` for one `requestId`.\n- \"Which keys are close to their cap?\" → `account_list_api_keys`. Secrets are never returned.\n\nUsage, requests, and keys cover the credential's environment only. The balance is shared by Test and Live.\n\nIf an account tool says the connection lacks the `read:account` scope, tell the user to disconnect Openhandle and connect again. If it says the user may not view the data, the user who approved the connection no longer has that access in the workspace.\n\n## Limits\n\n- The tools read public data only. They cannot post, follow, like, or read private accounts.\n- The tools cannot top up the balance, create keys, or change settings. Send the user to https://app.openhandle.dev for that.\n"
}