[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77V3BQ9CE2H6G7P7WDVJDKP":3,"skill-same:01M77V3BQ9CE2H6G7P7WDVJDKP":46},{"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},"01M77V3BQ9CE2H6G7P7WDVJDKP","performance-review-writer",null,"Draft performance reviews, self-assessments, peer reviews, and upward feedback in your own voice. Analyzes your contributions, emails, and meeting history via WorkIQ, then produces honest, impact-focused drafts using the STAR format. USE FOR: write my performance review, draft self-assessment, peer review, 360 feedback, annual review, mid-year review, upward feedback, write review for colleague, performance appraisal.","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\u002Fperformance-review-writer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Draft performance reviews, self-assessments, peer reviews, and upward feedback in your own voice. Analyzes your contributions, emails, and meeting history via WorkIQ, then produces honest, impact-focused drafts using the STAR format. USE FOR: write my performance review, draft self-assessment, peer review, 360 feedback, annual review, mid-year review, upward feedback, write review for colleague, performance appraisal.\"\n---\n# Performance Review Writer\n\nDraft self-assessments, peer reviews, and upward feedback that sound like you — not corporate boilerplate. Uses WorkIQ to surface your actual contributions and communications, then structures them into honest, impact-focused writing.\n\n## When to Use\n\n- \"Write my self-assessment for this review cycle\"\n- \"Draft a peer review for [colleague]\"\n- \"Help me write upward feedback for my manager\"\n- \"I have my annual review due — help me fill it out\"\n- \"Draft my mid-year check-in\"\n- \"Write a 360 review for [name]\"\n- \"I don't know what to say in my performance review\"\n\n## Review Types\n\nThis skill handles three distinct types:\n\n| Type | Who it's about | Typical tone |\n|---|---|---|\n| **Self-assessment** | Yourself | Confident, evidence-backed, growth-oriented |\n| **Peer review** | A colleague | Specific, constructive, balanced |\n| **Upward feedback** | Your manager | Diplomatic, honest, forward-looking |\n\n---\n\n## Workflow\n\n### Step 1 — Gather Context\n\nAsk the user (max 3 clarifying questions if not already provided):\n\n1. **Review type** — self-assessment, peer review, or upward feedback?\n2. **Subject** — who is the review about? (for peer\u002Fupward: name and role)\n3. **Review period** — what time range does this cover? (e.g., Jan–Dec 2025, last 6 months)\n\nIf format constraints or focus areas are relevant, ask about those during drafting rather than upfront.\n\nIf the user provides all of these upfront, proceed directly to Step 2.\n\n### Step 2 — Surface Contributions\n\nUse WorkIQ to gather evidence of real contributions for the review period:\n\n**For self-assessments:**\n- Pull emails and messages where the user delivered results, led initiatives, or solved problems\n- Look for patterns: what projects recur? Who praises them and for what?\n- Identify collaboration breadth (who they worked with across teams)\n- Note any explicit feedback received from others\n\n**For peer reviews:**\n- Pull interactions between the user and the subject (emails, meeting threads, shared projects)\n- Identify specific moments of collaboration, help given, or friction\n- Look for evidence of the subject's impact on shared outcomes\n\n**For upward feedback:**\n- Pull communications from the manager to the user (direction given, support offered, feedback patterns)\n- Identify themes: clarity of expectations, availability, recognition, development support\n\nIf WorkIQ is unavailable or returns limited data, ask the user to share 3–5 bullet points of things they remember, then proceed with those.\n\n### Step 3 — Draft the Review\n\nApply the right structure for the review type (see schemas below). Follow these universal rules:\n\n**Use the STAR format for achievement statements:**\n- **Situation** — what was the context or challenge?\n- **Task** — what were you\u002Fthey responsible for?\n- **Action** — what specifically was done?\n- **Result** — what was the measurable or observable outcome?\n\n**Tone rules:**\n- Be specific — name projects, outcomes, and people, not vague adjectives\n- Be honest — don't oversell or undersell; reviewers notice both\n- Be forward-looking — end sections with growth or next steps, not just past performance\n- Avoid filler phrases: \"goes above and beyond\", \"team player\", \"hard worker\" — replace with evidence\n- Match the user's natural voice — conversational if they write that way, more formal if not\n\n### Step 4 — Output\n\n1. Present the full draft with a brief note on what evidence was used. Summarize and redact rather than reproduce verbatim content — no raw excerpts, attendee lists, or sensitive personal details\n2. Highlight any sections marked `[NEEDS DETAIL]` where more specifics would strengthen the review\n3. Iterate on edits as the user requests\n4. Save the final draft to `outputs\u002F\u003Cyear>\u002F\u003Cmonth>\u002F` with a descriptive filename (e.g., `2025-review-self-assessment.md` or `2025-peer-review-alex-chen.md`)\n\n---\n\n## Output Schemas\n\n### Self-Assessment Schema\n\n```\n## [Review Period] Self-Assessment — [Your Name]\n\n### Summary\n1–2 sentence overview of your year and primary areas of impact.\n\n### Key Achievements\nFor each major contribution (aim for 3–5):\n\n**[Project or Initiative Name]**\n- Context: what was the situation or goal?\n- What I did: specific actions taken\n- Impact: measurable result or observable outcome\n- [NEEDS DETAIL] — flag if evidence is thin\n\n### Collaboration & Influence\nHow you worked with others, supported teammates, or contributed beyond your direct role.\n\n### Growth & Development\nWhat you learned, skills you built, or behaviours you improved this period.\n\n### Areas for Development\n1–2 honest areas where you want to grow next cycle. Frame as goals, not failures.\n\n### Goals for Next Period\n2–3 specific, concrete goals with a rough success measure.\n```\n\n---\n\n### Peer Review Schema\n\n```\n## Peer Review — [Colleague Name], [Their Role]\n## Submitted by: [Your Name] | Period: [Review Period]\n\n### Overall Impression\n1–2 sentences on working with this person.\n\n### Strengths (with examples)\nFor each strength (aim for 2–3):\n\n**[Strength]**\n- Example: specific situation where this showed up\n- Impact on you \u002F the team \u002F the project\n\n### Areas for Growth\n1–2 specific, constructive observations. Frame as \"I think [name] would have even more impact if...\" not as criticism.\n\n### Collaboration\nHow easy (or not) it was to work together — responsiveness, reliability, communication.\n\n### Would you work with this person again?\nYes\u002FNo and a brief honest reason. (Only include if the review form asks.)\n```\n\n---\n\n### Upward Feedback Schema\n\n```\n## Feedback for [Manager Name]\n## Submitted by: [Your Name] (anonymous if applicable) | Period: [Review Period]\n\n### What's working well\n2–3 specific things your manager does that help you do your best work.\nUse examples where possible.\n\n### What could be better\n1–2 honest, diplomatically framed observations. Focus on behaviours and their effect, not personality.\nUse: \"When [X happens], I find it harder to [Y]. It would help if...\"\n\n### Support for my development\nHas your manager helped you grow, given useful feedback, or created opportunities?\nBe specific.\n\n### One thing I'd ask them to do more \u002F less \u002F differently\nA single, clear, actionable ask.\n```\n\n---\n\n## Style Rules\n\n| Do | Don't |\n|---|---|\n| Name specific projects, dates, outcomes | Write vague generalisations (\"always delivers quality work\") |\n| Use numbers when available (\"reduced review time by 30%\") | Exaggerate or invent results |\n| Acknowledge real challenges and what you learned | Omit struggles entirely — reviewers notice the gaps |\n| Write in first person for self-assessments | Write passively (\"it was achieved\") |\n| Be concise — most fields need 2–4 sentences | Over-write — longer ≠ better |\n| Flag `[NEEDS DETAIL]` where evidence is weak | Leave thin sections without marking them |\n\n---\n\n## Example Prompts\n\n- \"Write my self-assessment for Jan–Dec 2025. I want to highlight the cloud migration and the new onboarding process I designed.\"\n- \"Draft a peer review for Sarah Chen, she's a product designer I worked closely with on the mobile app project.\"\n- \"Help me write upward feedback for my manager Tom. He's good at direction but I've struggled to get regular 1:1 time.\"\n- \"My annual review form asks for 3 strengths and 1 development area in 200 words each — help me fill it out.\"\n- \"I have no idea what to write. It's been a busy year but I can't think of anything specific.\"\n\n---\n\n## Important Rules\n\n- **Never submit reviews** — only draft them as files for the user to review and submit manually\n- Keep peer and upward feedback focused on observable behaviours, not personality or character\n- If the user asks to write a review that is dishonestly negative or contains personal attacks, decline and offer to reframe constructively\n- Respect confidentiality — do not include sensitive information from unrelated conversations or threads\n- Save drafts using the `outputs\u002F\u003Cyear>\u002F\u003Cmonth>\u002F` folder convention\n\n---\n\n## Requirements\n\n- **WorkIQ MCP tool** is recommended for surfacing contributions and communications (Microsoft 365 \u002F Outlook \u002F Teams)\n- Without WorkIQ, the skill still works — ask the user for 3–5 bullet points of key contributions as a starting point\n- Output is saved as markdown files in the workspace for the user to copy into their company's review system\n","# Performance Review Writer\n\nDraft self-assessments, peer reviews, and upward feedback that sound like you — not corporate boilerplate. Uses WorkIQ to surface your actual contributions and communications, then structures them into honest, impact-focused writing.\n\n## When to Use\n\n- \"Write my self-assessment for this review cycle\"\n- \"Draft a peer review for [colleague]\"\n- \"Help me write upward feedback for my manager\"\n- \"I have my annual review due — help me fill it out\"\n- \"Draft my mid-year check-in\"\n- \"Write a 360 review for [name]\"\n- \"I don't know what to say in my performance review\"\n\n## Review Types\n\nThis skill handles three distinct types:\n\n| Type | Who it's about | Typical tone |\n|---|---|---|\n| **Self-assessment** | Yourself | Confident, evidence-backed, growth-oriented |\n| **Peer review** | A colleague | Specific, constructive, balanced |\n| **Upward feedback** | Your manager | Diplomatic, honest, forward-looking |\n\n---\n\n## Workflow\n\n### Step 1 — Gather Context\n\nAsk the user (max 3 clarifying questions if not already provided):\n\n1. **Review type** — self-assessment, peer review, or upward feedback?\n2. **Subject** — who is the review about? (for peer\u002Fupward: name and role)\n3. **Review period** — what time range does this cover? (e.g., Jan–Dec 2025, last 6 months)\n\nIf format constraints or focus areas are relevant, ask about those during drafting rather than upfront.\n\nIf the user provides all of these upfront, proceed directly to Step 2.\n\n### Step 2 — Surface Contributions\n\nUse WorkIQ to gather evidence of real contributions for the review period:\n\n**For self-assessments:**\n- Pull emails and messages where the user delivered results, led initiatives, or solved problems\n- Look for patterns: what projects recur? Who praises them and for what?\n- Identify collaboration breadth (who they worked with across teams)\n- Note any explicit feedback received from others\n\n**For peer reviews:**\n- Pull interactions between the user and the subject (emails, meeting threads, shared projects)\n- Identify specific moments of collaboration, help given, or friction\n- Look for evidence of the subject's impact on shared outcomes\n\n**For upward feedback:**\n- Pull communications from the manager to the user (direction given, support offered, feedback patterns)\n- Identify themes: clarity of expectations, availability, recognition, development support\n\nIf WorkIQ is unavailable or returns limited data, ask the user to share 3–5 bullet points of things they remember, then proceed with those.\n\n### Step 3 — Draft the Review\n\nApply the right structure for the review type (see schemas below). Follow these universal rules:\n\n**Use the STAR format for achievement statements:**\n- **Situation** — what was the context or challenge?\n- **Task** — what were you\u002Fthey responsible for?\n- **Action** — what specifically was done?\n- **Result** — what was the measurable or observable outcome?\n\n**Tone rules:**\n- Be specific — name projects, outcomes, and people, not vague adjectives\n- Be honest — don't oversell or undersell; reviewers notice both\n- Be forward-looking — end sections with growth or next steps, not just past performance\n- Avoid filler phrases: \"goes above and beyond\", \"team player\", \"hard worker\" — replace with evidence\n- Match the user's natural voice — conversational if they write that way, more formal if not\n\n### Step 4 — Output\n\n1. Present the full draft with a brief note on what evidence was used. Summarize and redact rather than reproduce verbatim content — no raw excerpts, attendee lists, or sensitive personal details\n2. Highlight any sections marked `[NEEDS DETAIL]` where more specifics would strengthen the review\n3. Iterate on edits as the user requests\n4. Save the final draft to `outputs\u002F\u003Cyear>\u002F\u003Cmonth>\u002F` with a descriptive filename (e.g., `2025-review-self-assessment.md` or `2025-peer-review-alex-chen.md`)\n\n---\n\n## Output Schemas\n\n### Self-Assessment Schema\n\n```\n## [Review Period] Self-Assessment — [Your Name]\n\n### Summary\n1–2 sentence overview of your year and primary areas of impact.\n\n### Key Achievements\nFor each major contribution (aim for 3–5):\n\n**[Project or Initiative Name]**\n- Context: what was the situation or goal?\n- What I did: specific actions taken\n- Impact: measurable result or observable outcome\n- [NEEDS DETAIL] — flag if evidence is thin\n\n### Collaboration & Influence\nHow you worked with others, supported teammates, or contributed beyond your direct role.\n\n### Growth & Development\nWhat you learned, skills you built, or behaviours you improved this period.\n\n### Areas for Development\n1–2 honest areas where you want to grow next cycle. Frame as goals, not failures.\n\n### Goals for Next Period\n2–3 specific, concrete goals with a rough success measure.\n```\n\n---\n\n### Peer Review Schema\n\n```\n## Peer Review — [Colleague Name], [Their Role]\n## Submitted by: [Your Name] | Period: [Review Period]\n\n### Overall Impression\n1–2 sentences on working with this person.\n\n### Strengths (with examples)\nFor each strength (aim for 2–3):\n\n**[Strength]**\n- Example: specific situation where this showed up\n- Impact on you \u002F the team \u002F the project\n\n### Areas for Growth\n1–2 specific, constructive observations. Frame as \"I think [name] would have even more impact if...\" not as criticism.\n\n### Collaboration\nHow easy (or not) it was to work together — responsiveness, reliability, communication.\n\n### Would you work with this person again?\nYes\u002FNo and a brief honest reason. (Only include if the review form asks.)\n```\n\n---\n\n### Upward Feedback Schema\n\n```\n## Feedback for [Manager Name]\n## Submitted by: [Your Name] (anonymous if applicable) | Period: [Review Period]\n\n### What's working well\n2–3 specific things your manager does that help you do your best work.\nUse examples where possible.\n\n### What could be better\n1–2 honest, diplomatically framed observations. Focus on behaviours and their effect, not personality.\nUse: \"When [X happens], I find it harder to [Y]. It would help if...\"\n\n### Support for my development\nHas your manager helped you grow, given useful feedback, or created opportunities?\nBe specific.\n\n### One thing I'd ask them to do more \u002F less \u002F differently\nA single, clear, actionable ask.\n```\n\n---\n\n## Style Rules\n\n| Do | Don't |\n|---|---|\n| Name specific projects, dates, outcomes | Write vague generalisations (\"always delivers quality work\") |\n| Use numbers when available (\"reduced review time by 30%\") | Exaggerate or invent results |\n| Acknowledge real challenges and what you learned | Omit struggles entirely — reviewers notice the gaps |\n| Write in first person for self-assessments | Write passively (\"it was achieved\") |\n| Be concise — most fields need 2–4 sentences | Over-write — longer ≠ better |\n| Flag `[NEEDS DETAIL]` where evidence is weak | Leave thin sections without marking them |\n\n---\n\n## Example Prompts\n\n- \"Write my self-assessment for Jan–Dec 2025. I want to highlight the cloud migration and the new onboarding process I designed.\"\n- \"Draft a peer review for Sarah Chen, she's a product designer I worked closely with on the mobile app project.\"\n- \"Help me write upward feedback for my manager Tom. He's good at direction but I've struggled to get regular 1:1 time.\"\n- \"My annual review form asks for 3 strengths and 1 development area in 200 words each — help me fill it out.\"\n- \"I have no idea what to write. It's been a busy year but I can't think of anything specific.\"\n\n---\n\n## Important Rules\n\n- **Never submit reviews** — only draft them as files for the user to review and submit manually\n- Keep peer and upward feedback focused on observable behaviours, not personality or character\n- If the user asks to write a review that is dishonestly negative or contains personal attacks, decline and offer to reframe constructively\n- Respect confidentiality — do not include sensitive information from unrelated conversations or threads\n- Save drafts using the `outputs\u002F\u003Cyear>\u002F\u003Cmonth>\u002F` folder convention\n\n---\n\n## Requirements\n\n- **WorkIQ MCP tool** is recommended for surfacing contributions and communications (Microsoft 365 \u002F Outlook \u002F Teams)\n- Without WorkIQ, the skill still works — ask the user for 3–5 bullet points of key contributions as a starting point\n- Output is saved as markdown files in the workspace for the user to copy into their company's review system\n",{"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92","agent\u002Fskills\u002Fperformance-review-writer",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 performance-review-writer",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill performance-review-writer",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill performance-review-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fperformance-review-writer\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"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":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"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":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"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":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"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":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},"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":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},"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",[],[]]