[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77X9C7BTJ2M8GP41XCEAD74":3,"skill-same:01M77X9C7BTJ2M8GP41XCEAD74":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},"01M77X9C7BTJ2M8GP41XCEAD74","whose-number-is-this",null,"Investigate a phone number — E.164 normalisation with libphonenumber, phoneinfoga scanning, carrier and line-type identification, VoIP and burner detection, messaging-app registration checks, and reverse-lookup and caller-ID sources. Use for phone OSINT and reverse phone lookup, \"who owns this number\", identifying a burner or VoIP number, or checking whether a number is registered on WhatsApp, Telegram or Signal. Applies to vishing and business email compromise investigation, verifying a counterparty before sending payment, recruitment and marketplace scam checks, and fraud triage. Reference at useosint.com\u002Fskills\u002Fwhose-number-is-this.","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\u002Fwhose-number-is-this\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Investigate a phone number — E.164 normalisation with libphonenumber, phoneinfoga scanning, carrier and line-type identification, VoIP and burner detection, messaging-app registration checks, and reverse-lookup and caller-ID sources. Use for phone OSINT and reverse phone lookup, \\\"who owns this number\\\", identifying a burner or VoIP number, or checking whether a number is registered on WhatsApp, Telegram or Signal. Applies to vishing and business email compromise investigation, verifying a counterparty before sending payment, recruitment and marketplace scam checks, and fraud triage. Reference at useosint.com\u002Fskills\u002Fwhose-number-is-this.\"\n---\n# Whose number is this\n\nA phone number is a strong selector: expensive to acquire, hard to change, and\nused as an account-recovery anchor almost everywhere. It is also the selector\ninvestigators get most wrong, because the metadata everyone quotes — the carrier\n— is frequently stale, and because a large share of numbers now belong to\nsoftware rather than to a SIM in someone's pocket. Do not call or text the\nsubject; that is contact, not research.\n\n## Step 1 — Authorized scope\n\nRead [..\u002F..\u002FETHICS.md](..\u002F..\u002FETHICS.md). Write down subject, objective,\nin-bounds selectors, out-of-bounds actions, and the governing jurisdiction —\nwhich matters more here than in most skills, because reverse phone lookup is\nspecifically regulated in many places. Decide now whether messaging-app\ncontact-discovery checks are authorized; they are interactive.\n\n**Done when** scope is written and the contact-discovery decision is recorded.\n\n## Step 2 — Normalise to E.164 first\n\nEverything downstream breaks on a badly parsed number. E.164 is `+`, country\ncalling code, national number — no spaces, punctuation, or trunk prefix.\n\nThe trap is the national trunk prefix. A UK number written `07700 900123` is\n`+447700900123`: the leading `0` is dropped, not kept. Italy keeps its leading\nzero for landlines. Guessing wrong shifts every subsequent lookup onto a\ndifferent subscriber.\n\nUse `libphonenumber` (Google's parsing library, with bindings for most\nlanguages) rather than a regex. It knows per-country trunk prefixes, valid\nlength ranges, and which prefix ranges are assignable, so it distinguishes a\nnumber that is well-formed from one that is actually possible in that country.\n\nFrom the normalised form, read off the **country calling code** (the country,\nnot the subscriber's location), the **national destination code** — area code or\nmobile prefix, giving the geographic region for landlines or the *originally\nallocated* operator for mobiles — and the **line type**: fixed, mobile, VoIP,\ntoll-free, premium, shared cost, or unknown. Line type is the most\ndecision-relevant field.\n\n`phoneinfoga` wraps normalisation, format generation and lookup scanners:\n\n```bash\nphoneinfoga scan -n \"+15551234567\"\n```\n\n**Done when** the E.164 form, country, national destination code, and line type\nare recorded.\n\n## Step 3 — Carrier, VoIP, and why both lie\n\nAn HLR query for a mobile number reaches the subscriber's home register and\nreturns the network the number is *currently* homed on, whether it is reachable,\nand often whether it is roaming. That is live data and the only carrier answer\nworth much. Everything else — prefix-to-carrier tables, most free lookup sites —\nmaps the number's original allocation block. **Portability breaks this.** A\nsubscriber keeps the number and changes networks; the allocation table still\nnames the original operator. So \"carrier: X\" from a prefix lookup means \"this\nblock was issued to X\", not \"this person is a customer of X\". Say which kind of\nlookup produced your answer, every time.\n\nThen classify VoIP. For fraud, trust-and-safety, and sockpuppet work this is\nusually the highest-signal finding in the whole skill: a number resolving to a\nvirtual-number provider rather than a mobile network operator was cheap,\ndisposable, obtainable without identity verification in many jurisdictions, and\npossibly one of hundreds held by the same party. Indicators are a VoIP line\ntype, an allocated operator that hosts numbers rather than serving consumers,\nand an area code unrelated to any other location evidence. Interpretation and\nthe per-app disclosure matrix:\n[reference\u002Fline-types.md](reference\u002Fline-types.md). A VoIP result is not proof\nof bad faith — most businesses use VoIP — but it does mean the number is a weak\nidentity anchor.\n\n**Done when** carrier is recorded with its lookup method and portability caveat,\nand the number is classed likely-SIM, likely-VoIP, or unknown.\n\n## Step 4 — Messaging-app disclosure\n\nContact discovery on messaging platforms reveals whether a number is registered\nand, depending on the user's privacy settings, a display name, an avatar, an\nabout line, and sometimes last-seen. It is genuinely informative — registration\nis a fact about a person, and an avatar pivots straight to\n`find-the-original-image`.\n\nIt is also **interactive and privacy-sensitive**. You are querying the platform\nabout a named individual, usually from an account, and contact-list sync uploads\nthat list to the platform. Most platforms restrict automated or bulk lookup. Do\nit only with explicit authorization, one number at a time, from an account and\ndevice managed under `investigate-without-getting-made`, and record it as an\ninteractive step. The reference above lists what each app exposes.\n\n**Done when** app presence is recorded, or marked not-attempted with the reason.\n\n## Step 5 — Search the number as a string, in every format\n\nThis is the highest-yield passive step and it is the one most often skipped.\nNumbers are written in a dozen conventions and search engines do not normalise\nbetween them. Search each format, quoted, with and without the country code:\n\n```\n\"+1 555 123 4567\"  \"+15551234567\"  \"(555) 123-4567\"  \"555-123-4567\"\n\"555.123.4567\"     \"555 123 4567\"  \"5551234567\"      \"001 555 123 4567\"\n```\n\nFull permutation guide, including national conventions and obfuscated forms:\n[reference\u002Fformat-permutations.md](reference\u002Fformat-permutations.md).\n\nRun these through `google-like-a-spy` across multiple engines — coverage of the\nsame number differs sharply between them — plus `find-leaks-in-the-wild`,\n`read-deleted-pages`, and `what-leaked-about-you`. Classified ads, business\ndirectories, resumes, and old forum signatures are where numbers live in public.\n\nCrowd-sourced caller-ID apps and reverse-lookup databases will also offer a\nname. Treat these as leads, never attribution: their name data comes from other\nusers' address books and submitted labels, so it inherits every mislabel, stale\ncontact, and deliberate poisoning. Spam scores are gameable, and many of these\nservices demand your own contacts as the price of entry.\n\n**Done when** every format has been searched across two engines and each\ncandidate name is recorded with its source, marked unverified.\n\n## Where this goes wrong\n\n- **Portability makes carrier data stale** silently: a confident wrong answer,\n  not an error. It also breaks area code as a location proxy, along with VoIP\n  allocation and people who kept a number through three moves.\n- **Recycling.** Disconnected numbers get reassigned. A number in an old breach\n  may belong to someone unconnected today — who may still be receiving the\n  previous owner's account-recovery codes.\n- **Caller-ID spoofing** is trivial, so a number on a call log is not evidence\n  its owner called. **SIM swap** transfers control while ownership records stay\n  unchanged: in fraud work the registered owner and the person receiving the SMS\n  may be different people, and that is the attack.\n- **Shared and business numbers.** One number, many people.\n- **Aggregator staleness.** Reverse-lookup data is copied between vendors and\n  rarely re-verified; two sites agreeing usually means one source.\n\n## Confidence grading\n\n- **Confirmed** — published by the subject on a source they control, or in an\n  authoritative record (filing, licence, registration) tied to the subject, or\n  two genuinely independent sources agree.\n- **Probable** — messaging-app registration with a display name consistent with\n  the subject, plus one corroborating public listing.\n- **Unconfirmed** — a name from a caller-ID or reverse-lookup service, an\n  aggregator record, or a single breach row, however confident the vendor's UI\n  looks.\n- **Rejected** — line type, allocation, or timeline contradicts the subject, or\n  it is a shared business line with no individual attribution possible.\n\nShow line type next to the grade — naming an owner for a VoIP number is always\nthe weaker claim.\n\n## Worked example\n\nGiven `07700 900123`, claimed to belong to a UK supplier contact. Normalised to\n`+447700900123`; libphonenumber classes the prefix as a mobile range. A prefix\nlookup names one operator, an HLR-based lookup a different one — the number was\nported. Record the current network, flag the prefix answer as historical.\n\nThe dead end: reverse-lookup sites return a name that does not match the\nsupplier contact, and two other services return the identical string. One source\nechoed three times, not corroboration. Dropped.\n\nSearching every written format via `google-like-a-spy` finds the number in a\ncached trade-directory listing under a company name, with a different registered\naddress than the invoices show. That company goes to `x-ray-a-company` and the\ndiscrepancy becomes the finding. Number attribution stays probable; the\ncorporate link is what gets reported.\n\n## Pivots\n\n| New selector | Skill |\n|---|---|\n| Owner name | `find-anyone` |\n| Business name from a listing | `x-ray-a-company`, `who-really-owns-it` |\n| Messaging-app avatar | `find-the-original-image` |\n| Display name or handle | `hunt-a-handle` |\n| Email alongside the number | `what-an-email-reveals` |\n| Number in breach records | `what-leaked-about-you` |\n| Number in pastes or channels | `find-leaks-in-the-wild`, `dig-through-data-brokers` |\n\n## Legal and ToS notes\n\nPhone lookup is more regulated than most OSINT. Several jurisdictions restrict\nwho may run reverse lookups and for what purpose, and consumer-reporting rules\nin some countries govern using this data for employment, tenancy, or credit\ndecisions regardless of how public the source was. Numbers are personal data\nunder GDPR and UK law, and contact-list uploads and automated app-registration\nchecks breach most platforms' terms. Using a number to locate a private\nindividual's home or to enable unconsented contact is out of bounds; the\nlegitimate uses are fraud work, due diligence, authorized skip tracing, and\nself-audit.\n\n## Step 6 — Report\n\nRun `write-the-intel-brief`. State the E.164 form, line type, carrier with\nlookup method and portability caveat, app presence with an interactive-step\nflag, and the owner attribution with its confidence grade and sources.\n\n**Done when** no carrier claim appears without its lookup method, and every\ninteractive check is labelled as one.\n","# Whose number is this\n\nA phone number is a strong selector: expensive to acquire, hard to change, and\nused as an account-recovery anchor almost everywhere. It is also the selector\ninvestigators get most wrong, because the metadata everyone quotes — the carrier\n— is frequently stale, and because a large share of numbers now belong to\nsoftware rather than to a SIM in someone's pocket. Do not call or text the\nsubject; that is contact, not research.\n\n## Step 1 — Authorized scope\n\nRead [..\u002F..\u002FETHICS.md](..\u002F..\u002FETHICS.md). Write down subject, objective,\nin-bounds selectors, out-of-bounds actions, and the governing jurisdiction —\nwhich matters more here than in most skills, because reverse phone lookup is\nspecifically regulated in many places. Decide now whether messaging-app\ncontact-discovery checks are authorized; they are interactive.\n\n**Done when** scope is written and the contact-discovery decision is recorded.\n\n## Step 2 — Normalise to E.164 first\n\nEverything downstream breaks on a badly parsed number. E.164 is `+`, country\ncalling code, national number — no spaces, punctuation, or trunk prefix.\n\nThe trap is the national trunk prefix. A UK number written `07700 900123` is\n`+447700900123`: the leading `0` is dropped, not kept. Italy keeps its leading\nzero for landlines. Guessing wrong shifts every subsequent lookup onto a\ndifferent subscriber.\n\nUse `libphonenumber` (Google's parsing library, with bindings for most\nlanguages) rather than a regex. It knows per-country trunk prefixes, valid\nlength ranges, and which prefix ranges are assignable, so it distinguishes a\nnumber that is well-formed from one that is actually possible in that country.\n\nFrom the normalised form, read off the **country calling code** (the country,\nnot the subscriber's location), the **national destination code** — area code or\nmobile prefix, giving the geographic region for landlines or the *originally\nallocated* operator for mobiles — and the **line type**: fixed, mobile, VoIP,\ntoll-free, premium, shared cost, or unknown. Line type is the most\ndecision-relevant field.\n\n`phoneinfoga` wraps normalisation, format generation and lookup scanners:\n\n```bash\nphoneinfoga scan -n \"+15551234567\"\n```\n\n**Done when** the E.164 form, country, national destination code, and line type\nare recorded.\n\n## Step 3 — Carrier, VoIP, and why both lie\n\nAn HLR query for a mobile number reaches the subscriber's home register and\nreturns the network the number is *currently* homed on, whether it is reachable,\nand often whether it is roaming. That is live data and the only carrier answer\nworth much. Everything else — prefix-to-carrier tables, most free lookup sites —\nmaps the number's original allocation block. **Portability breaks this.** A\nsubscriber keeps the number and changes networks; the allocation table still\nnames the original operator. So \"carrier: X\" from a prefix lookup means \"this\nblock was issued to X\", not \"this person is a customer of X\". Say which kind of\nlookup produced your answer, every time.\n\nThen classify VoIP. For fraud, trust-and-safety, and sockpuppet work this is\nusually the highest-signal finding in the whole skill: a number resolving to a\nvirtual-number provider rather than a mobile network operator was cheap,\ndisposable, obtainable without identity verification in many jurisdictions, and\npossibly one of hundreds held by the same party. Indicators are a VoIP line\ntype, an allocated operator that hosts numbers rather than serving consumers,\nand an area code unrelated to any other location evidence. Interpretation and\nthe per-app disclosure matrix:\n[reference\u002Fline-types.md](reference\u002Fline-types.md). A VoIP result is not proof\nof bad faith — most businesses use VoIP — but it does mean the number is a weak\nidentity anchor.\n\n**Done when** carrier is recorded with its lookup method and portability caveat,\nand the number is classed likely-SIM, likely-VoIP, or unknown.\n\n## Step 4 — Messaging-app disclosure\n\nContact discovery on messaging platforms reveals whether a number is registered\nand, depending on the user's privacy settings, a display name, an avatar, an\nabout line, and sometimes last-seen. It is genuinely informative — registration\nis a fact about a person, and an avatar pivots straight to\n`find-the-original-image`.\n\nIt is also **interactive and privacy-sensitive**. You are querying the platform\nabout a named individual, usually from an account, and contact-list sync uploads\nthat list to the platform. Most platforms restrict automated or bulk lookup. Do\nit only with explicit authorization, one number at a time, from an account and\ndevice managed under `investigate-without-getting-made`, and record it as an\ninteractive step. The reference above lists what each app exposes.\n\n**Done when** app presence is recorded, or marked not-attempted with the reason.\n\n## Step 5 — Search the number as a string, in every format\n\nThis is the highest-yield passive step and it is the one most often skipped.\nNumbers are written in a dozen conventions and search engines do not normalise\nbetween them. Search each format, quoted, with and without the country code:\n\n```\n\"+1 555 123 4567\"  \"+15551234567\"  \"(555) 123-4567\"  \"555-123-4567\"\n\"555.123.4567\"     \"555 123 4567\"  \"5551234567\"      \"001 555 123 4567\"\n```\n\nFull permutation guide, including national conventions and obfuscated forms:\n[reference\u002Fformat-permutations.md](reference\u002Fformat-permutations.md).\n\nRun these through `google-like-a-spy` across multiple engines — coverage of the\nsame number differs sharply between them — plus `find-leaks-in-the-wild`,\n`read-deleted-pages`, and `what-leaked-about-you`. Classified ads, business\ndirectories, resumes, and old forum signatures are where numbers live in public.\n\nCrowd-sourced caller-ID apps and reverse-lookup databases will also offer a\nname. Treat these as leads, never attribution: their name data comes from other\nusers' address books and submitted labels, so it inherits every mislabel, stale\ncontact, and deliberate poisoning. Spam scores are gameable, and many of these\nservices demand your own contacts as the price of entry.\n\n**Done when** every format has been searched across two engines and each\ncandidate name is recorded with its source, marked unverified.\n\n## Where this goes wrong\n\n- **Portability makes carrier data stale** silently: a confident wrong answer,\n  not an error. It also breaks area code as a location proxy, along with VoIP\n  allocation and people who kept a number through three moves.\n- **Recycling.** Disconnected numbers get reassigned. A number in an old breach\n  may belong to someone unconnected today — who may still be receiving the\n  previous owner's account-recovery codes.\n- **Caller-ID spoofing** is trivial, so a number on a call log is not evidence\n  its owner called. **SIM swap** transfers control while ownership records stay\n  unchanged: in fraud work the registered owner and the person receiving the SMS\n  may be different people, and that is the attack.\n- **Shared and business numbers.** One number, many people.\n- **Aggregator staleness.** Reverse-lookup data is copied between vendors and\n  rarely re-verified; two sites agreeing usually means one source.\n\n## Confidence grading\n\n- **Confirmed** — published by the subject on a source they control, or in an\n  authoritative record (filing, licence, registration) tied to the subject, or\n  two genuinely independent sources agree.\n- **Probable** — messaging-app registration with a display name consistent with\n  the subject, plus one corroborating public listing.\n- **Unconfirmed** — a name from a caller-ID or reverse-lookup service, an\n  aggregator record, or a single breach row, however confident the vendor's UI\n  looks.\n- **Rejected** — line type, allocation, or timeline contradicts the subject, or\n  it is a shared business line with no individual attribution possible.\n\nShow line type next to the grade — naming an owner for a VoIP number is always\nthe weaker claim.\n\n## Worked example\n\nGiven `07700 900123`, claimed to belong to a UK supplier contact. Normalised to\n`+447700900123`; libphonenumber classes the prefix as a mobile range. A prefix\nlookup names one operator, an HLR-based lookup a different one — the number was\nported. Record the current network, flag the prefix answer as historical.\n\nThe dead end: reverse-lookup sites return a name that does not match the\nsupplier contact, and two other services return the identical string. One source\nechoed three times, not corroboration. Dropped.\n\nSearching every written format via `google-like-a-spy` finds the number in a\ncached trade-directory listing under a company name, with a different registered\naddress than the invoices show. That company goes to `x-ray-a-company` and the\ndiscrepancy becomes the finding. Number attribution stays probable; the\ncorporate link is what gets reported.\n\n## Pivots\n\n| New selector | Skill |\n|---|---|\n| Owner name | `find-anyone` |\n| Business name from a listing | `x-ray-a-company`, `who-really-owns-it` |\n| Messaging-app avatar | `find-the-original-image` |\n| Display name or handle | `hunt-a-handle` |\n| Email alongside the number | `what-an-email-reveals` |\n| Number in breach records | `what-leaked-about-you` |\n| Number in pastes or channels | `find-leaks-in-the-wild`, `dig-through-data-brokers` |\n\n## Legal and ToS notes\n\nPhone lookup is more regulated than most OSINT. Several jurisdictions restrict\nwho may run reverse lookups and for what purpose, and consumer-reporting rules\nin some countries govern using this data for employment, tenancy, or credit\ndecisions regardless of how public the source was. Numbers are personal data\nunder GDPR and UK law, and contact-list uploads and automated app-registration\nchecks breach most platforms' terms. Using a number to locate a private\nindividual's home or to enable unconsented contact is out of bounds; the\nlegitimate uses are fraud work, due diligence, authorized skip tracing, and\nself-audit.\n\n## Step 6 — Report\n\nRun `write-the-intel-brief`. State the E.164 form, line type, carrier with\nlookup method and portability caveat, app presence with an interactive-step\nflag, and the owner attribution with its confidence grade and sources.\n\n**Done when** no carrier claim appears without its lookup method, and every\ninteractive check is labelled as one.\n",{"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92","agent\u002Fskills\u002Fwhose-number-is-this",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 whose-number-is-this",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill whose-number-is-this",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill whose-number-is-this","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fwhose-number-is-this\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"reference\u002Fformat-permutations.md","REFERENCE","参考文档",5245,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fwhose-number-is-this\u002Freference\u002Fformat-permutations.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"reference\u002Fline-types.md",5393,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fwhose-number-is-this\u002Freference\u002Fline-types.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",[],[]]