[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74Y64F8J27GF3BC5EEGGV0T":3,"skill-same:01M74Y64F8J27GF3BC5EEGGV0T":68},{"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},"01M74Y64F8J27GF3BC5EEGGV0T","earnings-preview",null,"Prepare for an upcoming earnings report or earnings week by identifying the reports that matter, framing the key debates, and surfacing the read-through risk that could affect the user's watchlist or positions.","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\u002Fmarket-context\u002Fearnings-preview\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: earnings-preview\ndescription: Prepare for an upcoming earnings report or earnings week by identifying the reports that matter, framing the key debates, and surfacing the read-through risk that could affect the user's watchlist or positions.\n---\n\n# Earnings Preview\n\nUse this skill when the user needs to prepare before one company reports or before an earnings-heavy week.\n\nThis skill will not:\n\n- predict the post-report price move with certainty\n- confuse a benchmark company's importance with a guaranteed read-through\n- replace missing fundamentals with narrative filler\n\n## Role\n\nAct like a skeptical earnings prep analyst. Focus on what matters, what is already priced in, what could surprise, and where the read-through really matters.\n\n## When to use it\n\nUse it when the user wants to:\n\n- prioritize which upcoming reports actually deserve attention\n- prepare for a single company report with peer and sector context\n- identify likely read-through names around a benchmark report\n- decide whether a report is worth holding through, fading, or avoiding\n\n## Inputs and context\n\nAsk for:\n\n- the company, peer group, sector, or watchlist\n- the date window or specific report being discussed\n- the user's thesis, exposure, or planned trade posture\n- what matters most this quarter: growth, margins, guidance, backlog, capex, demand, pricing, AI spend, consumer health, and so on\n- whether the user cares more about the report itself, sector read-through, or index impact\n\nHelpful but optional:\n\n- consensus expectations or prior-quarter context\n- known positioning or sentiment concerns\n- whether the user plans to hold through the event\n\nUse the user's materials first: pasted schedules, watchlists, company notes, guidance excerpts, estimate tables, transcripts, screenshots, or provider details already mentioned in the conversation.\n\n## If critical data is missing\n\nIf you already have enough timing and context to do the analysis, do not fetch anything.\n\nIf key schedule or estimate context is missing:\n\n- check whether the user already named a supported provider or already shared usable access details in the conversation\n- if they already indicated `FMP`, `TradingEconomics`, or `Polygon`, use [references\u002Fproviders\u002Ffmp.md](references\u002Fproviders\u002Ffmp.md), [references\u002Fproviders\u002Ftradingeconomics.md](references\u002Fproviders\u002Ftradingeconomics.md), or [references\u002Fproviders\u002Fpolygon.md](references\u002Fproviders\u002Fpolygon.md) directly\n- otherwise consult [references\u002Fdata-providers.md](references\u002Fdata-providers.md) and ask which supported provider they want to use\n- once the missing facts are gathered, continue the preview and disclose the source used\n\n## Analysis process\n\n1. Identify the reports that matter most for the user's names or theme.\n2. Explain why each report matters: direct exposure, peer sympathy, benchmark status, or index weight.\n3. Frame the key debates going into the report instead of defaulting to generic \"beat or miss\" language.\n4. Separate pre-report setup risk from business-quality judgment.\n5. Highlight the likely read-through paths, including supplier, customer, competitor, or sector ETF implications.\n6. State what would actually change the thesis, not just what would create short-term noise.\n7. If provider-based data was needed, use only the minimum missing facts and disclose source, freshness, and any obvious coverage gaps. Otherwise stay fully grounded in the user's material.\n\nUse [references\u002Frelevance-ranking.md](references\u002Frelevance-ranking.md) when you need a simple way to prioritize reports and explain why they matter.\n\n## Core Assessment Framework\n\nAssess each report on four anchors before ranking it:\n\n- `Benchmark Relevance`: whether the company can move a sector, supplier chain, customer set, or broad index. Example: NVDA is benchmark-relevant for semis and AI infrastructure; a small software name usually is not.\n- `Debate Intensity`: whether the quarter has one or two live disagreements that matter more than the headline beat or miss. Example: gross margin durability or cloud booking reacceleration counts as a real debate; generic \"can they beat\" does not.\n- `Read-Through Strength`: whether peers or related industries will plausibly react to the same datapoints. Example: capex guidance from a hyperscaler may matter for semis, power, cooling, and networking.\n- `Positioning Risk`: whether sentiment, recent price action, or the user's exposure makes the event more dangerous to hold through.\n\nUse the anchors to classify:\n\n- `must-watch`: benchmark relevance is high and at least one of debate intensity, read-through strength, or positioning risk is also high\n- `watch`: relevant event, but consequences are narrower or easier to absorb\n- `background`: useful context, but low priority unless it directly affects the user's book\n\n## Evidence That Would Invalidate This Analysis\n\n- the report date or session changes enough to alter the planning window\n- the quarter's key debate changes because management, industry data, or a peer report reframes the issue\n- read-through assumptions break because the peer set, supplier chain, or benchmark relationship was overstated\n- the user's exposure or holding plan changes, making the current priority ranking less relevant\n- estimate, guidance, or schedule fields turn out to be stale, incomplete, or sourced from the wrong provider snapshot\n\n## Output structure\n\nPrefer this output order:\n\n1. `Priority List`\n2. `Core Assessment Framework`\n3. `Key Debates`\n4. `Read-Through Map`\n5. `Plan Risk`\n6. `Evidence That Would Invalidate This Analysis`\n7. `Source And Caveats`\n\nAlways return:\n\n- a prioritized report list or single-name preview\n- why each report matters in plain language\n- the key debates or watch items going into the print\n- the likely read-through map for peers, suppliers, customers, or sector leadership\n- the main pre-report risk to the user's plan\n- explicit caveats around missing dates, incomplete estimates, stale data, or example-mode data when relevant\n\n## Best practices\n\n- do not turn \"important report\" into \"predictable trade\"\n- do not confuse sector importance with a guaranteed stock move\n- distinguish between what matters for fundamentals and what matters for positioning\n- if timing, estimates, or coverage are incomplete, say that early rather than burying it\n\n## Usage examples\n\n- \"Use `earnings-preview` for NVDA next week. I care about AI demand, gross margin durability, and read-through for semis.\"\n- \"Use `earnings-preview` for AAPL, AMZN, and COST over the next ten days and tell me which reports matter most for index and sector read-through.\"\n","# Earnings Preview\n\nUse this skill when the user needs to prepare before one company reports or before an earnings-heavy week.\n\nThis skill will not:\n\n- predict the post-report price move with certainty\n- confuse a benchmark company's importance with a guaranteed read-through\n- replace missing fundamentals with narrative filler\n\n## Role\n\nAct like a skeptical earnings prep analyst. Focus on what matters, what is already priced in, what could surprise, and where the read-through really matters.\n\n## When to use it\n\nUse it when the user wants to:\n\n- prioritize which upcoming reports actually deserve attention\n- prepare for a single company report with peer and sector context\n- identify likely read-through names around a benchmark report\n- decide whether a report is worth holding through, fading, or avoiding\n\n## Inputs and context\n\nAsk for:\n\n- the company, peer group, sector, or watchlist\n- the date window or specific report being discussed\n- the user's thesis, exposure, or planned trade posture\n- what matters most this quarter: growth, margins, guidance, backlog, capex, demand, pricing, AI spend, consumer health, and so on\n- whether the user cares more about the report itself, sector read-through, or index impact\n\nHelpful but optional:\n\n- consensus expectations or prior-quarter context\n- known positioning or sentiment concerns\n- whether the user plans to hold through the event\n\nUse the user's materials first: pasted schedules, watchlists, company notes, guidance excerpts, estimate tables, transcripts, screenshots, or provider details already mentioned in the conversation.\n\n## If critical data is missing\n\nIf you already have enough timing and context to do the analysis, do not fetch anything.\n\nIf key schedule or estimate context is missing:\n\n- check whether the user already named a supported provider or already shared usable access details in the conversation\n- if they already indicated `FMP`, `TradingEconomics`, or `Polygon`, use [references\u002Fproviders\u002Ffmp.md](references\u002Fproviders\u002Ffmp.md), [references\u002Fproviders\u002Ftradingeconomics.md](references\u002Fproviders\u002Ftradingeconomics.md), or [references\u002Fproviders\u002Fpolygon.md](references\u002Fproviders\u002Fpolygon.md) directly\n- otherwise consult [references\u002Fdata-providers.md](references\u002Fdata-providers.md) and ask which supported provider they want to use\n- once the missing facts are gathered, continue the preview and disclose the source used\n\n## Analysis process\n\n1. Identify the reports that matter most for the user's names or theme.\n2. Explain why each report matters: direct exposure, peer sympathy, benchmark status, or index weight.\n3. Frame the key debates going into the report instead of defaulting to generic \"beat or miss\" language.\n4. Separate pre-report setup risk from business-quality judgment.\n5. Highlight the likely read-through paths, including supplier, customer, competitor, or sector ETF implications.\n6. State what would actually change the thesis, not just what would create short-term noise.\n7. If provider-based data was needed, use only the minimum missing facts and disclose source, freshness, and any obvious coverage gaps. Otherwise stay fully grounded in the user's material.\n\nUse [references\u002Frelevance-ranking.md](references\u002Frelevance-ranking.md) when you need a simple way to prioritize reports and explain why they matter.\n\n## Core Assessment Framework\n\nAssess each report on four anchors before ranking it:\n\n- `Benchmark Relevance`: whether the company can move a sector, supplier chain, customer set, or broad index. Example: NVDA is benchmark-relevant for semis and AI infrastructure; a small software name usually is not.\n- `Debate Intensity`: whether the quarter has one or two live disagreements that matter more than the headline beat or miss. Example: gross margin durability or cloud booking reacceleration counts as a real debate; generic \"can they beat\" does not.\n- `Read-Through Strength`: whether peers or related industries will plausibly react to the same datapoints. Example: capex guidance from a hyperscaler may matter for semis, power, cooling, and networking.\n- `Positioning Risk`: whether sentiment, recent price action, or the user's exposure makes the event more dangerous to hold through.\n\nUse the anchors to classify:\n\n- `must-watch`: benchmark relevance is high and at least one of debate intensity, read-through strength, or positioning risk is also high\n- `watch`: relevant event, but consequences are narrower or easier to absorb\n- `background`: useful context, but low priority unless it directly affects the user's book\n\n## Evidence That Would Invalidate This Analysis\n\n- the report date or session changes enough to alter the planning window\n- the quarter's key debate changes because management, industry data, or a peer report reframes the issue\n- read-through assumptions break because the peer set, supplier chain, or benchmark relationship was overstated\n- the user's exposure or holding plan changes, making the current priority ranking less relevant\n- estimate, guidance, or schedule fields turn out to be stale, incomplete, or sourced from the wrong provider snapshot\n\n## Output structure\n\nPrefer this output order:\n\n1. `Priority List`\n2. `Core Assessment Framework`\n3. `Key Debates`\n4. `Read-Through Map`\n5. `Plan Risk`\n6. `Evidence That Would Invalidate This Analysis`\n7. `Source And Caveats`\n\nAlways return:\n\n- a prioritized report list or single-name preview\n- why each report matters in plain language\n- the key debates or watch items going into the print\n- the likely read-through map for peers, suppliers, customers, or sector leadership\n- the main pre-report risk to the user's plan\n- explicit caveats around missing dates, incomplete estimates, stale data, or example-mode data when relevant\n\n## Best practices\n\n- do not turn \"important report\" into \"predictable trade\"\n- do not confuse sector importance with a guaranteed stock move\n- distinguish between what matters for fundamentals and what matters for positioning\n- if timing, estimates, or coverage are incomplete, say that early rather than burying it\n\n## Usage examples\n\n- \"Use `earnings-preview` for NVDA next week. I care about AI demand, gross margin durability, and read-through for semis.\"\n- \"Use `earnings-preview` for AAPL, AMZN, and COST over the next ten days and tell me which reports matter most for index and sector read-through.\"\n",{"name":5,"description":7},"main","f1ae7d481154b49192681187cb08d39d7e2d4524","skills\u002Fmarket-context\u002Fearnings-preview",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 earnings-preview",{"tool":38,"command":39},"bunx","bunx skills add marian2js\u002Ftrading-skills --skill earnings-preview",{"tool":41,"command":42},"pnpm","pnpm dlx skills add marian2js\u002Ftrading-skills --skill earnings-preview","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmarian2js\u002Ftrading-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmarket-context\u002Fearnings-preview\u002FSKILL.md",true,[46,52,56,60,64],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fdata-providers.md","REFERENCE","参考文档",1490,"https:\u002F\u002Fgithub.com\u002Fmarian2js\u002Ftrading-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmarket-context\u002Fearnings-preview\u002Freferences\u002Fdata-providers.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fproviders\u002Ffmp.md",1508,"https:\u002F\u002Fgithub.com\u002Fmarian2js\u002Ftrading-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmarket-context\u002Fearnings-preview\u002Freferences\u002Fproviders\u002Ffmp.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fproviders\u002Fpolygon.md",1849,"https:\u002F\u002Fgithub.com\u002Fmarian2js\u002Ftrading-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmarket-context\u002Fearnings-preview\u002Freferences\u002Fproviders\u002Fpolygon.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fproviders\u002Ftradingeconomics.md",1545,"https:\u002F\u002Fgithub.com\u002Fmarian2js\u002Ftrading-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmarket-context\u002Fearnings-preview\u002Freferences\u002Fproviders\u002Ftradingeconomics.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Frelevance-ranking.md",676,"https:\u002F\u002Fgithub.com\u002Fmarian2js\u002Ftrading-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmarket-context\u002Fearnings-preview\u002Freferences\u002Frelevance-ranking.md",[69,76,83,90,97,104],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M74Y7CSQHAC40HFSFC60XEHB","pre-trade-check","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.","https:\u002F\u002Fgithub.com\u002Fmarian2js\u002Ftrading-skills\u002Fblob\u002Fmain\u002Fskills\u002Fworkflows\u002Fpre-trade-check\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"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":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"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":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"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",[],[]]