[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EM7JD9VNEB03CK7DKM8WS7":3,"skill-same:01M7EM7JD9VNEB03CK7DKM8WS7":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},"01M7EM7JD9VNEB03CK7DKM8WS7","conducting-pre-trade-compliance-checks",null,"Structures pre-trade compliance with restricted list screening, position limits, and regulatory constraint verification. Use when running pre-trade compliance, screening restricted securities, or verifying trading limits.","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\u002Fconducting-pre-trade-compliance-checks\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: conducting-pre-trade-compliance-checks\nlanguage: en\ndescription: Structures pre-trade compliance with restricted list screening, position limits, and regulatory constraint verification. Use when running pre-trade compliance, screening restricted securities, or verifying trading limits.\ntags:\n  - process\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    - Process Documentation\n  skill_modes:\n    - Process Management\nsource: \"https:\u002F\u002Fgithub.com\u002FCaseMark\u002Fskills\"\nsource_repository: \"CaseMark\u002Fskills\"\nsource_path: \"skills\u002Fcapital\u002Fconducting-pre-trade-compliance-checks\u002FSKILL.md\"\nlicense: \"Apache-2.0\"\nimported_at: \"2026-09-20\"\n---\n# Conducting Pre Trade Compliance Checks\n\nStructures pre-trade compliance workflows covering restricted list screening, position and concentration limit verification, and regulatory constraint checks before order submission.\n\n## When To Use\n\n- Before submitting any order to verify the trade does not violate firm or regulatory constraints\n- When onboarding a new security or counterparty to confirm it is not on a restricted or watch list\n- When a trader or PM requests a compliance greenlight on a proposed position change\n- During periodic review of standing orders or strategy-level allocations against updated restricted lists\n- When market conditions or corporate events (e.g., MNPI receipt, blackout periods) trigger re-screening\n\n## Inputs To Gather\n\n- **Proposed trade details**: security identifier (CUSIP\u002FISIN\u002Fticker), side (buy\u002Fsell\u002Fshort), notional or share quantity, order type, account\u002Ffund\n- **Restricted and watch lists**: firm restricted list, issuer-level watch list, MNPI-flagged names, sanctions lists (OFAC SDN, EU consolidated list) [VERIFY applicable sanctions regimes]\n- **Current portfolio positions**: existing holdings in the security and correlated instruments across all accounts\n- **Position and concentration limits**: regulatory limits (e.g., 13D\u002F13G 5% beneficial ownership threshold, Reg SHO locate requirements), fund mandate limits, internal risk limits, single-issuer concentration caps [VERIFY fund-specific or strategy-specific thresholds]\n- **Regulatory calendars**: blackout windows, quiet periods, earnings-related trading restrictions\n- **Client or account restrictions**: IPS constraints, ESG exclusion lists, sector\u002Fcountry prohibitions\n\n## Workflow\n\n1. **Identify the trade and account context**\n   - Confirm security identifier, direction, size, and target account\n   - Determine whether the account is discretionary, advisory, or proprietary — each may carry different compliance rules\n\n2. **Screen against restricted and watch lists**\n   - Check the security and its issuer against the firm restricted list and any MNPI-flagged names\n   - Screen the counterparty (if OTC) and the issuer against OFAC SDN, sectoral sanctions, and any jurisdiction-specific denied-party lists [VERIFY which sanctions programs apply]\n   - If the security is on the watch list (not restricted), flag for enhanced monitoring but do not auto-block\n   - Document the list version\u002Fdate used for screening\n\n3. **Verify position and ownership limits**\n   - Calculate the pro-forma position (current holdings + proposed trade) across all accounts under common control\n   - Check against regulatory ownership thresholds: 5% beneficial ownership (13D\u002F13G), 10% short-swing profit (Section 16), exchange position limits [VERIFY exchange-specific limits for derivatives]\n   - Confirm the trade does not breach fund-level concentration limits (single issuer, sector, geography, liquidity bucket)\n\n4. **Check short-sale and locate compliance**\n   - For short sales, confirm a valid locate has been obtained per Reg SHO Rule 203(b) [VERIFY if the security is on the threshold list or is hard-to-borrow]\n   - Verify the security is not subject to an active short-sale circuit breaker (Rule 201 alternative uptick)\n\n5. **Validate against trading window and blackout restrictions**\n   - Confirm the firm is not in a blackout or quiet period for the issuer\n   - Cross-check personal trading pre-clearance if the order is from a covered person under the firm's Code of Ethics\n\n6. **Apply account-level and mandate restrictions**\n   - Verify the trade is consistent with the investment policy statement, prospectus limits, or client guidelines\n   - Screen against ESG exclusion lists and sector\u002Fcountry prohibitions if applicable\n\n7. **Record the compliance determination**\n   - Stamp the order with a compliance pass\u002Ffail\u002Fconditional result and timestamp\n   - If conditional, specify the remediation needed (e.g., reduce size below threshold, obtain locate confirmation)\n   - Archive the screening evidence for audit trail purposes\n\n## Output\n\n- **Compliance determination**: clear pass, fail (with blocking reason), or conditional approval with required remediation steps\n- **Screening log**: list of each check performed, data sources used, list versions\u002Fdates, and result per check\n- **Flagged items**: any watch-list hits, near-limit warnings, or items requiring enhanced monitoring\n- **Exception escalation memo** (if needed): narrative explaining the issue, relevant rule or policy, and recommended resolution for compliance officer review\n\n## Quality Checks\n\n- Confirm all security identifiers were resolved correctly — ticker aliases and class shares can cause false negatives\n- Verify restricted list and sanctions list versions are current (stale lists are a common audit finding)\n- Ensure pro-forma position calculations include all accounts under common beneficial ownership, not just the requesting account\n- Cross-check that the compliance timestamp precedes the order submission timestamp in the audit trail\n- For any [VERIFY] items, confirm resolution before releasing the order — do not default to pass on unresolved flags\n- Escalate to the Chief Compliance Officer when a proposed trade is within 80% of a hard regulatory threshold or involves a watch-list name with active MNPI concerns\n","# Conducting Pre Trade Compliance Checks\n\nStructures pre-trade compliance workflows covering restricted list screening, position and concentration limit verification, and regulatory constraint checks before order submission.\n\n## When To Use\n\n- Before submitting any order to verify the trade does not violate firm or regulatory constraints\n- When onboarding a new security or counterparty to confirm it is not on a restricted or watch list\n- When a trader or PM requests a compliance greenlight on a proposed position change\n- During periodic review of standing orders or strategy-level allocations against updated restricted lists\n- When market conditions or corporate events (e.g., MNPI receipt, blackout periods) trigger re-screening\n\n## Inputs To Gather\n\n- **Proposed trade details**: security identifier (CUSIP\u002FISIN\u002Fticker), side (buy\u002Fsell\u002Fshort), notional or share quantity, order type, account\u002Ffund\n- **Restricted and watch lists**: firm restricted list, issuer-level watch list, MNPI-flagged names, sanctions lists (OFAC SDN, EU consolidated list) [VERIFY applicable sanctions regimes]\n- **Current portfolio positions**: existing holdings in the security and correlated instruments across all accounts\n- **Position and concentration limits**: regulatory limits (e.g., 13D\u002F13G 5% beneficial ownership threshold, Reg SHO locate requirements), fund mandate limits, internal risk limits, single-issuer concentration caps [VERIFY fund-specific or strategy-specific thresholds]\n- **Regulatory calendars**: blackout windows, quiet periods, earnings-related trading restrictions\n- **Client or account restrictions**: IPS constraints, ESG exclusion lists, sector\u002Fcountry prohibitions\n\n## Workflow\n\n1. **Identify the trade and account context**\n   - Confirm security identifier, direction, size, and target account\n   - Determine whether the account is discretionary, advisory, or proprietary — each may carry different compliance rules\n\n2. **Screen against restricted and watch lists**\n   - Check the security and its issuer against the firm restricted list and any MNPI-flagged names\n   - Screen the counterparty (if OTC) and the issuer against OFAC SDN, sectoral sanctions, and any jurisdiction-specific denied-party lists [VERIFY which sanctions programs apply]\n   - If the security is on the watch list (not restricted), flag for enhanced monitoring but do not auto-block\n   - Document the list version\u002Fdate used for screening\n\n3. **Verify position and ownership limits**\n   - Calculate the pro-forma position (current holdings + proposed trade) across all accounts under common control\n   - Check against regulatory ownership thresholds: 5% beneficial ownership (13D\u002F13G), 10% short-swing profit (Section 16), exchange position limits [VERIFY exchange-specific limits for derivatives]\n   - Confirm the trade does not breach fund-level concentration limits (single issuer, sector, geography, liquidity bucket)\n\n4. **Check short-sale and locate compliance**\n   - For short sales, confirm a valid locate has been obtained per Reg SHO Rule 203(b) [VERIFY if the security is on the threshold list or is hard-to-borrow]\n   - Verify the security is not subject to an active short-sale circuit breaker (Rule 201 alternative uptick)\n\n5. **Validate against trading window and blackout restrictions**\n   - Confirm the firm is not in a blackout or quiet period for the issuer\n   - Cross-check personal trading pre-clearance if the order is from a covered person under the firm's Code of Ethics\n\n6. **Apply account-level and mandate restrictions**\n   - Verify the trade is consistent with the investment policy statement, prospectus limits, or client guidelines\n   - Screen against ESG exclusion lists and sector\u002Fcountry prohibitions if applicable\n\n7. **Record the compliance determination**\n   - Stamp the order with a compliance pass\u002Ffail\u002Fconditional result and timestamp\n   - If conditional, specify the remediation needed (e.g., reduce size below threshold, obtain locate confirmation)\n   - Archive the screening evidence for audit trail purposes\n\n## Output\n\n- **Compliance determination**: clear pass, fail (with blocking reason), or conditional approval with required remediation steps\n- **Screening log**: list of each check performed, data sources used, list versions\u002Fdates, and result per check\n- **Flagged items**: any watch-list hits, near-limit warnings, or items requiring enhanced monitoring\n- **Exception escalation memo** (if needed): narrative explaining the issue, relevant rule or policy, and recommended resolution for compliance officer review\n\n## Quality Checks\n\n- Confirm all security identifiers were resolved correctly — ticker aliases and class shares can cause false negatives\n- Verify restricted list and sanctions list versions are current (stale lists are a common audit finding)\n- Ensure pro-forma position calculations include all accounts under common beneficial ownership, not just the requesting account\n- Cross-check that the compliance timestamp precedes the order submission timestamp in the audit trail\n- For any [VERIFY] items, confirm resolution before releasing the order — do not default to pass on unresolved flags\n- Escalate to the Chief Compliance Officer when a proposed trade is within 80% of a hard regulatory threshold or involves a watch-list name with active MNPI concerns\n",{"name":5,"tags":24,"source":29,"license":15,"language":30,"metadata":31,"description":7,"imported_at":41,"source_path":42,"source_repository":43},[25,26,27,28],"process","public-markets-and-trading","compliance","regulatory","https:\u002F\u002Fgithub.com\u002FCaseMark\u002Fskills","en",{"author":32,"skill_modes":33,"document_types":35,"practice_areas":37},"casemark",[34],"Process Management",[36],"Process Documentation",[38,39,40],"Trading","Market Making","Execution","2026-09-20","skills\u002Fcapital\u002Fconducting-pre-trade-compliance-checks\u002FSKILL.md","CaseMark\u002Fskills","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Fcompliance\u002Fconducting-pre-trade-compliance-checks","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 conducting-pre-trade-compliance-checks",{"tool":56,"command":57},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill conducting-pre-trade-compliance-checks",{"tool":59,"command":60},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill conducting-pre-trade-compliance-checks","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fcompliance\u002Fconducting-pre-trade-compliance-checks\u002FSKILL.md",true,[],[65,74,81,88,95,102],{"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":73},"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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":73},"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":73},"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":73},"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":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":73},"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":73},"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",[],[]]