@sureshotlabs/hunch-agent-tools 0.1.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json ADDED
@@ -0,0 +1,41 @@
1
+ {
2
+ "name": "@sureshotlabs/hunch-agent-tools",
3
+ "version": "0.1.1",
4
+ "description": "Public read-only MCP server and CLI for Hunch prediction-market research.",
5
+ "license": "UNLICENSED",
6
+ "type": "module",
7
+ "bin": {
8
+ "hunch-agent-tools": "./build/hunch-mcp.js",
9
+ "hunch-mcp": "./build/hunch-mcp.js",
10
+ "hunch-agent": "./build/hunch-agent.js"
11
+ },
12
+ "files": [
13
+ "build",
14
+ "skills",
15
+ "README.md"
16
+ ],
17
+ "keywords": [
18
+ "hunch",
19
+ "prediction-markets",
20
+ "mcp",
21
+ "mcp-server",
22
+ "model-context-protocol",
23
+ "codex",
24
+ "trading-research"
25
+ ],
26
+ "engines": {
27
+ "node": ">=20.19.0"
28
+ },
29
+ "repository": {
30
+ "type": "git",
31
+ "url": "git+ssh://git@github.com/x0rb0t/hunch-agent-tools.git"
32
+ },
33
+ "homepage": "https://github.com/x0rb0t/hunch-agent-tools#readme",
34
+ "bugs": {
35
+ "url": "https://github.com/x0rb0t/hunch-agent-tools/issues"
36
+ },
37
+ "publishConfig": {
38
+ "access": "public",
39
+ "provenance": true
40
+ }
41
+ }
@@ -0,0 +1,67 @@
1
+ ---
2
+ name: hunch-trading
3
+ description: Use when an agent needs to search public Hunch markets, inspect market/event/cluster data, read public wallet intelligence, use Hunch MCP or CLI tools, or compare public prediction-market context. This skill is read-only and must not claim to log in, read private accounts, create intents, execute, trade, bridge, redeem, transfer, withdraw, convert, fund, or sign.
4
+ metadata: {"openclaw":{"requires":{"bins":["node"]}}}
5
+ ---
6
+
7
+ # Hunch Trading
8
+
9
+ Use MCP tools first when available. If MCP is unavailable, use the bundled
10
+ `scripts/hunch` wrapper. It runs the bundled skill CLI when this folder is
11
+ installed by itself, or the plugin CLI when installed through the Codex plugin.
12
+
13
+ ## Boundary
14
+
15
+ - Public read-only Hunch research, discovery, tracking, wallet-intel, signal,
16
+ holder, price-history, and trade-tape inspection.
17
+ - No login flow.
18
+ - No private account reads.
19
+ - No intents, funding plans, review links, execution, trading, bridging,
20
+ redemption, transfers, withdrawals, conversions, funding, or signing.
21
+ - Do not ask the user to paste secrets, session tokens, private keys, wallet
22
+ signatures, or approval payloads into chat.
23
+
24
+ ## Workflow
25
+
26
+ 1. Browse or search with `hunch_browse_discovery`, `hunch_search_discovery`, or
27
+ CLI `discovery-browse` / `discovery-search`. Discovery returns event-shaped
28
+ rows even when `view=markets`; fetch `hunch_get_market_detail` for one flat
29
+ market object.
30
+ 2. Fetch stable details with `hunch_get_market_detail`,
31
+ `hunch_get_event_detail`, or CLI `market-detail` / `event-detail`. Use
32
+ `marketsPreviewLimit` on event detail when compact output is still too
33
+ large.
34
+ 3. Use `hunch_get_discovery_top_lists`, `hunch_get_discovery_map`, and
35
+ `hunch_get_arbitrage_clusters` for discovery, map, and arbitrage context.
36
+ 4. Use `hunch_get_market_alternatives` when the user wants exact cross-venue
37
+ alternatives for one known market ID, including midpoint spread, venue
38
+ badges/icons, and Hunch market links.
39
+ 5. Use `hunch_get_similar_events`, `hunch_get_similar_markets`,
40
+ `hunch_get_event_price_history`, `hunch_get_market_price_history`,
41
+ `hunch_get_market_holders`, `hunch_get_signals`, and `hunch_get_trades` for
42
+ public event-page context such as the chart, similar markets, holders, trade
43
+ tape, and catalyst/risk/update notes.
44
+ 6. Use `hunch_get_tracking_overview`, `hunch_get_wallet_intel`,
45
+ `hunch_get_wallet_activity`, `hunch_get_wallet_positions`,
46
+ `hunch_get_wallet_series`, and `hunch_get_wallet_signals` for tracking-page
47
+ and public wallet-intel workflows. Public wallet tools accept a Hunch UUID
48
+ `walletId`; most can also resolve `address` plus optional `chain`.
49
+ 7. Use compact results by default. Request `standard` when descriptions or
50
+ metadata matter, and `full` only for debugging or exact backend payloads.
51
+ 8. Present titles, venues, odds/metrics, and Hunch links first. Use raw IDs only
52
+ as secondary technical references when useful.
53
+
54
+ ## Tool Selection Rules
55
+
56
+ - For market research, search or browse first, then fetch market/event detail.
57
+ - Use alternatives for exact cross-venue equivalents.
58
+ - Use arbitrage clusters for broad mispricing discovery.
59
+ - Use similar tools for semantic discovery.
60
+ - For public wallet intelligence, use wallet tools.
61
+ - For recent public market tape, use `hunch_get_trades`.
62
+ - If the user asks for private account state or execution, explain that this
63
+ public package is read-only and does not include that workflow.
64
+
65
+ ## References
66
+
67
+ - Read `references/tools.md` for CLI commands and MCP tool names.
@@ -0,0 +1,7 @@
1
+ interface:
2
+ display_name: "Hunch Trading"
3
+ short_description: "Use public Hunch market research and wallet-intel tools"
4
+ default_prompt: "Use $hunch-trading to research active Hunch markets and public wallet intelligence."
5
+
6
+ policy:
7
+ allow_implicit_invocation: true