[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74Y7CSQHAC40HFSFC60XEHB":3,"skill-same:01M74Y7CSQHAC40HFSFC60XEHB":52},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M74Y7CSQHAC40HFSFC60XEHB","pre-trade-check",null,"Orchestrate a disciplined pre-trade workflow by routing a watchlist or trade idea through the minimum set of underlying skills needed to decide whether the trade is ready, not ready, or should be resized or reworked first.","marian2js\u002Ftrading-skills","marian2js","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F4909681?v=4","01M74Y5RKC5X9VJFH50MP3MCCB","Mariano Pardo","01M74Y5RM1A93P6YCX90C4MT76",33,"MIT","https:\u002F\u002Fgithub.com\u002Fmarian2js\u002Ftrading-skills\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Fpre-trade-check\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: pre-trade-check\ndescription: Orchestrate a disciplined pre-trade workflow by routing a watchlist or trade idea through the minimum set of underlying skills needed to decide whether the trade is ready, not ready, or should be resized or reworked first.\n---\n\n# Pre Trade Check\n\nUse this workflow skill when the user wants one disciplined answer to the question, \"Is this trade actually ready?\" rather than running each underlying check manually.\n\nThis workflow will not:\n\n- place or stage orders\n- skip missing-information problems just to reach a yes or no answer\n- force every trade through every skill if the shorter path is sufficient\n\n## Role\n\nAct like a pre-trade gatekeeper. Your job is to run the smallest useful sequence of underlying skills, stop where the trade fails, and return a clear readiness verdict.\n\n## When to use it\n\nUse it when the user wants to:\n\n- check a trade idea end to end before entering\n- know whether the issue is the thesis, event risk, structure, execution, concentration, or size\n- turn a messy idea into a clear go \u002F no-go \u002F not-yet decision\n- avoid skipping important checks under time pressure\n\n## Inputs and context\n\nAsk for the minimum information needed to route the workflow:\n\n- whether the user has a single idea or a watchlist\n- instrument, direction, and intended timeframe\n- thesis or rough claim\n- entry, stop, and target if already known\n- any upcoming catalyst or event concern\n- account or portfolio context if concentration or size may matter\n\nHelpful but optional:\n\n- current regime observations\n- watchlist notes\n- order-type plan\n- constraints such as regular-hours only, no event holds, or maximum portfolio risk\n\nUse the user's materials first.\n\nIf the user only has a rough idea, start with discovery and evidence checks instead of pretending the trade is already in construction mode.\n\n## Workflow routing\n\nUse the shortest chain that answers the user's actual problem:\n\n1. If the user starts with many names, run `watchlist-review`.\n2. If those names still need one event picture, run `catalyst-map`.\n3. If the idea is under-researched, run `evidence-gap-check`.\n4. If the claim is still not testable, run `thesis-validation`.\n5. If event risk matters, run `earnings-preview` or `macro-event-analysis`.\n6. If broader context matters, run `market-regime-analysis`.\n7. If structure is defined, run `risk-reward-sanity-check`.\n8. If order logic matters, run `execution-plan-check`.\n9. If portfolio overlap matters, run `portfolio-concentration`.\n10. If the trade is still viable and the stop is stable, run `position-sizing`.\n\nStop the workflow as soon as a blocking issue appears and say why the trade is not ready yet.\n\n## Decision logic\n\nClassify the result as:\n\n- `ready`: the trade has passed the relevant checks and can move to entry discipline\n- `ready with conditions`: the trade may proceed only if the stated constraints are respected\n- `not ready yet`: the trade needs more research, cleaner structure, better execution logic, or smaller risk before it deserves action\n- `reject`: the current idea is weak enough that forcing it forward would be process failure\n\n## Output structure\n\nPrefer this output order:\n\n1. `Pre-Trade Verdict`\n2. `Checks Run`\n3. `Blocking Issue`\n4. `What Passed`\n5. `What Still Needs Work`\n6. `Updated Trade Context`\n7. `Next Skill Or Action`\n\nAlways include:\n\n- the minimum set of checks actually used\n- the main reason the trade is ready or not ready\n- the most important unresolved issue\n- what the user should do next if the answer is not ready\n- a compact updated trade context block when enough information exists\n\n## Updated Trade Context\n\nWhen enough context exists, carry forward a compact block like this:\n\n```markdown\n## Trade Context\n\n- instrument:\n- direction:\n- timeframe:\n- thesis:\n- key_drivers:\n- key_risks:\n- upcoming_events:\n- invalidation:\n- entry_idea:\n- stop_idea:\n- target_idea:\n- position_size_hint:\n- portfolio_impact:\n- confidence_notes:\n- open_questions:\n- source_freshness:\n- assumptions:\n- next_recommended_skill:\n```\n\nOnly populate the fields supported by the checks that actually ran. Do not invent missing fields just to make the block look complete.\n\n## Best practices\n\n- do not run every skill by default if two checks already answer the question\n- do not continue past a blocking issue without saying it is blocking\n- do not let a valid setup skip execution, concentration, or sizing when those are the real risks\n- do not let the wrapper hide which underlying skill produced the key concern\n\n## Usage examples\n\n- \"Use `pre-trade-check` on this swing long idea in semis and tell me if it is actually ready.\"\n- \"Use `pre-trade-check` on my watchlist for next week and route the best setup through the minimum checks needed before entry.\"\n","# Pre Trade Check\n\nUse this workflow skill when the user wants one disciplined answer to the question, \"Is this trade actually ready?\" rather than running each underlying check manually.\n\nThis workflow will not:\n\n- place or stage orders\n- skip missing-information problems just to reach a yes or no answer\n- force every trade through every skill if the shorter path is sufficient\n\n## Role\n\nAct like a pre-trade gatekeeper. Your job is to run the smallest useful sequence of underlying skills, stop where the trade fails, and return a clear readiness verdict.\n\n## When to use it\n\nUse it when the user wants to:\n\n- check a trade idea end to end before entering\n- know whether the issue is the thesis, event risk, structure, execution, concentration, or size\n- turn a messy idea into a clear go \u002F no-go \u002F not-yet decision\n- avoid skipping important checks under time pressure\n\n## Inputs and context\n\nAsk for the minimum information needed to route the workflow:\n\n- whether the user has a single idea or a watchlist\n- instrument, direction, and intended timeframe\n- thesis or rough claim\n- entry, stop, and target if already known\n- any upcoming catalyst or event concern\n- account or portfolio context if concentration or size may matter\n\nHelpful but optional:\n\n- current regime observations\n- watchlist notes\n- order-type plan\n- constraints such as regular-hours only, no event holds, or maximum portfolio risk\n\nUse the user's materials first.\n\nIf the user only has a rough idea, start with discovery and evidence checks instead of pretending the trade is already in construction mode.\n\n## Workflow routing\n\nUse the shortest chain that answers the user's actual problem:\n\n1. If the user starts with many names, run `watchlist-review`.\n2. If those names still need one event picture, run `catalyst-map`.\n3. If the idea is under-researched, run `evidence-gap-check`.\n4. If the claim is still not testable, run `thesis-validation`.\n5. If event risk matters, run `earnings-preview` or `macro-event-analysis`.\n6. If broader context matters, run `market-regime-analysis`.\n7. If structure is defined, run `risk-reward-sanity-check`.\n8. If order logic matters, run `execution-plan-check`.\n9. If portfolio overlap matters, run `portfolio-concentration`.\n10. If the trade is still viable and the stop is stable, run `position-sizing`.\n\nStop the workflow as soon as a blocking issue appears and say why the trade is not ready yet.\n\n## Decision logic\n\nClassify the result as:\n\n- `ready`: the trade has passed the relevant checks and can move to entry discipline\n- `ready with conditions`: the trade may proceed only if the stated constraints are respected\n- `not ready yet`: the trade needs more research, cleaner structure, better execution logic, or smaller risk before it deserves action\n- `reject`: the current idea is weak enough that forcing it forward would be process failure\n\n## Output structure\n\nPrefer this output order:\n\n1. `Pre-Trade Verdict`\n2. `Checks Run`\n3. `Blocking Issue`\n4. `What Passed`\n5. `What Still Needs Work`\n6. `Updated Trade Context`\n7. `Next Skill Or Action`\n\nAlways include:\n\n- the minimum set of checks actually used\n- the main reason the trade is ready or not ready\n- the most important unresolved issue\n- what the user should do next if the answer is not ready\n- a compact updated trade context block when enough information exists\n\n## Updated Trade Context\n\nWhen enough context exists, carry forward a compact block like this:\n\n```markdown\n## Trade Context\n\n- instrument:\n- direction:\n- timeframe:\n- thesis:\n- key_drivers:\n- key_risks:\n- upcoming_events:\n- invalidation:\n- entry_idea:\n- stop_idea:\n- target_idea:\n- position_size_hint:\n- portfolio_impact:\n- confidence_notes:\n- open_questions:\n- source_freshness:\n- assumptions:\n- next_recommended_skill:\n```\n\nOnly populate the fields supported by the checks that actually ran. Do not invent missing fields just to make the block look complete.\n\n## Best practices\n\n- do not run every skill by default if two checks already answer the question\n- do not continue past a blocking issue without saying it is blocking\n- do not let a valid setup skip execution, concentration, or sizing when those are the real risks\n- do not let the wrapper hide which underlying skill produced the key concern\n\n## Usage examples\n\n- \"Use `pre-trade-check` on this swing long idea in semis and tell me if it is actually ready.\"\n- \"Use `pre-trade-check` on my watchlist for next week and route the best setup through the minimum checks needed before entry.\"\n",{"name":5,"description":7},"main","f1ae7d481154b49192681187cb08d39d7e2d4524","skills\u002Fworkflows\u002Fpre-trade-check",9,"https:\u002F\u002Fgithub.com\u002Fmarian2js\u002Ftrading-skills","https:\u002F\u002Fgithub.com\u002Fmarian2js","eToro Elite Pro PI","2026-03-17 02:55:25",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add marian2js\u002Ftrading-skills --skill pre-trade-check",{"tool":38,"command":39},"bunx","bunx skills add marian2js\u002Ftrading-skills --skill pre-trade-check",{"tool":41,"command":42},"pnpm","pnpm dlx skills add marian2js\u002Ftrading-skills --skill pre-trade-check","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmarian2js\u002Ftrading-skills\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Fpre-trade-check\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fworkflow-framework.md","REFERENCE","参考文档",1238,"https:\u002F\u002Fgithub.com\u002Fmarian2js\u002Ftrading-skills\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Fpre-trade-check\u002Freferences\u002Fworkflow-framework.md",[53,60,67,74,81,88],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M74Y7A4YHWG129S4KM7ANN6R","post-trade-debrief","Orchestrate a disciplined post-trade workflow by reconstructing the original plan, reviewing execution and rule adherence, and deciding whether the lesson is trade-specific or part of a larger repeatable pattern.","https:\u002F\u002Fgithub.com\u002Fmarian2js\u002Ftrading-skills\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Fpost-trade-debrief\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M74Y77P03W7KF07BC1M9Y0SG","portfolio-risk-review","Orchestrate a whole-book risk review by checking concentration, correlated exposure, catalyst clustering, market-context sensitivity, and live-position fragility before the user adds, holds, or reduces portfolio risk.","https:\u002F\u002Fgithub.com\u002Fmarian2js\u002Ftrading-skills\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Fportfolio-risk-review\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M74Y74RGSA17NMGDQBJ3AC2E","earnings-trade-prep","Orchestrate a disciplined earnings-event workflow by deciding which names deserve prep, mapping the key debates and read-through paths, pressure-testing the thesis and structure, and ending with a clear pre-earnings hold, avoid, or trade decision.","https:\u002F\u002Fgithub.com\u002Fmarian2js\u002Ftrading-skills\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Fearnings-trade-prep\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M74Y724D0XA2BX1CE67RS5KP","risk-reward-sanity-check","Use when the user wants to test whether a proposed entry, stop, and target structure is coherent, asymmetric enough, and vulnerable to obvious failure modes before the trade is placed.","https:\u002F\u002Fgithub.com\u002Fmarian2js\u002Ftrading-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftrade-construction\u002Frisk-reward-sanity-check\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M74Y7057CQ1FMMEA98ZJHKX7","position-sizing","Use when the user needs a conservative position size from account equity, risk budget, entry, stop, and trading friction before entering a trade.","https:\u002F\u002Fgithub.com\u002Fmarian2js\u002Ftrading-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftrade-construction\u002Fposition-sizing\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M74Y6WXF77BTGRP6EV0BAACA","portfolio-concentration","Evaluate whether a portfolio, account, or planned position is too dependent on a small number of issuers, sectors, themes, or correlated exposures before the user adds or holds more risk.","https:\u002F\u002Fgithub.com\u002Fmarian2js\u002Ftrading-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftrade-construction\u002Fportfolio-concentration\u002FSKILL.md",[],[]]