[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F8JS0WM4HJ2D62W01DFQXN":3,"skill-same:01M7F8JS0WM4HJ2D62W01DFQXN":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},"01M7F8JS0WM4HJ2D62W01DFQXN","managing-fund-compliance-monitoring",null,"Structures investment compliance testing with guideline monitoring and breach reporting. Use when monitoring investment guidelines, testing compliance, or reporting breaches.","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-fund-compliance-monitoring\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: managing-fund-compliance-monitoring\nlanguage: en\ndescription: Structures investment compliance testing with guideline monitoring and breach reporting. Use when monitoring investment guidelines, testing compliance, or reporting breaches.\ntags:\n  - management\n  - fund-operations\n  - compliance\n  - investment\nmetadata:\n  author: casemark\n  practice_areas:\n    - Fund Administration\n    - Investment Operations\n    - Fund Accounting\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-fund-compliance-monitoring\u002FSKILL.md\"\nlicense: \"Apache-2.0\"\nimported_at: \"2026-09-20\"\n---\n# Managing Fund Compliance Monitoring\n\nStructures investment compliance testing with guideline monitoring and breach reporting.\n\n## When To Use\n\n- Setting up or reviewing pre-trade and post-trade compliance testing frameworks\n- Monitoring portfolio holdings against investment policy statement (IPS) guidelines, prospectus limits, or regulatory constraints\n- Investigating and documenting guideline breaches (active or passive)\n- Producing periodic compliance status reports for fund boards, trustees, or regulators\n- Onboarding a new fund or strategy into the compliance monitoring system\n- Responding to regulatory inquiries about investment guideline adherence\n\n## Inputs To Gather\n\n- **Investment guidelines source**: IPS, prospectus, side letters, board resolutions, or regulatory orders defining permissible investments, concentration limits, and prohibited holdings\n- **Portfolio data**: Current holdings, NAV, sector\u002Fgeography\u002Fasset-class breakdowns, counterparty exposures, liquidity profiles\n- **Guideline parameter schedule**: Specific quantitative limits (e.g., max 5% single issuer, max 25% sector, min credit rating BBB-) and qualitative restrictions (e.g., no tobacco, no sanctioned entities)\n- **Prior breach log**: History of past breaches, remediation actions taken, and cure deadlines\n- **Testing frequency**: Daily, weekly, monthly — per guideline category\n- **Escalation contacts**: Portfolio manager, CCO, fund board representative, external compliance counsel\n\n## Workflow\n\n1. **Map guidelines to testable rules**\n   - Parse each investment guideline into a discrete, testable compliance rule (e.g., \"single-issuer equity exposure ≤ 5% of NAV\")\n   - Classify each rule by type: concentration limit, asset-class restriction, credit quality floor, liquidity requirement, leverage cap, prohibited investment, diversification test\n   - Note whether each rule applies pre-trade, post-trade, or both\n   - Flag any guideline language that is ambiguous or requires interpretation [VERIFY with fund counsel]\n\n2. **Configure monitoring parameters**\n   - Set quantitative thresholds with hard limits and warning bands (e.g., hard limit 5%, warning at 4.5%)\n   - Define the NAV denominator and valuation methodology for percentage-based tests [VERIFY — some guidelines use gross assets, others use net assets]\n   - Establish look-through requirements for fund-of-funds, ETF holdings, or derivative exposures\n   - Specify cure periods for passive breaches caused by market movements vs. active breaches from trades\n\n3. **Run compliance tests**\n   - Execute each mapped rule against current portfolio data\n   - For pre-trade tests: validate proposed trades against guidelines before execution\n   - For post-trade tests: scan end-of-day holdings against all applicable rules\n   - Record pass\u002Ffail status, current value vs. limit, and margin to breach for each test\n   - Apply look-through analysis where required for underlying exposures\n\n4. **Detect and classify breaches**\n   - Identify any rule where the current exposure exceeds the hard limit\n   - Classify each breach: **active** (caused by a new trade) vs. **passive** (caused by market movement, redemptions, or corporate actions)\n   - Determine severity: technical\u002Fde minimis vs. material\n   - Check whether the breach falls within a defined cure period or requires immediate remediation\n   - Cross-reference against prior breach log for repeat patterns\n\n5. **Escalate and remediate**\n   - Notify the portfolio manager immediately for active breaches\n   - Escalate to the CCO per the fund's breach escalation matrix\n   - Document proposed remediation plan with target cure date\n   - For passive breaches within cure period, monitor daily until resolved\n   - If remediation requires trading, confirm the corrective trade itself does not trigger a new breach\n\n6. **Report**\n   - Produce compliance status report covering all tested guidelines, pass\u002Ffail results, and open breaches\n   - Include breach detail section: date detected, classification, current exposure vs. limit, remediation status, expected cure date\n   - Summarize trends: new breaches this period, cured breaches, aging breaches, repeat breaches\n   - Note any guideline changes, new fund onboardings, or parameter updates since last report\n   - Append attestation language for board or trustee sign-off [VERIFY — attestation format varies by jurisdiction and fund structure]\n\n## Output\n\nThe compliance monitoring report should include:\n\n- **Dashboard summary**: Total rules tested, pass count, warning count, breach count\n- **Breach register**: Each open breach with classification, severity, exposure detail, cure deadline, and remediation owner\n- **Guideline-by-guideline results**: Tabular view of every tested rule showing current value, limit, headroom, and status\n- **Trend analysis**: Period-over-period breach counts, time-to-cure metrics, repeat-breach flags\n- **Action items**: Outstanding remediation tasks with owners and deadlines\n- **Regulatory disclosure notes**: Any breaches that may trigger regulatory reporting obligations [VERIFY — reporting thresholds and timelines vary by regulator: SEC, FCA, CSSF, MAS, etc.]\n\n## Quality Checks\n\n- Confirm all investment guidelines from the governing documents are mapped to testable rules — no gaps\n- Verify portfolio data is as-of the correct date and reconciles to the fund administrator's records\n- Validate that percentage calculations use the correct denominator (gross vs. net assets) per each guideline's terms\n- Check that look-through analysis is applied consistently for pooled vehicles and derivatives\n- Ensure active vs. passive breach classification is accurate — misclassification affects cure period eligibility\n- Confirm escalation timelines were met per the fund's compliance manual\n- Review breach descriptions for completeness: a third party should be able to understand the breach without additional context\n- Cross-check that remediation actions do not themselves create new compliance issues\n","# Managing Fund Compliance Monitoring\n\nStructures investment compliance testing with guideline monitoring and breach reporting.\n\n## When To Use\n\n- Setting up or reviewing pre-trade and post-trade compliance testing frameworks\n- Monitoring portfolio holdings against investment policy statement (IPS) guidelines, prospectus limits, or regulatory constraints\n- Investigating and documenting guideline breaches (active or passive)\n- Producing periodic compliance status reports for fund boards, trustees, or regulators\n- Onboarding a new fund or strategy into the compliance monitoring system\n- Responding to regulatory inquiries about investment guideline adherence\n\n## Inputs To Gather\n\n- **Investment guidelines source**: IPS, prospectus, side letters, board resolutions, or regulatory orders defining permissible investments, concentration limits, and prohibited holdings\n- **Portfolio data**: Current holdings, NAV, sector\u002Fgeography\u002Fasset-class breakdowns, counterparty exposures, liquidity profiles\n- **Guideline parameter schedule**: Specific quantitative limits (e.g., max 5% single issuer, max 25% sector, min credit rating BBB-) and qualitative restrictions (e.g., no tobacco, no sanctioned entities)\n- **Prior breach log**: History of past breaches, remediation actions taken, and cure deadlines\n- **Testing frequency**: Daily, weekly, monthly — per guideline category\n- **Escalation contacts**: Portfolio manager, CCO, fund board representative, external compliance counsel\n\n## Workflow\n\n1. **Map guidelines to testable rules**\n   - Parse each investment guideline into a discrete, testable compliance rule (e.g., \"single-issuer equity exposure ≤ 5% of NAV\")\n   - Classify each rule by type: concentration limit, asset-class restriction, credit quality floor, liquidity requirement, leverage cap, prohibited investment, diversification test\n   - Note whether each rule applies pre-trade, post-trade, or both\n   - Flag any guideline language that is ambiguous or requires interpretation [VERIFY with fund counsel]\n\n2. **Configure monitoring parameters**\n   - Set quantitative thresholds with hard limits and warning bands (e.g., hard limit 5%, warning at 4.5%)\n   - Define the NAV denominator and valuation methodology for percentage-based tests [VERIFY — some guidelines use gross assets, others use net assets]\n   - Establish look-through requirements for fund-of-funds, ETF holdings, or derivative exposures\n   - Specify cure periods for passive breaches caused by market movements vs. active breaches from trades\n\n3. **Run compliance tests**\n   - Execute each mapped rule against current portfolio data\n   - For pre-trade tests: validate proposed trades against guidelines before execution\n   - For post-trade tests: scan end-of-day holdings against all applicable rules\n   - Record pass\u002Ffail status, current value vs. limit, and margin to breach for each test\n   - Apply look-through analysis where required for underlying exposures\n\n4. **Detect and classify breaches**\n   - Identify any rule where the current exposure exceeds the hard limit\n   - Classify each breach: **active** (caused by a new trade) vs. **passive** (caused by market movement, redemptions, or corporate actions)\n   - Determine severity: technical\u002Fde minimis vs. material\n   - Check whether the breach falls within a defined cure period or requires immediate remediation\n   - Cross-reference against prior breach log for repeat patterns\n\n5. **Escalate and remediate**\n   - Notify the portfolio manager immediately for active breaches\n   - Escalate to the CCO per the fund's breach escalation matrix\n   - Document proposed remediation plan with target cure date\n   - For passive breaches within cure period, monitor daily until resolved\n   - If remediation requires trading, confirm the corrective trade itself does not trigger a new breach\n\n6. **Report**\n   - Produce compliance status report covering all tested guidelines, pass\u002Ffail results, and open breaches\n   - Include breach detail section: date detected, classification, current exposure vs. limit, remediation status, expected cure date\n   - Summarize trends: new breaches this period, cured breaches, aging breaches, repeat breaches\n   - Note any guideline changes, new fund onboardings, or parameter updates since last report\n   - Append attestation language for board or trustee sign-off [VERIFY — attestation format varies by jurisdiction and fund structure]\n\n## Output\n\nThe compliance monitoring report should include:\n\n- **Dashboard summary**: Total rules tested, pass count, warning count, breach count\n- **Breach register**: Each open breach with classification, severity, exposure detail, cure deadline, and remediation owner\n- **Guideline-by-guideline results**: Tabular view of every tested rule showing current value, limit, headroom, and status\n- **Trend analysis**: Period-over-period breach counts, time-to-cure metrics, repeat-breach flags\n- **Action items**: Outstanding remediation tasks with owners and deadlines\n- **Regulatory disclosure notes**: Any breaches that may trigger regulatory reporting obligations [VERIFY — reporting thresholds and timelines vary by regulator: SEC, FCA, CSSF, MAS, etc.]\n\n## Quality Checks\n\n- Confirm all investment guidelines from the governing documents are mapped to testable rules — no gaps\n- Verify portfolio data is as-of the correct date and reconciles to the fund administrator's records\n- Validate that percentage calculations use the correct denominator (gross vs. net assets) per each guideline's terms\n- Check that look-through analysis is applied consistently for pooled vehicles and derivatives\n- Ensure active vs. passive breach classification is accurate — misclassification affects cure period eligibility\n- Confirm escalation timelines were met per the fund's compliance manual\n- Review breach descriptions for completeness: a third party should be able to understand the breach without additional context\n- Cross-check that remediation actions do not themselves create new compliance issues\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","fund-operations","compliance","investment","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],"Fund Administration","Investment Operations","Fund Accounting","2026-09-20","skills\u002Ffinance\u002Fmanaging-fund-compliance-monitoring\u002FSKILL.md","CaseMark\u002Fskills","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Ffinance\u002Fmanaging-fund-compliance-monitoring","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-fund-compliance-monitoring",{"tool":57,"command":58},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill managing-fund-compliance-monitoring",{"tool":60,"command":61},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill managing-fund-compliance-monitoring","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Ffinance\u002Fmanaging-fund-compliance-monitoring\u002FSKILL.md",true,[],[66,74,81,88,95,102],{"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":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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"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":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"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",[],[]]