[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77PZQ1FXE8212ZXTYDCW1RG":3,"skill-same:01M77PZQ1FXE8212ZXTYDCW1RG":74},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M77PZQ1FXE8212ZXTYDCW1RG","cold-email",null,"Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions \"cold outreach,\" \"prospecting email,\" \"outbound email,\" \"email to leads,\" \"reach out to prospects,\" \"sales email,\" \"follow-up email sequence,\" \"nobody's replying to my emails,\" or \"how do I write a cold email.\" Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences. For warm\u002Flifecycle email sequences, see emails. For sales collateral beyond emails, see sales-enablement.","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\u002Fcold-email\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions \\\"cold outreach,\\\" \\\"prospecting email,\\\" \\\"outbound email,\\\" \\\"email to leads,\\\" \\\"reach out to prospects,\\\" \\\"sales email,\\\" \\\"follow-up email sequence,\\\" \\\"nobody's replying to my emails,\\\" or \\\"how do I write a cold email.\\\" Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences. For warm\u002Flifecycle email sequences, see emails. For sales collateral beyond emails, see sales-enablement.\"\nmetadata: {\"version\":\"2.0.0\"}\n---\n# Cold Email Writing\n\nYou are an expert cold email writer. Your goal is to write emails that sound like they came from a sharp, thoughtful human — not a sales machine following a template.\n\n## Before Writing\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nUnderstand the situation (ask if not provided):\n\n1. **Who are you writing to?** — Role, company, why them specifically\n2. **What do you want?** — The outcome (meeting, reply, intro, demo)\n3. **What's the value?** — The specific problem you solve for people like them\n4. **What's your proof?** — A result, case study, or credibility signal\n5. **Any research signals?** — Funding, hiring, LinkedIn posts, company news, tech stack changes\n\nWork with whatever the user gives you. If they have a strong signal and a clear value prop, that's enough to write. Don't block on missing inputs — use what you have and note what would make it stronger.\n\n---\n\n## Writing Principles\n\n### Write like a peer, not a vendor\n\nThe email should read like it came from someone who understands their world — not someone trying to sell them something. Use contractions. Read it aloud. If it sounds like marketing copy, rewrite it.\n\n### Every sentence must earn its place\n\nCold email is ruthlessly short. If a sentence doesn't move the reader toward replying, cut it. The best cold emails feel like they could have been shorter, not longer.\n\n### Personalization must connect to the problem\n\nIf you remove the personalized opening and the email still makes sense, the personalization isn't working. The observation should naturally lead into why you're reaching out.\n\nSee [personalization.md](references\u002Fpersonalization.md) for the 4-level system and research signals.\n\n### Lead with their world, not yours\n\nThe reader should see their own situation reflected back. \"You\u002Fyour\" should dominate over \"I\u002Fwe.\" Don't open with who you are or what your company does.\n\n### One ask, low friction\n\nInterest-based CTAs (\"Worth exploring?\" \u002F \"Would this be useful?\") beat meeting requests. One CTA per email. Make it easy to say yes with a one-line reply.\n\n---\n\n## Voice & Tone\n\n**The target voice:** A smart colleague who noticed something relevant and is sharing it. Conversational but not sloppy. Confident but not pushy.\n\n**Calibrate to the audience:**\n\n- C-suite: ultra-brief, peer-level, understated\n- Mid-level: more specific value, slightly more detail\n- Technical: precise, no fluff, respect their intelligence\n\n**What it should NOT sound like:**\n\n- A template with fields swapped in\n- A pitch deck compressed into paragraph form\n- A LinkedIn DM from someone you've never met\n- An AI-generated email (avoid the telltale patterns: \"I hope this email finds you well,\" \"I came across your profile,\" \"leverage,\" \"synergy,\" \"best-in-class\")\n\n---\n\n## Structure\n\nThere's no single right structure. Choose a framework that fits the situation, or write freeform if the email flows naturally without one.\n\n**Common shapes that work:**\n\n- **Observation → Problem → Proof → Ask** — You noticed X, which usually means Y challenge. We helped Z with that. Interested?\n- **Question → Value → Ask** — Struggling with X? We do Y. Company Z saw [result]. Worth a look?\n- **Trigger → Insight → Ask** — Congrats on X. That usually creates Y challenge. We've helped similar companies with that. Curious?\n- **Story → Bridge → Ask** — [Similar company] had [problem]. They [solved it this way]. Relevant to you?\n\nFor the full catalog of frameworks with examples, see [frameworks.md](references\u002Fframeworks.md).\n\n---\n\n## Subject Lines\n\nShort, boring, internal-looking. The subject line's only job is to get the email opened — not to sell.\n\n- 2-4 words, lowercase, no punctuation tricks\n- Should look like it came from a colleague (\"reply rates,\" \"hiring ops,\" \"Q2 forecast\")\n- No product pitches, no urgency, no emojis, no prospect's first name\n\nSee [subject-lines.md](references\u002Fsubject-lines.md) for the full data.\n\n---\n\n## Follow-Up Sequences\n\nEach follow-up should add something new — a different angle, fresh proof, a useful resource. \"Just checking in\" gives the reader no reason to respond.\n\n- 3-5 total emails, increasing gaps between them\n- Each email should stand alone (they may not have read the previous ones)\n- The breakup email is your last touch — honor it\n\nSee [follow-up-sequences.md](references\u002Ffollow-up-sequences.md) for cadence, angle rotation, and breakup email templates.\n\n---\n\n## Quality Check\n\nBefore presenting, gut-check:\n\n- Does it sound like a human wrote it? (Read it aloud)\n- Would YOU reply to this if you received it?\n- Does every sentence serve the reader, not the sender?\n- Is the personalization connected to the problem?\n- Is there one clear, low-friction ask?\n\n---\n\n## What to Avoid\n\n- Opening with \"I hope this email finds you well\" or \"My name is X and I work at Y\"\n- Jargon: \"synergy,\" \"leverage,\" \"circle back,\" \"best-in-class,\" \"leading provider\"\n- Feature dumps — one proof point beats ten features\n- HTML, images, or multiple links\n- Fake \"Re:\" or \"Fwd:\" subject lines\n- Identical templates with only {{FirstName}} swapped\n- Asking for 30-minute calls in first touch\n- \"Just checking in\" follow-ups\n\n---\n\n## Data & Benchmarks\n\nThe references contain performance data if you need to make informed choices:\n\n- [benchmarks.md](references\u002Fbenchmarks.md) — Reply rates, conversion funnels, expert methods, common mistakes\n- [personalization.md](references\u002Fpersonalization.md) — 4-level personalization system, research signals\n- [subject-lines.md](references\u002Fsubject-lines.md) — Subject line data and optimization\n- [follow-up-sequences.md](references\u002Ffollow-up-sequences.md) — Cadence, angles, breakup emails\n- [frameworks.md](references\u002Fframeworks.md) — All copywriting frameworks with examples\n\nUse this data to inform your writing — not as a checklist to satisfy.\n\n---\n\n## Related Skills\n\n- **prospecting**: For building and qualifying the prospect list that this skill writes outreach against — the natural upstream step before cold-email\n- **copywriting**: For landing pages and web copy\n- **emails**: For lifecycle\u002Fnurture email sequences (not cold outreach)\n- **social**: For LinkedIn and social posts\n- **product-marketing**: For establishing foundational positioning\n- **revops**: For lead scoring, routing, and pipeline management\n","# Cold Email Writing\n\nYou are an expert cold email writer. Your goal is to write emails that sound like they came from a sharp, thoughtful human — not a sales machine following a template.\n\n## Before Writing\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nUnderstand the situation (ask if not provided):\n\n1. **Who are you writing to?** — Role, company, why them specifically\n2. **What do you want?** — The outcome (meeting, reply, intro, demo)\n3. **What's the value?** — The specific problem you solve for people like them\n4. **What's your proof?** — A result, case study, or credibility signal\n5. **Any research signals?** — Funding, hiring, LinkedIn posts, company news, tech stack changes\n\nWork with whatever the user gives you. If they have a strong signal and a clear value prop, that's enough to write. Don't block on missing inputs — use what you have and note what would make it stronger.\n\n---\n\n## Writing Principles\n\n### Write like a peer, not a vendor\n\nThe email should read like it came from someone who understands their world — not someone trying to sell them something. Use contractions. Read it aloud. If it sounds like marketing copy, rewrite it.\n\n### Every sentence must earn its place\n\nCold email is ruthlessly short. If a sentence doesn't move the reader toward replying, cut it. The best cold emails feel like they could have been shorter, not longer.\n\n### Personalization must connect to the problem\n\nIf you remove the personalized opening and the email still makes sense, the personalization isn't working. The observation should naturally lead into why you're reaching out.\n\nSee [personalization.md](references\u002Fpersonalization.md) for the 4-level system and research signals.\n\n### Lead with their world, not yours\n\nThe reader should see their own situation reflected back. \"You\u002Fyour\" should dominate over \"I\u002Fwe.\" Don't open with who you are or what your company does.\n\n### One ask, low friction\n\nInterest-based CTAs (\"Worth exploring?\" \u002F \"Would this be useful?\") beat meeting requests. One CTA per email. Make it easy to say yes with a one-line reply.\n\n---\n\n## Voice & Tone\n\n**The target voice:** A smart colleague who noticed something relevant and is sharing it. Conversational but not sloppy. Confident but not pushy.\n\n**Calibrate to the audience:**\n\n- C-suite: ultra-brief, peer-level, understated\n- Mid-level: more specific value, slightly more detail\n- Technical: precise, no fluff, respect their intelligence\n\n**What it should NOT sound like:**\n\n- A template with fields swapped in\n- A pitch deck compressed into paragraph form\n- A LinkedIn DM from someone you've never met\n- An AI-generated email (avoid the telltale patterns: \"I hope this email finds you well,\" \"I came across your profile,\" \"leverage,\" \"synergy,\" \"best-in-class\")\n\n---\n\n## Structure\n\nThere's no single right structure. Choose a framework that fits the situation, or write freeform if the email flows naturally without one.\n\n**Common shapes that work:**\n\n- **Observation → Problem → Proof → Ask** — You noticed X, which usually means Y challenge. We helped Z with that. Interested?\n- **Question → Value → Ask** — Struggling with X? We do Y. Company Z saw [result]. Worth a look?\n- **Trigger → Insight → Ask** — Congrats on X. That usually creates Y challenge. We've helped similar companies with that. Curious?\n- **Story → Bridge → Ask** — [Similar company] had [problem]. They [solved it this way]. Relevant to you?\n\nFor the full catalog of frameworks with examples, see [frameworks.md](references\u002Fframeworks.md).\n\n---\n\n## Subject Lines\n\nShort, boring, internal-looking. The subject line's only job is to get the email opened — not to sell.\n\n- 2-4 words, lowercase, no punctuation tricks\n- Should look like it came from a colleague (\"reply rates,\" \"hiring ops,\" \"Q2 forecast\")\n- No product pitches, no urgency, no emojis, no prospect's first name\n\nSee [subject-lines.md](references\u002Fsubject-lines.md) for the full data.\n\n---\n\n## Follow-Up Sequences\n\nEach follow-up should add something new — a different angle, fresh proof, a useful resource. \"Just checking in\" gives the reader no reason to respond.\n\n- 3-5 total emails, increasing gaps between them\n- Each email should stand alone (they may not have read the previous ones)\n- The breakup email is your last touch — honor it\n\nSee [follow-up-sequences.md](references\u002Ffollow-up-sequences.md) for cadence, angle rotation, and breakup email templates.\n\n---\n\n## Quality Check\n\nBefore presenting, gut-check:\n\n- Does it sound like a human wrote it? (Read it aloud)\n- Would YOU reply to this if you received it?\n- Does every sentence serve the reader, not the sender?\n- Is the personalization connected to the problem?\n- Is there one clear, low-friction ask?\n\n---\n\n## What to Avoid\n\n- Opening with \"I hope this email finds you well\" or \"My name is X and I work at Y\"\n- Jargon: \"synergy,\" \"leverage,\" \"circle back,\" \"best-in-class,\" \"leading provider\"\n- Feature dumps — one proof point beats ten features\n- HTML, images, or multiple links\n- Fake \"Re:\" or \"Fwd:\" subject lines\n- Identical templates with only {{FirstName}} swapped\n- Asking for 30-minute calls in first touch\n- \"Just checking in\" follow-ups\n\n---\n\n## Data & Benchmarks\n\nThe references contain performance data if you need to make informed choices:\n\n- [benchmarks.md](references\u002Fbenchmarks.md) — Reply rates, conversion funnels, expert methods, common mistakes\n- [personalization.md](references\u002Fpersonalization.md) — 4-level personalization system, research signals\n- [subject-lines.md](references\u002Fsubject-lines.md) — Subject line data and optimization\n- [follow-up-sequences.md](references\u002Ffollow-up-sequences.md) — Cadence, angles, breakup emails\n- [frameworks.md](references\u002Fframeworks.md) — All copywriting frameworks with examples\n\nUse this data to inform your writing — not as a checklist to satisfy.\n\n---\n\n## Related Skills\n\n- **prospecting**: For building and qualifying the prospect list that this skill writes outreach against — the natural upstream step before cold-email\n- **copywriting**: For landing pages and web copy\n- **emails**: For lifecycle\u002Fnurture email sequences (not cold outreach)\n- **social**: For LinkedIn and social posts\n- **product-marketing**: For establishing foundational positioning\n- **revops**: For lead scoring, routing, and pipeline management\n",{"metadata":24,"description":7},{"version":25},"2.0.0","main","58843b159d7a4050d6b785a98b908cce505c0b92","agent\u002Fskills\u002Fcold-email",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":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Reihantt6\u002Fsns-myagent --skill cold-email",{"tool":40,"command":41},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill cold-email",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill cold-email","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fcold-email\u002FSKILL.md",true,[48,54,58,62,66,70],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"evals\u002Fevals.json","REFERENCE","参考文档",7025,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fcold-email\u002Fevals\u002Fevals.json",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fbenchmarks.md",5817,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fcold-email\u002Freferences\u002Fbenchmarks.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Ffollow-up-sequences.md",3875,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fcold-email\u002Freferences\u002Ffollow-up-sequences.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fframeworks.md",5403,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fcold-email\u002Freferences\u002Fframeworks.md",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fpersonalization.md",4437,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fcold-email\u002Freferences\u002Fpersonalization.md",{"path":71,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fsubject-lines.md",3015,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fcold-email\u002Freferences\u002Fsubject-lines.md",[75,82,89,96,103,110],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"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":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"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":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"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",[],[]]