skills/blackforge-so__skill
1
0
Fork 0
mirror of https://github.com/blackforge-so/skill.git synced 2026-09-20 12:39:04 +08:00
Code Issues Packages Projects Releases Wiki Activity

fix: don't trigger on a pure trade recommendation (Marc's call)

Browse Source 
SKILL.md said to hold the measurement framing "even if the user's own question is phrased
as a trading question", while evals/trigger-eval.json marks "should i buy ETH right now?
give me a trade recommendation" as should_trigger:false. The two contradicted, and the eval
is what tunes the trigger description.

Marc's decision: the eval is right. The framing rule now draws the line explicitly — hold
it when there is a real market-data question wearing trading clothes ("is there a big sell
wall on DOGE, should I be worried?"), but a recommendation request with no data question
inside it is not a BlackForge question at all. Do not trigger, and do not reach for market
data to dress up an answer.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Marc
2026-07-28 16:20:58 +02:00
parent cf31829509
commit e2b9229c06
1 changed files with 8 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
SKILL.md
+8 -2
View File
@@ -39,8 +39,14 @@ It describes what happened in the book and on the tape — it does not tell the
next or what to trade. Do not describe any column, or the data as a whole, using the words **signal,
pump, anomaly, probability-scored, alpha, prediction, detection, or alert**, and do not imply
the data forecasts or recommends anything. Say what was *measured* ("bid depth within 5% fell from X
to Y"), not what it *means for a trade*. This framing is the whole point of the skill — hold it even
if the user's own question is phrased as a trading question; answer with the measurement.
to Y"), not what it *means for a trade*. This framing is the whole point of the skill.
**Where the line falls.** If the question contains a real market-data question wearing trading
clothes — "is there a big sell wall on DOGE, should I be worried?" — hold the framing and answer
with the measurement. But a request for a **recommendation with no data question inside it**
("should I buy ETH right now?") is **not** a BlackForge question: do not trigger on it, and do not
reach for market data to dress up an answer. Say plainly that you do not give trade advice, and
offer to show what the book and the tape actually measured if that would help.
("Flag" is the one exception, and only in its literal sense: `qualityFlags` is a real column and a
flagged *bucket* is a statement about data quality, never about the market.)