[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M738QPESTF92D110MWMEY0W6":3,"skill-same:01M738QPESTF92D110MWMEY0W6":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M738QPESTF92D110MWMEY0W6","enrich-industry",null,"Backfill contact-level industry from associated company records using a HubSpot workflow. Enables industry-based segmentation for targeted campaigns aligned with ICP verticals.","roohe\u002Fagentic-super-skills","roohe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99054084?v=4","01M734WCDFP6RZVT5CNM00QR26","01M734WCE4BD0T4NZS5PCV9V5F",10,"MIT","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fenrich-industry\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: enrich-industry\ndescription: \"Backfill contact-level industry from associated company records using a HubSpot workflow. Enables industry-based segmentation for targeted campaigns aligned with ICP verticals.\"\nlicense: MIT\nmetadata:\n  author: tomgranot\n  version: \"1.0\"\n  category: data-enrichment\n---\n\n# Enrich Contact Industry from Associated Company\n\nCopy industry data from company records to their associated contacts. In a typical B2B CRM, company records have industry populated at high rates (80-90%) while contact records have almost none. This workflow bridges that gap automatically.\n\n## Why This Matters\n\nWithout industry on contact records, you cannot segment email campaigns by vertical. For B2B companies targeting specific industries, this makes the difference between spray-and-pray email blasts and targeted, relevant messaging. Industry data on contacts also feeds ICP tier classification and lead scoring models.\n\n## Prerequisites\n\n- HubSpot Marketing Hub Professional or Sales Hub Professional (for Workflows)\n- Company name enrichment (enrich-company-name skill) should be completed first, as it may trigger new company associations\n- Access to Settings > Properties to verify\u002Fcreate the contact Industry property\n\n## Plan\n\n1. Verify the contact Industry property exists and is compatible with the company Industry property\n2. Audit how many contacts can be enriched (before state)\n3. Build a workflow that copies industry from the associated company\n4. Verify enrichment results (after state)\n\n## Before State\n\n### Check Property Compatibility\n\nThis is the most important pre-step. Contacts may have TWO industry properties: `industry` and `industry_name`. You must verify which one HubSpot uses for lists and reports.\n\n1. Go to **Settings > Properties > Contact properties**\n2. Search for \"Industry\"\n3. Note ALL industry-related properties on the contact object\n4. Check which property is used in existing lists, reports, and workflows\n5. The target property must be compatible with the company Industry property:\n   - If both are **dropdown select**: option values must match exactly (same spelling, same case)\n   - If the contact property is **single-line text**: it will accept any value (safest option)\n   - If unsure, use single-line text to avoid copy failures\n\n**If no contact Industry property exists**, create one:\n- Object: Contact\n- Group: Contact information\n- Label: Industry\n- Field type: Dropdown select (copy all values from the company Industry property) OR Single-line text (accepts any value)\n\n### Audit Enrichment Opportunity\n\n```python\nimport os\nfrom hubspot import HubSpot\nfrom dotenv import load_dotenv\n\nload_dotenv()\napi_client = HubSpot(access_token=os.getenv(\"HUBSPOT_API_TOKEN\"))\n\n# Count contacts missing industry\nresult = api_client.crm.contacts.search_api.do_search(\n    public_object_search_request={\n        \"filterGroups\": [{\n            \"filters\": [{\n                \"propertyName\": \"industry\",\n                \"operator\": \"NOT_HAS_PROPERTY\"\n            }]\n        }],\n        \"limit\": 0\n    }\n)\nprint(f\"Contacts missing industry: {result.total}\")\n```\n\nAlso create a HubSpot list to estimate enrichable contacts:\n- Filter 1: Contact Industry > is unknown\n- Filter 2: AND Associated company > Industry > is known\n- This count tells you how many contacts will actually be enriched\n\n## Execute\n\n### Create the Enrichment Workflow\n\nThis workflow is nearly identical to the company name enrichment workflow. If you already built that one, clone it and swap the property references.\n\n1. Go to **Automation > Workflows > Create workflow**\n2. Select **Contact-based > Blank workflow**\n3. Name: `AUTO-ENRICH: Copy Industry from Company`\n\n**Enrollment trigger:**\n- Contact property > Industry > **is unknown**\n- AND Associated company > Industry > **is known**\n\n**Re-enrollment:**\n- Enable re-enrollment on the same criteria. This ensures contacts that later get associated with a company are also enriched.\n\n**Action: Copy property**\n- Copy FROM: Company > Industry\n- Copy TO: Contact > Industry\n\n**Activate:**\n- Click Review > Turn on\n- Select **Yes, enroll existing contacts**\n\n**Note:** Unlike the company name workflow, no delay is needed here. If the contact already has an associated company with industry data (checked by the enrollment trigger), the copy can happen immediately.\n\n## After State\n\nWait 1-2 hours for the workflow to process, then verify.\n\n**Script approach:**\n\n```python\nresult = api_client.crm.contacts.search_api.do_search(\n    public_object_search_request={\n        \"filterGroups\": [{\n            \"filters\": [{\n                \"propertyName\": \"industry\",\n                \"operator\": \"NOT_HAS_PROPERTY\"\n            }]\n        }],\n        \"limit\": 0\n    }\n)\nprint(f\"Contacts still missing industry: {result.total}\")\n```\n\n**Verification checklist:**\n\n1. Contact industry count should jump from near-zero to tens of thousands\n2. The enrichment list (missing industry + has company association) should be near 0\n3. Spot-check 20+ contacts for accuracy:\n   - Open the contact record\n   - Verify the Industry field shows a value\n   - Click the associated company and confirm the industry matches\n4. Check that the industry distribution on contacts roughly mirrors the company industry distribution\n5. Check workflow history for failures — most common is property value mismatch (company has a value that does not match a dropdown option on the contact)\n\n## Key Technical Learnings\n\n- **Two industry properties can exist.** Some HubSpot portals have both `industry` and `industry_name` on contacts. Verify which one is authoritative before building the workflow. Writing to the wrong one means your lists and reports will not see the data.\n- **Dropdown value matching is case-sensitive and exact.** If the company Industry has \"Healthcare\" and the contact Industry dropdown has \"healthcare\" (lowercase), the copy will fail. Ensure values match exactly.\n- **Consider consolidating similar industries.** Many CRMs have overlapping values like \"Healthcare\" and \"Hospital & Health Care\". For segmentation, consider creating a separate \"Industry Group\" property that maps similar values into broader categories. This is optional but improves list usability.\n- **This does not overwrite existing values.** The enrollment trigger requires \"Industry is unknown\", so contacts that already have industry data are not affected.\n- **If using a text field instead of dropdown:** Enrichment works, but you lose the ability to filter by exact dropdown values in lists. You can convert to a dropdown later but will need to clean up inconsistent text values first.\n- **Run this after company name enrichment.** Company name enrichment may trigger new company associations, which increases the number of contacts eligible for industry enrichment.\n- **Clone the company name workflow.** The structure is nearly identical. Clone it in HubSpot and swap the property references to save time.\n","# Enrich Contact Industry from Associated Company\n\nCopy industry data from company records to their associated contacts. In a typical B2B CRM, company records have industry populated at high rates (80-90%) while contact records have almost none. This workflow bridges that gap automatically.\n\n## Why This Matters\n\nWithout industry on contact records, you cannot segment email campaigns by vertical. For B2B companies targeting specific industries, this makes the difference between spray-and-pray email blasts and targeted, relevant messaging. Industry data on contacts also feeds ICP tier classification and lead scoring models.\n\n## Prerequisites\n\n- HubSpot Marketing Hub Professional or Sales Hub Professional (for Workflows)\n- Company name enrichment (enrich-company-name skill) should be completed first, as it may trigger new company associations\n- Access to Settings > Properties to verify\u002Fcreate the contact Industry property\n\n## Plan\n\n1. Verify the contact Industry property exists and is compatible with the company Industry property\n2. Audit how many contacts can be enriched (before state)\n3. Build a workflow that copies industry from the associated company\n4. Verify enrichment results (after state)\n\n## Before State\n\n### Check Property Compatibility\n\nThis is the most important pre-step. Contacts may have TWO industry properties: `industry` and `industry_name`. You must verify which one HubSpot uses for lists and reports.\n\n1. Go to **Settings > Properties > Contact properties**\n2. Search for \"Industry\"\n3. Note ALL industry-related properties on the contact object\n4. Check which property is used in existing lists, reports, and workflows\n5. The target property must be compatible with the company Industry property:\n   - If both are **dropdown select**: option values must match exactly (same spelling, same case)\n   - If the contact property is **single-line text**: it will accept any value (safest option)\n   - If unsure, use single-line text to avoid copy failures\n\n**If no contact Industry property exists**, create one:\n- Object: Contact\n- Group: Contact information\n- Label: Industry\n- Field type: Dropdown select (copy all values from the company Industry property) OR Single-line text (accepts any value)\n\n### Audit Enrichment Opportunity\n\n```python\nimport os\nfrom hubspot import HubSpot\nfrom dotenv import load_dotenv\n\nload_dotenv()\napi_client = HubSpot(access_token=os.getenv(\"HUBSPOT_API_TOKEN\"))\n\n# Count contacts missing industry\nresult = api_client.crm.contacts.search_api.do_search(\n    public_object_search_request={\n        \"filterGroups\": [{\n            \"filters\": [{\n                \"propertyName\": \"industry\",\n                \"operator\": \"NOT_HAS_PROPERTY\"\n            }]\n        }],\n        \"limit\": 0\n    }\n)\nprint(f\"Contacts missing industry: {result.total}\")\n```\n\nAlso create a HubSpot list to estimate enrichable contacts:\n- Filter 1: Contact Industry > is unknown\n- Filter 2: AND Associated company > Industry > is known\n- This count tells you how many contacts will actually be enriched\n\n## Execute\n\n### Create the Enrichment Workflow\n\nThis workflow is nearly identical to the company name enrichment workflow. If you already built that one, clone it and swap the property references.\n\n1. Go to **Automation > Workflows > Create workflow**\n2. Select **Contact-based > Blank workflow**\n3. Name: `AUTO-ENRICH: Copy Industry from Company`\n\n**Enrollment trigger:**\n- Contact property > Industry > **is unknown**\n- AND Associated company > Industry > **is known**\n\n**Re-enrollment:**\n- Enable re-enrollment on the same criteria. This ensures contacts that later get associated with a company are also enriched.\n\n**Action: Copy property**\n- Copy FROM: Company > Industry\n- Copy TO: Contact > Industry\n\n**Activate:**\n- Click Review > Turn on\n- Select **Yes, enroll existing contacts**\n\n**Note:** Unlike the company name workflow, no delay is needed here. If the contact already has an associated company with industry data (checked by the enrollment trigger), the copy can happen immediately.\n\n## After State\n\nWait 1-2 hours for the workflow to process, then verify.\n\n**Script approach:**\n\n```python\nresult = api_client.crm.contacts.search_api.do_search(\n    public_object_search_request={\n        \"filterGroups\": [{\n            \"filters\": [{\n                \"propertyName\": \"industry\",\n                \"operator\": \"NOT_HAS_PROPERTY\"\n            }]\n        }],\n        \"limit\": 0\n    }\n)\nprint(f\"Contacts still missing industry: {result.total}\")\n```\n\n**Verification checklist:**\n\n1. Contact industry count should jump from near-zero to tens of thousands\n2. The enrichment list (missing industry + has company association) should be near 0\n3. Spot-check 20+ contacts for accuracy:\n   - Open the contact record\n   - Verify the Industry field shows a value\n   - Click the associated company and confirm the industry matches\n4. Check that the industry distribution on contacts roughly mirrors the company industry distribution\n5. Check workflow history for failures — most common is property value mismatch (company has a value that does not match a dropdown option on the contact)\n\n## Key Technical Learnings\n\n- **Two industry properties can exist.** Some HubSpot portals have both `industry` and `industry_name` on contacts. Verify which one is authoritative before building the workflow. Writing to the wrong one means your lists and reports will not see the data.\n- **Dropdown value matching is case-sensitive and exact.** If the company Industry has \"Healthcare\" and the contact Industry dropdown has \"healthcare\" (lowercase), the copy will fail. Ensure values match exactly.\n- **Consider consolidating similar industries.** Many CRMs have overlapping values like \"Healthcare\" and \"Hospital & Health Care\". For segmentation, consider creating a separate \"Industry Group\" property that maps similar values into broader categories. This is optional but improves list usability.\n- **This does not overwrite existing values.** The enrollment trigger requires \"Industry is unknown\", so contacts that already have industry data are not affected.\n- **If using a text field instead of dropdown:** Enrichment works, but you lose the ability to filter by exact dropdown values in lists. You can convert to a dropdown later but will need to clean up inconsistent text values first.\n- **Run this after company name enrichment.** Company name enrichment may trigger new company associations, which increases the number of contacts eligible for industry enrichment.\n- **Clone the company name workflow.** The structure is nearly identical. Clone it in HubSpot and swap the property references to save time.\n",{"name":5,"license":14,"metadata":23,"description":7},{"author":24,"version":25,"category":26},"tomgranot","1.0","data-enrichment","master","f483e54f3ad5f202a77d45f2e57f8d970b71195f","skills_library\u002Fenrich-industry",2,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills","https:\u002F\u002Fgithub.com\u002Froohe","yoou.link","2026-05-19 15:56:07",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add roohe\u002Fagentic-super-skills --skill enrich-industry",{"tool":41,"command":42},"bunx","bunx skills add roohe\u002Fagentic-super-skills --skill enrich-industry",{"tool":44,"command":45},"pnpm","pnpm dlx skills add roohe\u002Fagentic-super-skills --skill enrich-industry","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fenrich-industry\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":18},"01M73D865CZME2FCMKA4PQM348","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M73D7Z64J4ABWZJD7P44XBBF","youtube-downloader","Download and process YouTube content for research. Use when: downloading competitor videos for analysis; extracting audio for podcasts; getting transcripts for content repurposing; archiving webinars; research content curation","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyoutube-downloader\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M73D7K8778TGZV3GJFR3703D","yc-pitch-deck","Create a compelling startup pitch deck that follows the structure proven to raise billions from top investors. Master the YC and Sequoia formats that get founders funded. Use when: **Fundraising** to create investor pitch decks; **YC application** to structure your narrative; **Demo Day prep** to craft your 2-minute pitch; **Angel investors** to communicate your opportunity; **Partnership pitches** to structure compelling asks","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyc-pitch-deck\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M73D70KJSE0E8Z28YMNNRT04","x-twitter-scraper","Use when the user needs X (Twitter) data or confirmation-gated X actions through Xquik: tweet search, user lookup, follower extraction, media download, monitoring, webhooks, MCP, SDKs, posting, likes, DMs, and profile updates. Requires a Xquik API key. Never ask for X login material.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fx-twitter-scraper\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M73D6ED01GV077R7K4NZNFZJ","write-vignette","Create R package vignettes using R Markdown or Quarto. Covers vignette setup, YAML configuration, code chunk options, building and testing, and CRAN requirements for vignettes. Use when adding a Getting Started tutorial, documenting complex workflows spanning multiple functions, creating domain-specific guides, or when CRAN submission requires user-facing documentation beyond function help pages.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-vignette\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M73D69YJR0BK3NFHE0CYG3EF","write-validation-documentation","Write IQ\u002FOQ\u002FPQ validation documentation for computerized systems in regulated environments. Covers protocols, reports, test scripts, deviation handling, and approval workflows. Use when validating R or other software for regulated use, preparing for a regulatory audit, documenting qualification of computing environments, or creating and updating validation protocols and reports for new or re-qualified systems.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-validation-documentation\u002FSKILL.md",[],[]]