[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F8D3W9RP0RKFQC5P6239D1":3,"skill-same:01M7F8D3W9RP0RKFQC5P6239D1":64},{"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":44,"commitSha":45,"skillDirectory":46,"forksCount":14,"repositoryHtmlUrl":47,"repositoryHomepageUrl":47,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M7F8D3W9RP0RKFQC5P6239D1","managing-dodd-frank-reporting",null,"Structures Dodd-Frank derivatives reporting with trade reporting, position limits, and SEF compliance. Use when managing DFA reporting, submitting trade reports, or ensuring SEF compliance.","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\u002Ffinance\u002Fmanaging-dodd-frank-reporting\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: managing-dodd-frank-reporting\nlanguage: en\ndescription: Structures Dodd-Frank derivatives reporting with trade reporting, position limits, and SEF compliance. Use when managing DFA reporting, submitting trade reports, or ensuring SEF compliance.\ntags:\n  - management\n  - quantitative-finance\n  - compliance\nmetadata:\n  author: casemark\n  practice_areas:\n    - Derivatives\n    - Quantitative Analysis\n    - Structured Products\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\u002Ffinance\u002Fmanaging-dodd-frank-reporting\u002FSKILL.md\"\nlicense: \"Apache-2.0\"\nimported_at: \"2026-09-20\"\n---\n# Managing Dodd Frank Reporting\n\nStructures Dodd-Frank derivatives reporting with trade reporting, position limits, and SEF compliance.\n\n## When To Use\n\n- Onboarding a new swap dealer or major swap participant to CFTC reporting obligations\n- Setting up or auditing trade reporting flows to a Swap Data Repository (SDR)\n- Evaluating position limit compliance for physical commodity and economically equivalent swaps\n- Ensuring execution on a Swap Execution Facility (SEF) for mandated products\n- Preparing for CFTC examinations or responding to deficiency findings\n- Transitioning to updated reporting rules (e.g., CFTC Rewrite — Parts 43, 45, and 49 amendments)\n\n## Inputs To Gather\n\n- **Entity classification**: Swap dealer (SD), major swap participant (MSP), financial end-user, or non-financial end-user — determines reporting hierarchy and obligations\n- **Product scope**: Asset classes covered (rates, credit, FX, equity, commodities) and specific swap categories\n- **SDR relationships**: Which SDRs the firm reports to (e.g., DTCC DDR, ICE Trade Vault, CME SDR) and connectivity method (FpML, CSV, API)\n- **Unique Swap Identifier (USI) \u002F Unique Transaction Identifier (UTI)**: Generation methodology and who is the reporting counterparty\n- **Position data**: Current open interest by commodity reference contract, including all-months-combined and single-month positions\n- **SEF execution records**: Which products are subject to the made-available-to-trade (MAT) determination [VERIFY current MAT product list]\n- **Existing compliance gaps**: Prior exam findings, SDR rejection logs, late-reporting metrics\n\n## Workflow\n\n1. **Map reporting obligations by entity and product**\n   - Determine reporting counterparty hierarchy (SD > MSP > financial end-user > non-financial end-user)\n   - Classify each swap by asset class, cleared vs. uncleared, and whether it is a \"publicly reportable swap transaction\" under Part 43\n   - Identify real-time public reporting vs. regulatory reporting requirements\n\n2. **Validate SDR connectivity and data fields**\n   - Confirm all CFTC-required data elements are captured at trade inception (counterparty IDs via LEI, product taxonomy via UPI, valuation data, collateral and margin fields)\n   - Verify USI\u002FUTI generation logic and uniqueness controls\n   - Test lifecycle event reporting: amendments, novations, terminations, compressions, and portfolio-level valuations\n   - [VERIFY] Confirm compliance with current CFTC technical specifications (schema version, field formats, and validation rules)\n\n3. **Assess position limit compliance**\n   - Map positions against CFTC federal position limits for the 25 core referenced contracts [VERIFY current contract list and limit levels]\n   - Apply netting rules: aggregate positions across related accounts and affiliated entities\n   - Document any bona fide hedging exemptions — confirm each meets the enumerated hedging categories under CFTC Rule 150.1\n   - Track exchange-set spot-month position limits separately from federal limits\n   - Establish pre-trade and intraday position monitoring with automated alerts at threshold levels (e.g., 80%, 90%, 100% of limits)\n\n4. **Confirm SEF execution compliance**\n   - Identify all swaps subject to the trade execution requirement (MAT-determined products must execute on a SEF or DCM)\n   - Review execution methods: order book, request-for-quote (RFQ) with minimum participant requirements, or block trade exception\n   - Verify block trade thresholds and time delays for public reporting [VERIFY current block sizes by product]\n   - Ensure pre-trade and post-trade transparency obligations are met\n\n5. **Build reporting controls and exception management**\n   - Establish T+1 (or applicable) reporting SLAs with escalation for late or rejected submissions\n   - Create reconciliation process: compare internal books and records against SDR-held data at least quarterly\n   - Implement error-correction workflows for resubmissions and backloading\n   - Document all inter-affiliate swaps and confirm whether the inter-affiliate exemption from clearing\u002FSEF execution applies [VERIFY current no-action relief status]\n\n6. **Compile management report**\n   - Summarize reporting volumes by asset class, SDR, and submission status (accepted, rejected, pending)\n   - Present position limit utilization dashboard across all monitored contracts\n   - Flag open compliance items, remediation timelines, and upcoming regulatory deadlines\n   - Include trend analysis on rejection rates, late-reporting incidents, and reconciliation breaks\n\n## Output\n\n- **Dodd-Frank Reporting Status Report** covering:\n  - Entity-level obligation matrix (who reports what, to which SDR, under which Part)\n  - SDR data quality scorecard (field completeness, rejection rates, timeliness)\n  - Position limit utilization summary by core referenced contract\n  - SEF execution compliance log with any block trade elections\n  - Open items register with owners, deadlines, and risk ratings\n  - Recommendations for process or technology improvements\n\n## Quality Checks\n\n- Confirm every reportable swap has a valid LEI for both counterparties — reject submissions with missing or lapsed LEIs\n- Verify USI\u002FUTI uniqueness; no duplicates across the reporting population\n- Cross-check position limit calculations against independent source (clearing house reports, prime broker statements)\n- Validate that all lifecycle events (amendments, partial terminations) are reported within required timeframes\n- Ensure real-time public dissemination data has been properly masked for block trades and large notional off-facility swaps\n- [VERIFY] Confirm all reporting aligns with the most recent CFTC staff advisories, no-action letters, and rule amendments — Dodd-Frank reporting rules are subject to ongoing revisions\n- Flag any product where clearing mandate, SEF execution mandate, or position limit applicability is uncertain for senior compliance review\n","# Managing Dodd Frank Reporting\n\nStructures Dodd-Frank derivatives reporting with trade reporting, position limits, and SEF compliance.\n\n## When To Use\n\n- Onboarding a new swap dealer or major swap participant to CFTC reporting obligations\n- Setting up or auditing trade reporting flows to a Swap Data Repository (SDR)\n- Evaluating position limit compliance for physical commodity and economically equivalent swaps\n- Ensuring execution on a Swap Execution Facility (SEF) for mandated products\n- Preparing for CFTC examinations or responding to deficiency findings\n- Transitioning to updated reporting rules (e.g., CFTC Rewrite — Parts 43, 45, and 49 amendments)\n\n## Inputs To Gather\n\n- **Entity classification**: Swap dealer (SD), major swap participant (MSP), financial end-user, or non-financial end-user — determines reporting hierarchy and obligations\n- **Product scope**: Asset classes covered (rates, credit, FX, equity, commodities) and specific swap categories\n- **SDR relationships**: Which SDRs the firm reports to (e.g., DTCC DDR, ICE Trade Vault, CME SDR) and connectivity method (FpML, CSV, API)\n- **Unique Swap Identifier (USI) \u002F Unique Transaction Identifier (UTI)**: Generation methodology and who is the reporting counterparty\n- **Position data**: Current open interest by commodity reference contract, including all-months-combined and single-month positions\n- **SEF execution records**: Which products are subject to the made-available-to-trade (MAT) determination [VERIFY current MAT product list]\n- **Existing compliance gaps**: Prior exam findings, SDR rejection logs, late-reporting metrics\n\n## Workflow\n\n1. **Map reporting obligations by entity and product**\n   - Determine reporting counterparty hierarchy (SD > MSP > financial end-user > non-financial end-user)\n   - Classify each swap by asset class, cleared vs. uncleared, and whether it is a \"publicly reportable swap transaction\" under Part 43\n   - Identify real-time public reporting vs. regulatory reporting requirements\n\n2. **Validate SDR connectivity and data fields**\n   - Confirm all CFTC-required data elements are captured at trade inception (counterparty IDs via LEI, product taxonomy via UPI, valuation data, collateral and margin fields)\n   - Verify USI\u002FUTI generation logic and uniqueness controls\n   - Test lifecycle event reporting: amendments, novations, terminations, compressions, and portfolio-level valuations\n   - [VERIFY] Confirm compliance with current CFTC technical specifications (schema version, field formats, and validation rules)\n\n3. **Assess position limit compliance**\n   - Map positions against CFTC federal position limits for the 25 core referenced contracts [VERIFY current contract list and limit levels]\n   - Apply netting rules: aggregate positions across related accounts and affiliated entities\n   - Document any bona fide hedging exemptions — confirm each meets the enumerated hedging categories under CFTC Rule 150.1\n   - Track exchange-set spot-month position limits separately from federal limits\n   - Establish pre-trade and intraday position monitoring with automated alerts at threshold levels (e.g., 80%, 90%, 100% of limits)\n\n4. **Confirm SEF execution compliance**\n   - Identify all swaps subject to the trade execution requirement (MAT-determined products must execute on a SEF or DCM)\n   - Review execution methods: order book, request-for-quote (RFQ) with minimum participant requirements, or block trade exception\n   - Verify block trade thresholds and time delays for public reporting [VERIFY current block sizes by product]\n   - Ensure pre-trade and post-trade transparency obligations are met\n\n5. **Build reporting controls and exception management**\n   - Establish T+1 (or applicable) reporting SLAs with escalation for late or rejected submissions\n   - Create reconciliation process: compare internal books and records against SDR-held data at least quarterly\n   - Implement error-correction workflows for resubmissions and backloading\n   - Document all inter-affiliate swaps and confirm whether the inter-affiliate exemption from clearing\u002FSEF execution applies [VERIFY current no-action relief status]\n\n6. **Compile management report**\n   - Summarize reporting volumes by asset class, SDR, and submission status (accepted, rejected, pending)\n   - Present position limit utilization dashboard across all monitored contracts\n   - Flag open compliance items, remediation timelines, and upcoming regulatory deadlines\n   - Include trend analysis on rejection rates, late-reporting incidents, and reconciliation breaks\n\n## Output\n\n- **Dodd-Frank Reporting Status Report** covering:\n  - Entity-level obligation matrix (who reports what, to which SDR, under which Part)\n  - SDR data quality scorecard (field completeness, rejection rates, timeliness)\n  - Position limit utilization summary by core referenced contract\n  - SEF execution compliance log with any block trade elections\n  - Open items register with owners, deadlines, and risk ratings\n  - Recommendations for process or technology improvements\n\n## Quality Checks\n\n- Confirm every reportable swap has a valid LEI for both counterparties — reject submissions with missing or lapsed LEIs\n- Verify USI\u002FUTI uniqueness; no duplicates across the reporting population\n- Cross-check position limit calculations against independent source (clearing house reports, prime broker statements)\n- Validate that all lifecycle events (amendments, partial terminations) are reported within required timeframes\n- Ensure real-time public dissemination data has been properly masked for block trades and large notional off-facility swaps\n- [VERIFY] Confirm all reporting aligns with the most recent CFTC staff advisories, no-action letters, and rule amendments — Dodd-Frank reporting rules are subject to ongoing revisions\n- Flag any product where clearing mandate, SEF execution mandate, or position limit applicability is uncertain for senior compliance review\n",{"name":5,"tags":24,"source":28,"license":15,"language":29,"metadata":30,"description":7,"imported_at":41,"source_path":42,"source_repository":43},[25,26,27],"management","quantitative-finance","compliance","https:\u002F\u002Fgithub.com\u002FCaseMark\u002Fskills","en",{"author":31,"skill_modes":32,"document_types":35,"practice_areas":37},"casemark",[33,34],"Management","Coordination",[36],"Management Report",[38,39,40],"Derivatives","Quantitative Analysis","Structured Products","2026-09-20","skills\u002Ffinance\u002Fmanaging-dodd-frank-reporting\u002FSKILL.md","CaseMark\u002Fskills","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Ffinance\u002Fmanaging-dodd-frank-reporting","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":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill managing-dodd-frank-reporting",{"tool":56,"command":57},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill managing-dodd-frank-reporting",{"tool":59,"command":60},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill managing-dodd-frank-reporting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Ffinance\u002Fmanaging-dodd-frank-reporting\u002FSKILL.md",true,[],[65,73,80,87,94,101],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"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",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"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":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"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",[],[]]