[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMFTG1P77EQKBBA7W51G8W":3,"skill-same:01M7EMFTG1P77EQKBBA7W51G8W":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},"01M7EMFTG1P77EQKBBA7W51G8W","managing-investor-compliance-requests",null,"Coordinates regulatory and compliance information requests from institutional LPs including FOIA, regulatory filings, and audit support. Use when responding to compliance requests, managing FOIA inquiries, or supporting LP audit processes.","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-investor-compliance-requests\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: managing-investor-compliance-requests\nlanguage: en\ndescription: Coordinates regulatory and compliance information requests from institutional LPs including FOIA, regulatory filings, and audit support. Use when responding to compliance requests, managing FOIA inquiries, or supporting LP audit processes.\ntags:\n  - management\n  - investor-relations-and-lp-reporting\n  - compliance\n  - regulatory\nmetadata:\n  author: casemark\n  practice_areas:\n    - Investor Relations\n    - LP Reporting\n    - Fund Administration\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-investor-compliance-requests\u002FSKILL.md\"\nlicense: \"Apache-2.0\"\nimported_at: \"2026-09-20\"\n---\n# Managing Investor Compliance Requests\n\nCoordinates regulatory and compliance information requests from institutional LPs including FOIA, regulatory filings, and audit support.\n\n## When To Use\n\n- An institutional LP (pension fund, sovereign wealth fund, endowment, insurance company) submits a compliance questionnaire, regulatory data request, or audit inquiry\n- A public pension LP triggers a FOIA or public records request that may expose fund-level data\n- An LP's external auditor requests confirmations, fee schedules, capital account statements, or valuation backup\n- A regulatory filing deadline (e.g., Form PF data, Schedule of Investments, ILPA reporting) requires coordinated data collection from the GP side\n- An LP requests updated KYC\u002FAML documentation, beneficial ownership disclosures, or sanctions certifications from the fund\n\n## Inputs To Gather\n\n- **Request document**: The actual compliance questionnaire, audit confirmation letter, FOIA notice, or regulatory data template from the LP or their agent\n- **LP profile**: Investor type (public pension, ERISA plan, insurance company, endowment), jurisdiction, and any side letter provisions governing reporting obligations\n- **Prior responses**: Previous compliance submissions to this LP to ensure consistency and flag any changed positions\n- **Fund documents**: LPA, side letters, PPM, and subscription agreements that define information rights and confidentiality carve-outs\n- **Data sources**: Fund administrator records, audited financials, portfolio company data, fee and expense reports, capital account statements\n- **Internal contacts**: Investment team members, CFO\u002Fcontroller, legal counsel, compliance officer, and fund administrator contacts needed to compile responses\n- **Timeline**: Response deadline, any interim acknowledgment requirements, and internal review\u002Fapproval workflow lead times\n\n## Workflow\n\n1. **Classify the request**\n   - Determine request type: compliance questionnaire, FOIA\u002Fpublic records, audit confirmation, regulatory filing support, or KYC\u002FAML update\n   - Identify the requesting party (LP directly, LP's auditor, LP's regulatory body, or third-party consultant)\n   - Check side letter provisions for any enhanced reporting obligations or confidentiality restrictions specific to this LP\n   - Flag if the request touches FOIA-sensitive data (track record, fee terms, carried interest) that may require confidential treatment claims [VERIFY: state-specific FOIA exemption procedures vary]\n\n2. **Scope and assign**\n   - Map each data element requested to an internal owner (fund admin, controller, legal, investment team)\n   - Identify items that can be fulfilled from existing reports vs. items requiring new data pulls or calculations\n   - Set internal deadlines with buffer ahead of the LP's deadline (typically 5-7 business days early for review cycles)\n   - Flag any items that require legal review before disclosure (e.g., pending litigation, regulatory inquiries, MNPI considerations)\n\n3. **Compile response package**\n   - Gather data from each assigned owner; cross-check figures against audited financials and prior submissions for consistency\n   - For compliance questionnaires: answer each question directly, cite supporting documents, and note any qualifications or scope limitations\n   - For FOIA requests: prepare redaction recommendations for trade secrets, proprietary terms, and competitive information; draft confidential treatment request if applicable [VERIFY: specific FOIA exemptions and procedures by state]\n   - For audit confirmations: reconcile requested balances to fund records, note any timing differences, obtain controller sign-off\n   - For KYC\u002FAML updates: compile current entity documents, beneficial ownership certifications, OFAC\u002Fsanctions representations, and any Form W-8\u002FW-9 updates\n\n4. **Internal review and approval**\n   - Route completed response through compliance officer for regulatory accuracy\n   - Legal review for any items involving confidentiality, privilege, or disclosure risk\n   - Senior management sign-off where required by fund policy or side letter terms\n   - Confirm all attachments, exhibits, and supporting schedules are included and properly labeled\n\n5. **Submit and document**\n   - Deliver response via the LP's specified channel (portal upload, encrypted email, secure file transfer)\n   - Confirm receipt with the requesting party\n   - Archive the complete request-response package in the investor compliance file with date stamps\n   - Log the request in the LP compliance tracker for trend analysis and future reference\n\n## Output\n\n- **Response package**: Completed questionnaire, confirmation letter, or data submission formatted per LP\u002Fauditor specifications\n- **FOIA treatment memo** (if applicable): Redaction log and confidential treatment request with cited exemptions\n- **Internal tracking update**: Entry in compliance request log capturing request date, type, responding parties, submission date, and any open follow-up items\n- **Escalation notes**: Any unresolved items, disputed data points, or legal concerns flagged during the process\n\n## Quality Checks\n\n- All figures reconcile to audited financials or fund administrator records; no unsupported estimates\n- Response is consistent with prior submissions to the same LP — discrepancies are explained with a change narrative\n- Confidentiality provisions in side letters and LPA have been respected; no over-disclosure of co-investor or portfolio company data\n- FOIA redaction requests cite specific statutory exemptions, not generic objections [VERIFY: exemption language varies by jurisdiction]\n- Deadlines met or extension formally requested before expiration\n- Response reviewed by at least two internal parties (data owner + compliance\u002Flegal) before submission\n- KYC\u002FAML certifications are current (not expired) and match the fund's registered entity information\n","# Managing Investor Compliance Requests\n\nCoordinates regulatory and compliance information requests from institutional LPs including FOIA, regulatory filings, and audit support.\n\n## When To Use\n\n- An institutional LP (pension fund, sovereign wealth fund, endowment, insurance company) submits a compliance questionnaire, regulatory data request, or audit inquiry\n- A public pension LP triggers a FOIA or public records request that may expose fund-level data\n- An LP's external auditor requests confirmations, fee schedules, capital account statements, or valuation backup\n- A regulatory filing deadline (e.g., Form PF data, Schedule of Investments, ILPA reporting) requires coordinated data collection from the GP side\n- An LP requests updated KYC\u002FAML documentation, beneficial ownership disclosures, or sanctions certifications from the fund\n\n## Inputs To Gather\n\n- **Request document**: The actual compliance questionnaire, audit confirmation letter, FOIA notice, or regulatory data template from the LP or their agent\n- **LP profile**: Investor type (public pension, ERISA plan, insurance company, endowment), jurisdiction, and any side letter provisions governing reporting obligations\n- **Prior responses**: Previous compliance submissions to this LP to ensure consistency and flag any changed positions\n- **Fund documents**: LPA, side letters, PPM, and subscription agreements that define information rights and confidentiality carve-outs\n- **Data sources**: Fund administrator records, audited financials, portfolio company data, fee and expense reports, capital account statements\n- **Internal contacts**: Investment team members, CFO\u002Fcontroller, legal counsel, compliance officer, and fund administrator contacts needed to compile responses\n- **Timeline**: Response deadline, any interim acknowledgment requirements, and internal review\u002Fapproval workflow lead times\n\n## Workflow\n\n1. **Classify the request**\n   - Determine request type: compliance questionnaire, FOIA\u002Fpublic records, audit confirmation, regulatory filing support, or KYC\u002FAML update\n   - Identify the requesting party (LP directly, LP's auditor, LP's regulatory body, or third-party consultant)\n   - Check side letter provisions for any enhanced reporting obligations or confidentiality restrictions specific to this LP\n   - Flag if the request touches FOIA-sensitive data (track record, fee terms, carried interest) that may require confidential treatment claims [VERIFY: state-specific FOIA exemption procedures vary]\n\n2. **Scope and assign**\n   - Map each data element requested to an internal owner (fund admin, controller, legal, investment team)\n   - Identify items that can be fulfilled from existing reports vs. items requiring new data pulls or calculations\n   - Set internal deadlines with buffer ahead of the LP's deadline (typically 5-7 business days early for review cycles)\n   - Flag any items that require legal review before disclosure (e.g., pending litigation, regulatory inquiries, MNPI considerations)\n\n3. **Compile response package**\n   - Gather data from each assigned owner; cross-check figures against audited financials and prior submissions for consistency\n   - For compliance questionnaires: answer each question directly, cite supporting documents, and note any qualifications or scope limitations\n   - For FOIA requests: prepare redaction recommendations for trade secrets, proprietary terms, and competitive information; draft confidential treatment request if applicable [VERIFY: specific FOIA exemptions and procedures by state]\n   - For audit confirmations: reconcile requested balances to fund records, note any timing differences, obtain controller sign-off\n   - For KYC\u002FAML updates: compile current entity documents, beneficial ownership certifications, OFAC\u002Fsanctions representations, and any Form W-8\u002FW-9 updates\n\n4. **Internal review and approval**\n   - Route completed response through compliance officer for regulatory accuracy\n   - Legal review for any items involving confidentiality, privilege, or disclosure risk\n   - Senior management sign-off where required by fund policy or side letter terms\n   - Confirm all attachments, exhibits, and supporting schedules are included and properly labeled\n\n5. **Submit and document**\n   - Deliver response via the LP's specified channel (portal upload, encrypted email, secure file transfer)\n   - Confirm receipt with the requesting party\n   - Archive the complete request-response package in the investor compliance file with date stamps\n   - Log the request in the LP compliance tracker for trend analysis and future reference\n\n## Output\n\n- **Response package**: Completed questionnaire, confirmation letter, or data submission formatted per LP\u002Fauditor specifications\n- **FOIA treatment memo** (if applicable): Redaction log and confidential treatment request with cited exemptions\n- **Internal tracking update**: Entry in compliance request log capturing request date, type, responding parties, submission date, and any open follow-up items\n- **Escalation notes**: Any unresolved items, disputed data points, or legal concerns flagged during the process\n\n## Quality Checks\n\n- All figures reconcile to audited financials or fund administrator records; no unsupported estimates\n- Response is consistent with prior submissions to the same LP — discrepancies are explained with a change narrative\n- Confidentiality provisions in side letters and LPA have been respected; no over-disclosure of co-investor or portfolio company data\n- FOIA redaction requests cite specific statutory exemptions, not generic objections [VERIFY: exemption language varies by jurisdiction]\n- Deadlines met or extension formally requested before expiration\n- Response reviewed by at least two internal parties (data owner + compliance\u002Flegal) before submission\n- KYC\u002FAML certifications are current (not expired) and match the fund's registered entity information\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","investor-relations-and-lp-reporting","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],"Investor Relations","LP Reporting","Fund Administration","2026-09-20","skills\u002Fcapital\u002Fmanaging-investor-compliance-requests\u002FSKILL.md","CaseMark\u002Fskills","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Fcompliance\u002Fmanaging-investor-compliance-requests","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-investor-compliance-requests",{"tool":57,"command":58},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill managing-investor-compliance-requests",{"tool":60,"command":61},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill managing-investor-compliance-requests","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fcompliance\u002Fmanaging-investor-compliance-requests\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",[],[]]