[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F76KYD5MYT11JR0XG1PWMH":3,"skill-same:01M7F76KYD5MYT11JR0XG1PWMH":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7F76KYD5MYT11JR0XG1PWMH","connections",null,"Microwave-WYB\u002Famuse","Microwave-WYB","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F68882116?v=4","01M7BS08CP37AY1DCBEJD2N994","Yibo Wei","01M7F768TKD2FX303BJ45ZBAG9",3,"MIT","https:\u002F\u002Fgithub.com\u002FMicrowave-WYB\u002Famuse\u002Fblob\u002Fmain\u002Fpi\u002Fskills\u002Fconnections\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: connections\ndescription: The user's connected apps (mail, calendar, sheets, Slack, GitHub, …): unlocks `request_connection`, `app_tools`, `app_call` and the secret tools (`list_secrets`, `request_secret`, `use_secret`).\n---\n\n# The user's connections\n\n**Find and use.** For a connection, find the action with `app_tools` (the service's id, e.g. gmail, googlecalendar, and a few words), then run it with `app_call`. Give `summary` (what it does, as the user would say it, with the specifics) and `reason` (why, tied to what they asked): they show on the approval card when one is needed.\n\n**What runs at once and what is asked.** The user's rules decide, per connection and per kind of action (read, change, delete). Reading usually runs at once. Sending, changing, deleting or paying goes to the user on a card and runs in the background once approved; you hear how it went. **Deny is a hard no.** An action of a kind the user said no to (Deny) is still listed, marked as denied, so you can say why. Calling it is refused at once, with no card: the answer names the rule and where to change it (Settings › Connections › the connection › the kind). Tell the user in one line which rule it is. Do not call it again, and do not work around it: not through another tool, another account, or the service's website in the browser. Do not ask again unless the user brings it up.\n\n**Nothing back is not \"nothing there\".** If an action was refused, failed or found nothing, say which. Never take a refused read for an empty inbox or calendar.\n\n**Not connected yet.** When a request needs a service that is not connected, show its Connect card with `request_connection` instead of guessing.\n\n**More than one account.** A connection can have several accounts at once (two Gmail addresses, a work and a personal calendar). To add another, show the Connect card again with `request_connection`: the user signs in with the other account there, and the ones already connected stay. Once there are several, say which you act as (`account` in `app_call`), and ask when it is not clear which they mean.\n\n**Connections not set up at all.** Connections go through Composio, with the user's own Composio API key, added on a card in the chat (or in Settings › Connections). Why: each service only lets in software it has approved, and Composio is approved by them, so the user need not set each one up; it is their own Composio account, so their logins stay in it and they can revoke them there. Walk them through it a step at a time, in plain words:\n1. Sign in or sign up at dashboard.composio.dev.\n2. Open Settings, then Project Settings.\n3. Under API Keys, copy the key (it starts with ak_).\n4. Ask for the key with `request_secret` and `provider: \"composio\"`: a card opens the sheet where they paste it (the same as Settings › Connections › Add Composio key); it is tested at once. You hear when it is added.\nThe key goes only on that card or in Settings, never in the chat. Then show the Connect card for the service: it connects it.\n\n**Keeping an eye on things.** When the user connects mail or a calendar, or wants to keep up with them, offer a schedule (for instance new mail every two hours, telling them only what needs them; the day's calendar each morning). Set it up only if they want it (read the schedules skill).\n","# The user's connections\n\n**Find and use.** For a connection, find the action with `app_tools` (the service's id, e.g. gmail, googlecalendar, and a few words), then run it with `app_call`. Give `summary` (what it does, as the user would say it, with the specifics) and `reason` (why, tied to what they asked): they show on the approval card when one is needed.\n\n**What runs at once and what is asked.** The user's rules decide, per connection and per kind of action (read, change, delete). Reading usually runs at once. Sending, changing, deleting or paying goes to the user on a card and runs in the background once approved; you hear how it went. **Deny is a hard no.** An action of a kind the user said no to (Deny) is still listed, marked as denied, so you can say why. Calling it is refused at once, with no card: the answer names the rule and where to change it (Settings › Connections › the connection › the kind). Tell the user in one line which rule it is. Do not call it again, and do not work around it: not through another tool, another account, or the service's website in the browser. Do not ask again unless the user brings it up.\n\n**Nothing back is not \"nothing there\".** If an action was refused, failed or found nothing, say which. Never take a refused read for an empty inbox or calendar.\n\n**Not connected yet.** When a request needs a service that is not connected, show its Connect card with `request_connection` instead of guessing.\n\n**More than one account.** A connection can have several accounts at once (two Gmail addresses, a work and a personal calendar). To add another, show the Connect card again with `request_connection`: the user signs in with the other account there, and the ones already connected stay. Once there are several, say which you act as (`account` in `app_call`), and ask when it is not clear which they mean.\n\n**Connections not set up at all.** Connections go through Composio, with the user's own Composio API key, added on a card in the chat (or in Settings › Connections). Why: each service only lets in software it has approved, and Composio is approved by them, so the user need not set each one up; it is their own Composio account, so their logins stay in it and they can revoke them there. Walk them through it a step at a time, in plain words:\n1. Sign in or sign up at dashboard.composio.dev.\n2. Open Settings, then Project Settings.\n3. Under API Keys, copy the key (it starts with ak_).\n4. Ask for the key with `request_secret` and `provider: \"composio\"`: a card opens the sheet where they paste it (the same as Settings › Connections › Add Composio key); it is tested at once. You hear when it is added.\nThe key goes only on that card or in Settings, never in the chat. Then show the Connect card for the service: it connects it.\n\n**Keeping an eye on things.** When the user connects mail or a calendar, or wants to keep up with them, offer a schedule (for instance new mail every two hours, telling them only what needs them; the day's calendar each morning). Set it up only if they want it (read the schedules skill).\n",{},"main","afacc6214001268e7f41f0ba02a6ff38995b6429","pi\u002Fskills\u002Fconnections",2,"https:\u002F\u002Fgithub.com\u002FMicrowave-WYB\u002Famuse","https:\u002F\u002Fgithub.com\u002FMicrowave-WYB","PhD student at University of California, San Diego\r\nCurrently researching with Professor Aaron Schulman","2026-11-06 02:32:57",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Microwave-WYB\u002Famuse --skill connections",{"tool":37,"command":38},"bunx","bunx skills add Microwave-WYB\u002Famuse --skill connections",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Microwave-WYB\u002Famuse --skill connections","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMicrowave-WYB\u002Famuse\u002Fblob\u002Fmain\u002Fpi\u002Fskills\u002Fconnections\u002FSKILL.md",true,[],[46,53,60,67,74,80],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7F774YWZY9E1M56MCF1G97J","schedules","Work for later or on a schedule (a morning briefing, checking mail hourly, a reminder tomorrow); unlocks `schedule`, `list_schedules` and `cancel_schedule`.","https:\u002F\u002Fgithub.com\u002FMicrowave-WYB\u002Famuse\u002Fblob\u002Fmain\u002Fpi\u002Fskills\u002Fschedules\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M7F771E89B6JNN8FMBXBJKMN","sandbox","Your own computer for running programs (shell commands, installs, scripts, dev servers, background jobs); unlocks `run_command`, the file tools and the secret tools.","https:\u002F\u002Fgithub.com\u002FMicrowave-WYB\u002Famuse\u002Fblob\u002Fmain\u002Fpi\u002Fskills\u002Fsandbox\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7F76Z676DP4APED8Y1BNWFP","memory","Reading, tracing or forgetting memory files (`memory_get`, `memory_explain`, `forget`, `people\u002F`, `groups\u002F`). `remember` and `memory_search` are already active.","https:\u002F\u002Fgithub.com\u002FMicrowave-WYB\u002Famuse\u002Fblob\u002Fmain\u002Fpi\u002Fskills\u002Fmemory\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M7F76WY730ZTD6NCGHEG4CH2","herdr","Shared terminals in the sandbox through herdr (long-running processes, interactive CLI logins, REPLs, coding agents).","https:\u002F\u002Fgithub.com\u002FMicrowave-WYB\u002Famuse\u002Fblob\u002Fmain\u002Fpi\u002Fskills\u002Fherdr\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M7F76TAP9AKK7FV3VDEZME2Z","goals","https:\u002F\u002Fgithub.com\u002FMicrowave-WYB\u002Famuse\u002Fblob\u002Fmain\u002Fpi\u002Fskills\u002Fgoals\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M7F76SF7JR596PB9EZHQVH8V","files","https:\u002F\u002Fgithub.com\u002FMicrowave-WYB\u002Famuse\u002Fblob\u002Fmain\u002Fpi\u002Fskills\u002Ffiles\u002FSKILL.md",[],[]]