[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F70GCQT4WMKNWRYK0J3VQS":3,"skill-same:01M7F70GCQT4WMKNWRYK0J3VQS":70},{"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},"01M7F70GCQT4WMKNWRYK0J3VQS","auditing-aml-transactions",null,"Screens transaction data for suspicious patterns using red flag typologies and structures SAR narrative elements. Use when reviewing transactions for AML, identifying suspicious activity, or drafting SAR narratives.","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\u002Fauditing-aml-transactions\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: auditing-aml-transactions\nlanguage: en\ndescription: Screens transaction data for suspicious patterns using red flag typologies and structures SAR narrative elements. Use when reviewing transactions for AML, identifying suspicious activity, or drafting SAR narratives.\ntags:\n  - compliance\n  - financial-compliance\n  - aml\nmetadata:\n  author: casemark\n  practice_areas:\n    - Regulatory Compliance\n    - Financial Regulation\n    - Compliance\n  document_types:\n    - Compliance Report\n  skill_modes:\n    - Audit\n    - Review\nsource: \"https:\u002F\u002Fgithub.com\u002FCaseMark\u002Fskills\"\nsource_repository: \"CaseMark\u002Fskills\"\nsource_path: \"skills\u002Ffinance\u002Fauditing-aml-transactions\u002FSKILL.md\"\nlicense: \"Apache-2.0\"\nimported_at: \"2026-09-20\"\n---\n# Auditing AML Transactions\n\nScreens transaction data for suspicious patterns using red flag typologies and structures SAR narrative elements for BSA\u002FAML compliance.\n\n## When To Use\n\n- Transaction monitoring system generates an alert requiring human review\n- BSA officer receives a referral (internal, law enforcement, or examiner finding)\n- Periodic look-back or enhanced due diligence review of high-risk accounts\n- Continuation SAR is due on the 90-day cycle\n- Independent audit requires sample transaction review\n- 314(b) information-sharing request received from another institution\n\n## Inputs To Gather\n\nCollect all items below before starting review. If transaction records are unavailable, STOP — document the gap and escalate.\n\n### Institution & Scope\n\n- Institution type (bank, MSB, broker-dealer, credit union, insurance, casino, other) [VERIFY]\n- Charter\u002Flicense jurisdiction and primary regulator [VERIFY]\n- BSA\u002FAML program status (established \u002F recently remediated \u002F under consent order)\n- Review period (start and end dates)\n- Alert source and alert\u002Fcase ID\n\n### Subject Information\n\n- Subject name(s) — individuals and\u002For entities\n- Account number(s), account type(s), and open date\n- Customer risk rating (Low \u002F Medium \u002F High \u002F Unrated)\n- KYC profile: stated occupation, income, expected activity, source of funds\n- Prior SAR history on this subject\n\n### Data Sources\n\nConfirm availability of each: transaction records (debits\u002Fcredits), wire transfer details (originator\u002Fbeneficiary), cash activity and CTR history, check images and deposit slips, account statements, CDD\u002FEDD documentation, OFAC\u002Fsanctions screening results, negative news and adverse media, law enforcement subpoenas or 314(b) requests.\n\n## Workflow\n\n### Step 1 — Transaction Profiling\n\nSummarize account activity for the review period:\n\n| Metric | Value |\n|---|---|\n| Total credits (count \u002F dollar) | |\n| Total debits (count \u002F dollar) | |\n| Cash-in \u002F Cash-out (count \u002F dollar) | |\n| Wire-in \u002F Wire-out (count \u002F dollar) | |\n| ACH\u002FEFT and check activity (count \u002F dollar) | |\n| Average and largest single transaction | |\n| CTRs filed during period | |\n| Jurisdictions involved | |\n\nCompare observed activity against three baselines:\n- **KYC expected activity** — Does volume\u002Ftype match customer declarations?\n- **Peer group** — Consistent with similarly situated customers?\n- **Historical baseline** — Has pattern shifted from prior periods?\n\nFlag material deviations with `[DEVIATION]` and quantify the variance.\n\n### Step 2 — Red Flag Identification\n\nScreen activity against recognized typologies. For each red flag identified, document:\n\n- **Red flag typology** — Name from reference taxonomy\n- **Category** — Structuring \u002F Rapid Movement \u002F Geographic \u002F Shell-Layering \u002F Trade-Based \u002F Behavioral \u002F Other\n- **Transactions implicated** — Date, amount, type, counterparty\n- **Severity** — High \u002F Medium \u002F Low\n- **Explanation** — Why this pattern is suspicious in context\n\nKey thresholds:\n- **CTR**: $10,000 cash (single or aggregate same-business-day). Transactions just below are a structuring indicator. [VERIFY current threshold]\n- **SAR dollar minimum**: $5,000+ with known suspect; $25,000+ with no identified suspect (banks). No dollar minimum for MSBs. [VERIFY by institution type]\n- **Rapid movement**: Funds deposited and withdrawn\u002Ftransferred within 48 hours with no apparent business purpose.\n- **Round-dollar transfers**: Unusual frequency of round-amount wires inconsistent with commercial invoicing.\n\n### Step 3 — OFAC & Sanctions Screening\n\nConfirm whether any party to flagged transactions appears on:\n- OFAC SDN List and Consolidated Sanctions List\n- FinCEN 311 Special Measures (jurisdictions\u002Finstitutions)\n- EU\u002FUN sanctions lists (if applicable) [VERIFY applicability]\n- FATF High-Risk and Non-Cooperative Jurisdictions list\n\nRecord each counterparty\u002Fjurisdiction screened, the result, list version, and date. If a potential OFAC match is identified, **escalate immediately** — OFAC obligations are strict liability with a shorter timeline than SAR filing.\n\n### Step 4 — Disposition\n\nReach one of four dispositions:\n\n| Disposition | Criteria | Action |\n|---|---|---|\n| **File SAR** | Suspicious, unexplained, meets dollar thresholds | Proceed to Step 5 |\n| **Close — Below Threshold** | Concerning but below SAR dollar minimums | Document rationale; retain 5 years; consider enhanced monitoring |\n| **Close — Explained** | Legitimate purpose confirmed with documentation | Document rationale and evidence; retain 5 years |\n| **Escalate** | OFAC match, law enforcement nexus, or insider involvement | Immediate escalation per institution policy |\n\n**Document rationale for every disposition.** Examiners review closed cases as closely as filed SARs.\n\n### Step 5 — SAR Narrative Drafting\n\nThe narrative must answer **who, what, when, where, why, and how**.\n\n**Structure:**\n\n1. **Subject Information** — Full legal name(s), DOB, SSN\u002FTIN (if available), address, account relationship, risk rating and basis.\n2. **Suspicious Activity Description** — Nature of activity (use FinCEN characterization codes), identify all subjects and roles, specific transactions and patterns, date range, branches\u002Fjurisdictions, why activity is suspicious, method\u002Fmechanism used.\n3. **Transaction Detail** — Chronological summary of key transactions, total dollar amount, instruments\u002Fchannels (cash, wire, ACH, check, crypto).\n4. **Investigation Summary** — Detection method, investigation steps, CDD\u002FEDD reviewed, third-party information (314(b), public records, adverse media).\n5. **Supporting Documentation** — Exhibit list, reference to prior SARs if continuation filing.\n\n**Narrative rules:**\n- Factual, not conclusory — state what happened; never assert a crime was committed\n- Chronological presentation\n- Specific — dates, amounts, account numbers, counterparty names\n- Self-contained — reader with no prior knowledge should understand the case\n- Quantified — total suspicious amounts and transaction counts\n- **No SAR-tipping language** — never indicate the customer was or will be notified (31 USC 5318(g)(2)) [VERIFY current statutory cite]\n\n**Filing deadlines** [VERIFY current FinCEN guidance]:\n\n| Scenario | Deadline |\n|---|---|\n| Standard SAR | 30 calendar days from initial detection |\n| No suspect identified | 30 days; may extend to 60 days to identify suspect |\n| Ongoing activity | Continuing SARs every 90 days |\n| Criminal referral | Notify law enforcement immediately; SAR still due within 30 days |\n\n## Output\n\nDeliverables for each review:\n\n1. **Transaction summary table** with profiling metrics and baseline comparisons\n2. **Red flag log** — each flag with typology, category, severity, implicated transactions, and explanation\n3. **OFAC\u002Fsanctions screening record** with list versions and dates\n4. **Disposition memo** — selected outcome with written rationale\n5. **SAR narrative** (if filing) — structured per the template above, ready for BSA officer review\n6. **Filing deadline tracker** — calculated deadline with calendar entry\n\n## Quality Checks\n\n### Completeness\n- [ ] Intake items fully populated or gaps explicitly documented\n- [ ] Transaction profiling covers all activity types in the review period\n- [ ] Every red flag has severity rating and supporting transactions\n- [ ] Disposition is one of the four defined outcomes with written rationale\n\n### Accuracy\n- [ ] Dollar amounts cross-referenced to source transaction data\n- [ ] Dates confirmed against bank records (not estimated)\n- [ ] Counterparty names verified against wire details \u002F account records\n- [ ] OFAC screening uses current list version\n\n### Regulatory Compliance\n- [ ] SAR narrative answers all six questions (who\u002Fwhat\u002Fwhen\u002Fwhere\u002Fwhy\u002Fhow)\n- [ ] No SAR-tipping or customer-notification language anywhere in output\n- [ ] Filing deadline documented and within regulatory window [VERIFY]\n- [ ] CTR analysis included for cash-intensive accounts\n- [ ] 5-year record retention requirement noted\n\n### Professional Standards\n- [ ] Findings distinguish confirmed facts from inferences\n- [ ] All inferences and assumptions marked with `[VERIFY]`\n- [ ] Terminology consistent throughout\n- [ ] Output actionable for BSA officer \u002F compliance committee\n- [ ] Escalation triggers clearly identified\n\n## Reference Files\n\n| File | Description |\n|---|---|\n| `references\u002FAML-RED-FLAGS.md` | Categorized AML red flag typologies with indicators and activity patterns for transaction screening |\n","# Auditing AML Transactions\n\nScreens transaction data for suspicious patterns using red flag typologies and structures SAR narrative elements for BSA\u002FAML compliance.\n\n## When To Use\n\n- Transaction monitoring system generates an alert requiring human review\n- BSA officer receives a referral (internal, law enforcement, or examiner finding)\n- Periodic look-back or enhanced due diligence review of high-risk accounts\n- Continuation SAR is due on the 90-day cycle\n- Independent audit requires sample transaction review\n- 314(b) information-sharing request received from another institution\n\n## Inputs To Gather\n\nCollect all items below before starting review. If transaction records are unavailable, STOP — document the gap and escalate.\n\n### Institution & Scope\n\n- Institution type (bank, MSB, broker-dealer, credit union, insurance, casino, other) [VERIFY]\n- Charter\u002Flicense jurisdiction and primary regulator [VERIFY]\n- BSA\u002FAML program status (established \u002F recently remediated \u002F under consent order)\n- Review period (start and end dates)\n- Alert source and alert\u002Fcase ID\n\n### Subject Information\n\n- Subject name(s) — individuals and\u002For entities\n- Account number(s), account type(s), and open date\n- Customer risk rating (Low \u002F Medium \u002F High \u002F Unrated)\n- KYC profile: stated occupation, income, expected activity, source of funds\n- Prior SAR history on this subject\n\n### Data Sources\n\nConfirm availability of each: transaction records (debits\u002Fcredits), wire transfer details (originator\u002Fbeneficiary), cash activity and CTR history, check images and deposit slips, account statements, CDD\u002FEDD documentation, OFAC\u002Fsanctions screening results, negative news and adverse media, law enforcement subpoenas or 314(b) requests.\n\n## Workflow\n\n### Step 1 — Transaction Profiling\n\nSummarize account activity for the review period:\n\n| Metric | Value |\n|---|---|\n| Total credits (count \u002F dollar) | |\n| Total debits (count \u002F dollar) | |\n| Cash-in \u002F Cash-out (count \u002F dollar) | |\n| Wire-in \u002F Wire-out (count \u002F dollar) | |\n| ACH\u002FEFT and check activity (count \u002F dollar) | |\n| Average and largest single transaction | |\n| CTRs filed during period | |\n| Jurisdictions involved | |\n\nCompare observed activity against three baselines:\n- **KYC expected activity** — Does volume\u002Ftype match customer declarations?\n- **Peer group** — Consistent with similarly situated customers?\n- **Historical baseline** — Has pattern shifted from prior periods?\n\nFlag material deviations with `[DEVIATION]` and quantify the variance.\n\n### Step 2 — Red Flag Identification\n\nScreen activity against recognized typologies. For each red flag identified, document:\n\n- **Red flag typology** — Name from reference taxonomy\n- **Category** — Structuring \u002F Rapid Movement \u002F Geographic \u002F Shell-Layering \u002F Trade-Based \u002F Behavioral \u002F Other\n- **Transactions implicated** — Date, amount, type, counterparty\n- **Severity** — High \u002F Medium \u002F Low\n- **Explanation** — Why this pattern is suspicious in context\n\nKey thresholds:\n- **CTR**: $10,000 cash (single or aggregate same-business-day). Transactions just below are a structuring indicator. [VERIFY current threshold]\n- **SAR dollar minimum**: $5,000+ with known suspect; $25,000+ with no identified suspect (banks). No dollar minimum for MSBs. [VERIFY by institution type]\n- **Rapid movement**: Funds deposited and withdrawn\u002Ftransferred within 48 hours with no apparent business purpose.\n- **Round-dollar transfers**: Unusual frequency of round-amount wires inconsistent with commercial invoicing.\n\n### Step 3 — OFAC & Sanctions Screening\n\nConfirm whether any party to flagged transactions appears on:\n- OFAC SDN List and Consolidated Sanctions List\n- FinCEN 311 Special Measures (jurisdictions\u002Finstitutions)\n- EU\u002FUN sanctions lists (if applicable) [VERIFY applicability]\n- FATF High-Risk and Non-Cooperative Jurisdictions list\n\nRecord each counterparty\u002Fjurisdiction screened, the result, list version, and date. If a potential OFAC match is identified, **escalate immediately** — OFAC obligations are strict liability with a shorter timeline than SAR filing.\n\n### Step 4 — Disposition\n\nReach one of four dispositions:\n\n| Disposition | Criteria | Action |\n|---|---|---|\n| **File SAR** | Suspicious, unexplained, meets dollar thresholds | Proceed to Step 5 |\n| **Close — Below Threshold** | Concerning but below SAR dollar minimums | Document rationale; retain 5 years; consider enhanced monitoring |\n| **Close — Explained** | Legitimate purpose confirmed with documentation | Document rationale and evidence; retain 5 years |\n| **Escalate** | OFAC match, law enforcement nexus, or insider involvement | Immediate escalation per institution policy |\n\n**Document rationale for every disposition.** Examiners review closed cases as closely as filed SARs.\n\n### Step 5 — SAR Narrative Drafting\n\nThe narrative must answer **who, what, when, where, why, and how**.\n\n**Structure:**\n\n1. **Subject Information** — Full legal name(s), DOB, SSN\u002FTIN (if available), address, account relationship, risk rating and basis.\n2. **Suspicious Activity Description** — Nature of activity (use FinCEN characterization codes), identify all subjects and roles, specific transactions and patterns, date range, branches\u002Fjurisdictions, why activity is suspicious, method\u002Fmechanism used.\n3. **Transaction Detail** — Chronological summary of key transactions, total dollar amount, instruments\u002Fchannels (cash, wire, ACH, check, crypto).\n4. **Investigation Summary** — Detection method, investigation steps, CDD\u002FEDD reviewed, third-party information (314(b), public records, adverse media).\n5. **Supporting Documentation** — Exhibit list, reference to prior SARs if continuation filing.\n\n**Narrative rules:**\n- Factual, not conclusory — state what happened; never assert a crime was committed\n- Chronological presentation\n- Specific — dates, amounts, account numbers, counterparty names\n- Self-contained — reader with no prior knowledge should understand the case\n- Quantified — total suspicious amounts and transaction counts\n- **No SAR-tipping language** — never indicate the customer was or will be notified (31 USC 5318(g)(2)) [VERIFY current statutory cite]\n\n**Filing deadlines** [VERIFY current FinCEN guidance]:\n\n| Scenario | Deadline |\n|---|---|\n| Standard SAR | 30 calendar days from initial detection |\n| No suspect identified | 30 days; may extend to 60 days to identify suspect |\n| Ongoing activity | Continuing SARs every 90 days |\n| Criminal referral | Notify law enforcement immediately; SAR still due within 30 days |\n\n## Output\n\nDeliverables for each review:\n\n1. **Transaction summary table** with profiling metrics and baseline comparisons\n2. **Red flag log** — each flag with typology, category, severity, implicated transactions, and explanation\n3. **OFAC\u002Fsanctions screening record** with list versions and dates\n4. **Disposition memo** — selected outcome with written rationale\n5. **SAR narrative** (if filing) — structured per the template above, ready for BSA officer review\n6. **Filing deadline tracker** — calculated deadline with calendar entry\n\n## Quality Checks\n\n### Completeness\n- [ ] Intake items fully populated or gaps explicitly documented\n- [ ] Transaction profiling covers all activity types in the review period\n- [ ] Every red flag has severity rating and supporting transactions\n- [ ] Disposition is one of the four defined outcomes with written rationale\n\n### Accuracy\n- [ ] Dollar amounts cross-referenced to source transaction data\n- [ ] Dates confirmed against bank records (not estimated)\n- [ ] Counterparty names verified against wire details \u002F account records\n- [ ] OFAC screening uses current list version\n\n### Regulatory Compliance\n- [ ] SAR narrative answers all six questions (who\u002Fwhat\u002Fwhen\u002Fwhere\u002Fwhy\u002Fhow)\n- [ ] No SAR-tipping or customer-notification language anywhere in output\n- [ ] Filing deadline documented and within regulatory window [VERIFY]\n- [ ] CTR analysis included for cash-intensive accounts\n- [ ] 5-year record retention requirement noted\n\n### Professional Standards\n- [ ] Findings distinguish confirmed facts from inferences\n- [ ] All inferences and assumptions marked with `[VERIFY]`\n- [ ] Terminology consistent throughout\n- [ ] Output actionable for BSA officer \u002F compliance committee\n- [ ] Escalation triggers clearly identified\n\n## Reference Files\n\n| File | Description |\n|---|---|\n| `references\u002FAML-RED-FLAGS.md` | Categorized AML red flag typologies with indicators and activity patterns for transaction screening |\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],"compliance","financial-compliance","aml","https:\u002F\u002Fgithub.com\u002FCaseMark\u002Fskills","en",{"author":31,"skill_modes":32,"document_types":35,"practice_areas":37},"casemark",[33,34],"Audit","Review",[36],"Compliance Report",[38,39,40],"Regulatory Compliance","Financial Regulation","Compliance","2026-09-20","skills\u002Ffinance\u002Fauditing-aml-transactions\u002FSKILL.md","CaseMark\u002Fskills","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Ffinance\u002Fauditing-aml-transactions","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 auditing-aml-transactions",{"tool":56,"command":57},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill auditing-aml-transactions",{"tool":59,"command":60},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill auditing-aml-transactions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Ffinance\u002Fauditing-aml-transactions\u002FSKILL.md",true,[64],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002FAML-RED-FLAGS.md","REFERENCE","参考文档",9581,"https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Ffinance\u002Fauditing-aml-transactions\u002Freferences\u002FAML-RED-FLAGS.md",[71,79,86,93,100,107],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"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":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"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":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"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":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"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",[],[]]