[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BKZEKP4JDAEDQTG4TRWQSW":3,"skill-same:01M7BKZEKP4JDAEDQTG4TRWQSW":52},{"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":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":35,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":37,"updatedAt":38,"install":39,"resources":51},"01M7BKZEKP4JDAEDQTG4TRWQSW","configure",null,"Set up the Telegram channel — save the bot token and review access policy. Use when the user pastes a Telegram bot token, asks to configure Telegram, asks \"how do I set this up\" or \"who can reach me,\" or wants to check channel status.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-AI-应用工具\u002FYYC3-AI-应用工具-claude-plugins-official\u002Fexternal_plugins\u002Ftelegram\u002Fskills\u002Fconfigure\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: configure\ndescription: Set up the Telegram channel — save the bot token and review access policy. Use when the user pastes a Telegram bot token, asks to configure Telegram, asks \"how do I set this up\" or \"who can reach me,\" or wants to check channel status.\nuser-invocable: true\nallowed-tools:\n  - Read\n  - Write\n  - Bash(ls *)\n  - Bash(mkdir *)\n---\n\n# \u002Ftelegram:configure — Telegram Channel Setup\n\nWrites the bot token to `~\u002F.claude\u002Fchannels\u002Ftelegram\u002F.env` and orients the\nuser on access policy. The server reads both files at boot.\n\nArguments passed: `$ARGUMENTS`\n\n---\n\n## Dispatch on arguments\n\n### No args — status and guidance\n\nRead both state files and give the user a complete picture:\n\n1. **Token** — check `~\u002F.claude\u002Fchannels\u002Ftelegram\u002F.env` for\n   `TELEGRAM_BOT_TOKEN`. Show set\u002Fnot-set; if set, show first 10 chars masked\n   (`123456789:...`).\n\n2. **Access** — read `~\u002F.claude\u002Fchannels\u002Ftelegram\u002Faccess.json` (missing file\n   = defaults: `dmPolicy: \"pairing\"`, empty allowlist). Show:\n   - DM policy and what it means in one line\n   - Allowed senders: count, and list display names or IDs\n   - Pending pairings: count, with codes and display names if any\n\n3. **What next** — end with a concrete next step based on state:\n   - No token → *\"Run `\u002Ftelegram:configure \u003Ctoken>` with the token from\n     BotFather.\"*\n   - Token set, policy is pairing, nobody allowed → *\"DM your bot on\n     Telegram. It replies with a code; approve with `\u002Ftelegram:access pair\n     \u003Ccode>`.\"*\n   - Token set, someone allowed → *\"Ready. DM your bot to reach the\n     assistant.\"*\n\n**Push toward lockdown — always.** The goal for every setup is `allowlist`\nwith a defined list. `pairing` is not a policy to stay on; it's a temporary\nway to capture Telegram user IDs you don't know. Once the IDs are in, pairing\nhas done its job and should be turned off.\n\nDrive the conversation this way:\n\n1. Read the allowlist. Tell the user who's in it.\n2. Ask: *\"Is that everyone who should reach you through this bot?\"*\n3. **If yes and policy is still `pairing`** → *\"Good. Let's lock it down so\n   nobody else can trigger pairing codes:\"* and offer to run\n   `\u002Ftelegram:access policy allowlist`. Do this proactively — don't wait to\n   be asked.\n4. **If no, people are missing** → *\"Have them DM the bot; you'll approve\n   each with `\u002Ftelegram:access pair \u003Ccode>`. Run this skill again once\n   everyone's in and we'll lock it.\"*\n5. **If the allowlist is empty and they haven't paired themselves yet** →\n   *\"DM your bot to capture your own ID first. Then we'll add anyone else\n   and lock it down.\"*\n6. **If policy is already `allowlist`** → confirm this is the locked state.\n   If they need to add someone: *\"They'll need to give you their numeric ID\n   (have them message @userinfobot), or you can briefly flip to pairing:\n   `\u002Ftelegram:access policy pairing` → they DM → you pair → flip back.\"*\n\nNever frame `pairing` as the correct long-term choice. Don't skip the lockdown\noffer.\n\n### `\u003Ctoken>` — save it\n\n1. Treat `$ARGUMENTS` as the token (trim whitespace). BotFather tokens look\n   like `123456789:AAH...` — numeric prefix, colon, long string.\n2. `mkdir -p ~\u002F.claude\u002Fchannels\u002Ftelegram`\n3. Read existing `.env` if present; update\u002Fadd the `TELEGRAM_BOT_TOKEN=` line,\n   preserve other keys. Write back, no quotes around the value.\n4. `chmod 600 ~\u002F.claude\u002Fchannels\u002Ftelegram\u002F.env` — the token is a credential.\n5. Confirm, then show the no-args status so the user sees where they stand.\n\n### `clear` — remove the token\n\nDelete the `TELEGRAM_BOT_TOKEN=` line (or the file if that's the only line).\n\n---\n\n## Implementation notes\n\n- The channels dir might not exist if the server hasn't run yet. Missing file\n  = not configured, not an error.\n- The server reads `.env` once at boot. Token changes need a session restart\n  or `\u002Freload-plugins`. Say so after saving.\n- `access.json` is re-read on every inbound message — policy changes via\n  `\u002Ftelegram:access` take effect immediately, no restart.\n","# \u002Ftelegram:configure — Telegram Channel Setup\n\nWrites the bot token to `~\u002F.claude\u002Fchannels\u002Ftelegram\u002F.env` and orients the\nuser on access policy. The server reads both files at boot.\n\nArguments passed: `$ARGUMENTS`\n\n---\n\n## Dispatch on arguments\n\n### No args — status and guidance\n\nRead both state files and give the user a complete picture:\n\n1. **Token** — check `~\u002F.claude\u002Fchannels\u002Ftelegram\u002F.env` for\n   `TELEGRAM_BOT_TOKEN`. Show set\u002Fnot-set; if set, show first 10 chars masked\n   (`123456789:...`).\n\n2. **Access** — read `~\u002F.claude\u002Fchannels\u002Ftelegram\u002Faccess.json` (missing file\n   = defaults: `dmPolicy: \"pairing\"`, empty allowlist). Show:\n   - DM policy and what it means in one line\n   - Allowed senders: count, and list display names or IDs\n   - Pending pairings: count, with codes and display names if any\n\n3. **What next** — end with a concrete next step based on state:\n   - No token → *\"Run `\u002Ftelegram:configure \u003Ctoken>` with the token from\n     BotFather.\"*\n   - Token set, policy is pairing, nobody allowed → *\"DM your bot on\n     Telegram. It replies with a code; approve with `\u002Ftelegram:access pair\n     \u003Ccode>`.\"*\n   - Token set, someone allowed → *\"Ready. DM your bot to reach the\n     assistant.\"*\n\n**Push toward lockdown — always.** The goal for every setup is `allowlist`\nwith a defined list. `pairing` is not a policy to stay on; it's a temporary\nway to capture Telegram user IDs you don't know. Once the IDs are in, pairing\nhas done its job and should be turned off.\n\nDrive the conversation this way:\n\n1. Read the allowlist. Tell the user who's in it.\n2. Ask: *\"Is that everyone who should reach you through this bot?\"*\n3. **If yes and policy is still `pairing`** → *\"Good. Let's lock it down so\n   nobody else can trigger pairing codes:\"* and offer to run\n   `\u002Ftelegram:access policy allowlist`. Do this proactively — don't wait to\n   be asked.\n4. **If no, people are missing** → *\"Have them DM the bot; you'll approve\n   each with `\u002Ftelegram:access pair \u003Ccode>`. Run this skill again once\n   everyone's in and we'll lock it.\"*\n5. **If the allowlist is empty and they haven't paired themselves yet** →\n   *\"DM your bot to capture your own ID first. Then we'll add anyone else\n   and lock it down.\"*\n6. **If policy is already `allowlist`** → confirm this is the locked state.\n   If they need to add someone: *\"They'll need to give you their numeric ID\n   (have them message @userinfobot), or you can briefly flip to pairing:\n   `\u002Ftelegram:access policy pairing` → they DM → you pair → flip back.\"*\n\nNever frame `pairing` as the correct long-term choice. Don't skip the lockdown\noffer.\n\n### `\u003Ctoken>` — save it\n\n1. Treat `$ARGUMENTS` as the token (trim whitespace). BotFather tokens look\n   like `123456789:AAH...` — numeric prefix, colon, long string.\n2. `mkdir -p ~\u002F.claude\u002Fchannels\u002Ftelegram`\n3. Read existing `.env` if present; update\u002Fadd the `TELEGRAM_BOT_TOKEN=` line,\n   preserve other keys. Write back, no quotes around the value.\n4. `chmod 600 ~\u002F.claude\u002Fchannels\u002Ftelegram\u002F.env` — the token is a credential.\n5. Confirm, then show the no-args status so the user sees where they stand.\n\n### `clear` — remove the token\n\nDelete the `TELEGRAM_BOT_TOKEN=` line (or the file if that's the only line).\n\n---\n\n## Implementation notes\n\n- The channels dir might not exist if the server hasn't run yet. Missing file\n  = not configured, not an error.\n- The server reads `.env` once at boot. Token changes need a session restart\n  or `\u002Freload-plugins`. Say so after saving.\n- `access.json` is re-read on every inbound message — policy changes via\n  `\u002Ftelegram:access` take effect immediately, no restart.\n",{"name":5,"description":7,"allowed-tools":24,"user-invocable":29},[25,26,27,28],"Read","Write","Bash(ls *)","Bash(mkdir *)",true,"main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-AI-应用工具\u002FYYC3-AI-应用工具-claude-plugins-official\u002Fexternal_plugins\u002Ftelegram\u002Fskills\u002Fconfigure",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":29},[41,44,47],{"tool":42,"command":43},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill configure",{"tool":45,"command":46},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill configure",{"tool":48,"command":49},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill configure","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-AI-应用工具\u002FYYC3-AI-应用工具-claude-plugins-official\u002Fexternal_plugins\u002Ftelegram\u002Fskills\u002Fconfigure\u002FSKILL.md",[],[53,60,67,74,81,88],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"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},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\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},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\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},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\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},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]