[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FAQZWJS684K8ETX2HCPYG1":3,"skill-same:01M6FAQZWJS684K8ETX2HCPYG1":79},{"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":22,"publishedAt":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":27,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":6,"ownerHtmlUrl":63,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":64,"install":65,"resources":78},"01M6FAQZWJS684K8ETX2HCPYG1","recon-scope-triage",null,"Triage ASM\u002Frecon output for ownership before testing","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-recon-scope-triage\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"triage","recon scope triage","recon","scope","main","2026","blob","for","output","relevant","helper","scripts","commands","testing","community","engagement","only","https","license","testing tools","security","github","docs","2026-11-10 10:12:30",false,"---\nname: recon-scope-triage\ndescription: Triage ASM\u002Frecon output for ownership before testing\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: authorized-engagement\nreport_count: 1\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## When to use this skill\n\nTrigger when:\n- The target brand is a common\u002Fdictionary word or shared term (e.g. `apex`, `summit`, `vertex`, `nova`, `core`, `orbit`, `pulse`, `unity`…)\n- You receive an ASM report, recon export, breach combo, repo list, bucket list, or mobile-app list to act on\n- A \"Critical\" count looks implausibly high (hundreds) for the org's size\n- Any asset's ownership is asserted by the tool but not *proven*\n\nThe two failure modes this skill prevents:\n1. **Wasting the engagement** testing\u002Ftriaging assets that aren't the target's.\n2. **Attacking an innocent third party** that merely shares the name — out of scope, and real harm.\n\n**Rule: ownership must be evidenced, and ownership is not permission.** Even a confirmed subsidiary\u002Fdomain\u002Fbucket remains excluded unless the written scope authorizes its testing.\n\n---\n\n## The collision sources (where keyword-matching lies)\n\n| Recon source | How it collides | Verify ownership by |\n|---|---|---|\n| **GitHub repos** | Search matched the brand word in repo name \u002F topic \u002F a string | Repo owner is the org's GH org; commits from org emails; code references the org's real domains\u002Finfra. A repo named `\u003Cword>-backend` by a random user = noise. |\n| **Cloud buckets** (S3\u002FGCS) | Bucket names are a **global namespace**; `\u003Cword>-static`, `\u003Cword>-data`, `\u003Cword>-public` exist for *someone* | Bucket content references the target; bucket name correlates with a *confirmed* target subdomain (`x.target.com` ↔ `x-public`) AND content matches; ACL\u002Fowner metadata. Generic content (other-language, other-industry) = not theirs. |\n| **Mobile apps** | Store search matched the brand word in app name \u002F package | Publisher account = the org; package reverse-DNS = an owned domain (`com.\u003Cowneddomain>.app`); dev cert; app calls owned API hosts. Mature ASM tools emit an \"apps_accepted=0\" \u002F ownership-confidence field — read it. |\n| **Breach corpora \u002F combos** | Email local-or-domain contains the brand word | **Exact** owned-domain match only (`@target.com`), not `@\u003Cword>group.com` \u002F `@something\u003Cword>.com`. A different domain that contains the word is a different org. |\n| **Typosquats** | Generated permutations of the name | These are *defensive*\u002Fbrand-protection findings, not offensive scope — note and move on. |\n| **Stack\u002Fforum\u002Fpaste hits** | Brand word in body | Body references the target's real domain\u002Fsubdomain\u002Femployee\u002Fsecret. Ownership-confidence \u003C threshold = drop. |\n\n---\n\n## Web \"Critical\" triage — the soft-404 control\n\nAutomated `.env` \u002F `.git` \u002F `actuator` \u002F admin-panel \"Criticals\" are overwhelmingly **soft-404s**: SPA\u002Fframework catch-alls returning HTTP 200 (or 403) for *every* path. Verify EACH before believing it:\n```bash\n# the \"finding\"\ncurl -s -o \u002Ftmp\u002Fa -w \"%{http_code} %{size_download}\\n\" https:\u002F\u002Fhost.target.com\u002F.env\n# a junk control on the same host\ncurl -s -o \u002Ftmp\u002Fb -w \"%{http_code} %{size_download}\\n\" https:\u002F\u002Fhost.target.com\u002Fzzz-nonsense-$RANDOM\n# Identical bodies suggest a catch-all; compare status, headers, redirects\n# and content semantics before disposing the finding. Size alone is insufficient.\ncmp -s \u002Ftmp\u002Fa \u002Ftmp\u002Fb && echo \"SOFT-404 false positive\" || echo \"differs — investigate\"\n```\nReal exposures have a content-type + signature that differs from the catch-all (`.git\u002Fconfig` starts `[core]`; `.env` has `KEY=value`; phpinfo has the XHTML-transitional doctype + `PHP Version`). A different body alone does not prove exposure: confirm actual sensitive content with minimal redacted evidence and avoid downloading credential data unnecessarily.\n\n---\n\nUse private per-run temporary paths with bounded response size\u002Ftimeouts rather than shared `\u002Ftmp\u002Fa` and `\u002Ftmp\u002Fb`; do not preserve discovered secrets in a general recon report.\n\n## The triage workflow\n\n1. **Confirm the canonical owned-domain set first** (the SOW\u002Fprogram domain + its verified subdomains + the verified Entra\u002FOkta\u002FGoogle tenant brand name). This is your ownership anchor.\n2. **For each asset class, apply the verify-by column above.** No signal → quarantine, don't test.\n3. **Re-baseline the severity counts** against only-owned assets. Report the *delta* — \"N Criticals → M after ownership + soft-404 triage\" is itself a finding about the ASM program.\n4. **Quarantine collisions explicitly** (a `loot\u002Fquarantined_\u003Csource>.txt`) so it's auditable that you saw them and chose not to target them.\n5. **Surface the meta-finding:** if the supplied ASM\u002Frecon feed is mostly false-positive, that misallocates the owner's remediation budget and buries real risk — write it up (Medium\u002FStrategic).\n\n---\n\n## Anti-patterns\n\n- **Trusting the tool's \"owned\" label.** Tools keyword-match; they don't prove ownership. Verify.\n- **Targeting a same-named third party** because it was \"in the report.\" Out of scope + real harm. A combo line `user@\u003Cword>company.com` is a different company's employee.\n- **Reporting soft-404s as exposures.** Always run the junk-path control.\n- **Counting typosquats \u002F missing-headers \u002F brand-collision repos as offensive findings.** They're defensive\u002Fhygiene\u002Fnoise — they pad the report and erode credibility.\n- **Skipping triage \"to save time.\"** Untriaged, you spend the whole engagement on other people's assets and find nothing real.\n\n---\n\n## Why this matters (calibration)\n\nFor a target whose brand is a common word, expect the bulk of automated \"owned\" assets to be collisions:\n- **Repos** that are unrelated open-source projects (ad-block lists, scrapers, student projects, a different company's SDK) merely containing the word.\n- **Mobile apps** published by entirely different companies that share the name — banks, credit unions, dating apps, dispensaries, home-care services are all real-world collision categories. (Good ASM tooling will tell you it accepted *zero* as owned.)\n- **Cloud buckets** in the global namespace holding some unrelated org's content (other-language documents, demo\u002Fsample data, another industry's files).\n- **Breach combos** full of emails from sibling-named-but-different companies (`\u003Cword>group.com`, `\u003Cregion>\u003Cword>.com`).\n\nOn a real engagement against a dictionary-word brand, after clearing this noise the only genuinely-owned high-severity finding was discoverable solely by manual tradecraft (a JS-bundle → API discovery, see `hunt-spa-api`) — it was nowhere in the hundreds of scanner \"Criticals.\" Triage-first is what made the engagement productive instead of a goose chase.\n\n---\n\n## Related Skills & Chains\n\n- **`triage-validation`** — asset-ownership triage (this skill) precedes finding-validity triage (the 7-Question Gate). Ownership first, then validity.\n- **`redteam-mindset`** — \"aggressive default\" means probe every *owned* live surface; this skill defines which surfaces are owned so persistence isn't wasted on collisions.\n- **`hunt-spa-api`** — once an API host passes ownership triage, this is how you test it.\n- **`offensive-osint` \u002F `osint-methodology`** — feed ownership anchors (verified domains, tenant brand, dev accounts) from OSINT into this triage.\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## When to use this skill\n\nTrigger when:\n- The target brand is a common\u002Fdictionary word or shared term (e.g. `apex`, `summit`, `vertex`, `nova`, `core`, `orbit`, `pulse`, `unity`…)\n- You receive an ASM report, recon export, breach combo, repo list, bucket list, or mobile-app list to act on\n- A \"Critical\" count looks implausibly high (hundreds) for the org's size\n- Any asset's ownership is asserted by the tool but not *proven*\n\nThe two failure modes this skill prevents:\n1. **Wasting the engagement** testing\u002Ftriaging assets that aren't the target's.\n2. **Attacking an innocent third party** that merely shares the name — out of scope, and real harm.\n\n**Rule: ownership must be evidenced, and ownership is not permission.** Even a confirmed subsidiary\u002Fdomain\u002Fbucket remains excluded unless the written scope authorizes its testing.\n\n---\n\n## The collision sources (where keyword-matching lies)\n\n| Recon source | How it collides | Verify ownership by |\n|---|---|---|\n| **GitHub repos** | Search matched the brand word in repo name \u002F topic \u002F a string | Repo owner is the org's GH org; commits from org emails; code references the org's real domains\u002Finfra. A repo named `\u003Cword>-backend` by a random user = noise. |\n| **Cloud buckets** (S3\u002FGCS) | Bucket names are a **global namespace**; `\u003Cword>-static`, `\u003Cword>-data`, `\u003Cword>-public` exist for *someone* | Bucket content references the target; bucket name correlates with a *confirmed* target subdomain (`x.target.com` ↔ `x-public`) AND content matches; ACL\u002Fowner metadata. Generic content (other-language, other-industry) = not theirs. |\n| **Mobile apps** | Store search matched the brand word in app name \u002F package | Publisher account = the org; package reverse-DNS = an owned domain (`com.\u003Cowneddomain>.app`); dev cert; app calls owned API hosts. Mature ASM tools emit an \"apps_accepted=0\" \u002F ownership-confidence field — read it. |\n| **Breach corpora \u002F combos** | Email local-or-domain contains the brand word | **Exact** owned-domain match only (`@target.com`), not `@\u003Cword>group.com` \u002F `@something\u003Cword>.com`. A different domain that contains the word is a different org. |\n| **Typosquats** | Generated permutations of the name | These are *defensive*\u002Fbrand-protection findings, not offensive scope — note and move on. |\n| **Stack\u002Fforum\u002Fpaste hits** | Brand word in body | Body references the target's real domain\u002Fsubdomain\u002Femployee\u002Fsecret. Ownership-confidence \u003C threshold = drop. |\n\n---\n\n## Web \"Critical\" triage — the soft-404 control\n\nAutomated `.env` \u002F `.git` \u002F `actuator` \u002F admin-panel \"Criticals\" are overwhelmingly **soft-404s**: SPA\u002Fframework catch-alls returning HTTP 200 (or 403) for *every* path. Verify EACH before believing it:\n```bash\n# the \"finding\"\ncurl -s -o \u002Ftmp\u002Fa -w \"%{http_code} %{size_download}\\n\" https:\u002F\u002Fhost.target.com\u002F.env\n# a junk control on the same host\ncurl -s -o \u002Ftmp\u002Fb -w \"%{http_code} %{size_download}\\n\" https:\u002F\u002Fhost.target.com\u002Fzzz-nonsense-$RANDOM\n# Identical bodies suggest a catch-all; compare status, headers, redirects\n# and content semantics before disposing the finding. Size alone is insufficient.\ncmp -s \u002Ftmp\u002Fa \u002Ftmp\u002Fb && echo \"SOFT-404 false positive\" || echo \"differs — investigate\"\n```\nReal exposures have a content-type + signature that differs from the catch-all (`.git\u002Fconfig` starts `[core]`; `.env` has `KEY=value`; phpinfo has the XHTML-transitional doctype + `PHP Version`). A different body alone does not prove exposure: confirm actual sensitive content with minimal redacted evidence and avoid downloading credential data unnecessarily.\n\n---\n\nUse private per-run temporary paths with bounded response size\u002Ftimeouts rather than shared `\u002Ftmp\u002Fa` and `\u002Ftmp\u002Fb`; do not preserve discovered secrets in a general recon report.\n\n## The triage workflow\n\n1. **Confirm the canonical owned-domain set first** (the SOW\u002Fprogram domain + its verified subdomains + the verified Entra\u002FOkta\u002FGoogle tenant brand name). This is your ownership anchor.\n2. **For each asset class, apply the verify-by column above.** No signal → quarantine, don't test.\n3. **Re-baseline the severity counts** against only-owned assets. Report the *delta* — \"N Criticals → M after ownership + soft-404 triage\" is itself a finding about the ASM program.\n4. **Quarantine collisions explicitly** (a `loot\u002Fquarantined_\u003Csource>.txt`) so it's auditable that you saw them and chose not to target them.\n5. **Surface the meta-finding:** if the supplied ASM\u002Frecon feed is mostly false-positive, that misallocates the owner's remediation budget and buries real risk — write it up (Medium\u002FStrategic).\n\n---\n\n## Anti-patterns\n\n- **Trusting the tool's \"owned\" label.** Tools keyword-match; they don't prove ownership. Verify.\n- **Targeting a same-named third party** because it was \"in the report.\" Out of scope + real harm. A combo line `user@\u003Cword>company.com` is a different company's employee.\n- **Reporting soft-404s as exposures.** Always run the junk-path control.\n- **Counting typosquats \u002F missing-headers \u002F brand-collision repos as offensive findings.** They're defensive\u002Fhygiene\u002Fnoise — they pad the report and erode credibility.\n- **Skipping triage \"to save time.\"** Untriaged, you spend the whole engagement on other people's assets and find nothing real.\n\n---\n\n## Why this matters (calibration)\n\nFor a target whose brand is a common word, expect the bulk of automated \"owned\" assets to be collisions:\n- **Repos** that are unrelated open-source projects (ad-block lists, scrapers, student projects, a different company's SDK) merely containing the word.\n- **Mobile apps** published by entirely different companies that share the name — banks, credit unions, dating apps, dispensaries, home-care services are all real-world collision categories. (Good ASM tooling will tell you it accepted *zero* as owned.)\n- **Cloud buckets** in the global namespace holding some unrelated org's content (other-language documents, demo\u002Fsample data, another industry's files).\n- **Breach combos** full of emails from sibling-named-but-different companies (`\u003Cword>group.com`, `\u003Cregion>\u003Cword>.com`).\n\nOn a real engagement against a dictionary-word brand, after clearing this noise the only genuinely-owned high-severity finding was discoverable solely by manual tradecraft (a JS-bundle → API discovery, see `hunt-spa-api`) — it was nowhere in the hundreds of scanner \"Criticals.\" Triage-first is what made the engagement productive instead of a goose chase.\n\n---\n\n## Related Skills & Chains\n\n- **`triage-validation`** — asset-ownership triage (this skill) precedes finding-validity triage (the 7-Question Gate). Ownership first, then validity.\n- **`redteam-mindset`** — \"aggressive default\" means probe every *owned* live surface; this skill defines which surfaces are owned so persistence isn't wasted on collisions.\n- **`hunt-spa-api`** — once an API host passes ownership triage, this is how you test it.\n- **`offensive-osint` \u002F `osint-methodology`** — feed ownership anchors (verified domains, tenant brand, dev accounts) from OSINT into this triage.\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":51,"source":52,"license":14,"sources":53,"category":43,"date_added":54,"description":7,"source_repo":55,"source_type":37,"report_count":56,"compatibility":57,"license_source":58},"offensive","https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter","authorized-engagement","2026-09-20","elementalsouls\u002FClaude-BugHunter",1,"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-recon-scope-triage",3,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections","https:\u002F\u002Fgithub.com\u002Fboisenoise","2026-11-10 14:20:15",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add boisenoise\u002Fskills-collections --skill recon-scope-triage",{"tool":71,"command":72},"bunx","bunx skills add boisenoise\u002Fskills-collections --skill recon-scope-triage",{"tool":74,"command":75},"pnpm","pnpm dlx skills add boisenoise\u002Fskills-collections --skill recon-scope-triage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-recon-scope-triage\u002FSKILL.md",true,[],[80,108,131,155,174,197],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":84,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":46},"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",[],[89,90,91,92,93,94,95,96,97,98,99,39,100,101,102,103,104,105,106,107,28],"web","access","web access","official","development","browser","search","data","Tools","read","fetch","youtube","free tools","platform","critical","free","cover","normal","when",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":84,"licenseFileUrl":112,"sourceHtmlUrl":113,"categories":114,"keywords":118,"publishedAt":46},"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",[115],{"categoryNo":116,"categoryName":117,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[110,119,120,44,92,93,41,97,121,122,123,124,125,126,127,103,128,129,130,29,28],"MCP","cli","Budget","credentials","team","catalog","use","call","discover","external tools","with","scoped",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":84,"licenseFileUrl":135,"sourceHtmlUrl":136,"categories":137,"keywords":143,"publishedAt":46},"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",[138],{"categoryNo":139,"categoryName":140,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[133,44,92,41,40,144,145,146,147,148,103,149,150,151,129,30,152,153,154,29,110,28],"email","enrichment","business","evidence","phone","ranking","post","job description","person","candidate","reason",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":84,"licenseFileUrl":159,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":46},"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",[],[163,164,165,44,92,41,166,167,40,168,121,169,170,171,147,103,172,173,29,110,28],"growth","rea","rea growth","produce","content","playbook","marketing","analyze","public","observations","company",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":84,"licenseFileUrl":178,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":46},"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",[],[182,183,44,184,92,185,41,186,187,188,189,190,103,191,192,193,194,195,196,29],"make","make ugc","research","create","Video","Captions","ads","short","hooks","head","style","niche","trending","talking-head","approve",{"skillNo":198,"name":199,"nameZh":6,"description":200,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":84,"licenseFileUrl":201,"sourceHtmlUrl":202,"categories":203,"keywords":204,"publishedAt":46},"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",[],[205,206,207,44,92,41,208,209,146,210,211,103,212,213,214,215,216,217,218,29],"signals","lead","lead signals","how","find","ready","as","how to","qualify","people","information","enrich","changes","funding"]