[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77SZWR2CWG3WH68358QJBBT":3,"skill-same:01M77SZWR2CWG3WH68358QJBBT":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M77SZWR2CWG3WH68358QJBBT","hunt-a-handle",null,"Enumerate a username across hundreds of platforms with sherlock, maigret and WhatsMyName, then correlate and confirm which accounts genuinely belong to the same person. Use for username OSINT and handle enumeration, \"find all accounts for this username\", cross-platform account correlation, nickname and screen-name pivots, or turning a handle into a real name. Applies to fraud and synthetic-identity investigation, recruitment and marketplace scam checks, trust-and-safety enforcement, insider-threat work, and personal exposure audits. Reference at useosint.com\u002Fskills\u002Fhunt-a-handle.","Reihantt6\u002Fsns-myagent","Reihantt6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F219822095?v=4","01M77KK94PV8B7C2D9XWXNS8DJ","Mohamad Reihan tegar prasetya","01M77KK958QFMTHYXGXFV7KZ79",2,"MIT","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fhunt-a-handle\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Enumerate a username across hundreds of platforms with sherlock, maigret and WhatsMyName, then correlate and confirm which accounts genuinely belong to the same person. Use for username OSINT and handle enumeration, \\\"find all accounts for this username\\\", cross-platform account correlation, nickname and screen-name pivots, or turning a handle into a real name. Applies to fraud and synthetic-identity investigation, recruitment and marketplace scam checks, trust-and-safety enforcement, insider-threat work, and personal exposure audits. Reference at useosint.com\u002Fskills\u002Fhunt-a-handle.\"\n---\n# Hunt a handle\n\nHandle reuse is the cheapest strong link in OSINT: one string, checked in\nminutes, potentially tying a dozen platforms to one person. It is also the most\nover-trusted. Enumerators do not verify identity — they perform HTTP existence\nchecks — and a hit list is a list of *candidates*, nothing more. The mistake\nthat ruins these investigations is pasting the tool's output into the report.\nEnumeration is the cheap half; confirmation is the work.\n\n## Step 1 — Authorized scope\n\nRead [..\u002F..\u002FETHICS.md](..\u002F..\u002FETHICS.md) and write down, before any query:\nsubject, objective, in-bounds selectors, out-of-bounds actions (logging in,\ncontacting, requesting follows), and the governing jurisdiction. Handle hunting\ndrifts easily — one run hands you thirty new platforms, and it is trivial to end\nup profiling an uninvolved person who shares the string.\n\n**Done when** scope is written down and you can name what would put you out of\nbounds.\n\n## Step 2 — Pick your enumerator\n\n| Holding | Reach for | Why |\n|---|---|---|\n| One handle, need breadth fast | `sherlock` | Largest quick sweep, existence only |\n| One handle, need profile content | `maigret` | Parses the page: display name, bio, IDs, links, sometimes country and creation date |\n| Need to see why a hit fired | WhatsMyName data | Every check is a declared URI plus a match rule you can read |\n| A handle on one known platform | Manual visit | Nothing beats reading the actual profile |\n\n```bash\nsherlock jdoe_92 --timeout 10 --csv\nmaigret jdoe_92 --html\n```\n\nmaigret is the higher-value tool for correlation because it returns *fields*,\nnot booleans. A display name, avatar URL, self-declared location, numeric user\nID and an \"also known as\" list give you material to test the next platform\nagainst. Sherlock gives you a URL and a claim.\n\nWhatsMyName is a detection list, not a scanner: a JSON file of site entries,\neach with a URI template and explicit match criteria (an expected HTTP status\nand an expected string in the body, plus the equivalent for \"missing\"). Read the\nentry for any site you doubt — it tells you exactly what the tool considered\nproof. Many wrappers and web front-ends consume the same list, so a hit in three\ndifferent tools is often one rule firing three times, not three independent\nconfirmations.\n\n**Done when** every candidate is recorded with platform, URL, the tool that\nfound it, and live\u002Fdead status.\n\n## Step 3 — Generate variants\n\nThe handle you were given is one point in a person's naming habit. Recover the\nhabit and you find the accounts the first sweep missed.\n\n- Separator swaps: `john.doe`, `john_doe`, `john-doe`, `johndoe`\n- Truncations and initials: `jdoe`, `johnd`, `j_doe`, `doej`\n- Number suffixes: birth year, birth year two-digit, `1`, `99`, `007`\n- Leetspeak and character substitution: `j0hnd0e`, `johnd0e`\n- Email local part as handle, and handle as email local part\n- Gamer-tag morphology: prefixes, `xX…Xx`, clan tags, doubled letters\n\nFull pattern list: [reference\u002Fvariant-patterns.md](reference\u002Fvariant-patterns.md).\n\nTwo inference directions matter. Handle → name: `jdoe_92` suggests a\nfirst-initial-lastname pattern and a 1992 birth year, which is a hypothesis to\ntest, not a finding. Name → handle: if you already have a real name, generate\nthe handles that name would plausibly produce and enumerate those too — it often\noutperforms starting from a handle someone gave you.\n\n**Done when** the variant set is enumerated and the ones that produced hits are\nfolded back into Step 2.\n\n## Step 4 — Confirm, or reject\n\nFor each candidate, look for evidence that survives a skeptical reader.\n\nStrong:\n\n- Same avatar. Verify with `find-the-original-image` — a match to a stock photo\n  or a third party's picture is a rejection, not a confirmation.\n- Byte-identical or near-identical bio text, especially with a typo or an unusual\n  phrasing carried across.\n- A self-declared cross-link: the profile links the other profile. Best evidence\n  available short of an admission.\n- A contact selector present on both (same email, same personal domain).\n\nModerate:\n\n- Account creation dates clustering in a narrow window across platforms — people\n  sign up for things in bursts.\n- Follower\u002Ffollowing overlap with the same distinctive small accounts.\n- Writing style: idiom, punctuation habits, timezone of posting.\n\nWeak on its own: the handle matching. That is the thing you are testing, not\nevidence for it.\n\nPlatforms exposing a **numeric user ID** are disproportionately useful. Where\nIDs are issued in registration order, the ID bounds an account's creation date\neven when the profile hides it. GitHub's\n`https:\u002F\u002Fapi.github.com\u002Fusers\u002F\u003Clogin>` returns a numeric `id` and `created_at`;\nDiscord's snowflake IDs encode a creation timestamp directly. Per-platform\ndetail: [reference\u002Fplatform-leakage.md](reference\u002Fplatform-leakage.md).\n\n**Done when** every candidate is graded confirmed, probable, or rejected, each\nwith its evidence written next to it.\n\n## Where this goes wrong\n\nExistence checks are HTTP heuristics. Every one of these produces a false\npositive:\n\n- **Soft 404s.** The site returns 200 with a \"user not found\" page. If the match\n  rule keys on status code, everything exists.\n- **Catch-all profile pages.** Some platforms render a generic shell for any\n  string and only 404 on the API.\n- **Rate-limit and CAPTCHA interstitials.** A challenge page is a 200 with body\n  content, so it can satisfy both the \"found\" and \"missing\" rules — and once you\n  are rate-limited, results for the rest of the run are garbage. Re-run failures\n  separately rather than trusting a single sweep.\n- **Reserved, squatted, and impersonation accounts.** Registered, real, not your\n  subject.\n- **Stale entries.** Sites change their 404 behaviour and detection lists lag.\n  Absence of a hit is not absence of an account.\n\nThe deeper problem is collision. Common handles belong to many unrelated people,\nand a short or dictionary-word handle across ten platforms is ten people far\nmore often than one. Confidence should scale with the handle's distinctiveness:\na rare invented string is itself weak-to-moderate evidence, `mike` is none.\n\nDo not resolve ambiguity by logging in, messaging, or requesting a follow. That\nis interaction, out of scope by default, and it tells the subject you exist —\nsee `investigate-without-getting-made`.\n\n## Confidence grading\n\n- **Confirmed** — an avatar match verified through `find-the-original-image`\n  plus one other strong item, or a self-declared cross-link between the two\n  profiles, or a shared contact selector.\n- **Probable** — distinctive handle plus one moderate item (creation-date\n  cluster, follower overlap, consistent style) and no contradicting evidence.\n- **Unconfirmed** — the handle matches and nothing else does. Report it as an\n  enumeration hit, not as the subject's account.\n- **Rejected** — content, language, timeline, or avatar provenance contradicts\n  the subject. Record rejections; they stop the next analyst redoing the work.\n\n## Worked example\n\nGiven `sunfish_ada`. Sherlock returns 14 hits. maigret returns 9 with content,\nincluding a code-hosting profile with display name \"A. Okonkwo\", a photography\nsite with the same avatar, and a forum with an empty shell profile.\n\nThe forum hit is discarded first: fetching a deliberately absurd handle on the\nsame forum also returns 200 with an identical empty page. Catch-all, not an\naccount.\n\nThe avatar on the photography site reverse-searches (via\n`find-the-original-image`) to the same image on the code-hosting profile and\nnowhere else — good. The code-hosting API gives a numeric ID and a creation date\nin the same month as the photography account's stated join date. Two moderate\nitems plus an avatar match: confirmed for both.\n\nA microblog hit with the same handle posts in a different language about\nunrelated subjects, on an account predating the others by six years. Different\nperson, same string — rejected, and stated explicitly, because it is the first\nthing a reviewer will find.\n\n## Pivots\n\n| New selector | Skill |\n|---|---|\n| Display name \u002F real name | `find-anyone` |\n| Exposed or inferred email | `what-an-email-reveals` |\n| Phone number on a profile | `whose-number-is-this` |\n| Avatar or posted photos | `find-the-original-image`, `secrets-in-file-metadata` |\n| Photos with location context | `where-was-this-taken` |\n| Code-hosting handle | `secrets-in-git-history` |\n| Personal domain in a bio | `who-owns-this-domain` |\n| Handle in credential dumps | `what-leaked-about-you` |\n| Full posting history on a confirmed account | `pattern-of-life-from-socials` |\n| The account map itself | `graph-the-network` |\n\n## Legal and ToS notes\n\nAutomated enumeration hits platforms with scripted requests, which most terms of\nservice prohibit regardless of the data being public. Keep concurrency low, do\nnot defeat CAPTCHAs, and stop when a platform signals refusal. In the EU and UK,\nassembling scattered public accounts into a profile of a living person is\nprocessing personal data and needs a lawful basis and data minimisation.\n\n## Step 5 — Report\n\nRun `write-the-intel-brief`. Give the platform\u002FURL\u002Fconfidence\u002Fevidence table,\nlist rejections with reasons, and lead with the real-name and contact selectors\nthe handles produced.\n\n**Done when** every candidate in the table carries a grade and a source, and no\nenumeration hit appears without one.\n","# Hunt a handle\n\nHandle reuse is the cheapest strong link in OSINT: one string, checked in\nminutes, potentially tying a dozen platforms to one person. It is also the most\nover-trusted. Enumerators do not verify identity — they perform HTTP existence\nchecks — and a hit list is a list of *candidates*, nothing more. The mistake\nthat ruins these investigations is pasting the tool's output into the report.\nEnumeration is the cheap half; confirmation is the work.\n\n## Step 1 — Authorized scope\n\nRead [..\u002F..\u002FETHICS.md](..\u002F..\u002FETHICS.md) and write down, before any query:\nsubject, objective, in-bounds selectors, out-of-bounds actions (logging in,\ncontacting, requesting follows), and the governing jurisdiction. Handle hunting\ndrifts easily — one run hands you thirty new platforms, and it is trivial to end\nup profiling an uninvolved person who shares the string.\n\n**Done when** scope is written down and you can name what would put you out of\nbounds.\n\n## Step 2 — Pick your enumerator\n\n| Holding | Reach for | Why |\n|---|---|---|\n| One handle, need breadth fast | `sherlock` | Largest quick sweep, existence only |\n| One handle, need profile content | `maigret` | Parses the page: display name, bio, IDs, links, sometimes country and creation date |\n| Need to see why a hit fired | WhatsMyName data | Every check is a declared URI plus a match rule you can read |\n| A handle on one known platform | Manual visit | Nothing beats reading the actual profile |\n\n```bash\nsherlock jdoe_92 --timeout 10 --csv\nmaigret jdoe_92 --html\n```\n\nmaigret is the higher-value tool for correlation because it returns *fields*,\nnot booleans. A display name, avatar URL, self-declared location, numeric user\nID and an \"also known as\" list give you material to test the next platform\nagainst. Sherlock gives you a URL and a claim.\n\nWhatsMyName is a detection list, not a scanner: a JSON file of site entries,\neach with a URI template and explicit match criteria (an expected HTTP status\nand an expected string in the body, plus the equivalent for \"missing\"). Read the\nentry for any site you doubt — it tells you exactly what the tool considered\nproof. Many wrappers and web front-ends consume the same list, so a hit in three\ndifferent tools is often one rule firing three times, not three independent\nconfirmations.\n\n**Done when** every candidate is recorded with platform, URL, the tool that\nfound it, and live\u002Fdead status.\n\n## Step 3 — Generate variants\n\nThe handle you were given is one point in a person's naming habit. Recover the\nhabit and you find the accounts the first sweep missed.\n\n- Separator swaps: `john.doe`, `john_doe`, `john-doe`, `johndoe`\n- Truncations and initials: `jdoe`, `johnd`, `j_doe`, `doej`\n- Number suffixes: birth year, birth year two-digit, `1`, `99`, `007`\n- Leetspeak and character substitution: `j0hnd0e`, `johnd0e`\n- Email local part as handle, and handle as email local part\n- Gamer-tag morphology: prefixes, `xX…Xx`, clan tags, doubled letters\n\nFull pattern list: [reference\u002Fvariant-patterns.md](reference\u002Fvariant-patterns.md).\n\nTwo inference directions matter. Handle → name: `jdoe_92` suggests a\nfirst-initial-lastname pattern and a 1992 birth year, which is a hypothesis to\ntest, not a finding. Name → handle: if you already have a real name, generate\nthe handles that name would plausibly produce and enumerate those too — it often\noutperforms starting from a handle someone gave you.\n\n**Done when** the variant set is enumerated and the ones that produced hits are\nfolded back into Step 2.\n\n## Step 4 — Confirm, or reject\n\nFor each candidate, look for evidence that survives a skeptical reader.\n\nStrong:\n\n- Same avatar. Verify with `find-the-original-image` — a match to a stock photo\n  or a third party's picture is a rejection, not a confirmation.\n- Byte-identical or near-identical bio text, especially with a typo or an unusual\n  phrasing carried across.\n- A self-declared cross-link: the profile links the other profile. Best evidence\n  available short of an admission.\n- A contact selector present on both (same email, same personal domain).\n\nModerate:\n\n- Account creation dates clustering in a narrow window across platforms — people\n  sign up for things in bursts.\n- Follower\u002Ffollowing overlap with the same distinctive small accounts.\n- Writing style: idiom, punctuation habits, timezone of posting.\n\nWeak on its own: the handle matching. That is the thing you are testing, not\nevidence for it.\n\nPlatforms exposing a **numeric user ID** are disproportionately useful. Where\nIDs are issued in registration order, the ID bounds an account's creation date\neven when the profile hides it. GitHub's\n`https:\u002F\u002Fapi.github.com\u002Fusers\u002F\u003Clogin>` returns a numeric `id` and `created_at`;\nDiscord's snowflake IDs encode a creation timestamp directly. Per-platform\ndetail: [reference\u002Fplatform-leakage.md](reference\u002Fplatform-leakage.md).\n\n**Done when** every candidate is graded confirmed, probable, or rejected, each\nwith its evidence written next to it.\n\n## Where this goes wrong\n\nExistence checks are HTTP heuristics. Every one of these produces a false\npositive:\n\n- **Soft 404s.** The site returns 200 with a \"user not found\" page. If the match\n  rule keys on status code, everything exists.\n- **Catch-all profile pages.** Some platforms render a generic shell for any\n  string and only 404 on the API.\n- **Rate-limit and CAPTCHA interstitials.** A challenge page is a 200 with body\n  content, so it can satisfy both the \"found\" and \"missing\" rules — and once you\n  are rate-limited, results for the rest of the run are garbage. Re-run failures\n  separately rather than trusting a single sweep.\n- **Reserved, squatted, and impersonation accounts.** Registered, real, not your\n  subject.\n- **Stale entries.** Sites change their 404 behaviour and detection lists lag.\n  Absence of a hit is not absence of an account.\n\nThe deeper problem is collision. Common handles belong to many unrelated people,\nand a short or dictionary-word handle across ten platforms is ten people far\nmore often than one. Confidence should scale with the handle's distinctiveness:\na rare invented string is itself weak-to-moderate evidence, `mike` is none.\n\nDo not resolve ambiguity by logging in, messaging, or requesting a follow. That\nis interaction, out of scope by default, and it tells the subject you exist —\nsee `investigate-without-getting-made`.\n\n## Confidence grading\n\n- **Confirmed** — an avatar match verified through `find-the-original-image`\n  plus one other strong item, or a self-declared cross-link between the two\n  profiles, or a shared contact selector.\n- **Probable** — distinctive handle plus one moderate item (creation-date\n  cluster, follower overlap, consistent style) and no contradicting evidence.\n- **Unconfirmed** — the handle matches and nothing else does. Report it as an\n  enumeration hit, not as the subject's account.\n- **Rejected** — content, language, timeline, or avatar provenance contradicts\n  the subject. Record rejections; they stop the next analyst redoing the work.\n\n## Worked example\n\nGiven `sunfish_ada`. Sherlock returns 14 hits. maigret returns 9 with content,\nincluding a code-hosting profile with display name \"A. Okonkwo\", a photography\nsite with the same avatar, and a forum with an empty shell profile.\n\nThe forum hit is discarded first: fetching a deliberately absurd handle on the\nsame forum also returns 200 with an identical empty page. Catch-all, not an\naccount.\n\nThe avatar on the photography site reverse-searches (via\n`find-the-original-image`) to the same image on the code-hosting profile and\nnowhere else — good. The code-hosting API gives a numeric ID and a creation date\nin the same month as the photography account's stated join date. Two moderate\nitems plus an avatar match: confirmed for both.\n\nA microblog hit with the same handle posts in a different language about\nunrelated subjects, on an account predating the others by six years. Different\nperson, same string — rejected, and stated explicitly, because it is the first\nthing a reviewer will find.\n\n## Pivots\n\n| New selector | Skill |\n|---|---|\n| Display name \u002F real name | `find-anyone` |\n| Exposed or inferred email | `what-an-email-reveals` |\n| Phone number on a profile | `whose-number-is-this` |\n| Avatar or posted photos | `find-the-original-image`, `secrets-in-file-metadata` |\n| Photos with location context | `where-was-this-taken` |\n| Code-hosting handle | `secrets-in-git-history` |\n| Personal domain in a bio | `who-owns-this-domain` |\n| Handle in credential dumps | `what-leaked-about-you` |\n| Full posting history on a confirmed account | `pattern-of-life-from-socials` |\n| The account map itself | `graph-the-network` |\n\n## Legal and ToS notes\n\nAutomated enumeration hits platforms with scripted requests, which most terms of\nservice prohibit regardless of the data being public. Keep concurrency low, do\nnot defeat CAPTCHAs, and stop when a platform signals refusal. In the EU and UK,\nassembling scattered public accounts into a profile of a living person is\nprocessing personal data and needs a lawful basis and data minimisation.\n\n## Step 5 — Report\n\nRun `write-the-intel-brief`. Give the platform\u002FURL\u002Fconfidence\u002Fevidence table,\nlist rejections with reasons, and lead with the real-name and contact selectors\nthe handles produced.\n\n**Done when** every candidate in the table carries a grade and a source, and no\nenumeration hit appears without one.\n",{"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92","agent\u002Fskills\u002Fhunt-a-handle",0,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent","https:\u002F\u002Fgithub.com\u002FReihantt6","reihsns.web.id","2026-08-19 20:08:18",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Reihantt6\u002Fsns-myagent --skill hunt-a-handle",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill hunt-a-handle",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill hunt-a-handle","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fhunt-a-handle\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"reference\u002Fplatform-leakage.md","REFERENCE","参考文档",5251,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fhunt-a-handle\u002Freference\u002Fplatform-leakage.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"reference\u002Fvariant-patterns.md",4588,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fhunt-a-handle\u002Freference\u002Fvariant-patterns.md",[57,64,71,78,85,92],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M77XDCYZ407XYMF2T4P6F7VT","youtube-transcript","Extract transcripts from YouTube videos. Use when the user asks for a transcript, subtitles, or captions of a YouTube video and provides a YouTube URL (youtube.com\u002Fwatch?v=, youtu.be\u002F, or similar). Supports output with or without timestamps.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-transcript\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M77XD7PBC98J6MXGJJ2TJ8DX","youtube-thumbnail-design","YouTube thumbnail design with specific dimensions, contrast rules, and mobile preview optimization. Covers safe zones, text placement, face expression psychology, and A\u002FB testing. Use for: YouTube thumbnails, video cover images, click-through optimization. Triggers: youtube thumbnail, thumbnail design, video thumbnail, click through rate, ctr optimization, youtube cover, video cover image, thumbnail maker, thumbnail tips, youtube design, video preview image","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-thumbnail-design\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M77XD2541C8HXJ6RHYZP4NGJ","youtube-short-maker","Make YouTube Shorts that hold attention with Pexo — vertical 9:16, fast-paced, hook in the first 3 seconds. Describe your topic and Pexo writes the script, generates the shots, picks the models, and assembles a finished Short with music and captions. Use for YouTube Shorts: \"youtube short\", \"make a youtube short\", \"shorts video\", \"short-form video\". NOT for long-form or landscape video.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-short-maker\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M77XCXKVSYK7KTZ3PQBVVGFD","xcode-project-setup","Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fxcode-project-setup\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M77XCR1DV8ZQK2NHWKVY4EWX","x402","Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — \"just use it\" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or \"build it in\" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the user asks about x402, pay-per-use, USDC payments, or wants Browser Use Cloud without an API key. For the free-tier signup (reverse-CAPTCHA → API key), use `browser-use cloud signup` or the `cloud` skill instead.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx402\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M77XCMD3R3ZBZQQSW6E0793B","x-twitter-scraper","Build GitHub Copilot workflows with Xquik X API SDKs, REST endpoints, hosted Apify Actor runs, MCP tools, TweetClaw OpenClaw plugin installs, signed webhooks, tweet search, user lookup, follower exports, media actions, and agent automation.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx-twitter-scraper\u002FSKILL.md",[],[]]