abel-ask

Name: abel-ask
Author: Abel-ai-lab

17stars0forks

How to install abel-ask?

abel-ai-lab/predict-anything/abel-ask

$npx -y skills add Abel-ai-lab/predict-anything --skill abel-ask

Installs into the current project.

Summary

Use when the user wants an Abel causal map, graph exploration, target or candidate discovery, company/market mechanism read, or life/business investment decision read rather than auth setup or tradable strategy discovery.

Files · 1

View on GitHub

SKILL.md

1	Abel Ask explains mechanisms, candidate lists, and decision rules. Finance and
2	crypto nodes are proxy vocabulary, not the product. Do not use Ask for pure fact
3	lookup, news recap, operational how-to, buy/sell guidance, alpha, backtests,
4	backtesting, options strategy, Sharpe/MaxDD, or tradable strategy validation.
5
6	If the request needs auth repair, stop and use `abel-auth`. If the request asks
7	for tradable validation, use `abel-invest`.
8
9	## 1. Classify
10
11	Classify in two layers.
12
13	Product intent:
14
15	- `direct_graph_read`: literal node, ticker, path, neighborhood, driver, or CAP
16	graph fact. Read `references/intents/direct-graph-read.md`.
17	- `candidate_discovery`: companies, assets, sectors, beneficiaries, suppliers,
18	competitors, or "where are the opportunities?" Read
19	`references/intents/candidate-discovery.md`.
20	- `life_investment_decision`: education, career, consumption, housing,
21	entrepreneurship, health, attention, or other opportunity-cost decisions. Read
22	`references/intents/life-investment-decision.md`.
23	- `general_causal_read`: mechanism questions such as "how does X affect Y?" Read
24	`references/intents/general-causal-read.md`.
25
26	Execution route:
27
28	- `direct_graph`: user supplied a graph-ready node, ticker, asset, path, driver,
29	or neighborhood. Read `references/routes/direct-graph.md`.
30	- `proxy_routed`: the real-world issue must first be mapped into graph anchors,
31	proxies, or web-grounded mechanism evidence. Read
32	`references/routes/proxy-routed.md`.
33
34	Most `candidate_discovery`, `life_investment_decision`, and
35	`general_causal_read` requests are `proxy_routed`. A ticker can still be
36	`proxy_routed` when it is only a proxy inside a broader question.
37
38	## Data API
39
40	When supplemental structured data is needed, read
41	`references/data-api-usage.md` and use `scripts/data_api.py`. The script calls
42	the Abel gateway with `Authorization: Bearer <api-key>` and discovers the
43	current key's available datasets through the catalog endpoint.
44
45	## 2. Work The Question
46
47	- For proxy-routed questions, generate the obvious mechanism, a second-order
48	mechanism, a contrarian, and a confounder before graph work.
49	- Use narrative CAP only as a scout when anchors are unclear or a broad theme
50	needs candidate seeds. Read `references/narrative-probe-usage.md` only then.
51	- Use graph structure for confidence: `node_description`, `graph.neighbors`,
52	`graph.paths`, `graph.markov_blanket`, `discover_consensus`,
53	`discover_deconsensus`, `discover_fragility`.
54	- Use web grounding when freshness, policy, prices, current events, or personal
55	decision mechanics materially affect the answer. Read
56	`references/web-grounding.md`.
57	- Do not declare graph-sparse until proxy and capillary discovery are exhausted.
58	- Do not carry raw node ids, graph paths, payloads, or model decimals into the
59	normal visible answer.
60
61	## 3. Handoff
62
63	Do not upsell another skill by default. Handoff only when intent moves layers:
64
65	- mechanism read -> candidate discovery: offer to continue if candidates are the
66	natural next step.
67	- candidate discovery -> `abel-invest`: switch when the user asks which one to
68	buy/trade, whether it has alpha, or whether it can be backtested.
69	- direct graph read -> `abel-invest`: switch when a ticker driver read becomes a
70	trading request.
71	- life investment decision: stay in Ask unless the user explicitly asks to turn
72	it into a market trade or strategy.
73
74	## 4. Write
75
76	Before finalizing, read:
77
78	- `references/rendering.md` for visible/internal separation
79	- `assets/report-guide.md` for the compact output contract
80
81	Default to the main answer only. Do not emit appendices, trace blocks, probe
82	transcripts, raw payloads, or rendering scratch work unless the user explicitly
83	asks for trace, debug output, evidence details, reproducibility, or raw output.

