[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F7DFWVDAENV57JKBPQR0RF":3,"skill-same:01M6F7DFWVDAENV57JKBPQR0RF":74},{"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":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":20,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":59,"install":60,"resources":73},"01M6F7DFWVDAENV57JKBPQR0RF","hunt-brute-force",null,"Hunt Missing\u002FWeak Rate Limiting","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-brute-force\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"hunt brute force","hunt","main","2026","blob","for","relevant","helper","missing","scripts","scope","rate limiting","commands","testing","community","only","public","https","license","testing tools","research","security","github","2026-11-10 10:12:30",false,"---\nname: hunt-brute-force\ndescription: Hunt Missing\u002FWeak Rate Limiting\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: public_research\nreport_count: 0\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# HUNT-BRUTE-FORCE — Rate Limiting \u002F Brute Force \u002F Enumeration\n\n> Grounding note: this skill is built from published technique classes, not from a\n> curated set of named HackerOne reports. `report_count` is intentionally `0` — do\n> not cite an exact payout or report ID you cannot verify. Where a public case is\n> well-documented (e.g. Laxman Muthiyah's Instagram password-reset OTP race\u002Frotation\n> research, 2019–2021), it is named below as a *technique reference*, not a payout claim.\n\n## Crown Jewel Targets\n\nA uniform six-digit code has 1,000,000 possibilities; account-takeover feasibility depends on effective attempt budgets, binding, lifetime and other controls.\n\n**Highest-value chains:**\n- **OTP \u002F 2FA brute → MFA bypass → ATO** — no effective rate limit on `\u002Fverify-otp`, full 000000–999999 keyspace reachable\n- **Password-reset token brute** — short\u002Fpredictable\u002Fnon-expiring tokens + no rate limit → ATO (the Instagram 2019 case combined a 6-digit reset code, no rate limit per request-source, and IP rotation to make 10^6 tractable)\n- **Username\u002Femail enumeration → targeted credential stuffing** — valid\u002Finvalid distinguishable by response string, status code, or timing, use only controlled synthetic identities; never acquire\u002Fspray breach corpora\n- **Coupon \u002F gift-card \u002F referral code brute** — no rate limit on code validation → financial impact\n- **ReDoS** — attacker-controlled input hits a catastrophic-backtracking regex → CPU exhaustion → DoS\n\n---\n\n## Controlled assessment procedure\n\nAbsence of a 429 after 3–5 attempts does not prove a missing limiter. Do not use\nweak\u002Fdefault passwords, leaked credential corpora, account spraying, full OTP lists,\nsource\u002Fproxy rotation, mass registration or victim lockouts as the default probe.\nUse two owner-controlled synthetic accounts and an explicit per-account\u002Fglobal\nrequest, time and concurrency budget below agreed lockout\u002Fnotification thresholds.\nPrefer an isolated test environment with configurable small limits and known state.\nStop on throttling, account lockout, service errors or unexpected real data\u002Fmessages.\n\n1. Record endpoint\u002Fmethod, expected response, limiter key\u002Fwindow, token lifetime,\n   maximum attempts, recovery path and the identity authorized for testing.\n2. Establish known-good and known-bad synthetic controls before testing. Keep secrets\n   out of command arguments, output, screenshots, predictable `\u002Ftmp` files and Git.\n3. Exercise the approved tiny budget, recording status, latency, sanitized semantic\n   outcome and server-side limiter events. Bound every request timeout\u002Fbody length.\n4. Distinguish account lockout, source throttling, CAPTCHA\u002Fchallenge, delayed\u002Fqueued\n   processing and dropped submissions. An expired\u002Fconsumed OTP, changed session or\n   downstream failure can also reject a correct code; that is not proof of shadow\n   throttling. A timing\u002Fbody-size change is only a clue.\n5. Compare trusted-proxy behavior in the lab with one controlled changed header;\n   a restored 200 does not prove authentication attempts are processed or that every\n   endpoint’s limits are defeated. Coordinate rather than bypass an active block.\n6. For enumeration use only controlled valid\u002Fnonexistent identities and a randomized,\n   small, preapproved comparison with statistical uncertainty and confounders. Do not\n   cause real reset messages or registration churn. State whether information is\n   intended public and what actual privacy boundary is crossed.\n7. Reconcile persisted server state, clean up fixtures and report coverage\u002Funknowns.\n   No vulnerable\u002Fclean verdict follows from an incomplete or rejected request.\n\n## Worked OTP feasibility example\n\nFor a uniformly random six-digit code, N=1,000,000. If the server permits five unique\nattempts per code window, a single-window success probability is at most 5\u002FN = 0.0005%\nunder the stated assumptions. At 50 requests\u002Fsecond with no other limit, exhaustively\ncovering N would take 20,000 seconds (~5.56 hours), but that is hypothetical throughput,\nnot proof a live service sustains it or that the code remains valid. Account\u002Fsource\nlimits, cooldowns, code rotation, single-use state and independent windows matter.\nUse measured approved limits\u002Fconfiguration and bound uncertainty; never actually\nexhaust the keyspace to demonstrate impact. Severity depends on the complete access\nboundary and threat model, not the six-digit format alone.\n\n## Token unpredictability\n\nCharacter-frequency Shannon entropy or a short token sample does not measure the\ngenerator’s cryptographic entropy or predictability. Statistical suites cannot prove\na secure CSPRNG, and a universal 64-bit cutoff is inappropriate for all token types.\nReview the generator, randomness source, secret state, format, effective lifetime,\nrate limits and token binding. A counter\u002Ftimestamp may be one public component of a\nsecure MAC-protected token; demonstrate a synthetic prediction\u002Fforgery before claiming\npredictability. Do not collect thousands of password-reset emails for a heuristic.\n\n## ReDoS boundary\n\nNever send escalating catastrophic-backtracking inputs to a shared production service.\nReview the actual regex\u002Fengine, then use a disposable subprocess with a hard wall-time\nand memory cap, tiny synthetic cases and same-size benign controls. Remote latency\ncan reflect network\u002Fqueue\u002Fcache\u002Fload; neither doubling latency nor a single slow\nrequest proves regex-driven CPU exhaustion. Record engine\u002Fversion, regex, input and\nlocal CPU\u002Ftime evidence without causing a real outage.\n\n## Validation and reporting\n\n- State exact approved scope, tested identities and budget; proposed checks are not results.\n- Show a minimal repeatable synthetic unauthorized state transition or measured control\n  failure; retain unknown processing\u002Fcoverage states rather than claim no protection.\n- Keep actual tokens\u002Fpasswords\u002Fsession cookies private and rotate\u002Fdelete test artifacts.\n- Classify severity by reachability, lifetime, impact and compensating controls; no\n  automatic Critical\u002FHigh from a missing header, sample count or body difference.\n- Historical named cases in the overview are unverified technique leads, not payout,\n  current-vulnerability or patch-status evidence. Fetch original disclosures before citation.\n- No login\u002FOTP\u002Freset request, scanner, statistical test, brute-force or DoS was run here.\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; review separately obtained official tools and provenance before installation.\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# HUNT-BRUTE-FORCE — Rate Limiting \u002F Brute Force \u002F Enumeration\n\n> Grounding note: this skill is built from published technique classes, not from a\n> curated set of named HackerOne reports. `report_count` is intentionally `0` — do\n> not cite an exact payout or report ID you cannot verify. Where a public case is\n> well-documented (e.g. Laxman Muthiyah's Instagram password-reset OTP race\u002Frotation\n> research, 2019–2021), it is named below as a *technique reference*, not a payout claim.\n\n## Crown Jewel Targets\n\nA uniform six-digit code has 1,000,000 possibilities; account-takeover feasibility depends on effective attempt budgets, binding, lifetime and other controls.\n\n**Highest-value chains:**\n- **OTP \u002F 2FA brute → MFA bypass → ATO** — no effective rate limit on `\u002Fverify-otp`, full 000000–999999 keyspace reachable\n- **Password-reset token brute** — short\u002Fpredictable\u002Fnon-expiring tokens + no rate limit → ATO (the Instagram 2019 case combined a 6-digit reset code, no rate limit per request-source, and IP rotation to make 10^6 tractable)\n- **Username\u002Femail enumeration → targeted credential stuffing** — valid\u002Finvalid distinguishable by response string, status code, or timing, use only controlled synthetic identities; never acquire\u002Fspray breach corpora\n- **Coupon \u002F gift-card \u002F referral code brute** — no rate limit on code validation → financial impact\n- **ReDoS** — attacker-controlled input hits a catastrophic-backtracking regex → CPU exhaustion → DoS\n\n---\n\n## Controlled assessment procedure\n\nAbsence of a 429 after 3–5 attempts does not prove a missing limiter. Do not use\nweak\u002Fdefault passwords, leaked credential corpora, account spraying, full OTP lists,\nsource\u002Fproxy rotation, mass registration or victim lockouts as the default probe.\nUse two owner-controlled synthetic accounts and an explicit per-account\u002Fglobal\nrequest, time and concurrency budget below agreed lockout\u002Fnotification thresholds.\nPrefer an isolated test environment with configurable small limits and known state.\nStop on throttling, account lockout, service errors or unexpected real data\u002Fmessages.\n\n1. Record endpoint\u002Fmethod, expected response, limiter key\u002Fwindow, token lifetime,\n   maximum attempts, recovery path and the identity authorized for testing.\n2. Establish known-good and known-bad synthetic controls before testing. Keep secrets\n   out of command arguments, output, screenshots, predictable `\u002Ftmp` files and Git.\n3. Exercise the approved tiny budget, recording status, latency, sanitized semantic\n   outcome and server-side limiter events. Bound every request timeout\u002Fbody length.\n4. Distinguish account lockout, source throttling, CAPTCHA\u002Fchallenge, delayed\u002Fqueued\n   processing and dropped submissions. An expired\u002Fconsumed OTP, changed session or\n   downstream failure can also reject a correct code; that is not proof of shadow\n   throttling. A timing\u002Fbody-size change is only a clue.\n5. Compare trusted-proxy behavior in the lab with one controlled changed header;\n   a restored 200 does not prove authentication attempts are processed or that every\n   endpoint’s limits are defeated. Coordinate rather than bypass an active block.\n6. For enumeration use only controlled valid\u002Fnonexistent identities and a randomized,\n   small, preapproved comparison with statistical uncertainty and confounders. Do not\n   cause real reset messages or registration churn. State whether information is\n   intended public and what actual privacy boundary is crossed.\n7. Reconcile persisted server state, clean up fixtures and report coverage\u002Funknowns.\n   No vulnerable\u002Fclean verdict follows from an incomplete or rejected request.\n\n## Worked OTP feasibility example\n\nFor a uniformly random six-digit code, N=1,000,000. If the server permits five unique\nattempts per code window, a single-window success probability is at most 5\u002FN = 0.0005%\nunder the stated assumptions. At 50 requests\u002Fsecond with no other limit, exhaustively\ncovering N would take 20,000 seconds (~5.56 hours), but that is hypothetical throughput,\nnot proof a live service sustains it or that the code remains valid. Account\u002Fsource\nlimits, cooldowns, code rotation, single-use state and independent windows matter.\nUse measured approved limits\u002Fconfiguration and bound uncertainty; never actually\nexhaust the keyspace to demonstrate impact. Severity depends on the complete access\nboundary and threat model, not the six-digit format alone.\n\n## Token unpredictability\n\nCharacter-frequency Shannon entropy or a short token sample does not measure the\ngenerator’s cryptographic entropy or predictability. Statistical suites cannot prove\na secure CSPRNG, and a universal 64-bit cutoff is inappropriate for all token types.\nReview the generator, randomness source, secret state, format, effective lifetime,\nrate limits and token binding. A counter\u002Ftimestamp may be one public component of a\nsecure MAC-protected token; demonstrate a synthetic prediction\u002Fforgery before claiming\npredictability. Do not collect thousands of password-reset emails for a heuristic.\n\n## ReDoS boundary\n\nNever send escalating catastrophic-backtracking inputs to a shared production service.\nReview the actual regex\u002Fengine, then use a disposable subprocess with a hard wall-time\nand memory cap, tiny synthetic cases and same-size benign controls. Remote latency\ncan reflect network\u002Fqueue\u002Fcache\u002Fload; neither doubling latency nor a single slow\nrequest proves regex-driven CPU exhaustion. Record engine\u002Fversion, regex, input and\nlocal CPU\u002Ftime evidence without causing a real outage.\n\n## Validation and reporting\n\n- State exact approved scope, tested identities and budget; proposed checks are not results.\n- Show a minimal repeatable synthetic unauthorized state transition or measured control\n  failure; retain unknown processing\u002Fcoverage states rather than claim no protection.\n- Keep actual tokens\u002Fpasswords\u002Fsession cookies private and rotate\u002Fdelete test artifacts.\n- Classify severity by reachability, lifetime, impact and compensating controls; no\n  automatic Critical\u002FHigh from a missing header, sample count or body difference.\n- Historical named cases in the overview are unverified technique leads, not payout,\n  current-vulnerability or patch-status evidence. Fetch original disclosures before citation.\n- No login\u002FOTP\u002Freset request, scanner, statistical test, brute-force or DoS was run here.\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; review separately obtained official tools and provenance before installation.\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":46,"source":47,"license":14,"sources":48,"category":39,"date_added":49,"description":7,"source_repo":50,"source_type":32,"report_count":51,"compatibility":52,"license_source":53},"offensive","https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter","public_research","2026-09-20","elementalsouls\u002FClaude-BugHunter",0,"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-brute-force",3,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections","https:\u002F\u002Fgithub.com\u002Fboisenoise","2026-11-11 14:20:43",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add boisenoise\u002Fskills-collections --skill hunt-brute-force",{"tool":66,"command":67},"bunx","bunx skills add boisenoise\u002Fskills-collections --skill hunt-brute-force",{"tool":69,"command":70},"pnpm","pnpm dlx skills add boisenoise\u002Fskills-collections --skill hunt-brute-force","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-hunt-brute-force\u002FSKILL.md",true,[],[75,103,128,152,170,192],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":41},"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",[],[84,85,86,87,88,89,90,91,92,93,94,33,95,96,97,98,99,100,101,102,21],"web","access","web access","official","development","browser","search","data","Tools","read","fetch","youtube","free tools","platform","critical","free","cover","normal","when",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":115,"publishedAt":41},"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",[110],{"categoryNo":111,"categoryName":112,"taxonomyType":113,"taxonomyTypeDesc":114},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[105,116,117,40,87,88,36,92,118,119,120,121,122,123,124,98,125,126,127,22,21],"MCP","cli","Budget","credentials","team","catalog","use","call","discover","external tools","with","scoped",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":132,"sourceHtmlUrl":133,"categories":134,"keywords":140,"publishedAt":41},"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",[135],{"categoryNo":136,"categoryName":137,"taxonomyType":138,"taxonomyTypeDesc":139},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[130,40,87,36,35,141,142,143,144,145,98,146,147,148,126,23,149,150,151,22,105,21],"email","enrichment","business","evidence","phone","ranking","post","job description","person","candidate","reason",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":156,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":41},"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",[],[160,161,162,40,87,36,163,164,35,165,118,166,167,34,144,98,168,169,22,105,21],"growth","rea","rea growth","produce","content","playbook","marketing","analyze","observations","company",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":174,"sourceHtmlUrl":175,"categories":176,"keywords":177,"publishedAt":41},"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",[],[178,179,40,38,87,180,36,181,182,183,184,185,98,186,187,188,189,190,191,22],"make","make ugc","create","Video","Captions","ads","short","hooks","head","style","niche","trending","talking-head","approve",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":196,"sourceHtmlUrl":197,"categories":198,"keywords":199,"publishedAt":41},"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",[],[200,201,202,40,87,36,203,204,143,205,206,98,207,208,209,210,211,212,213,22],"signals","lead","lead signals","how","find","ready","as","how to","qualify","people","information","enrich","changes","funding"]