- name
SKILL.md
ไฟล์สกิลยังคงอยู่ในรีโพซิทอรีของผู้เผยแพร่
วางคำสั่งที่คัดลอกไว้ในเทอร์มินัล คำสั่งจะติดตั้ง SKILL.md นี้ลงในเอเจนต์ตัวนั้น
npx skills add galleonlabs/hypergrok-trading-desk --skill desk-post-trade-review -a cursor -yวางคำสั่งที่คัดลอกไว้ในเทอร์มินัล คำสั่งจะติดตั้ง SKILL.md นี้ลงในเอเจนต์ตัวนั้น
npx skills add galleonlabs/hypergrok-trading-desk --skill desk-post-trade-review -a claude-code -yวางคำสั่งที่คัดลอกไว้ในเทอร์มินัล คำสั่งจะติดตั้ง SKILL.md นี้ลงในเอเจนต์ตัวนั้น
npx skills add galleonlabs/hypergrok-trading-desk --skill desk-post-trade-review -a codex -yวางคำสั่งที่คัดลอกไว้ในเทอร์มินัล คำสั่งจะติดตั้ง SKILL.md นี้ลงในเอเจนต์ตัวนั้น
npx skills add galleonlabs/hypergrok-trading-desk --skill desk-post-trade-review -a grok -yส่งข้อความที่คัดลอกไว้ในแชต Grok Bot แล้ว Bot จะดึง SKILL.md นี้จาก GitHub และเพิ่มลงในสกิลที่ Bot ทุกตัวของคุณใช้ร่วมกัน
Install this skill: https://github.com/galleonlabs/hypergrok-trading-desk/tree/HEAD/skills/desk-post-trade-reviewจากผู้เผยแพร่
The journal is the desk's memory; the review is how the desk learns. Both come from the exchange record first and chat second, and both keep process and outcome apart.
/workspace/trading-desk/journal/YYYY-MM-DD.md, one file per active day, appended in time order. Entry types:
14:02 UTC HG-20260816-01 opened ETH-PERP long idea (user); status evidence
14:12 UTC HG-20260816-01 risk PASS 0.4827 ETH, stop 2,900, 0.5% risk stressed (risk-limits v3)
14:29 UTC HG-20260816-01 approval "approve HG-20260816-01" (user)
14:31 UTC HG-20260816-01 sent buy 0.4827 @ 3,000 Gtc + sl 2,900 (normalTpsl); cloid 0x9f3e...; oid 1839201122, sl waitingForFill
16:05 UTC HG-20260816-01 fill 0.4827 @ 3,000.0 maker, fee $0.29
09:12 UTC HG-20260816-01 closed tp 3,089.6, fee $1.44; position flat; sl 2,900 cancelled 09:13
10:00 UTC limits risk-limits v3 -> v4: max positions 3 -> 4 (user, reason: adding HYPE)
11:40 UTC incident INC-20260817-01 send timeout on HG-20260817-02; not on exchange, waited out expiresAfter 11:41, re-checked clean, re-approved and sent 11:47
18:00 UTC note maker entries at 10 bps depth filled within 2h on both attempts this week
Under a standing mandate, the approval line names the mandate instead of the user, and suspensions use a fixed form that scripts/standing_mandate.py reads:
08:15 UTC HG-20261116-03 approval mandate 2026-11-16 sha 5cbb094fee79f518 (mandate check all ok)
14:05 UTC mandate suspended mandate 2026-11-16 reason daily-loss-stop day pnl -2.1% of start-of-day equity
Rules: append only; corrections are new lines with correction:; every line has a UTC time and an id where one exists; no opinions in the journal (those go in reviews).
Trigger: a proposal reaches closed, or the user asks. Inputs, always listed with timestamps:
userFills / userFillsByTime for the window: price, size, fee, side, crossedhistoricalOrders and orderStatus by cloid: what rested when, what cancelleduserFunding for the holding windowCompute:
Grade:
Then one thing: a leak, a control that worked, or a break, chosen because it is repeatable. Not a list.
Write the review under ## review in the proposal file and send the block (format in agents/trade-reviewer.md) by DM to the Desk Lead and the user. Set status: closed.
From the journal, proposals and the exchange record for the week:
portfolio or start/end equityNo recommendations about what to trade. If the user asks, hand strategy questions to the Strategist and sizing questions to the Risk Manager.
For each INC-YYYYMMDD-NN: timeline (journal + exchange record), what the desk did, what the controls did, exposure during the incident, root cause where knowable, one corrective action with an owner and a date. Blameless in tone, exact in fact. Written to /workspace/trading-desk/journal/incidents/<id>.md and linked from the daily journal.
The Trade Reviewer's procedure for journaling desk activity and reviewing trades from the exchange record - process graded separately from outcome, execution costs measured, one repeatable finding per
---name: desk-post-trade-reviewdescription: The Trade Reviewer's procedure for journaling desk activity and reviewing trades from the exchange record -…---# skills/desk-post-trade-review/SKILL.mdภาพรวม
The Trade Reviewer's procedure for journaling desk activity and reviewing trades from the exchange record - process graded separately from outcome, execution costs measured, one repeatable finding per review, plus the weekly desk review. Use after any send, when a trade closes, on the weekly routine, or when the user asks "how did that go".
FAQ
ดาวน์โหลด skills/desk-post-trade-review/SKILL.md จากผู้เผยแพร่ หรือคัดลอกพาธแล้วเปิดรีโพซิทอรี PlugMCP แสดงรายการสกิลเท่านั้น ไม่ได้โฮสต์ไฟล์
ผู้เผยแพร่เก็บไว้ที่ https://github.com/galleonlabs/hypergrok-trading-desk
Claude, Cursor, Codex และ Grok Build อ่าน SKILL.md ที่คุณเพิ่มจากรีโพซิทอรีของผู้เผยแพร่ได้ ส่วน Grok Bot จะติดตั้งให้เมื่อคุณส่งลิงก์โฟลเดอร์ GitHub ของสกิลในแชต