People who liked this also viewed

6 picks

Type

abel-ask

17stars0forks

View on GitHub

How to install abel-ask?

abel-ai-lab/predict-anything/abel-ask

$npx -y skills add Abel-ai-lab/predict-anything --skill abel-ask

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	Abel Ask explains mechanisms, candidate lists, and decision rules. Finance and
2	crypto nodes are proxy vocabulary, not the product. Do not use Ask for pure fact
3	lookup, news recap, operational how-to, buy/sell guidance, alpha, backtests,
4	backtesting, options strategy, Sharpe/MaxDD, or tradable strategy validation.
5
6	If the request needs auth repair, stop and use `abel-auth`. If the request asks
7	for tradable validation, use `abel-invest`.
8
9	## 1. Classify
10
11	Classify in two layers.
12
13	Product intent:
14
15	- `direct_graph_read`: literal node, ticker, path, neighborhood, driver, or CAP
16	graph fact. Read `references/intents/direct-graph-read.md`.
17	- `candidate_discovery`: companies, assets, sectors, beneficiaries, suppliers,
18	competitors, or "where are the opportunities?" Read
19	`references/intents/candidate-discovery.md`.
20	- `life_investment_decision`: education, career, consumption, housing,
21	entrepreneurship, health, attention, or other opportunity-cost decisions. Read
22	`references/intents/life-investment-decision.md`.
23	- `general_causal_read`: mechanism questions such as "how does X affect Y?" Read
24	`references/intents/general-causal-read.md`.
25
26	Execution route:
27
28	- `direct_graph`: user supplied a graph-ready node, ticker, asset, path, driver,
29	or neighborhood. Read `references/routes/direct-graph.md`.
30	- `proxy_routed`: the real-world issue must first be mapped into graph anchors,
31	proxies, or web-grounded mechanism evidence. Read
32	`references/routes/proxy-routed.md`.
33
34	Most `candidate_discovery`, `life_investment_decision`, and
35	`general_causal_read` requests are `proxy_routed`. A ticker can still be
36	`proxy_routed` when it is only a proxy inside a broader question.
37
38	## Data API
39
40	When supplemental structured data is needed, read
41	`references/data-api-usage.md` and use `scripts/data_api.py`. The script calls
42	the Abel gateway with `Authorization: Bearer <api-key>` and discovers the
43	current key's available datasets through the catalog endpoint.
44
45	## 2. Work The Question
46
47	- For proxy-routed questions, generate the obvious mechanism, a second-order
48	mechanism, a contrarian, and a confounder before graph work.
49	- Use narrative CAP only as a scout when anchors are unclear or a broad theme
50	needs candidate seeds. Read `references/narrative-probe-usage.md` only then.
51	- Use graph structure for confidence: `node_description`, `graph.neighbors`,
52	`graph.paths`, `graph.markov_blanket`, `discover_consensus`,
53	`discover_deconsensus`, `discover_fragility`.
54	- Use web grounding when freshness, policy, prices, current events, or personal
55	decision mechanics materially affect the answer. Read
56	`references/web-grounding.md`.
57	- Do not declare graph-sparse until proxy and capillary discovery are exhausted.
58	- Do not carry raw node ids, graph paths, payloads, or model decimals into the
59	normal visible answer.
60
61	## 3. Handoff
62
63	Do not upsell another skill by default. Handoff only when intent moves layers:
64
65	- mechanism read -> candidate discovery: offer to continue if candidates are the
66	natural next step.
67	- candidate discovery -> `abel-invest`: switch when the user asks which one to
68	buy/trade, whether it has alpha, or whether it can be backtested.
69	- direct graph read -> `abel-invest`: switch when a ticker driver read becomes a
70	trading request.
71	- life investment decision: stay in Ask unless the user explicitly asks to turn
72	it into a market trade or strategy.
73
74	## 4. Write
75
76	Before finalizing, read:
77
78	- `references/rendering.md` for visible/internal separation
79	- `assets/report-guide.md` for the compact output contract
80
81	Default to the main answer only. Do not emit appendices, trace blocks, probe
82	transcripts, raw payloads, or rendering scratch work unless the user explicitly
83	asks for trace, debug output, evidence details, reproducibility, or raw output.

People who liked this also viewed

6 picks

Type