[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7348EHTWS9BXE2RSGS94D97":3,"skill-same:01M7348EHTWS9BXE2RSGS94D97":58},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7348EHTWS9BXE2RSGS94D97","research-call-tracker",null,"Log, update, and close published research calls and positions in shared-brain ledgers (Operations\u002FResearch\u002FCall Tracker.md and Trade Journal.md), and compute the measured win rate. Use whenever a research note, market call, thesis, or trade idea is published or shipped; when a position opens, closes, or hits a stop\u002Fkill condition; or when asked \"what's our win rate\", \"log this call\", \"update the tracker\", or \"close the position\".","LiamVisionary\u002Fhivemindos","LiamVisionary","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F102138294?v=4","01M73379NZZ99TT4ZS17XR3Q9D","01M73379PX6AKQNWN05VNSYRXW",13,"MIT","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Fhivemindos\u002Fblob\u002Fmain\u002Fpackaged-skills\u002Foptional\u002Fresearch\u002Fhivemindos\u002Fresearch-call-tracker\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: research-call-tracker\ndescription: Log, update, and close published research calls and positions in shared-brain ledgers (Operations\u002FResearch\u002FCall Tracker.md and Trade Journal.md), and compute the measured win rate. Use whenever a research note, market call, thesis, or trade idea is published or shipped; when a position opens, closes, or hits a stop\u002Fkill condition; or when asked \"what's our win rate\", \"log this call\", \"update the tracker\", or \"close the position\".\n---\n\n# Research Call Tracker\n\nOutcome accountability for research. A researcher who publishes calls without tracking them has no feedback loop between thesis quality and results — win rate becomes remembered instead of measured. This skill maintains two ledgers in the shared brain vault:\n\n- `Operations\u002FResearch\u002FCall Tracker.md` — the research record: one row per published call.\n- `Operations\u002FResearch\u002FTrade Journal.md` — the position record: one row per actual position, with entry discipline.\n\nIf either ledger does not exist yet, seed it from the matching file in this skill's `templates\u002F` folder (copy verbatim, then set the `Last updated` date). Never invent a different table shape — future sessions and stats depend on the columns staying stable.\n\n## The publish-time rule (fail-closed)\n\nA research call is not \"published\" until its Call Tracker row exists. Log the row **at publish time**, never retroactively — the entire value of the ledger is that conviction tier, entry zone, stop, and kill conditions were committed before the outcome was known. If a note ships through you and has no row, that is a blocker to surface, not a detail to skip.\n\n## Logging a new call\n\nAppend a row with: date (absolute, YYYY-MM-DD), asset, venue published to, conviction tier (`High` \u002F `Medium` \u002F `Speculative` — exactly one, always), entry zone, stop, target(s), status `Watching` or `Open`, thesis in one line, the sharpest kill condition, and a link to the adversarial verdict file (from the `kill-my-thesis` skill, if installed) or the note itself.\n\nJournal entry: only if there is a real trade setup (entry + confirmation trigger + stop). Otherwise the call is research-only; `skip` is a valid outcome.\n\n## Updating and closing\n\n- `Watching → Open` when the confirmation trigger fires; the journal row must carry a live stop before it reads `Open`.\n- Close with `Closed (Win)` \u002F `Closed (Loss)` \u002F `Closed (BE)` plus outcome % in the tracker, and a one-sentence post-mortem in the journal: what the thesis got right, what it missed, disciplined or emotional exit.\n- A kill condition firing is a close signal, not a debate prompt. Surface it to the user the day it fires.\n\n## Stats\n\nRecompute the tracker's Stats block whenever any call closes: total, closed count by outcome, win rate (wins ÷ closed, BE excluded from both sides), average return on closed. Only Closed rows count — open positions are hope, not results. Update the `Last updated` date.\n\n## Boundaries\n\n- This is the decision record. Fill mechanics, paper trading, and live execution stay in the wallet\u002Ftrading rails the user has configured.\n- Never edit or delete historical rows to improve the record; corrections get a note in the row, not a rewrite.\n- Ledger rows may name prices and levels but never keys, balances, or private network addresses.\n","# Research Call Tracker\n\nOutcome accountability for research. A researcher who publishes calls without tracking them has no feedback loop between thesis quality and results — win rate becomes remembered instead of measured. This skill maintains two ledgers in the shared brain vault:\n\n- `Operations\u002FResearch\u002FCall Tracker.md` — the research record: one row per published call.\n- `Operations\u002FResearch\u002FTrade Journal.md` — the position record: one row per actual position, with entry discipline.\n\nIf either ledger does not exist yet, seed it from the matching file in this skill's `templates\u002F` folder (copy verbatim, then set the `Last updated` date). Never invent a different table shape — future sessions and stats depend on the columns staying stable.\n\n## The publish-time rule (fail-closed)\n\nA research call is not \"published\" until its Call Tracker row exists. Log the row **at publish time**, never retroactively — the entire value of the ledger is that conviction tier, entry zone, stop, and kill conditions were committed before the outcome was known. If a note ships through you and has no row, that is a blocker to surface, not a detail to skip.\n\n## Logging a new call\n\nAppend a row with: date (absolute, YYYY-MM-DD), asset, venue published to, conviction tier (`High` \u002F `Medium` \u002F `Speculative` — exactly one, always), entry zone, stop, target(s), status `Watching` or `Open`, thesis in one line, the sharpest kill condition, and a link to the adversarial verdict file (from the `kill-my-thesis` skill, if installed) or the note itself.\n\nJournal entry: only if there is a real trade setup (entry + confirmation trigger + stop). Otherwise the call is research-only; `skip` is a valid outcome.\n\n## Updating and closing\n\n- `Watching → Open` when the confirmation trigger fires; the journal row must carry a live stop before it reads `Open`.\n- Close with `Closed (Win)` \u002F `Closed (Loss)` \u002F `Closed (BE)` plus outcome % in the tracker, and a one-sentence post-mortem in the journal: what the thesis got right, what it missed, disciplined or emotional exit.\n- A kill condition firing is a close signal, not a debate prompt. Surface it to the user the day it fires.\n\n## Stats\n\nRecompute the tracker's Stats block whenever any call closes: total, closed count by outcome, win rate (wins ÷ closed, BE excluded from both sides), average return on closed. Only Closed rows count — open positions are hope, not results. Update the `Last updated` date.\n\n## Boundaries\n\n- This is the decision record. Fill mechanics, paper trading, and live execution stay in the wallet\u002Ftrading rails the user has configured.\n- Never edit or delete historical rows to improve the record; corrections get a note in the row, not a rewrite.\n- Ledger rows may name prices and levels but never keys, balances, or private network addresses.\n",{"name":5,"description":7},"main","f270c4ae4f9d09c4e5da9cfa8adab7e89ae1f53e","packaged-skills\u002Foptional\u002Fresearch\u002Fhivemindos\u002Fresearch-call-tracker",4,"https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Fhivemindos","https:\u002F\u002Fgithub.com\u002FLiamVisionary","2026-11-10 21:48:41",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add LiamVisionary\u002Fhivemindos --skill research-call-tracker",{"tool":36,"command":37},"bunx","bunx skills add LiamVisionary\u002Fhivemindos --skill research-call-tracker",{"tool":39,"command":40},"pnpm","pnpm dlx skills add LiamVisionary\u002Fhivemindos --skill research-call-tracker","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Fhivemindos\u002Fblob\u002Fmain\u002Fpackaged-skills\u002Foptional\u002Fresearch\u002Fhivemindos\u002Fresearch-call-tracker\u002FSKILL.md",true,[44,50,54],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},".hivemind-skill-source.json","REFERENCE","参考文档",1149,"https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Fhivemindos\u002Fblob\u002Fmain\u002Fpackaged-skills\u002Foptional\u002Fresearch\u002Fhivemindos\u002Fresearch-call-tracker\u002F.hivemind-skill-source.json",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"templates\u002FCall Tracker.md",819,"https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Fhivemindos\u002Fblob\u002Fmain\u002Fpackaged-skills\u002Foptional\u002Fresearch\u002Fhivemindos\u002Fresearch-call-tracker\u002Ftemplates\u002FCall Tracker.md",{"path":55,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":56,"sourceHtmlUrl":57},"templates\u002FTrade Journal.md",1036,"https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Fhivemindos\u002Fblob\u002Fmain\u002Fpackaged-skills\u002Foptional\u002Fresearch\u002Fhivemindos\u002Fresearch-call-tracker\u002Ftemplates\u002FTrade Journal.md",[59,66,73,80,87,94],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M734AA85KQEXDQXQJ3T7769M","tailscale-generation-skill-authoring","This skill should be used when the user asks to \"create a Tailscale generation skill\", \"add a local generation skill\", \"document a generation endpoint\", \"add an image generation provider\", \"add a TTS provider\", \"add video generation\", \"add 3D generation\", or needs guidance on where HivemindOS Tailscale or local generation providers belong in the shared skills shelf.","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Fhivemindos\u002Fblob\u002Fmain\u002Fskills\u002Ftailscale-generation-skill-authoring\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M734A7VD69PRA0C0EV5EFY9T","localtts","This skill should be used when the user asks to \"generate local TTS\", \"use local text to speech\", \"use remote TTS over Tailscale\", \"make speech audio\", \"add a TTS provider\", \"use Qwen3-TTS\", or needs TTS endpoint setup through local or HivemindOS Tailscale routes.","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Fhivemindos\u002Fblob\u002Fmain\u002Fskills\u002Flocaltts\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M734A4K2Z0F74QZP7V7WBFRY","karpathy-guidelines","Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Fhivemindos\u002Fblob\u002Fmain\u002Fskills\u002Fkarpathy-guidelines\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M734A1HMVYVJX3YJGNQ6KF6C","comfyui-image-generation","This skill should be used when the user asks to \"generate images\", \"generate images with ComfyUI\", \"use local ComfyUI\", \"use remote ComfyUI\", \"use Z-Image\", \"add an image generation provider\", or needs image-generation endpoint setup through local or HivemindOS Tailscale routes.","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Fhivemindos\u002Fblob\u002Fmain\u002Fskills\u002Fcomfyui-image-generation\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M7349Y684Q676DNNHZPSC8W1","wrangler","Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Fhivemindos\u002Fblob\u002Fmain\u002Fskills\u002Fcloudflare\u002Fwrangler\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":18},"01M7349V3WCBF835QP74SA9Q8C","workers-best-practices","Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002FLiamVisionary\u002Fhivemindos\u002Fblob\u002Fmain\u002Fskills\u002Fcloudflare\u002Fworkers-best-practices\u002FSKILL.md",[],[]]