[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MGRARDNADW598YG89XYFQG":3,"skill-same:01M6MGRARDNADW598YG89XYFQG":115},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":63,"ownerHtmlUrl":64,"ownerBlogUrl":65,"ownerDescription":66,"updatedAt":67,"install":68,"resources":80},"01M6MGRARDNADW598YG89XYFQG","shots",null,"Generate, revise, translate, and manage App Store marketing screenshots and app icon candidates through the hosted Shots MCP tools. Use for App Store screenshot creation, app icon generation, ASO screenshot strategy, screenshot revisions, localization, App Store listing scraping, and public App Store screenshot inspiration. Do not use for generic image generation.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FhitSlop\u002Fshots\u002Fskills\u002Fshots\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"scraping","listing","app store","locale","icon generation","URL","app","localization","revise","creation","MCP","node","aso","marketing","Bash","Tools","screenshot","generate","translate","image","2026-11-10 10:12:30",false,"---\nname: shots\nversion: 0.1.0\ndescription: >\n  Generate, revise, translate, and manage App Store marketing screenshots and\n  app icon candidates through the hosted Shots MCP tools. Use for App Store\n  screenshot creation, app icon generation, ASO screenshot strategy,\n  screenshot revisions, localization, App Store listing scraping, and public\n  App Store screenshot inspiration. Do not use for generic image generation.\nuser-invocable: true\nargument-hint: \"[app store url, job id, locale, or description]\"\nauthor:\n  name: hitSlop\n  url: https:\u002F\u002Fhitslop.com\nlicense: MIT\nallowed-tools:\n  - Bash(node *)\n---\n\n# Shots\n\nShots runs through hosted MCP tools. Durable state lives in Convex, generated\nscreenshots and icons are uploaded to the Shots CDN, and completed jobs return\nCDN URLs plus stable ids.\n\nThe hosted MCP server instructions are the source of truth for tool names,\narguments, billing recovery, polling cadence, app setup, and review URLs. Use\n`help.schema`, `help.examples`, and `help.search` before guessing command args.\n\n## Use The References\n\n- Create screenshot campaigns: [reference\u002Fcreate.md](reference\u002Fcreate.md)\n- Write screenshot prompts: [reference\u002Fprompting.md](reference\u002Fprompting.md)\n- Visual inspiration and style examples: [reference\u002Finspiration.md](reference\u002Finspiration.md)\n- Research positioning and ASO copy: [reference\u002Fstrategy.md](reference\u002Fstrategy.md)\n- Generate app icons: [reference\u002Ficons.md](reference\u002Ficons.md)\n- Revise screenshots: [reference\u002Frevise.md](reference\u002Frevise.md)\n- Translate screenshots: [reference\u002Ftranslate.md](reference\u002Ftranslate.md)\n- Lookup App Store listings: [reference\u002Fscrape.md](reference\u002Fscrape.md)\n\n## Intent Router\n\n| Intent | Use |\n| --- | --- |\n| Create screenshots | Resolve the app, gather references, use `reference\u002Fcreate.md`, then call `generate_screenshot` once per approved panel. |\n| Use another app as inspiration | Treat the other App Store URL as public gallery inspiration, not the user's app. Use `gallery.ensure_app` \u002F `gallery.get_app`, then pass `galleryInspirationScreenshotId`. |\n| App icons | Use `reference\u002Ficons.md`, start with `generate_icon_moodboard`, then generate individual finals with `generate_icon`. |\n| Revise | For small targeted changes to an existing screenshot, use `screenshots.revise` with precise feedback about what changes and what stays fixed. |\n| Translate\u002Flocalize | Use `screenshots.translate`; preserve the campaign system unless the user asks for locale-specific repositioning. |\n| Promote listing screenshots | Use `screenshots.promote` \u002F `screenshots.unpromote` with only the screenshot `mediaId`; Shots derives app, locale, and platform from the media record. |\n| Listing\u002FASO copy | Use `reference\u002Fstrategy.md`; save durable listing copy with `apps.update_listing` and research with `apps.update_research`. |\n| Account or billing | Use `usage.get` or `billing`; always ask before spending money. |\n\n## Local Project Rules\n\n- The user's app repo is the source of product truth. The Shots plugin files are\n  only tool documentation; never infer the target app identity from them.\n- For a new app record, the agent must know the app name, what it does, App\n  Store URL if published, and target platform before calling `apps.upsert` or\n  `apps.import`.\n- Inspect local files, saved app context, and existing media before asking the\n  user, but do not guess when ambiguity changes the product or creative\n  direction. Ask for missing positioning, audience, real UI truth, style\n  preferences, or approval when needed.\n- Before screenshot generation, require at least one real app UI reference:\n  uploaded `app_screenshot`, a `reference` image showing actual app UI, or\n  scraped App Store screenshots. An icon, palette, or written description alone\n  is not enough.\n- If the user provides local image files, or you discover useful local\n  screenshots\u002Fassets in the repo, upload them first and use the returned media\n  IDs. Do not put local paths in the prompt and assume the image model can see\n  them.\n- Codex\u002Flocal-agent screenshot generation is explicit-reference-first. Inspect\n  available media, choose the exact references for each panel, pass them as\n  `referenceMediaIds`, and describe each reference's job in the prompt. Do not\n  rely on Studio\u002Fbackend default reference selection for quality; that fallback\n  exists for non-agent UI flows.\n- For unpublished apps, inspect local screens, navigation, theme tokens, preview\n  fixtures, docs, and screenshots. Save durable findings to the app record so\n  Studio and future sessions share the same context.\n- Before generating a screenshot set, present a markdown table with one row per\n  screenshot and wait for approval or edits.\n- Do not choose a public gallery app as inspiration from a vague request like\n  \"try a new style\" or \"different style.\" Use gallery inspiration only when the\n  user names\u002Fprovides an inspiration source or explicitly approves the exact\n  gallery app\u002Fscreenshot in the plan. Gallery-inspiration generation should\n  stay on medium quality.\n- If the user asks for a new or different style without specifics, ask for\n  style preferences or propose 2-4 concrete directions and get approval before\n  generating.\n- If the user asks for a small change to an existing generated screenshot, skip\n  a new campaign plan and use `screenshots.revise` instead.\n\n## Local Upload Helper\n\nUse `media.import_url` for HTTPS images. For local files, use the bundled helper:\n\n```bash\nnode \u003Cplugin-root>\u002Fscripts\u002Fupload-asset.mjs --file .\u002Fpath\u002Fto\u002Fimage.png --app-id \u003CappId> --kind reference\n```\n\nResolve `\u003Cplugin-root>` as the plugin root directory. From this `SKILL.md`, the\nhelper is at `..\u002F..\u002Fscripts\u002Fupload-asset.mjs`.\n\nUseful `kind` values:\n\n- `app_screenshot` for real product UI\n- `icon` for the app icon\n- `inspo` for user-provided mood references\n- `reference` for general brand or product references\n\nThe helper calls `POST https:\u002F\u002Fshots.run\u002Fapi\u002Fupload` by default. The endpoint is\nintentionally open and unauthenticated; it only needs `appId` and enforces\nserver-side upload safety checks. Do not skip local uploads because R2 or cloud\ncredentials are unavailable.\n\nIf an upload fails, stop and call `feedback.report` with `category: \"bug\"`,\nthe HTTP status or error message in `details`, and `relatedTool: \"upload-asset\"`\nplus the `appId`. Do not generate while treating a required local reference as\nunavailable unless the user explicitly approves continuing without it.\n\n## App Icon Discovery\n\nIf the user gives an App Store URL or app id, prefer `apps.import`; it imports\nthe public icon and saves it as an app icon asset.\n\nIf there is no App Store URL, inspect the local app repo and upload the best\nsource icon with `--kind icon`:\n\n- iOS\u002FXcode: `*.xcassets\u002FAppIcon.appiconset\u002FContents.json`, then referenced PNGs\n- Expo: `app.json`, `app.config.*`, `expo.icon`, `ios.icon`, `android.icon`\n- React Native: iOS app icon sets and Android `mipmap-*` assets\n- Web\u002FPWA fallback: `public\u002Fmanifest.json`, `public\u002Ficon.png`, favicons\n\n## Quality Bar\n\n- Screenshots are ads, not documentation. Each panel needs a user-facing promise\n  and a specific UI moment that proves it.\n- Use real UI facts in prompts: screen names, layout, visible data, controls,\n  states, and emotional payload.\n- Treat visible product UI as closed-world. Critical user direction overrides\n  references; otherwise preserve reference UI and never invent plausible rows,\n  controls, labels, values, or states the references do not show.\n- Keep references selective. Pass only the images that a specific screenshot\n  actually needs.\n- Prefer selected\u002Fpromoted App Store screenshots for product and campaign\n  continuity when they are relevant. Do not pass recent unpromoted generations\n  as references unless the user selects them or asks to continue from them.\n- Do not request fake App Store chrome, gutters, dividers, rounded screenshot\n  borders, or fictional product UI.\n\n## Feedback Reporting\n\nUse `feedback.report` to notify the Shots team about product feedback, feature\nideas, unsupported workflows, confusing behavior, user frustration or delight,\nrepeated generation or revision quality issues, and tool or infrastructure errors.\n\nReport when:\n\n- The user directly says something is broken, confusing, annoying, useful, or\n  delightful.\n- The user asks for a workflow Shots does not support, such as bulk applying one\n  revision to a whole set.\n- You infer a feature idea from the user's goal or repeated workaround.\n- A generated or revised screenshot still looks wrong after multiple tries.\n- Billing, authentication, setup, upload, or gallery inspiration behavior\n  confuses the user.\n- Any MCP tool call returns an unexpected error, including HTTP errors from the\n  upload helper, `isError: true` responses from Shots commands, or other\n  infrastructure failures. Use `category: \"bug\"` with `severity: \"high\"`,\n  include the error message or HTTP status in `details`, and set `relatedTool`\n  or `relatedCommand` to identify the failing operation.\n\nInclude any relevant `appId`, `mediaId`, `jobId`, `relatedTool`, or\n`relatedCommand`. Use a short `userQuote` when the user's exact words matter,\nand concise `agentContext` for what you observed or tried.\n\nAfter reporting a derived idea or issue, briefly tell the user you notified the\nShots team. Do not imply this creates a support ticket, guaranteed fix, or\npersonal follow-up.\n","# Shots\n\nShots runs through hosted MCP tools. Durable state lives in Convex, generated\nscreenshots and icons are uploaded to the Shots CDN, and completed jobs return\nCDN URLs plus stable ids.\n\nThe hosted MCP server instructions are the source of truth for tool names,\narguments, billing recovery, polling cadence, app setup, and review URLs. Use\n`help.schema`, `help.examples`, and `help.search` before guessing command args.\n\n## Use The References\n\n- Create screenshot campaigns: [reference\u002Fcreate.md](reference\u002Fcreate.md)\n- Write screenshot prompts: [reference\u002Fprompting.md](reference\u002Fprompting.md)\n- Visual inspiration and style examples: [reference\u002Finspiration.md](reference\u002Finspiration.md)\n- Research positioning and ASO copy: [reference\u002Fstrategy.md](reference\u002Fstrategy.md)\n- Generate app icons: [reference\u002Ficons.md](reference\u002Ficons.md)\n- Revise screenshots: [reference\u002Frevise.md](reference\u002Frevise.md)\n- Translate screenshots: [reference\u002Ftranslate.md](reference\u002Ftranslate.md)\n- Lookup App Store listings: [reference\u002Fscrape.md](reference\u002Fscrape.md)\n\n## Intent Router\n\n| Intent | Use |\n| --- | --- |\n| Create screenshots | Resolve the app, gather references, use `reference\u002Fcreate.md`, then call `generate_screenshot` once per approved panel. |\n| Use another app as inspiration | Treat the other App Store URL as public gallery inspiration, not the user's app. Use `gallery.ensure_app` \u002F `gallery.get_app`, then pass `galleryInspirationScreenshotId`. |\n| App icons | Use `reference\u002Ficons.md`, start with `generate_icon_moodboard`, then generate individual finals with `generate_icon`. |\n| Revise | For small targeted changes to an existing screenshot, use `screenshots.revise` with precise feedback about what changes and what stays fixed. |\n| Translate\u002Flocalize | Use `screenshots.translate`; preserve the campaign system unless the user asks for locale-specific repositioning. |\n| Promote listing screenshots | Use `screenshots.promote` \u002F `screenshots.unpromote` with only the screenshot `mediaId`; Shots derives app, locale, and platform from the media record. |\n| Listing\u002FASO copy | Use `reference\u002Fstrategy.md`; save durable listing copy with `apps.update_listing` and research with `apps.update_research`. |\n| Account or billing | Use `usage.get` or `billing`; always ask before spending money. |\n\n## Local Project Rules\n\n- The user's app repo is the source of product truth. The Shots plugin files are\n  only tool documentation; never infer the target app identity from them.\n- For a new app record, the agent must know the app name, what it does, App\n  Store URL if published, and target platform before calling `apps.upsert` or\n  `apps.import`.\n- Inspect local files, saved app context, and existing media before asking the\n  user, but do not guess when ambiguity changes the product or creative\n  direction. Ask for missing positioning, audience, real UI truth, style\n  preferences, or approval when needed.\n- Before screenshot generation, require at least one real app UI reference:\n  uploaded `app_screenshot`, a `reference` image showing actual app UI, or\n  scraped App Store screenshots. An icon, palette, or written description alone\n  is not enough.\n- If the user provides local image files, or you discover useful local\n  screenshots\u002Fassets in the repo, upload them first and use the returned media\n  IDs. Do not put local paths in the prompt and assume the image model can see\n  them.\n- Codex\u002Flocal-agent screenshot generation is explicit-reference-first. Inspect\n  available media, choose the exact references for each panel, pass them as\n  `referenceMediaIds`, and describe each reference's job in the prompt. Do not\n  rely on Studio\u002Fbackend default reference selection for quality; that fallback\n  exists for non-agent UI flows.\n- For unpublished apps, inspect local screens, navigation, theme tokens, preview\n  fixtures, docs, and screenshots. Save durable findings to the app record so\n  Studio and future sessions share the same context.\n- Before generating a screenshot set, present a markdown table with one row per\n  screenshot and wait for approval or edits.\n- Do not choose a public gallery app as inspiration from a vague request like\n  \"try a new style\" or \"different style.\" Use gallery inspiration only when the\n  user names\u002Fprovides an inspiration source or explicitly approves the exact\n  gallery app\u002Fscreenshot in the plan. Gallery-inspiration generation should\n  stay on medium quality.\n- If the user asks for a new or different style without specifics, ask for\n  style preferences or propose 2-4 concrete directions and get approval before\n  generating.\n- If the user asks for a small change to an existing generated screenshot, skip\n  a new campaign plan and use `screenshots.revise` instead.\n\n## Local Upload Helper\n\nUse `media.import_url` for HTTPS images. For local files, use the bundled helper:\n\n```bash\nnode \u003Cplugin-root>\u002Fscripts\u002Fupload-asset.mjs --file .\u002Fpath\u002Fto\u002Fimage.png --app-id \u003CappId> --kind reference\n```\n\nResolve `\u003Cplugin-root>` as the plugin root directory. From this `SKILL.md`, the\nhelper is at `..\u002F..\u002Fscripts\u002Fupload-asset.mjs`.\n\nUseful `kind` values:\n\n- `app_screenshot` for real product UI\n- `icon` for the app icon\n- `inspo` for user-provided mood references\n- `reference` for general brand or product references\n\nThe helper calls `POST https:\u002F\u002Fshots.run\u002Fapi\u002Fupload` by default. The endpoint is\nintentionally open and unauthenticated; it only needs `appId` and enforces\nserver-side upload safety checks. Do not skip local uploads because R2 or cloud\ncredentials are unavailable.\n\nIf an upload fails, stop and call `feedback.report` with `category: \"bug\"`,\nthe HTTP status or error message in `details`, and `relatedTool: \"upload-asset\"`\nplus the `appId`. Do not generate while treating a required local reference as\nunavailable unless the user explicitly approves continuing without it.\n\n## App Icon Discovery\n\nIf the user gives an App Store URL or app id, prefer `apps.import`; it imports\nthe public icon and saves it as an app icon asset.\n\nIf there is no App Store URL, inspect the local app repo and upload the best\nsource icon with `--kind icon`:\n\n- iOS\u002FXcode: `*.xcassets\u002FAppIcon.appiconset\u002FContents.json`, then referenced PNGs\n- Expo: `app.json`, `app.config.*`, `expo.icon`, `ios.icon`, `android.icon`\n- React Native: iOS app icon sets and Android `mipmap-*` assets\n- Web\u002FPWA fallback: `public\u002Fmanifest.json`, `public\u002Ficon.png`, favicons\n\n## Quality Bar\n\n- Screenshots are ads, not documentation. Each panel needs a user-facing promise\n  and a specific UI moment that proves it.\n- Use real UI facts in prompts: screen names, layout, visible data, controls,\n  states, and emotional payload.\n- Treat visible product UI as closed-world. Critical user direction overrides\n  references; otherwise preserve reference UI and never invent plausible rows,\n  controls, labels, values, or states the references do not show.\n- Keep references selective. Pass only the images that a specific screenshot\n  actually needs.\n- Prefer selected\u002Fpromoted App Store screenshots for product and campaign\n  continuity when they are relevant. Do not pass recent unpromoted generations\n  as references unless the user selects them or asks to continue from them.\n- Do not request fake App Store chrome, gutters, dividers, rounded screenshot\n  borders, or fictional product UI.\n\n## Feedback Reporting\n\nUse `feedback.report` to notify the Shots team about product feedback, feature\nideas, unsupported workflows, confusing behavior, user frustration or delight,\nrepeated generation or revision quality issues, and tool or infrastructure errors.\n\nReport when:\n\n- The user directly says something is broken, confusing, annoying, useful, or\n  delightful.\n- The user asks for a workflow Shots does not support, such as bulk applying one\n  revision to a whole set.\n- You infer a feature idea from the user's goal or repeated workaround.\n- A generated or revised screenshot still looks wrong after multiple tries.\n- Billing, authentication, setup, upload, or gallery inspiration behavior\n  confuses the user.\n- Any MCP tool call returns an unexpected error, including HTTP errors from the\n  upload helper, `isError: true` responses from Shots commands, or other\n  infrastructure failures. Use `category: \"bug\"` with `severity: \"high\"`,\n  include the error message or HTTP status in `details`, and set `relatedTool`\n  or `relatedCommand` to identify the failing operation.\n\nInclude any relevant `appId`, `mediaId`, `jobId`, `relatedTool`, or\n`relatedCommand`. Use a short `userQuote` when the user's exact words matter,\nand concise `agentContext` for what you observed or tried.\n\nAfter reporting a derived idea or issue, briefly tell the user you notified the\nShots team. Do not imply this creates a support ticket, guaranteed fix, or\npersonal follow-up.\n",{"name":5,"author":49,"license":15,"version":52,"description":53,"allowed-tools":54,"argument-hint":56,"user-invocable":57},{"url":50,"name":51},"https:\u002F\u002Fhitslop.com","hitSlop","0.1.0","Generate, revise, translate, and manage App Store marketing screenshots and app icon candidates through the hosted Shots MCP tools. Use for App Store screenshot creation, app icon generation, ASO screenshot strategy, screenshot revisions, localization, App Store listing scraping, and public App Store screenshot inspiration. Do not use for generic image generation.\n",[55],"Bash(node *)","[app store url, job id, locale, or description]",true,"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FhitSlop\u002Fshots\u002Fskills\u002Fshots",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":57},[70,73,76],{"tool":71,"command":72},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill shots",{"tool":74,"command":75},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill shots",{"tool":77,"command":78},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill shots","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FhitSlop\u002Fshots\u002Fskills\u002Fshots\u002FSKILL.md",[81,87,91,95,99,103,107,111],{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"reference\u002Fcreate.md","REFERENCE","参考文档",9808,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FhitSlop\u002Fshots\u002Fskills\u002Fshots\u002Freference\u002Fcreate.md",{"path":88,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":89,"sourceHtmlUrl":90},"reference\u002Ficons.md",8645,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FhitSlop\u002Fshots\u002Fskills\u002Fshots\u002Freference\u002Ficons.md",{"path":92,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":93,"sourceHtmlUrl":94},"reference\u002Finspiration.md",25459,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FhitSlop\u002Fshots\u002Fskills\u002Fshots\u002Freference\u002Finspiration.md",{"path":96,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":97,"sourceHtmlUrl":98},"reference\u002Fprompting.md",27047,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FhitSlop\u002Fshots\u002Fskills\u002Fshots\u002Freference\u002Fprompting.md",{"path":100,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":101,"sourceHtmlUrl":102},"reference\u002Frevise.md",1747,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FhitSlop\u002Fshots\u002Fskills\u002Fshots\u002Freference\u002Frevise.md",{"path":104,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":105,"sourceHtmlUrl":106},"reference\u002Fscrape.md",906,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FhitSlop\u002Fshots\u002Fskills\u002Fshots\u002Freference\u002Fscrape.md",{"path":108,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":109,"sourceHtmlUrl":110},"reference\u002Fstrategy.md",6076,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FhitSlop\u002Fshots\u002Fskills\u002Fshots\u002Freference\u002Fstrategy.md",{"path":112,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":113,"sourceHtmlUrl":114},"reference\u002Ftranslate.md",910,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FhitSlop\u002Fshots\u002Fskills\u002Fshots\u002Freference\u002Ftranslate.md",[116,125,133,141,149,157],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":120,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":124},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":129,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":124},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":137,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":124},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":145,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":124},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":153,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":124},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":161,"sourceHtmlUrl":162,"categories":163,"keywords":164,"publishedAt":124},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]