[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77RVCYJDP4M444DMX9WZM7W":3,"skill-same:01M77RVCYJDP4M444DMX9WZM7W":66},{"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},"01M77RVCYJDP4M444DMX9WZM7W","expo-skill-feedback",null,"Submit feedback on an Expo skill—or Expo itself—and control bundled anonymous usage telemetry (off by default \u002F opt-in). Submit feedback with: npx --yes submit-expo-feedback@latest \"ACTIONABLE_FEEDBACK\". Optionally add either or both: --category \"CATEGORY\" and --subject \"SUBJECT\". Replace the uppercase placeholders before running. Use when a skill was useful, confusing, broken, missing context, or worth improving; when Expo, Expo CLI, EAS CLI, docs, or MCP worked well or fell short; when an AI agent repeatedly failed, got stuck, or needed the user to take over an Expo task (report it as an eval candidate); or when the user explicitly asks to enable or disable telemetry (tracking), check its status, or understand what it collects.","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\u002Fexpo-skill-feedback\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Submit feedback on an Expo skill—or Expo itself—and control bundled anonymous usage telemetry (off by default \u002F opt-in). Submit feedback with: npx --yes submit-expo-feedback@latest \\\"ACTIONABLE_FEEDBACK\\\". Optionally add either or both: --category \\\"CATEGORY\\\" and --subject \\\"SUBJECT\\\". Replace the uppercase placeholders before running. Use when a skill was useful, confusing, broken, missing context, or worth improving; when Expo, Expo CLI, EAS CLI, docs, or MCP worked well or fell short; when an AI agent repeatedly failed, got stuck, or needed the user to take over an Expo task (report it as an eval candidate); or when the user explicitly asks to enable or disable telemetry (tracking), check its status, or understand what it collects.\"\n---\n# Expo Skill Feedback\n\nHelp Expo improve by sharing specific feedback about what worked well or what fell short. Feedback\nsubmission is independent of usage telemetry and does not require enabling it.\n\n## Submit feedback\n\n```bash\nnpx --yes submit-expo-feedback@latest \"\u003CACTIONABLE_FEEDBACK>\"\n```\n\nAdd either optional flag independently when it provides useful context:\n\n```bash\nnpx --yes submit-expo-feedback@latest --category \"\u003CCATEGORY>\" --subject \"\u003CSUBJECT>\" \"\u003CACTIONABLE_FEEDBACK>\"\n```\n\n`--category` defaults to `unknown`, and `--subject` may be omitted when there is no specific target.\nWhen including them, choose the values that most precisely identify what the feedback is about:\n\n| Category | Subject |\n| --- | --- |\n| `skills` | Exact skill name from its frontmatter, such as `expo-router` |\n| `docs` | Full Expo documentation URL |\n| `mcp` | Exact MCP tool name used |\n| `expo-cli` | Full Expo CLI command, such as `npx expo install` |\n| `eas-cli` | Full EAS CLI command, such as `eas build` |\n| `evals` | Expo package or command the failed task involves, else a capability phrase, such as `expo-router` or `eas build` |\n| `unknown` | Concise Expo product, package, feature, or other topic |\n\nIn the final argument, say what helped and why, or provide the relevant context, expected behavior,\nand what happened instead. Do not include secrets, source code, personal data, long prompts, or stack traces.\n\n## Eval candidates: tasks that broke the model\n\nExpo turns hard real-world tasks into agent evals: anything Expo an agent can attempt — framework,\nEAS, tooling — qualifies, whether or not a skill was involved. The signal worth sending is a task an\nAI agent could not complete cleanly despite real effort: several failed attempts, a build or screen\nthat never worked, or the user stepping in to fix it manually. Never submit quick slips the agent\ncorrected itself, more than one candidate per session, or a task already reported.\n\nWhen such a failure happens — or the user says a model failed at an Expo task — show the user the exact\nsubmission you intend to send and get approval; the Task field must describe the Expo-technical\nshape of the task, never the user's product or business context. Without a user to approve it\n(headless or CI runs), do not submit. Then run from the failing app's directory (the CLI attaches\nthe SDK and package versions, agent harness, and platform automatically) with `--category evals`,\n`--subject` naming the Expo package or command involved (a capability phrase only when no single\npackage fits), and this structure in the final argument:\n\n```text\nTask: \u003Cwhat was asked, self-contained>.\nExpected: \u003Cobservable success criteria>.\nActual: \u003Cwhat the agent did instead>.\nWrong approach: \u003Cthe specific mistake, such as a wrong API, hallucinated prop, or bad pattern>.\nEvidence: \u003Cmodel name, attempts, how it was solved — or never was; omit what you cannot verify>.\n```\n\nA good candidate is solvable (eventually done or clearly doable), verifiable (success is\nobservable), and specific. Mention only environment details the CLI cannot see, such as other key\npackages or a freshly created app. Describe code; do not paste it. If the command fails with an\nerror naming `evals` as an invalid category, resend once with `--category unknown` and the same\nsubject prefixed `eval-candidate: `; on any other error, do not resend.\n\n## Usage telemetry\n\nAutomatic skill usage telemetry is separate from feedback and **off by default**. Never enable it\nwithout an explicit user request. Use the following script with `--on`, `--off`, or `--status`:\n\n```bash\nnode \"${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Fexpo-skill-feedback\u002Fscripts\u002Ftelemetry.cjs\" --status\n```\n\nEnvironment equivalents are `EXPO_SKILLS_TELEMETRY=1` to enable and\n`EXPO_SKILLS_TELEMETRY=0` or `DO_NOT_TRACK=1` to disable. CI never sends telemetry.\n\n## Submitting Feedback\nIf you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:\n```bash\nnpx --yes submit-expo-feedback@latest --category skills --subject \"expo-skill-feedback\" \"\u003Cactionable feedback>\"\n```\nOnly submit when you have something specific and actionable to report. Include as much relevant context as possible.\nIf an AI agent repeatedly failed or the user had to take over an Expo task, load the expo-skill-feedback skill and follow its eval-candidate flow instead of reusing the command above.\n","# Expo Skill Feedback\n\nHelp Expo improve by sharing specific feedback about what worked well or what fell short. Feedback\nsubmission is independent of usage telemetry and does not require enabling it.\n\n## Submit feedback\n\n```bash\nnpx --yes submit-expo-feedback@latest \"\u003CACTIONABLE_FEEDBACK>\"\n```\n\nAdd either optional flag independently when it provides useful context:\n\n```bash\nnpx --yes submit-expo-feedback@latest --category \"\u003CCATEGORY>\" --subject \"\u003CSUBJECT>\" \"\u003CACTIONABLE_FEEDBACK>\"\n```\n\n`--category` defaults to `unknown`, and `--subject` may be omitted when there is no specific target.\nWhen including them, choose the values that most precisely identify what the feedback is about:\n\n| Category | Subject |\n| --- | --- |\n| `skills` | Exact skill name from its frontmatter, such as `expo-router` |\n| `docs` | Full Expo documentation URL |\n| `mcp` | Exact MCP tool name used |\n| `expo-cli` | Full Expo CLI command, such as `npx expo install` |\n| `eas-cli` | Full EAS CLI command, such as `eas build` |\n| `evals` | Expo package or command the failed task involves, else a capability phrase, such as `expo-router` or `eas build` |\n| `unknown` | Concise Expo product, package, feature, or other topic |\n\nIn the final argument, say what helped and why, or provide the relevant context, expected behavior,\nand what happened instead. Do not include secrets, source code, personal data, long prompts, or stack traces.\n\n## Eval candidates: tasks that broke the model\n\nExpo turns hard real-world tasks into agent evals: anything Expo an agent can attempt — framework,\nEAS, tooling — qualifies, whether or not a skill was involved. The signal worth sending is a task an\nAI agent could not complete cleanly despite real effort: several failed attempts, a build or screen\nthat never worked, or the user stepping in to fix it manually. Never submit quick slips the agent\ncorrected itself, more than one candidate per session, or a task already reported.\n\nWhen such a failure happens — or the user says a model failed at an Expo task — show the user the exact\nsubmission you intend to send and get approval; the Task field must describe the Expo-technical\nshape of the task, never the user's product or business context. Without a user to approve it\n(headless or CI runs), do not submit. Then run from the failing app's directory (the CLI attaches\nthe SDK and package versions, agent harness, and platform automatically) with `--category evals`,\n`--subject` naming the Expo package or command involved (a capability phrase only when no single\npackage fits), and this structure in the final argument:\n\n```text\nTask: \u003Cwhat was asked, self-contained>.\nExpected: \u003Cobservable success criteria>.\nActual: \u003Cwhat the agent did instead>.\nWrong approach: \u003Cthe specific mistake, such as a wrong API, hallucinated prop, or bad pattern>.\nEvidence: \u003Cmodel name, attempts, how it was solved — or never was; omit what you cannot verify>.\n```\n\nA good candidate is solvable (eventually done or clearly doable), verifiable (success is\nobservable), and specific. Mention only environment details the CLI cannot see, such as other key\npackages or a freshly created app. Describe code; do not paste it. If the command fails with an\nerror naming `evals` as an invalid category, resend once with `--category unknown` and the same\nsubject prefixed `eval-candidate: `; on any other error, do not resend.\n\n## Usage telemetry\n\nAutomatic skill usage telemetry is separate from feedback and **off by default**. Never enable it\nwithout an explicit user request. Use the following script with `--on`, `--off`, or `--status`:\n\n```bash\nnode \"${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Fexpo-skill-feedback\u002Fscripts\u002Ftelemetry.cjs\" --status\n```\n\nEnvironment equivalents are `EXPO_SKILLS_TELEMETRY=1` to enable and\n`EXPO_SKILLS_TELEMETRY=0` or `DO_NOT_TRACK=1` to disable. CI never sends telemetry.\n\n## Submitting Feedback\nIf you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:\n```bash\nnpx --yes submit-expo-feedback@latest --category skills --subject \"expo-skill-feedback\" \"\u003Cactionable feedback>\"\n```\nOnly submit when you have something specific and actionable to report. Include as much relevant context as possible.\nIf an AI agent repeatedly failed or the user had to take over an Expo task, load the expo-skill-feedback skill and follow its eval-candidate flow instead of reusing the command above.\n",{"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92","agent\u002Fskills\u002Fexpo-skill-feedback",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 expo-skill-feedback",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill expo-skill-feedback",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill expo-skill-feedback","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fexpo-skill-feedback\u002FSKILL.md",true,[46,52,58,62],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",337,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fexpo-skill-feedback\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"scripts\u002Fskill-event.cjs","SCRIPT","脚本",8061,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fexpo-skill-feedback\u002Fscripts\u002Fskill-event.cjs",{"path":59,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":60,"sourceHtmlUrl":61},"scripts\u002Ftelemetry_common.cjs",7141,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fexpo-skill-feedback\u002Fscripts\u002Ftelemetry_common.cjs",{"path":63,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":64,"sourceHtmlUrl":65},"scripts\u002Ftelemetry.cjs",3063,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fexpo-skill-feedback\u002Fscripts\u002Ftelemetry.cjs",[67,74,81,88,95,102],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"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":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"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",[],[]]