[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FBEE11HAWD161691CTD7H6":3,"skill-same:01M7FBEE11HAWD161691CTD7H6":58},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":47},"01M7FBEE11HAWD161691CTD7H6","analysis",null,"Guide Kalshi, Polymarket, and cross-venue analysis workflows for prediction-market-analysis.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fprediction-market-analysis\u002Fsub-skills\u002Fanalysis\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: analysis\ndescription: \"Guide Kalshi, Polymarket, and cross-venue analysis workflows for\n  prediction-market-analysis.\"\nmetadata:\n  disco-role: operating\ndisable-model-invocation: true\nlicense: MIT\n---\n\n# analysis\n\nUse this sub-skill for anything that runs, interprets, or extends the repo's analysis classes.\nIt covers both the menu-driven CLI and the Python `Analysis` framework.\n\n## Use this route when\n\n- The user wants to run a named analysis or all analyses.\n- The user wants calibration, return, volume, category, or statistical-study guidance.\n- The user wants a new analysis class or a fix to an existing one.\n- The user wants help understanding `Analysis`, `AnalysisOutput`, or `ChartConfig`.\n\n## Scope\n\n### Included\n\n- Kalshi calibration and pricing analyses.\n- Kalshi maker\u002Ftaker, category, hour-of-day, and volume analyses.\n- Kalshi meta statistics and paper-style statistical tests.\n- Polymarket calibration, volume, and trade-time analyses.\n- The cross-venue animated calibration comparison.\n- `Analysis.save()` output formats and `ChartConfig` JSON export.\n\n### Excluded\n\n- Market\u002Ftrade\u002Fblock backfills and cursor recovery, which belong to `sub-skills\u002Findexing\u002F`.\n- Dataset download, archive creation, and host-tool installation, which belong to `sub-skills\u002Fdata-ops\u002F`.\n\n## Read first\n\n- `..\u002F..\u002Freferences\u002Fanalysis-catalog.md` for the full analysis list.\n- `..\u002F..\u002Freferences\u002Fapi-reference.md` for the `Analysis` and `ChartConfig` APIs.\n- `..\u002F..\u002Freferences\u002Fdata-layout.md` for the required Parquet inputs.\n- `..\u002F..\u002Freferences\u002Ftroubleshooting.md` for cross-cutting failures.\n\n## Core workflow\n\n1. Identify the analysis name from the catalog or from `scripts\u002Fcatalog.py`.\n2. Confirm the required input directories exist.\n3. Run the analysis with `uv run main.py analyze \u003Cname>` or the equivalent wrapper.\n4. Read the saved outputs under `output\u002F\u003Canalysis-name>.*`.\n5. If the analysis is missing, thin, or failing, inspect the relevant source module and the family-specific troubleshooting notes.\n\n## Analysis families\n\n### Kalshi calibration and pricing\n\nUse these when the task is about price calibration, mispricing, or expected value:\n\n- `win_rate_by_price`\n- `mispricing_by_price`\n- `win_rate_by_trade_size`\n- `ev_yes_vs_no`\n\nTypical inputs:\n`data\u002Fkalshi\u002Ftrades\u002F`, `data\u002Fkalshi\u002Fmarkets\u002F`.\n\n### Kalshi time and volume\n\nUse these when the task is about temporal trends or notional volume:\n\n- `returns_by_hour`\n- `vwap_by_hour`\n- `volume_over_time`\n- `longshot_volume_share_over_time`\n- `kalshi_calibration_deviation_over_time`\n- `maker_taker_gap_over_time`\n\nTypical inputs:\n`data\u002Fkalshi\u002Ftrades\u002F`, sometimes `data\u002Fkalshi\u002Fmarkets\u002F`.\n\n### Kalshi maker\u002Ftaker and category studies\n\nUse these when the task compares makers and takers, direction, or category grouping:\n\n- `trade_size_by_role`\n- `maker_returns_by_direction`\n- `maker_win_rate_by_direction`\n- `maker_vs_taker_returns`\n- `maker_taker_returns_by_category`\n- `market_types`\n- `yes_vs_no_by_price`\n- `meta_stats`\n- `statistical_tests`\n\nTypical inputs:\n`data\u002Fkalshi\u002Ftrades\u002F`, `data\u002Fkalshi\u002Fmarkets\u002F`, and `src.analysis.kalshi.util.categories`.\n\n### Polymarket analyses\n\nUse these when the task is about Polymarket calibration, volume, or block-level trade history:\n\n- `polymarket_win_rate_by_price`\n- `polymarket_calibration_by_bucket`\n- `polymarket_volume_over_time`\n- `polymarket_trades_over_time`\n\nTypical inputs:\n`data\u002Fpolymarket\u002Ftrades\u002F`, `data\u002Fpolymarket\u002Flegacy_trades\u002F`, `data\u002Fpolymarket\u002Fmarkets\u002F`, `data\u002Fpolymarket\u002Fblocks\u002F`, and `data\u002Fpolymarket\u002Ffpmm_collateral_lookup.json`.\n\n### Cross-venue comparison\n\nUse `win_rate_by_price_animated` when the user wants a single workflow that compares Kalshi and Polymarket in one animated calibration plot.\n\nTypical inputs:\nBoth platforms' data directories plus `data\u002Fpolymarket\u002Fblocks\u002F` and the collateral lookup file.\n\n## Adding or fixing an analysis\n\n- Subclass `Analysis`.\n- Set a stable `name` and a human-readable `description` in `__init__`.\n- Keep data selection, transformations, figure creation, and chart serialization inside `run()` or helper methods.\n- Return `AnalysisOutput`.\n- Use `self.progress()` for longer SQL or dataframe steps.\n- Prefer `ChartConfig` helpers when the analysis should also emit JSON chart output.\n- Use the category helpers from `src.analysis.kalshi.util.categories` when grouping Kalshi markets.\n\n## Common failure patterns\n\n- Missing or empty `data\u002F` subtrees.\n- No finalized or resolved markets, leading to empty dataframes.\n- Missing Polymarket helper files, especially the collateral lookup or block timestamps.\n- `Analysis.load()` returning no classes because the command was run from the wrong directory.\n- Matplotlib backend issues on headless hosts.\n\n## Helpful helper\n\n- `..\u002F..\u002Fscripts\u002Fcatalog.py` lists the analysis names without opening the interactive menu when run through the repo environment.\n","# analysis\n\nUse this sub-skill for anything that runs, interprets, or extends the repo's analysis classes.\nIt covers both the menu-driven CLI and the Python `Analysis` framework.\n\n## Use this route when\n\n- The user wants to run a named analysis or all analyses.\n- The user wants calibration, return, volume, category, or statistical-study guidance.\n- The user wants a new analysis class or a fix to an existing one.\n- The user wants help understanding `Analysis`, `AnalysisOutput`, or `ChartConfig`.\n\n## Scope\n\n### Included\n\n- Kalshi calibration and pricing analyses.\n- Kalshi maker\u002Ftaker, category, hour-of-day, and volume analyses.\n- Kalshi meta statistics and paper-style statistical tests.\n- Polymarket calibration, volume, and trade-time analyses.\n- The cross-venue animated calibration comparison.\n- `Analysis.save()` output formats and `ChartConfig` JSON export.\n\n### Excluded\n\n- Market\u002Ftrade\u002Fblock backfills and cursor recovery, which belong to `sub-skills\u002Findexing\u002F`.\n- Dataset download, archive creation, and host-tool installation, which belong to `sub-skills\u002Fdata-ops\u002F`.\n\n## Read first\n\n- `..\u002F..\u002Freferences\u002Fanalysis-catalog.md` for the full analysis list.\n- `..\u002F..\u002Freferences\u002Fapi-reference.md` for the `Analysis` and `ChartConfig` APIs.\n- `..\u002F..\u002Freferences\u002Fdata-layout.md` for the required Parquet inputs.\n- `..\u002F..\u002Freferences\u002Ftroubleshooting.md` for cross-cutting failures.\n\n## Core workflow\n\n1. Identify the analysis name from the catalog or from `scripts\u002Fcatalog.py`.\n2. Confirm the required input directories exist.\n3. Run the analysis with `uv run main.py analyze \u003Cname>` or the equivalent wrapper.\n4. Read the saved outputs under `output\u002F\u003Canalysis-name>.*`.\n5. If the analysis is missing, thin, or failing, inspect the relevant source module and the family-specific troubleshooting notes.\n\n## Analysis families\n\n### Kalshi calibration and pricing\n\nUse these when the task is about price calibration, mispricing, or expected value:\n\n- `win_rate_by_price`\n- `mispricing_by_price`\n- `win_rate_by_trade_size`\n- `ev_yes_vs_no`\n\nTypical inputs:\n`data\u002Fkalshi\u002Ftrades\u002F`, `data\u002Fkalshi\u002Fmarkets\u002F`.\n\n### Kalshi time and volume\n\nUse these when the task is about temporal trends or notional volume:\n\n- `returns_by_hour`\n- `vwap_by_hour`\n- `volume_over_time`\n- `longshot_volume_share_over_time`\n- `kalshi_calibration_deviation_over_time`\n- `maker_taker_gap_over_time`\n\nTypical inputs:\n`data\u002Fkalshi\u002Ftrades\u002F`, sometimes `data\u002Fkalshi\u002Fmarkets\u002F`.\n\n### Kalshi maker\u002Ftaker and category studies\n\nUse these when the task compares makers and takers, direction, or category grouping:\n\n- `trade_size_by_role`\n- `maker_returns_by_direction`\n- `maker_win_rate_by_direction`\n- `maker_vs_taker_returns`\n- `maker_taker_returns_by_category`\n- `market_types`\n- `yes_vs_no_by_price`\n- `meta_stats`\n- `statistical_tests`\n\nTypical inputs:\n`data\u002Fkalshi\u002Ftrades\u002F`, `data\u002Fkalshi\u002Fmarkets\u002F`, and `src.analysis.kalshi.util.categories`.\n\n### Polymarket analyses\n\nUse these when the task is about Polymarket calibration, volume, or block-level trade history:\n\n- `polymarket_win_rate_by_price`\n- `polymarket_calibration_by_bucket`\n- `polymarket_volume_over_time`\n- `polymarket_trades_over_time`\n\nTypical inputs:\n`data\u002Fpolymarket\u002Ftrades\u002F`, `data\u002Fpolymarket\u002Flegacy_trades\u002F`, `data\u002Fpolymarket\u002Fmarkets\u002F`, `data\u002Fpolymarket\u002Fblocks\u002F`, and `data\u002Fpolymarket\u002Ffpmm_collateral_lookup.json`.\n\n### Cross-venue comparison\n\nUse `win_rate_by_price_animated` when the user wants a single workflow that compares Kalshi and Polymarket in one animated calibration plot.\n\nTypical inputs:\nBoth platforms' data directories plus `data\u002Fpolymarket\u002Fblocks\u002F` and the collateral lookup file.\n\n## Adding or fixing an analysis\n\n- Subclass `Analysis`.\n- Set a stable `name` and a human-readable `description` in `__init__`.\n- Keep data selection, transformations, figure creation, and chart serialization inside `run()` or helper methods.\n- Return `AnalysisOutput`.\n- Use `self.progress()` for longer SQL or dataframe steps.\n- Prefer `ChartConfig` helpers when the analysis should also emit JSON chart output.\n- Use the category helpers from `src.analysis.kalshi.util.categories` when grouping Kalshi markets.\n\n## Common failure patterns\n\n- Missing or empty `data\u002F` subtrees.\n- No finalized or resolved markets, leading to empty dataframes.\n- Missing Polymarket helper files, especially the collateral lookup or block timestamps.\n- `Analysis.load()` returning no classes because the command was run from the wrong directory.\n- Matplotlib backend issues on headless hosts.\n\n## Helpful helper\n\n- `..\u002F..\u002Fscripts\u002Fcatalog.py` lists the analysis names without opening the interactive menu when run through the repo environment.\n",{"name":5,"license":15,"metadata":24,"description":7,"disable-model-invocation":26},{"disco-role":25},"operating",true,"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","06-前端与设计\u002Fprediction-market-analysis\u002Fsub-skills\u002Fanalysis",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":26},[37,40,43],{"tool":38,"command":39},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill analysis",{"tool":41,"command":42},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill analysis",{"tool":44,"command":45},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill analysis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fprediction-market-analysis\u002Fsub-skills\u002Fanalysis\u002FSKILL.md",[48,54],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Ftroubleshooting.md","REFERENCE","参考文档",1677,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fprediction-market-analysis\u002Fsub-skills\u002Fanalysis\u002Freferences\u002Ftroubleshooting.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fworkflows.md",1588,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fprediction-market-analysis\u002Fsub-skills\u002Fanalysis\u002Freferences\u002Fworkflows.md",[59,66,71,78,85,92],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":67,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]