[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AYVF14RT739NF49J7HP3SH":3,"skill-same:01M7AYVF14RT739NF49J7HP3SH":69},{"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":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M7AYVF14RT739NF49J7HP3SH","privacy-regulatory-research",null,"Use for privacy research. Build sourced checklists.","oat431\u002Fhermes_config_backup","oat431","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54722120?v=4","01M7AYD07EH8SYPMYY8CGZKS22","Oralita","01M7AYD0816QDF77E3TWCRSQC9",1,"MIT","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fproduct-owner\u002Fprivacy-regulatory-research\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: privacy-regulatory-research\ndescription: \"Use for privacy research. Build sourced checklists.\"\nversion: 1.0.0\nauthor: Hermes Agent\nlicense: MIT\nmetadata:\n  hermes:\n    tags: [privacy, regulatory, legal-research, data-protection, product, compliance]\n    related_skills: []\n---\n\n# Privacy and Regulatory Research for Product Decisions\n\n## Overview\n\nUse this class-level skill when a product, feature, integration, or hosted service raises privacy or data-protection questions. The deliverable is decision-ready product guidance grounded in current primary sources: a cautious bottom line, a processing map, purpose-by-purpose legal-basis analysis, and an implementation checklist. Do not present the result as definitive legal advice.\n\nResearch must distinguish what the law says from what the product should do conservatively. Public, pseudonymous, normalized, hashed, or user-supplied identifiers may remain personal data when they can be linked to a person or combined with other records.\n\nFor a Thai PDPA public-identifier\u002Fscoreboard pattern, load the source-specific knowledge bank at `references\u002Fthai-pdpa-youtube-scoreboard.md`; for an owner-facing MUST DO\u002FMUST NOT DO handoff and cross-document release-gate pattern, also load `references\u002Fthai-pdpa-owner-readiness.md`. Treat both files' links and section notes as starting points and re-check current regulator pages before relying on them.\n\n## When to Use\n\n- A user asks whether names, handles, IDs, aliases, donations, scores, or logs are personal data.\n- A product publicly displays an identifier, ranking, profile, contribution, or behavior-derived score.\n- Data is imported from a platform, payment\u002Fdonation service, API, chatbot, or other third party.\n- A developer, agency, cloud host, or SaaS provider stores or processes data for an owner.\n- The user needs lawful-basis, consent, privacy-notice, rights, deletion, retention, breach, transfer, or controller\u002Fprocessor guidance.\n\nDo not use this as a substitute for jurisdiction-specific counsel on high-risk processing, sensitive data, children, regulated sectors, employment, health, finance, or disputed legal interpretation. Escalate those issues explicitly instead of hiding uncertainty.\n\n## Research Workflow\n\n### 1. Define the processing before researching the law\n\nWrite a compact fact pattern:\n\n- jurisdiction(s), location of controller\u002Fprocessor, and location of data subjects;\n- product purpose and whether the feature is optional or necessary;\n- each data source and whether it is collected directly or from another source;\n- each data field, including derived scores, normalized values, IDs, logs, and backups;\n- every operation: collect, observe, match, infer, store, use, disclose, publish, export, and delete;\n- audiences\u002Frecipients, subprocessors, hosting regions, and public visibility;\n- expected scale, monitoring frequency, minors, and sensitive-data risk.\n\nDo not jump from “the user entered a command” to “consent exists.” A command can be an input mechanism, but consent still needs a clear purpose, timing, voluntariness, and evidence.\n\n### 2. Use a primary-source hierarchy\n\nSearch in this order:\n\n1. statute, regulation, official gazette, and regulator guidance;\n2. official regulator translations, FAQs, templates, and enforcement\u002Fconsultation pages;\n3. reputable secondary commentary for orientation and issue spotting;\n4. vendor\u002Fplatform privacy notices for factual data-flow details, never as the legal basis for the customer’s separate processing.\n\nFor every material conclusion, record the exact section\u002Fclause, official URL, document title, and whether the translation is unofficial. Where a translated text says that the local-language gazette controls, say so. If an official page or vendor policy cannot be retrieved, do not fill the gap with assumptions; report the limitation and use the statute or another primary source.\n\n### 3. Classify identifiers conservatively\n\nAsk whether the field relates to a natural person and enables direct or indirect identification in context. Analyze combinations, not isolated strings:\n\n- public display names, handles, aliases, and usernames can identify an account or person;\n- a stable provider ID is usually an identifier even if never displayed;\n- normalization, tokenization, hashing, or pseudonymization usually reduces exposure but does not itself anonymize data;\n- donation, purchase, participation, ranking, location, and behavioral data become personal when linked to an identifier;\n- a brand or organization name may not relate to a natural person, but chat authors, operators, and linked accounts can still be in scope;\n- inferential or derived data deserves the same analysis as source data;\n- classify possible sensitive-data leakage separately, especially where messages or transactions reveal health, religion, politics, sexuality, criminal history, or similar traits.\n\n### 4. Separate the purpose-by-purpose legal-basis analysis\n\nCreate a table with: purpose, fields, operation, legal basis candidate, necessity, balancing\u002Fconsent evidence, recipients, retention, and risk.\n\nDo not use one vague basis for the entire system. At minimum separate:\n\n- account\u002Fmember registration;\n- internal scoring or service delivery;\n- third-party matching or reconciliation;\n- public display or search indexing;\n- abuse prevention and security logs;\n- billing, tax, or legal records;\n- analytics or product improvement.\n\nFor consent, verify: prior or contemporaneous timing; specific purpose; plain, accessible, distinguishable presentation; affirmative and freely given choice; no unrelated service bundling; recorded notice\u002Fversion\u002Ftime; and withdrawal that is as easy as giving consent. Public visibility should normally have its own opt-in when it is optional.\n\nFor legitimate interests, document the three-part assessment: legitimate purpose, necessity, and balancing against the person’s rights\u002Fexpectations. Public availability of a handle is evidence for expectations, not a blanket permission to republish or link it. A technical exact-match rule is not a legal basis.\n\n### 5. Treat public display and matching as high-attention operations\n\nA public leaderboard, profile, alert, or ranking is a disclosure\u002Fpublication, not merely internal storage. State exactly what the audience sees and what it can infer. A score may reveal donations, spending, loyalty, or behavior even when the amount is hidden.\n\nPrefer, in order:\n\n1. a member-chosen public alias;\n2. an explicit public-visibility choice with private mode available;\n3. the minimum public fields, such as alias\u002Fhandle plus a coarse score or tier;\n4. no raw donor name, message, payment identifier, or internal ID in the public response.\n\nUse a private stable provider ID for matching where possible. Treat exact string matching as a heuristic: names can collide, a donor can enter another person’s handle, and handles can change. Provide a correction\u002Fmanual-review path and avoid awarding or publishing an ambiguous match.\n\n### 6. Build the notice and rights path into the product\n\nA useful notice should identify the controller and contact channel; purposes and bases; data categories; sources; whether fields are optional; recipients; hosting\u002Ftransfer locations; retention; and the available access, correction, objection, restriction, withdrawal, and erasure paths.\n\nIf data comes from another source, check the jurisdiction’s special notice deadline and any first-contact\u002Ffirst-disclosure rule. Do not assume the upstream platform’s notice covers a downstream owner’s new matching or publication purpose.\n\nProvide a low-friction privacy control: hide\u002Fremove command or form, account-based authentication, correction\u002Ffalse-match appeal, and a channel-independent contact route. Define what happens to the public projection, caches, exports, logs, and backups. Explain lawful exceptions without making removal unnecessarily difficult.\n\n### 7. Assign controller\u002Fprocessor roles from facts\n\nThe party deciding why and how processing occurs is generally the Controller. A developer\u002Fhost is a Processor only when operating on the controller’s instructions and not reusing the data for its own purposes. If the developer decides purposes, combines data across customers, profiles users, or independently determines material means, analyze separate or joint-controller status.\n\nFor a processor arrangement, require a written data-processing agreement covering: instructions and permitted purposes; fields; confidentiality; least privilege; security; subprocessors; hosting\u002Ftransfer locations; rights assistance; breach escalation; audit\u002Fcooperation; retention; backup deletion; return\u002Fdestruction; and no independent reuse. Contract wording cannot override the actual relationship.\n\n### 8. Specify retention and security instead of saying “keep only as long as necessary”\n\nSet a field-level schedule for raw events, names, IDs, member records, public projections, consent evidence, support tickets, logs, exports, and backups. Explain the period in the notice and trigger deletion when the purpose ends, consent is withdrawn without another basis, the data is stale, or a request succeeds. A small-business or record-keeping exemption is not a general exemption from privacy duties.\n\nUse risk-appropriate organizational, technical, and physical measures: role-based access, least privilege, authentication, encryption in transit and at rest, secret management, no sensitive data in logs, audit trails, isolated public\u002Fread-only projections, backup expiry, access review, and incident playbooks. Include the controller’s breach deadline and the processor’s faster internal escalation target.\n\n### 9. Produce a cautious, usable deliverable\n\nLead with three to five outcome bullets. Then provide:\n\n1. a data-classification table;\n2. a purpose\u002Flegal-basis table with uncertainty labels;\n3. a product\u002Fprivacy checklist grouped by priority;\n4. controller\u002Fprocessor and vendor-contract actions;\n5. retention\u002Fsecurity\u002Fbreach actions;\n6. official source links with section numbers;\n7. a short “not legal advice \u002F local-language text controls” caveat;\n8. research limitations, including inaccessible or unverified vendor pages.\n\nUse “likely,” “conservative approach,” “depends on facts,” and “confirm with local counsel” where appropriate. Do not claim a vendor’s terms, a current law, or an API behavior without a source.\n\n## Common Pitfalls\n\n1. **“It is public, so it is not Personal Data.”** Public visibility does not eliminate identifiability or the need for a lawful basis for a new disclosure.\n2. **“Normalization\u002Fhash = anonymization.”** If the system can link the value back to a member, it remains personal or pseudonymous data.\n3. **“The registration command is consent.”** It is not enough unless the specific processing, optionality, timing, and withdrawal path are clear.\n4. **Bundling public display with service access.** Keep optional publication separate so consent is freely given.\n5. **Relying on the upstream platform’s notice.** The owner needs a downstream notice for its own matching, scoring, and publication.\n6. **Assuming exact matching proves identity.** Handle\u002Fname collisions, impersonation, stale names, and false attribution require validation and correction.\n7. **Calling the developer a processor by contract alone.** Actual purposes and independent reuse determine roles.\n8. **Treating a small-enterprise exemption as a full exemption.** Check its exact scope and continue to implement notice, security, rights, and deletion.\n9. **No fixed retention schedule.** “Until no longer needed” is not an operational deletion control; set triggers and periods by field.\n10. **Ignoring secondary disclosure.** Public scores, rankings, and tiers can reveal sensitive behavior even when raw amounts or names are hidden.\n11. **Relying on an unofficial translation without warning.** Cite the official page, identify the translation status, and state that the local-language source controls.\n\n## Verification Checklist\n\n- [ ] Jurisdictions, roles, subjects, sources, fields, operations, recipients, and hosting regions are documented.\n- [ ] Public, normalized, pseudonymous, and derived identifiers were analyzed for indirect identification.\n- [ ] Each distinct purpose has a candidate legal basis and a necessity\u002Frisk explanation.\n- [ ] Public display is separately opted in where optional, or a legitimate-interest assessment is documented.\n- [ ] Third-party-source notice timing and upstream\u002Fdownstream responsibility are addressed.\n- [ ] Notice includes purposes, fields, sources, recipients, retention, contacts, rights, and consequences of non-provision.\n- [ ] Hide, withdraw, correct, access, and erasure workflows are usable and authenticated without demanding unnecessary real-world identity.\n- [ ] Raw donor names\u002Fmessages\u002Fpayment details are minimized and have a deletion trigger.\n- [ ] Public projections, caches, exports, logs, and backups are included in deletion design.\n- [ ] Controller–processor agreement covers instructions, security, subprocessors, transfers, rights, breach, retention, and no reuse.\n- [ ] Security controls and breach escalation are proportionate and testable.\n- [ ] Official sources, exact sections, retrieval date, translation caveats, and unresolved issues are listed.\n- [ ] The final response says “not legal advice” and does not overstate an unsettled interpretation.\n","# Privacy and Regulatory Research for Product Decisions\n\n## Overview\n\nUse this class-level skill when a product, feature, integration, or hosted service raises privacy or data-protection questions. The deliverable is decision-ready product guidance grounded in current primary sources: a cautious bottom line, a processing map, purpose-by-purpose legal-basis analysis, and an implementation checklist. Do not present the result as definitive legal advice.\n\nResearch must distinguish what the law says from what the product should do conservatively. Public, pseudonymous, normalized, hashed, or user-supplied identifiers may remain personal data when they can be linked to a person or combined with other records.\n\nFor a Thai PDPA public-identifier\u002Fscoreboard pattern, load the source-specific knowledge bank at `references\u002Fthai-pdpa-youtube-scoreboard.md`; for an owner-facing MUST DO\u002FMUST NOT DO handoff and cross-document release-gate pattern, also load `references\u002Fthai-pdpa-owner-readiness.md`. Treat both files' links and section notes as starting points and re-check current regulator pages before relying on them.\n\n## When to Use\n\n- A user asks whether names, handles, IDs, aliases, donations, scores, or logs are personal data.\n- A product publicly displays an identifier, ranking, profile, contribution, or behavior-derived score.\n- Data is imported from a platform, payment\u002Fdonation service, API, chatbot, or other third party.\n- A developer, agency, cloud host, or SaaS provider stores or processes data for an owner.\n- The user needs lawful-basis, consent, privacy-notice, rights, deletion, retention, breach, transfer, or controller\u002Fprocessor guidance.\n\nDo not use this as a substitute for jurisdiction-specific counsel on high-risk processing, sensitive data, children, regulated sectors, employment, health, finance, or disputed legal interpretation. Escalate those issues explicitly instead of hiding uncertainty.\n\n## Research Workflow\n\n### 1. Define the processing before researching the law\n\nWrite a compact fact pattern:\n\n- jurisdiction(s), location of controller\u002Fprocessor, and location of data subjects;\n- product purpose and whether the feature is optional or necessary;\n- each data source and whether it is collected directly or from another source;\n- each data field, including derived scores, normalized values, IDs, logs, and backups;\n- every operation: collect, observe, match, infer, store, use, disclose, publish, export, and delete;\n- audiences\u002Frecipients, subprocessors, hosting regions, and public visibility;\n- expected scale, monitoring frequency, minors, and sensitive-data risk.\n\nDo not jump from “the user entered a command” to “consent exists.” A command can be an input mechanism, but consent still needs a clear purpose, timing, voluntariness, and evidence.\n\n### 2. Use a primary-source hierarchy\n\nSearch in this order:\n\n1. statute, regulation, official gazette, and regulator guidance;\n2. official regulator translations, FAQs, templates, and enforcement\u002Fconsultation pages;\n3. reputable secondary commentary for orientation and issue spotting;\n4. vendor\u002Fplatform privacy notices for factual data-flow details, never as the legal basis for the customer’s separate processing.\n\nFor every material conclusion, record the exact section\u002Fclause, official URL, document title, and whether the translation is unofficial. Where a translated text says that the local-language gazette controls, say so. If an official page or vendor policy cannot be retrieved, do not fill the gap with assumptions; report the limitation and use the statute or another primary source.\n\n### 3. Classify identifiers conservatively\n\nAsk whether the field relates to a natural person and enables direct or indirect identification in context. Analyze combinations, not isolated strings:\n\n- public display names, handles, aliases, and usernames can identify an account or person;\n- a stable provider ID is usually an identifier even if never displayed;\n- normalization, tokenization, hashing, or pseudonymization usually reduces exposure but does not itself anonymize data;\n- donation, purchase, participation, ranking, location, and behavioral data become personal when linked to an identifier;\n- a brand or organization name may not relate to a natural person, but chat authors, operators, and linked accounts can still be in scope;\n- inferential or derived data deserves the same analysis as source data;\n- classify possible sensitive-data leakage separately, especially where messages or transactions reveal health, religion, politics, sexuality, criminal history, or similar traits.\n\n### 4. Separate the purpose-by-purpose legal-basis analysis\n\nCreate a table with: purpose, fields, operation, legal basis candidate, necessity, balancing\u002Fconsent evidence, recipients, retention, and risk.\n\nDo not use one vague basis for the entire system. At minimum separate:\n\n- account\u002Fmember registration;\n- internal scoring or service delivery;\n- third-party matching or reconciliation;\n- public display or search indexing;\n- abuse prevention and security logs;\n- billing, tax, or legal records;\n- analytics or product improvement.\n\nFor consent, verify: prior or contemporaneous timing; specific purpose; plain, accessible, distinguishable presentation; affirmative and freely given choice; no unrelated service bundling; recorded notice\u002Fversion\u002Ftime; and withdrawal that is as easy as giving consent. Public visibility should normally have its own opt-in when it is optional.\n\nFor legitimate interests, document the three-part assessment: legitimate purpose, necessity, and balancing against the person’s rights\u002Fexpectations. Public availability of a handle is evidence for expectations, not a blanket permission to republish or link it. A technical exact-match rule is not a legal basis.\n\n### 5. Treat public display and matching as high-attention operations\n\nA public leaderboard, profile, alert, or ranking is a disclosure\u002Fpublication, not merely internal storage. State exactly what the audience sees and what it can infer. A score may reveal donations, spending, loyalty, or behavior even when the amount is hidden.\n\nPrefer, in order:\n\n1. a member-chosen public alias;\n2. an explicit public-visibility choice with private mode available;\n3. the minimum public fields, such as alias\u002Fhandle plus a coarse score or tier;\n4. no raw donor name, message, payment identifier, or internal ID in the public response.\n\nUse a private stable provider ID for matching where possible. Treat exact string matching as a heuristic: names can collide, a donor can enter another person’s handle, and handles can change. Provide a correction\u002Fmanual-review path and avoid awarding or publishing an ambiguous match.\n\n### 6. Build the notice and rights path into the product\n\nA useful notice should identify the controller and contact channel; purposes and bases; data categories; sources; whether fields are optional; recipients; hosting\u002Ftransfer locations; retention; and the available access, correction, objection, restriction, withdrawal, and erasure paths.\n\nIf data comes from another source, check the jurisdiction’s special notice deadline and any first-contact\u002Ffirst-disclosure rule. Do not assume the upstream platform’s notice covers a downstream owner’s new matching or publication purpose.\n\nProvide a low-friction privacy control: hide\u002Fremove command or form, account-based authentication, correction\u002Ffalse-match appeal, and a channel-independent contact route. Define what happens to the public projection, caches, exports, logs, and backups. Explain lawful exceptions without making removal unnecessarily difficult.\n\n### 7. Assign controller\u002Fprocessor roles from facts\n\nThe party deciding why and how processing occurs is generally the Controller. A developer\u002Fhost is a Processor only when operating on the controller’s instructions and not reusing the data for its own purposes. If the developer decides purposes, combines data across customers, profiles users, or independently determines material means, analyze separate or joint-controller status.\n\nFor a processor arrangement, require a written data-processing agreement covering: instructions and permitted purposes; fields; confidentiality; least privilege; security; subprocessors; hosting\u002Ftransfer locations; rights assistance; breach escalation; audit\u002Fcooperation; retention; backup deletion; return\u002Fdestruction; and no independent reuse. Contract wording cannot override the actual relationship.\n\n### 8. Specify retention and security instead of saying “keep only as long as necessary”\n\nSet a field-level schedule for raw events, names, IDs, member records, public projections, consent evidence, support tickets, logs, exports, and backups. Explain the period in the notice and trigger deletion when the purpose ends, consent is withdrawn without another basis, the data is stale, or a request succeeds. A small-business or record-keeping exemption is not a general exemption from privacy duties.\n\nUse risk-appropriate organizational, technical, and physical measures: role-based access, least privilege, authentication, encryption in transit and at rest, secret management, no sensitive data in logs, audit trails, isolated public\u002Fread-only projections, backup expiry, access review, and incident playbooks. Include the controller’s breach deadline and the processor’s faster internal escalation target.\n\n### 9. Produce a cautious, usable deliverable\n\nLead with three to five outcome bullets. Then provide:\n\n1. a data-classification table;\n2. a purpose\u002Flegal-basis table with uncertainty labels;\n3. a product\u002Fprivacy checklist grouped by priority;\n4. controller\u002Fprocessor and vendor-contract actions;\n5. retention\u002Fsecurity\u002Fbreach actions;\n6. official source links with section numbers;\n7. a short “not legal advice \u002F local-language text controls” caveat;\n8. research limitations, including inaccessible or unverified vendor pages.\n\nUse “likely,” “conservative approach,” “depends on facts,” and “confirm with local counsel” where appropriate. Do not claim a vendor’s terms, a current law, or an API behavior without a source.\n\n## Common Pitfalls\n\n1. **“It is public, so it is not Personal Data.”** Public visibility does not eliminate identifiability or the need for a lawful basis for a new disclosure.\n2. **“Normalization\u002Fhash = anonymization.”** If the system can link the value back to a member, it remains personal or pseudonymous data.\n3. **“The registration command is consent.”** It is not enough unless the specific processing, optionality, timing, and withdrawal path are clear.\n4. **Bundling public display with service access.** Keep optional publication separate so consent is freely given.\n5. **Relying on the upstream platform’s notice.** The owner needs a downstream notice for its own matching, scoring, and publication.\n6. **Assuming exact matching proves identity.** Handle\u002Fname collisions, impersonation, stale names, and false attribution require validation and correction.\n7. **Calling the developer a processor by contract alone.** Actual purposes and independent reuse determine roles.\n8. **Treating a small-enterprise exemption as a full exemption.** Check its exact scope and continue to implement notice, security, rights, and deletion.\n9. **No fixed retention schedule.** “Until no longer needed” is not an operational deletion control; set triggers and periods by field.\n10. **Ignoring secondary disclosure.** Public scores, rankings, and tiers can reveal sensitive behavior even when raw amounts or names are hidden.\n11. **Relying on an unofficial translation without warning.** Cite the official page, identify the translation status, and state that the local-language source controls.\n\n## Verification Checklist\n\n- [ ] Jurisdictions, roles, subjects, sources, fields, operations, recipients, and hosting regions are documented.\n- [ ] Public, normalized, pseudonymous, and derived identifiers were analyzed for indirect identification.\n- [ ] Each distinct purpose has a candidate legal basis and a necessity\u002Frisk explanation.\n- [ ] Public display is separately opted in where optional, or a legitimate-interest assessment is documented.\n- [ ] Third-party-source notice timing and upstream\u002Fdownstream responsibility are addressed.\n- [ ] Notice includes purposes, fields, sources, recipients, retention, contacts, rights, and consequences of non-provision.\n- [ ] Hide, withdraw, correct, access, and erasure workflows are usable and authenticated without demanding unnecessary real-world identity.\n- [ ] Raw donor names\u002Fmessages\u002Fpayment details are minimized and have a deletion trigger.\n- [ ] Public projections, caches, exports, logs, and backups are included in deletion design.\n- [ ] Controller–processor agreement covers instructions, security, subprocessors, transfers, rights, breach, retention, and no reuse.\n- [ ] Security controls and breach escalation are proportionate and testable.\n- [ ] Official sources, exact sections, retrieval date, translation caveats, and unresolved issues are listed.\n- [ ] The final response says “not legal advice” and does not overstate an unsettled interpretation.\n",{"name":5,"author":24,"license":15,"version":25,"metadata":26,"description":7},"Hermes Agent","1.0.0",{"hermes":27},{"tags":28,"related_skills":35},[29,30,31,32,33,34],"privacy","regulatory","legal-research","data-protection","product","compliance",[],"main","2988869c5a7d7be2225c9ea7a54a4a56a59b0d45","workflow\u002Fproduct-owner\u002Fprivacy-regulatory-research",0,"https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup","https:\u002F\u002Fgithub.com\u002Foat431","https:\u002F\u002Fpanomete.com\u002F","Hope and Luck is not a part of the strategy, \r\n\r\nSoftskill produces plan Hard skill produce product.","2026-11-03 00:43:08",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add oat431\u002Fhermes_config_backup --skill privacy-regulatory-research",{"tool":51,"command":52},"bunx","bunx skills add oat431\u002Fhermes_config_backup --skill privacy-regulatory-research",{"tool":54,"command":55},"pnpm","pnpm dlx skills add oat431\u002Fhermes_config_backup --skill privacy-regulatory-research","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fproduct-owner\u002Fprivacy-regulatory-research\u002FSKILL.md",true,[59,65],{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fthai-pdpa-owner-readiness.md","REFERENCE","参考文档",4684,"https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fproduct-owner\u002Fprivacy-regulatory-research\u002Freferences\u002Fthai-pdpa-owner-readiness.md",{"path":66,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fthai-pdpa-youtube-scoreboard.md",7839,"https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fproduct-owner\u002Fprivacy-regulatory-research\u002Freferences\u002Fthai-pdpa-youtube-scoreboard.md",[70,77,84,92,99,106],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AYZ2JY3NFKAPQSC39N5F3F","project-spec-docs","Fill\u002Fupdate project_spec docs (templates, MM handoffs).","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fui-ux\u002Fproject-spec-docs\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AYYRZPE7HQX7778558X52S","penpot-mcp","Penpot MCP: connect, verify, and fix streaming via nginx.","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fui-ux\u002Fpenpot-mcp\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7AYYNKP61CN2281VMJDXMB5","nginx-streaming-proxy","Configure nginx for streaming endpoints (SSE, MCP, WS).","Unlicense","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fui-ux\u002Fnginx-streaming-proxy\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7AYYJP0MDV1D3WVEEZB3SGA","branding-ci","Use for brand\u002FCI identity, style guides, and brand docs.","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fui-ux\u002Fbranding-ci\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7AYYGCXVT97DDTCM0ZJT6F6","yuanbao","Yuanbao (元宝) groups: @mention users, query info\u002Fmembers.","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fshared-skills\u002Fyuanbao\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M7AYYC2Y65NMGMD4GQXAZMMS","slidev","Create and present web-based slidedecks for developers using Slidev with Markdown, Vue components, code highlighting, animations, and interactive features. Use when building technical presentations, conference talks, code walkthroughs, teaching materials, or developer decks.","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fshared-skills\u002Fslidev\u002FSKILL.md",[],[]]