[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EME3PSDBR30BKVERE26BCT":3,"skill-same:01M7EME3PSDBR30BKVERE26BCT":65},{"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":45,"commitSha":46,"skillDirectory":47,"forksCount":14,"repositoryHtmlUrl":48,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M7EME3PSDBR30BKVERE26BCT","managing-best-execution-compliance",null,"Structures best execution monitoring with venue analysis, systematic internalization assessment, and regulatory compliance documentation. Use when managing best execution, documenting execution decisions, or conducting venue analysis.","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fcompliance\u002Fmanaging-best-execution-compliance\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: managing-best-execution-compliance\nlanguage: en\ndescription: Structures best execution monitoring with venue analysis, systematic internalization assessment, and regulatory compliance documentation. Use when managing best execution, documenting execution decisions, or conducting venue analysis.\ntags:\n  - management\n  - public-markets-and-trading\n  - compliance\n  - regulatory\nmetadata:\n  author: casemark\n  practice_areas:\n    - Trading\n    - Market Making\n    - Execution\n  document_types:\n    - Management Report\n  skill_modes:\n    - Management\n    - Coordination\nsource: \"https:\u002F\u002Fgithub.com\u002FCaseMark\u002Fskills\"\nsource_repository: \"CaseMark\u002Fskills\"\nsource_path: \"skills\u002Fcapital\u002Fmanaging-best-execution-compliance\u002FSKILL.md\"\nlicense: \"Apache-2.0\"\nimported_at: \"2026-09-20\"\n---\n# Managing Best Execution Compliance\n\nStructures best execution monitoring with venue analysis, systematic internalization assessment, and regulatory compliance documentation.\n\n## When To Use\n\n- Conducting periodic best execution reviews (quarterly, annual, or ad hoc)\n- Evaluating execution venue performance and routing decisions\n- Assessing systematic internalizer (SI) obligations and thresholds\n- Responding to regulatory inquiries on order execution quality\n- Onboarding new execution venues or broker-dealers\n- Documenting rationale for execution arrangements after material changes (new asset classes, venue outages, market structure shifts)\n\n## Inputs To Gather\n\n- **Order flow data**: Volume, notional value, and order types by asset class, venue, and time period\n- **Execution quality metrics**: Fill rates, price improvement\u002Fdisimprovement, effective spread vs. quoted spread, latency, and market impact\n- **Venue fee schedules**: Maker\u002Ftaker fees, rebates, tiered pricing, and payment-for-order-flow (PFOF) arrangements\n- **Regulatory framework**: Applicable regime — MiFID II RTS 27\u002F28 reports, SEC Rule 606, FINRA 5310, or equivalent [VERIFY jurisdiction-specific requirements]\n- **Prior review reports**: Previous best execution committee minutes, exception logs, and remediation items\n- **Client classification**: Retail vs. professional vs. eligible counterparty breakdown, as execution factors weighting differs by client type\n- **Benchmark selection**: Reference prices used (arrival price, VWAP, TWAP, midpoint, close)\n\n## Workflow\n\n1. **Define review scope**\n   - Specify asset classes (equities, fixed income, FX, listed derivatives, OTC derivatives)\n   - Set review period and confirm data completeness across all venues\n   - Identify any venue outages, market disruptions, or corporate actions that affected execution during the period\n\n2. **Aggregate and validate execution data**\n   - Pull execution reports from OMS\u002FEMS and venue-provided RTS 27-equivalent data\n   - Reconcile order counts and notional values against internal records\n   - Flag data gaps or mismatches — mark unresolved items with [VERIFY]\n\n3. **Conduct venue analysis**\n   - Rank venues by execution quality factors: price, cost, speed, likelihood of execution, settlement reliability\n   - Weight factors according to client type and order characteristics (size, urgency, instrument liquidity)\n   - Compare venue performance against the prior period and against peer venues\n   - Identify venues where quality has materially deteriorated and document root cause\n\n4. **Assess systematic internalization**\n   - Calculate SI threshold metrics: frequency, systematic basis, and substantial scale for each instrument class [VERIFY thresholds per current ESMA or local regulator guidance]\n   - Determine whether the firm triggers SI status for any instrument\n   - If SI status applies, confirm pre-trade transparency and quote obligations are met\n\n5. **Evaluate conflicts of interest**\n   - Review PFOF arrangements, affiliated venue routing, and soft-dollar benefits\n   - Confirm that conflicts are disclosed and do not compromise execution quality\n   - Document any instances where conflict mitigation controls were triggered\n\n6. **Document execution decisions**\n   - Record the rationale for venue selection, routing logic changes, and any deviations from standard execution policy\n   - Note exceptions where execution fell outside acceptable parameters and the remedial action taken\n   - Prepare committee-ready summary with recommendations (add venues, remove underperformers, adjust routing weights)\n\n7. **Produce regulatory deliverables**\n   - Generate required disclosures: RTS 28 top-five venue reports, SEC Rule 606 order routing reports, or equivalent [VERIFY applicable filings]\n   - Ensure disclosures are published within regulatory deadlines\n   - Archive supporting data with audit trail for the mandated retention period [VERIFY retention period — typically 5–7 years]\n\n## Output\n\n- **Best Execution Review Report**: Period-over-period venue scorecards, factor-weighted rankings, exception summary, SI threshold status, and conflict-of-interest review\n- **Regulatory Disclosure Package**: Formatted RTS 28 \u002F Rule 606 reports or equivalent, ready for publication or filing\n- **Action Items Log**: Specific remediation tasks with owners, deadlines, and escalation triggers\n- **Committee Minutes Template**: Pre-populated agenda, findings, and resolution language for the best execution committee\n\n## Quality Checks\n\n- All execution quality metrics tie back to source OMS\u002FEMS data — no manual overrides without documented justification\n- Venue rankings reflect the correct factor weightings for each client category\n- SI threshold calculations use current regulatory parameters, not stale figures — mark [VERIFY] if parameter source is older than 6 months\n- Conflicts-of-interest section addresses every affiliated venue and PFOF arrangement in scope\n- Regulatory filings match the format and content requirements of the applicable jurisdiction\n- Prior-period exceptions are tracked to closure — open items carried forward with updated status\n- Report language avoids conclusory compliance statements; instead, states factual findings and flags items requiring further review\n","# Managing Best Execution Compliance\n\nStructures best execution monitoring with venue analysis, systematic internalization assessment, and regulatory compliance documentation.\n\n## When To Use\n\n- Conducting periodic best execution reviews (quarterly, annual, or ad hoc)\n- Evaluating execution venue performance and routing decisions\n- Assessing systematic internalizer (SI) obligations and thresholds\n- Responding to regulatory inquiries on order execution quality\n- Onboarding new execution venues or broker-dealers\n- Documenting rationale for execution arrangements after material changes (new asset classes, venue outages, market structure shifts)\n\n## Inputs To Gather\n\n- **Order flow data**: Volume, notional value, and order types by asset class, venue, and time period\n- **Execution quality metrics**: Fill rates, price improvement\u002Fdisimprovement, effective spread vs. quoted spread, latency, and market impact\n- **Venue fee schedules**: Maker\u002Ftaker fees, rebates, tiered pricing, and payment-for-order-flow (PFOF) arrangements\n- **Regulatory framework**: Applicable regime — MiFID II RTS 27\u002F28 reports, SEC Rule 606, FINRA 5310, or equivalent [VERIFY jurisdiction-specific requirements]\n- **Prior review reports**: Previous best execution committee minutes, exception logs, and remediation items\n- **Client classification**: Retail vs. professional vs. eligible counterparty breakdown, as execution factors weighting differs by client type\n- **Benchmark selection**: Reference prices used (arrival price, VWAP, TWAP, midpoint, close)\n\n## Workflow\n\n1. **Define review scope**\n   - Specify asset classes (equities, fixed income, FX, listed derivatives, OTC derivatives)\n   - Set review period and confirm data completeness across all venues\n   - Identify any venue outages, market disruptions, or corporate actions that affected execution during the period\n\n2. **Aggregate and validate execution data**\n   - Pull execution reports from OMS\u002FEMS and venue-provided RTS 27-equivalent data\n   - Reconcile order counts and notional values against internal records\n   - Flag data gaps or mismatches — mark unresolved items with [VERIFY]\n\n3. **Conduct venue analysis**\n   - Rank venues by execution quality factors: price, cost, speed, likelihood of execution, settlement reliability\n   - Weight factors according to client type and order characteristics (size, urgency, instrument liquidity)\n   - Compare venue performance against the prior period and against peer venues\n   - Identify venues where quality has materially deteriorated and document root cause\n\n4. **Assess systematic internalization**\n   - Calculate SI threshold metrics: frequency, systematic basis, and substantial scale for each instrument class [VERIFY thresholds per current ESMA or local regulator guidance]\n   - Determine whether the firm triggers SI status for any instrument\n   - If SI status applies, confirm pre-trade transparency and quote obligations are met\n\n5. **Evaluate conflicts of interest**\n   - Review PFOF arrangements, affiliated venue routing, and soft-dollar benefits\n   - Confirm that conflicts are disclosed and do not compromise execution quality\n   - Document any instances where conflict mitigation controls were triggered\n\n6. **Document execution decisions**\n   - Record the rationale for venue selection, routing logic changes, and any deviations from standard execution policy\n   - Note exceptions where execution fell outside acceptable parameters and the remedial action taken\n   - Prepare committee-ready summary with recommendations (add venues, remove underperformers, adjust routing weights)\n\n7. **Produce regulatory deliverables**\n   - Generate required disclosures: RTS 28 top-five venue reports, SEC Rule 606 order routing reports, or equivalent [VERIFY applicable filings]\n   - Ensure disclosures are published within regulatory deadlines\n   - Archive supporting data with audit trail for the mandated retention period [VERIFY retention period — typically 5–7 years]\n\n## Output\n\n- **Best Execution Review Report**: Period-over-period venue scorecards, factor-weighted rankings, exception summary, SI threshold status, and conflict-of-interest review\n- **Regulatory Disclosure Package**: Formatted RTS 28 \u002F Rule 606 reports or equivalent, ready for publication or filing\n- **Action Items Log**: Specific remediation tasks with owners, deadlines, and escalation triggers\n- **Committee Minutes Template**: Pre-populated agenda, findings, and resolution language for the best execution committee\n\n## Quality Checks\n\n- All execution quality metrics tie back to source OMS\u002FEMS data — no manual overrides without documented justification\n- Venue rankings reflect the correct factor weightings for each client category\n- SI threshold calculations use current regulatory parameters, not stale figures — mark [VERIFY] if parameter source is older than 6 months\n- Conflicts-of-interest section addresses every affiliated venue and PFOF arrangement in scope\n- Regulatory filings match the format and content requirements of the applicable jurisdiction\n- Prior-period exceptions are tracked to closure — open items carried forward with updated status\n- Report language avoids conclusory compliance statements; instead, states factual findings and flags items requiring further review\n",{"name":5,"tags":24,"source":29,"license":15,"language":30,"metadata":31,"description":7,"imported_at":42,"source_path":43,"source_repository":44},[25,26,27,28],"management","public-markets-and-trading","compliance","regulatory","https:\u002F\u002Fgithub.com\u002FCaseMark\u002Fskills","en",{"author":32,"skill_modes":33,"document_types":36,"practice_areas":38},"casemark",[34,35],"Management","Coordination",[37],"Management Report",[39,40,41],"Trading","Market Making","Execution","2026-09-20","skills\u002Fcapital\u002Fmanaging-best-execution-compliance\u002FSKILL.md","CaseMark\u002Fskills","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Fcompliance\u002Fmanaging-best-execution-compliance","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill managing-best-execution-compliance",{"tool":57,"command":58},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill managing-best-execution-compliance",{"tool":60,"command":61},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill managing-best-execution-compliance","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fcompliance\u002Fmanaging-best-execution-compliance\u002FSKILL.md",true,[],[66,75,82,89,96,103],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":74},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":74},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":74},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":74},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":74},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":74},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]