[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMBPT930GD661Y0J52ZPCB":3,"skill-same:01M7EMBPT930GD661Y0J52ZPCB":48},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M7EMBPT930GD661Y0J52ZPCB","hipaa-baa-vendor-assessment",null,"Reviews Business Associate Agreements and subprocessors for LLM vendors, cloud providers, and MCP server operators under HIPAA (45 CFR §164.502(e), §164.504(e)). Trigger when onboarding OpenAI\u002FAnthropic\u002FAzure OpenAI, cloud hosts, observability tools, or MCP integrations that may access ePHI. Do not use for technical encryption testing (use hipaa-technical-safeguards) or general vendor SOC reports without BAA focus (use vendor-third-party-risk).","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fcompliance\u002Fhipaa-baa-vendor-assessment\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: hipaa-baa-vendor-assessment\ndescription: Reviews Business Associate Agreements and subprocessors for LLM vendors, cloud providers, and MCP server operators under HIPAA (45 CFR §164.502(e), §164.504(e)). Trigger when onboarding OpenAI\u002FAnthropic\u002FAzure OpenAI, cloud hosts, observability tools, or MCP integrations that may access ePHI. Do not use for technical encryption testing (use hipaa-technical-safeguards) or general vendor SOC reports without BAA focus (use vendor-third-party-risk).\nsource: \"https:\u002F\u002Fgithub.com\u002Fvaquarkhan\u002Fcompliance-agent-skills\"\nsource_repository: \"vaquarkhan\u002Fcompliance-agent-skills\"\nsource_path: \"skills\u002Fhipaa-baa-vendor-assessment\u002FSKILL.md\"\nlicense: \"MIT\"\nimported_at: \"2026-09-20\"\n---\n\n# HIPAA BAA Vendor Assessment\n\n## Overview\n\nThis skill performs structured **Business Associate Agreement (BAA)** review for vendors that create, receive, maintain, or transmit **ePHI** on behalf of a covered entity or business associate. Key regulations:\n\n- **45 CFR §164.502(e)**: BA may use\u002Fdisclose ePHI only per BAA or law\n- **45 CFR §164.504(e)**: Required BAA provisions\n- **45 CFR §164.308(b)(1)**: Business associate contracts and other arrangements\n\nLLM and MCP ecosystems introduce non-obvious subprocessors: model hosts, vector DBs, prompt logging, crash reporters, and MCP registry operators. This skill produces a **vendor-by-vendor compliance matrix** with pass\u002Ffail on mandatory BAA clauses—not a substitute for legal counsel.\n\n## When to Use\n\nUse this skill when:\n\n- Onboarding an **LLM provider** (OpenAI, Anthropic, Azure OpenAI, AWS Bedrock) for ePHI-adjacent workloads\n- Evaluating **cloud infrastructure** (AWS, GCP, Azure) for HIPAA workloads\n- Assessing **MCP server** operators or self-hosted MCP with third-party dependencies\n- Reviewing **observability, logging, or support tools** that may capture prompts\u002Fresponses\n- Annual **BAA renewal** or subprocessor change notification review\n- Determining whether a vendor is a **Business Associate** vs **conduit** exception\n\nDo **not** use this skill when:\n\n- Vendor handles only de-identified data with expert determination (confirm de-identification first)\n- Pure PCI card processing without ePHI (use PCI skills)\n- Technical control testing of encryption (use `hipaa-technical-safeguards`)\n\n## Core Process\n\nExecute steps **in order**.\n\n### Step 1: Vendor inventory and BA determination\n\n1. List all vendors in the ePHI processing chain:\n   - LLM API provider, cloud host, MCP server host, CDN, email, ticketing, SIEM\n2. For each vendor, determine status:\n   - **Business Associate**: accesses ePHI on behalf of CE\u002FBA → BAA **required**\n   - **Conduit**: transient access only (e.g., TLS VPN pipe)—document narrow exception analysis\n   - **Not in scope**: no ePHI access—document exclusion rationale\n3. Record: `vendor-inventory-{id}.csv` with data types, access mode, BAA status.\n\n### Step 2: BAA availability verification\n\n1. Confirm vendor offers a **HIPAA BAA** (signed or click-through for cloud).\n2. Verify BAA covers the **specific services** in use (e.g., Azure OpenAI vs general Azure—not all SKUs are covered).\n3. For LLM vendors, confirm:\n   - **Zero data retention** \u002F no training on customer data (contractual, not marketing)\n   - Geographic processing restrictions if required\n   - Subprocessor list and notification process\n4. **BLOCK** production ePHI flows to vendors without executed BAA.\n\n### Step 3: Mandatory BAA clause checklist (§164.504(e))\n\nReview executed or draft BAA for each required element:\n\n| §164.504(e) element | Pass criteria |\n| --- | --- |\n| Permitted uses\u002Fdisclosures | Limited to BAA, CE instruction, or law |\n| Safeguards | Appropriate safeguards per Security Rule |\n| Subcontractors | BA requires same restrictions via subcontractor agreement |\n| Report breaches | BA reports breaches to CE per §164.410 |\n| Access\u002Famendment\u002Faccounting | BA supports individual rights where applicable |\n| HHS access | BA makes internal practices available to HHS |\n| Termination | CE may terminate if BA violates material terms |\n| Return\u002Fdestruction | ePHI returned or destroyed at termination |\n\nMark each **PASS**, **FAIL**, or **NEEDS LEGAL REVIEW**.\n\n### Step 4: LLM-specific addendum review\n\nFor each LLM vendor, verify contractual terms on:\n\n1. **Input\u002Foutput logging**: what is logged, retention period, who can access\n2. **Model training**: explicit prohibition on training\u002Ffine-tuning on customer ePHI\n3. **Human review**: opt-out of human review of prompts containing ePHI\n4. **Region\u002Fdata residency**: matches organizational policy\n5. **API metadata**: request IDs in logs—confirm they cannot reconstruct ePHI alone\n6. **Enterprise vs consumer tier**: consumer tiers often **lack BAA**—FAIL if used for ePHI\n\n### Step 5: MCP server operator assessment\n\nFor each MCP server processing ePHI:\n\n1. Identify **operator** (self-hosted, vendor-hosted, open-source with cloud telemetry).\n2. Determine if operator accesses ePHI (tool inputs\u002Foutputs, server logs).\n3. Require BAA or confirm operator is **within CE boundary** (employee\u002Fcontractor under CE policies).\n4. Review MCP dependency chain: npm packages with phone-home, crash analytics.\n5. Document tool allowlist—MCP operator should not have broader access than BAA permits.\n\n### Step 6: Subprocessor cascade\n\n1. Obtain vendor **subprocessor list** (LLM → cloud → CDN → support SaaS).\n2. Verify flow-down obligations in BAA.\n3. Flag new subprocessors added since last review.\n4. Map subprocessors to ePHI exposure (HIGH: prompt storage; LOW: physical datacenter with no logical access).\n\n### Step 7: Gap remediation and risk acceptance\n\n1. FAIL items: block ePHI until remediated or alternative vendor selected.\n2. NEEDS LEGAL REVIEW: escalate with clause citation—do not auto-approve.\n3. Document compensating controls only with legal and privacy officer approval.\n4. Set BAA renewal calendar (annual minimum; 90-day subprocessor review).\n\n### Step 8: Evidence packaging\n\n1. Store executed BAAs (redacted signatures if needed), subprocessor lists, assessment matrix.\n2. SHA-256 hash all documents; link to vendor inventory IDs.\n3. Produce summary for privacy officer sign-off.\n\n## Common Rationalizations\n\n| Excuse the agent might generate | Required rebuttal |\n| --- | --- |\n| \"We redact PHI, so no BAA is needed with the LLM vendor.\" | Residual ePHI or re-identification risk may remain; **vendor role** is determined by access capability, not intent. Legal must confirm conduit\u002Fde-identified exceptions. |\n| \"Enterprise API terms say HIPAA—good enough without signed BAA.\" | Marketing language ≠ **executed BAA** with §164.504(e) clauses. |\n| \"MCP is open source, so there's no vendor.\" | **Operator** of the running instance and its telemetry dependencies may still be a BA. |\n| \"Subprocessors are the vendor's problem.\" | CE\u002FBA retains **oversight obligation**—subprocessor notification must be monitored. |\n| \"Consumer ChatGPT Plus works for clinical summaries.\" | Consumer products typically **lack BAA**—automatic FAIL for ePHI. |\n| \"BAA review can wait until after pilot.\" | Pilot with real ePHI **is production** under HIPAA—BAA must precede ePHI flow. |\n\n## Red Flags\n\n- Production ePHI sent to LLM without executed BAA\n- Consumer-tier LLM account used for clinical workflows\n- Vendor subprocessor added with ePHI access and no notification review\n- BAA missing breach notification or termination for cause clauses\n- MCP server logs full tool payloads to non-BAA analytics\n- \"Conduit\" exception claimed for vendor that stores prompts\n- Verbal vendor assurance substituted for contractual BAA language\n\n## Verification\n\n- [ ] Complete vendor inventory with BA\u002Fconduit\u002Fnot-in-scope determination\n- [ ] Executed BAA on file for every BA vendor before ePHI processing\n- [ ] §164.504(e) checklist completed for each BAA\n- [ ] LLM-specific addendum reviewed (training, logging, human review, tier)\n- [ ] MCP operators assessed with dependency chain documented\n- [ ] Subprocessor list current with change notification process verified\n- [ ] FAIL items blocked or remediated—none silently waived\n- [ ] Legal review queue documented for ambiguous clauses\n- [ ] Evidence bundle hashed with privacy officer sign-off field\n- [ ] BAA renewal and subprocessor review dates scheduled\n","# HIPAA BAA Vendor Assessment\n\n## Overview\n\nThis skill performs structured **Business Associate Agreement (BAA)** review for vendors that create, receive, maintain, or transmit **ePHI** on behalf of a covered entity or business associate. Key regulations:\n\n- **45 CFR §164.502(e)**: BA may use\u002Fdisclose ePHI only per BAA or law\n- **45 CFR §164.504(e)**: Required BAA provisions\n- **45 CFR §164.308(b)(1)**: Business associate contracts and other arrangements\n\nLLM and MCP ecosystems introduce non-obvious subprocessors: model hosts, vector DBs, prompt logging, crash reporters, and MCP registry operators. This skill produces a **vendor-by-vendor compliance matrix** with pass\u002Ffail on mandatory BAA clauses—not a substitute for legal counsel.\n\n## When to Use\n\nUse this skill when:\n\n- Onboarding an **LLM provider** (OpenAI, Anthropic, Azure OpenAI, AWS Bedrock) for ePHI-adjacent workloads\n- Evaluating **cloud infrastructure** (AWS, GCP, Azure) for HIPAA workloads\n- Assessing **MCP server** operators or self-hosted MCP with third-party dependencies\n- Reviewing **observability, logging, or support tools** that may capture prompts\u002Fresponses\n- Annual **BAA renewal** or subprocessor change notification review\n- Determining whether a vendor is a **Business Associate** vs **conduit** exception\n\nDo **not** use this skill when:\n\n- Vendor handles only de-identified data with expert determination (confirm de-identification first)\n- Pure PCI card processing without ePHI (use PCI skills)\n- Technical control testing of encryption (use `hipaa-technical-safeguards`)\n\n## Core Process\n\nExecute steps **in order**.\n\n### Step 1: Vendor inventory and BA determination\n\n1. List all vendors in the ePHI processing chain:\n   - LLM API provider, cloud host, MCP server host, CDN, email, ticketing, SIEM\n2. For each vendor, determine status:\n   - **Business Associate**: accesses ePHI on behalf of CE\u002FBA → BAA **required**\n   - **Conduit**: transient access only (e.g., TLS VPN pipe)—document narrow exception analysis\n   - **Not in scope**: no ePHI access—document exclusion rationale\n3. Record: `vendor-inventory-{id}.csv` with data types, access mode, BAA status.\n\n### Step 2: BAA availability verification\n\n1. Confirm vendor offers a **HIPAA BAA** (signed or click-through for cloud).\n2. Verify BAA covers the **specific services** in use (e.g., Azure OpenAI vs general Azure—not all SKUs are covered).\n3. For LLM vendors, confirm:\n   - **Zero data retention** \u002F no training on customer data (contractual, not marketing)\n   - Geographic processing restrictions if required\n   - Subprocessor list and notification process\n4. **BLOCK** production ePHI flows to vendors without executed BAA.\n\n### Step 3: Mandatory BAA clause checklist (§164.504(e))\n\nReview executed or draft BAA for each required element:\n\n| §164.504(e) element | Pass criteria |\n| --- | --- |\n| Permitted uses\u002Fdisclosures | Limited to BAA, CE instruction, or law |\n| Safeguards | Appropriate safeguards per Security Rule |\n| Subcontractors | BA requires same restrictions via subcontractor agreement |\n| Report breaches | BA reports breaches to CE per §164.410 |\n| Access\u002Famendment\u002Faccounting | BA supports individual rights where applicable |\n| HHS access | BA makes internal practices available to HHS |\n| Termination | CE may terminate if BA violates material terms |\n| Return\u002Fdestruction | ePHI returned or destroyed at termination |\n\nMark each **PASS**, **FAIL**, or **NEEDS LEGAL REVIEW**.\n\n### Step 4: LLM-specific addendum review\n\nFor each LLM vendor, verify contractual terms on:\n\n1. **Input\u002Foutput logging**: what is logged, retention period, who can access\n2. **Model training**: explicit prohibition on training\u002Ffine-tuning on customer ePHI\n3. **Human review**: opt-out of human review of prompts containing ePHI\n4. **Region\u002Fdata residency**: matches organizational policy\n5. **API metadata**: request IDs in logs—confirm they cannot reconstruct ePHI alone\n6. **Enterprise vs consumer tier**: consumer tiers often **lack BAA**—FAIL if used for ePHI\n\n### Step 5: MCP server operator assessment\n\nFor each MCP server processing ePHI:\n\n1. Identify **operator** (self-hosted, vendor-hosted, open-source with cloud telemetry).\n2. Determine if operator accesses ePHI (tool inputs\u002Foutputs, server logs).\n3. Require BAA or confirm operator is **within CE boundary** (employee\u002Fcontractor under CE policies).\n4. Review MCP dependency chain: npm packages with phone-home, crash analytics.\n5. Document tool allowlist—MCP operator should not have broader access than BAA permits.\n\n### Step 6: Subprocessor cascade\n\n1. Obtain vendor **subprocessor list** (LLM → cloud → CDN → support SaaS).\n2. Verify flow-down obligations in BAA.\n3. Flag new subprocessors added since last review.\n4. Map subprocessors to ePHI exposure (HIGH: prompt storage; LOW: physical datacenter with no logical access).\n\n### Step 7: Gap remediation and risk acceptance\n\n1. FAIL items: block ePHI until remediated or alternative vendor selected.\n2. NEEDS LEGAL REVIEW: escalate with clause citation—do not auto-approve.\n3. Document compensating controls only with legal and privacy officer approval.\n4. Set BAA renewal calendar (annual minimum; 90-day subprocessor review).\n\n### Step 8: Evidence packaging\n\n1. Store executed BAAs (redacted signatures if needed), subprocessor lists, assessment matrix.\n2. SHA-256 hash all documents; link to vendor inventory IDs.\n3. Produce summary for privacy officer sign-off.\n\n## Common Rationalizations\n\n| Excuse the agent might generate | Required rebuttal |\n| --- | --- |\n| \"We redact PHI, so no BAA is needed with the LLM vendor.\" | Residual ePHI or re-identification risk may remain; **vendor role** is determined by access capability, not intent. Legal must confirm conduit\u002Fde-identified exceptions. |\n| \"Enterprise API terms say HIPAA—good enough without signed BAA.\" | Marketing language ≠ **executed BAA** with §164.504(e) clauses. |\n| \"MCP is open source, so there's no vendor.\" | **Operator** of the running instance and its telemetry dependencies may still be a BA. |\n| \"Subprocessors are the vendor's problem.\" | CE\u002FBA retains **oversight obligation**—subprocessor notification must be monitored. |\n| \"Consumer ChatGPT Plus works for clinical summaries.\" | Consumer products typically **lack BAA**—automatic FAIL for ePHI. |\n| \"BAA review can wait until after pilot.\" | Pilot with real ePHI **is production** under HIPAA—BAA must precede ePHI flow. |\n\n## Red Flags\n\n- Production ePHI sent to LLM without executed BAA\n- Consumer-tier LLM account used for clinical workflows\n- Vendor subprocessor added with ePHI access and no notification review\n- BAA missing breach notification or termination for cause clauses\n- MCP server logs full tool payloads to non-BAA analytics\n- \"Conduit\" exception claimed for vendor that stores prompts\n- Verbal vendor assurance substituted for contractual BAA language\n\n## Verification\n\n- [ ] Complete vendor inventory with BA\u002Fconduit\u002Fnot-in-scope determination\n- [ ] Executed BAA on file for every BA vendor before ePHI processing\n- [ ] §164.504(e) checklist completed for each BAA\n- [ ] LLM-specific addendum reviewed (training, logging, human review, tier)\n- [ ] MCP operators assessed with dependency chain documented\n- [ ] Subprocessor list current with change notification process verified\n- [ ] FAIL items blocked or remediated—none silently waived\n- [ ] Legal review queue documented for ambiguous clauses\n- [ ] Evidence bundle hashed with privacy officer sign-off field\n- [ ] BAA renewal and subprocessor review dates scheduled\n",{"name":5,"source":24,"license":15,"description":7,"imported_at":25,"source_path":26,"source_repository":27},"https:\u002F\u002Fgithub.com\u002Fvaquarkhan\u002Fcompliance-agent-skills","2026-09-20","skills\u002Fhipaa-baa-vendor-assessment\u002FSKILL.md","vaquarkhan\u002Fcompliance-agent-skills","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Fcompliance\u002Fhipaa-baa-vendor-assessment","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":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill hipaa-baa-vendor-assessment",{"tool":40,"command":41},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill hipaa-baa-vendor-assessment",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill hipaa-baa-vendor-assessment","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fcompliance\u002Fhipaa-baa-vendor-assessment\u002FSKILL.md",true,[],[49,57,64,71,78,85],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":56},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","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":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":56},"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":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":56},"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":56},"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":56},"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":56},"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",[],[]]