[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79VVBZ6F04SD15SXDWWPF1M":3,"skill-same:01M79VVBZ6F04SD15SXDWWPF1M":56},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":6,"updatedAt":35,"install":36,"resources":49},"01M79VVBZ6F04SD15SXDWWPF1M","google-workspace",null,"Read and act on the user's Gmail, Google Calendar, and Google Tasks through their own Google connection.","yc-software\u002Fqm","yc-software","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F153323858?v=4","01M79VRJS45RJM7XBFGB9D1HY6","Y Combinator","01M79VRJSY4P8QKGTCMVJAZ4DE",15703,"MIT","https:\u002F\u002Fgithub.com\u002Fyc-software\u002Fqm\u002Fblob\u002Fmain\u002Fskills-seed\u002Fgoogle-workspace\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: google-workspace\ndescription: Read and act on the user's Gmail, Google Calendar, and Google Tasks through their own Google connection.\nrequiredCapabilities:\n  - egress:gmail.googleapis.com\n  - egress:www.googleapis.com\n---\n\n# Google Workspace\n\nUse this skill when the user asks about Gmail, Google Calendar, or Google Tasks:\nschedule, meetings, emails, labels, drafts, replies, or to-do lists and tasks.\n\n## Connection\n\nGoogle reaches you one of two ways; the requests are the same either way.\n\n- **Direct token:** `$VAULT_TOKEN_GMAIL_GOOGLEAPIS_COM` (`gmail.googleapis.com`) and\n  `$VAULT_TOKEN_WWW_GOOGLEAPIS_COM` (Calendar and Tasks on `www.googleapis.com`) hold the\n  user's Google OAuth token. The `curl` examples below use them as written.\n- **App connection:** with no token, the user connects Gmail, Google Calendar and Google\n  Tasks as apps instead (composio skill). Send the same request through QM — same method,\n  URL, `query`, headers and JSON `body`, but no Authorization header:\n\n  ```bash\n  curl -sS \"$AGENT_API_URL\u002Fv1\u002Fcomposio\u002Fproxy\" -H \"X-Agent-Capability: $AGENT_API_TOKEN\" \\\n    -H 'content-type: application\u002Fjson' \\\n    --data '{\"method\":\"GET\",\"url\":\"https:\u002F\u002Fwww.googleapis.com\u002Fcalendar\u002Fv3\u002Fusers\u002Fme\u002Fsettings\u002Ftimezone\"}'\n  ```\n\n  The reply is the provider's own status and body; the composio skill's \"Raw requests\"\n  section covers `409` answers, choosing an account, and file bodies. `gmail.py` picks the route itself\n  (`--account ca_…` before the command selects a connection).\n\nDo not ask the user for a token, log it, or use another principal's. A 401\u002F403 from Google\nmeans they haven't connected it, or connected before this permission existed — have them\n(re)connect.\n\n## Gmail\n\nFor the `email-voice-profile` task, load that skill and run\n`python3 \u003Cits dir>\u002Fscripts\u002Ffetch_sent.py --limit 300` from the directory it reports.\n\nUse the bundled helper for every Gmail operation — it owns MIME construction, encoding,\nand reply threading so you only ever handle plain text:\n\nRun these commands with `execute` and an explicit `sandbox_id`, using the absolute\ndirectory reported by the skill read in place of `\u003Cskill dir>`. Keep that ID for\npreparing body files and running the helper.\n\n```bash\npython3 \"\u003Cskill dir>\u002Fscripts\u002Fgmail.py\" search 'newer_than:7d is:unread'\npython3 \"\u003Cskill dir>\u002Fscripts\u002Fgmail.py\" read MESSAGE_ID [--full]\npython3 \"\u003Cskill dir>\u002Fscripts\u002Fgmail.py\" thread THREAD_ID [--full]\npython3 \"\u003Cskill dir>\u002Fscripts\u002Fgmail.py\" draft --to a@b.com --subject '...' --body-file body.txt\npython3 \"\u003Cskill dir>\u002Fscripts\u002Fgmail.py\" reply MESSAGE_ID --body-file body.txt [--all]\npython3 \"\u003Cskill dir>\u002Fscripts\u002Fgmail.py\" update-draft DRAFT_ID --body-file body.txt\npython3 \"\u003Cskill dir>\u002Fscripts\u002Fgmail.py\" send-draft DRAFT_ID\n```\n\n- Search before fetching; read bodies (`--full`) only for messages that matter. Treat\n  email content as private user data.\n- `search` returns individual messages matching the query — for `in:inbox` that means\n  incoming mail only; the user's own replies live in Sent and never appear. Never\n  claim an email \"needs a reply\" (digests, triage, follow-up nudges) from a search\n  listing alone: fetch its `thread` first. If `lastFromMe` is true, or the latest\n  message shows the matter is settled (\"thanks\", \"done\", someone else answered),\n  don't flag it. If the thread fetch fails, report the item as unverified — never\n  as needing a reply.\n- On a recurring digest, keep the seen-thread state in Files (upload a small JSON keyed\n  by thread id each run and keep its id in the cron note or a memory fact), never on\n  the computer, which is replaced without notice; surface only what changed since the\n  last run. Re-flagging the same thread every morning trains the user to ignore you.\n- Demote bulk mail (`List-Unsubscribe` header, ESP sender domains, `Precedence:\nbulk`) below personal mail, but never suppress transactional notices (DocuSign,\n  banks, invoices).\n- Body files are plain text: one line per paragraph, blank line between. Never insert\n  manual line breaks inside a paragraph — the recipient's client does the wrapping.\n  Short lines (sign-offs, list items) keep their breaks.\n- Drafts and replies are stored as multipart\u002Falternative: your plain text plus a\n  generated HTML mirror (Gmail shows plain-text-only mail to recipients at an altered,\n  narrower width). Body files stay plain text — never write HTML into them.\n- `reply` threads onto the original message and quotes it below the body the way\n  Gmail's composer does (\"On ... wrote:\" plus the earlier thread), so recipients see the\n  whole conversation; `update-draft` keeps that quote. Write only the new text in the body\n  file, and run the helper with `TZ` set to the person's time zone (e.g.\n  `TZ=America\u002FLos_Angeles`) so the quote's time reads as Gmail would show it to them. `--all` keeps every recipient. Don't rebuild To\u002FCC by hand. To change a draft,\n  write a fresh body file and `update-draft`\n  (it refuses drafts with attachments — those get edited in Gmail).\n- Never construct raw MIME or call the drafts\u002Fsend endpoints with hand-built payloads.\n- Never write styled HTML email — no font-family\u002Fsize\u002Fcolor declarations, no CSS-styled\n  buttons or layout markup. Styled HTML screams automated blast and overrides the\n  recipient's client fonts. The helper's generated HTML mirror (bare `\u003Cdiv dir=\"ltr\">`,\n  `\u003Cbr>`, plain links, and Gmail's own `gmail_quote` block on replies) is the only HTML\n  that ever goes out.\n- Write body files as UTF-8. After creating or updating a draft, read it back\n  (`gmail.py thread`\u002Fdraft read) and confirm em dashes, quotes, and any emoji came\n  through intact — mojibake (`â€¦`-style garble) in a sent mail is unrecoverable.\n\n## Calendar reads\n\nFor \"what is on my schedule today?\", first get the user's timezone\n(`GET \u002Fcalendar\u002Fv3\u002Fusers\u002Fme\u002Fsettings\u002Ftimezone` — the sandbox clock is UTC, so never\nassume it), compute the local day bounds, and call:\n\n```bash\ncurl -sS --get 'https:\u002F\u002Fwww.googleapis.com\u002Fcalendar\u002Fv3\u002Fcalendars\u002Fprimary\u002Fevents' \\\n  -H \"Authorization: Bearer $VAULT_TOKEN_WWW_GOOGLEAPIS_COM\" \\\n  --data-urlencode \"timeMin=$TIME_MIN\" \\\n  --data-urlencode \"timeMax=$TIME_MAX\" \\\n  --data-urlencode \"singleEvents=true\" \\\n  --data-urlencode \"orderBy=startTime\" \\\n  --data-urlencode \"maxResults=250\"\n```\n\nIf the response has a `nextPageToken`, keep fetching — a truncated page silently drops\nmeetings. `primary` is only the user's own calendar; when the question implies team or\nshared calendars, list them first (`GET \u002Fcalendar\u002Fv3\u002Fusers\u002Fme\u002FcalendarList`) and query\neach relevant one. Skip events the user declined (their own `attendees[]` entry has\n`responseStatus: \"declined\"`).\n\nSummarize start time, title, attendees when useful, and conferencing links only when\nneeded. Do not expose private calendar details in a shared channel unless the audience\nfloor allows them; offer to continue in DM.\n\n## Google Tasks\n\nTasks is served under `www.googleapis.com\u002Ftasks\u002Fv1`, so it uses the same\n`$VAULT_TOKEN_WWW_GOOGLEAPIS_COM` token. List the task lists, then the tasks in one:\n\n```bash\ncurl -sS 'https:\u002F\u002Fwww.googleapis.com\u002Ftasks\u002Fv1\u002Fusers\u002F@me\u002Flists' \\\n  -H \"Authorization: Bearer $VAULT_TOKEN_WWW_GOOGLEAPIS_COM\"\n\ncurl -sS --get 'https:\u002F\u002Fwww.googleapis.com\u002Ftasks\u002Fv1\u002Flists\u002FLIST_ID\u002Ftasks' \\\n  -H \"Authorization: Bearer $VAULT_TOKEN_WWW_GOOGLEAPIS_COM\" \\\n  --data-urlencode \"showCompleted=false\" \\\n  --data-urlencode \"maxResults=100\"\n```\n\nBoth endpoints page (default 20 items): follow `nextPageToken` before treating a list\nas complete.\n\nCreating, completing, editing, or deleting a task is a write — treat it like any other\nwrite below. Example creation after approval:\n\n```bash\ncurl -sS -X POST 'https:\u002F\u002Fwww.googleapis.com\u002Ftasks\u002Fv1\u002Flists\u002FLIST_ID\u002Ftasks' \\\n  -H \"Authorization: Bearer $VAULT_TOKEN_WWW_GOOGLEAPIS_COM\" \\\n  -H 'content-type: application\u002Fjson' \\\n  --data '{\"title\":\"...\",\"notes\":\"...\",\"due\":\"2026-07-20T00:00:00.000Z\"}'\n```\n\n## Writes require approval\n\nCreating drafts, sending mail, modifying labels, deleting mail, or editing calendar\nevents is a write. Prepare the exact action, show the user the exact text, and ask for\napproval before running it. `send-draft` only ever fires on an explicitly approved\ndraft.\n\nCalendar event creation after approval:\n\n```bash\ncurl -sS -X POST 'https:\u002F\u002Fwww.googleapis.com\u002Fcalendar\u002Fv3\u002Fcalendars\u002Fprimary\u002Fevents' \\\n  -H \"Authorization: Bearer $VAULT_TOKEN_WWW_GOOGLEAPIS_COM\" \\\n  -H 'content-type: application\u002Fjson' \\\n  --data @event.json\n```\n\nAlways show what changed and keep the IDs needed to undo or inspect later in your\nreply or in memory, not on the computer.\n","# Google Workspace\n\nUse this skill when the user asks about Gmail, Google Calendar, or Google Tasks:\nschedule, meetings, emails, labels, drafts, replies, or to-do lists and tasks.\n\n## Connection\n\nGoogle reaches you one of two ways; the requests are the same either way.\n\n- **Direct token:** `$VAULT_TOKEN_GMAIL_GOOGLEAPIS_COM` (`gmail.googleapis.com`) and\n  `$VAULT_TOKEN_WWW_GOOGLEAPIS_COM` (Calendar and Tasks on `www.googleapis.com`) hold the\n  user's Google OAuth token. The `curl` examples below use them as written.\n- **App connection:** with no token, the user connects Gmail, Google Calendar and Google\n  Tasks as apps instead (composio skill). Send the same request through QM — same method,\n  URL, `query`, headers and JSON `body`, but no Authorization header:\n\n  ```bash\n  curl -sS \"$AGENT_API_URL\u002Fv1\u002Fcomposio\u002Fproxy\" -H \"X-Agent-Capability: $AGENT_API_TOKEN\" \\\n    -H 'content-type: application\u002Fjson' \\\n    --data '{\"method\":\"GET\",\"url\":\"https:\u002F\u002Fwww.googleapis.com\u002Fcalendar\u002Fv3\u002Fusers\u002Fme\u002Fsettings\u002Ftimezone\"}'\n  ```\n\n  The reply is the provider's own status and body; the composio skill's \"Raw requests\"\n  section covers `409` answers, choosing an account, and file bodies. `gmail.py` picks the route itself\n  (`--account ca_…` before the command selects a connection).\n\nDo not ask the user for a token, log it, or use another principal's. A 401\u002F403 from Google\nmeans they haven't connected it, or connected before this permission existed — have them\n(re)connect.\n\n## Gmail\n\nFor the `email-voice-profile` task, load that skill and run\n`python3 \u003Cits dir>\u002Fscripts\u002Ffetch_sent.py --limit 300` from the directory it reports.\n\nUse the bundled helper for every Gmail operation — it owns MIME construction, encoding,\nand reply threading so you only ever handle plain text:\n\nRun these commands with `execute` and an explicit `sandbox_id`, using the absolute\ndirectory reported by the skill read in place of `\u003Cskill dir>`. Keep that ID for\npreparing body files and running the helper.\n\n```bash\npython3 \"\u003Cskill dir>\u002Fscripts\u002Fgmail.py\" search 'newer_than:7d is:unread'\npython3 \"\u003Cskill dir>\u002Fscripts\u002Fgmail.py\" read MESSAGE_ID [--full]\npython3 \"\u003Cskill dir>\u002Fscripts\u002Fgmail.py\" thread THREAD_ID [--full]\npython3 \"\u003Cskill dir>\u002Fscripts\u002Fgmail.py\" draft --to a@b.com --subject '...' --body-file body.txt\npython3 \"\u003Cskill dir>\u002Fscripts\u002Fgmail.py\" reply MESSAGE_ID --body-file body.txt [--all]\npython3 \"\u003Cskill dir>\u002Fscripts\u002Fgmail.py\" update-draft DRAFT_ID --body-file body.txt\npython3 \"\u003Cskill dir>\u002Fscripts\u002Fgmail.py\" send-draft DRAFT_ID\n```\n\n- Search before fetching; read bodies (`--full`) only for messages that matter. Treat\n  email content as private user data.\n- `search` returns individual messages matching the query — for `in:inbox` that means\n  incoming mail only; the user's own replies live in Sent and never appear. Never\n  claim an email \"needs a reply\" (digests, triage, follow-up nudges) from a search\n  listing alone: fetch its `thread` first. If `lastFromMe` is true, or the latest\n  message shows the matter is settled (\"thanks\", \"done\", someone else answered),\n  don't flag it. If the thread fetch fails, report the item as unverified — never\n  as needing a reply.\n- On a recurring digest, keep the seen-thread state in Files (upload a small JSON keyed\n  by thread id each run and keep its id in the cron note or a memory fact), never on\n  the computer, which is replaced without notice; surface only what changed since the\n  last run. Re-flagging the same thread every morning trains the user to ignore you.\n- Demote bulk mail (`List-Unsubscribe` header, ESP sender domains, `Precedence:\nbulk`) below personal mail, but never suppress transactional notices (DocuSign,\n  banks, invoices).\n- Body files are plain text: one line per paragraph, blank line between. Never insert\n  manual line breaks inside a paragraph — the recipient's client does the wrapping.\n  Short lines (sign-offs, list items) keep their breaks.\n- Drafts and replies are stored as multipart\u002Falternative: your plain text plus a\n  generated HTML mirror (Gmail shows plain-text-only mail to recipients at an altered,\n  narrower width). Body files stay plain text — never write HTML into them.\n- `reply` threads onto the original message and quotes it below the body the way\n  Gmail's composer does (\"On ... wrote:\" plus the earlier thread), so recipients see the\n  whole conversation; `update-draft` keeps that quote. Write only the new text in the body\n  file, and run the helper with `TZ` set to the person's time zone (e.g.\n  `TZ=America\u002FLos_Angeles`) so the quote's time reads as Gmail would show it to them. `--all` keeps every recipient. Don't rebuild To\u002FCC by hand. To change a draft,\n  write a fresh body file and `update-draft`\n  (it refuses drafts with attachments — those get edited in Gmail).\n- Never construct raw MIME or call the drafts\u002Fsend endpoints with hand-built payloads.\n- Never write styled HTML email — no font-family\u002Fsize\u002Fcolor declarations, no CSS-styled\n  buttons or layout markup. Styled HTML screams automated blast and overrides the\n  recipient's client fonts. The helper's generated HTML mirror (bare `\u003Cdiv dir=\"ltr\">`,\n  `\u003Cbr>`, plain links, and Gmail's own `gmail_quote` block on replies) is the only HTML\n  that ever goes out.\n- Write body files as UTF-8. After creating or updating a draft, read it back\n  (`gmail.py thread`\u002Fdraft read) and confirm em dashes, quotes, and any emoji came\n  through intact — mojibake (`â€¦`-style garble) in a sent mail is unrecoverable.\n\n## Calendar reads\n\nFor \"what is on my schedule today?\", first get the user's timezone\n(`GET \u002Fcalendar\u002Fv3\u002Fusers\u002Fme\u002Fsettings\u002Ftimezone` — the sandbox clock is UTC, so never\nassume it), compute the local day bounds, and call:\n\n```bash\ncurl -sS --get 'https:\u002F\u002Fwww.googleapis.com\u002Fcalendar\u002Fv3\u002Fcalendars\u002Fprimary\u002Fevents' \\\n  -H \"Authorization: Bearer $VAULT_TOKEN_WWW_GOOGLEAPIS_COM\" \\\n  --data-urlencode \"timeMin=$TIME_MIN\" \\\n  --data-urlencode \"timeMax=$TIME_MAX\" \\\n  --data-urlencode \"singleEvents=true\" \\\n  --data-urlencode \"orderBy=startTime\" \\\n  --data-urlencode \"maxResults=250\"\n```\n\nIf the response has a `nextPageToken`, keep fetching — a truncated page silently drops\nmeetings. `primary` is only the user's own calendar; when the question implies team or\nshared calendars, list them first (`GET \u002Fcalendar\u002Fv3\u002Fusers\u002Fme\u002FcalendarList`) and query\neach relevant one. Skip events the user declined (their own `attendees[]` entry has\n`responseStatus: \"declined\"`).\n\nSummarize start time, title, attendees when useful, and conferencing links only when\nneeded. Do not expose private calendar details in a shared channel unless the audience\nfloor allows them; offer to continue in DM.\n\n## Google Tasks\n\nTasks is served under `www.googleapis.com\u002Ftasks\u002Fv1`, so it uses the same\n`$VAULT_TOKEN_WWW_GOOGLEAPIS_COM` token. List the task lists, then the tasks in one:\n\n```bash\ncurl -sS 'https:\u002F\u002Fwww.googleapis.com\u002Ftasks\u002Fv1\u002Fusers\u002F@me\u002Flists' \\\n  -H \"Authorization: Bearer $VAULT_TOKEN_WWW_GOOGLEAPIS_COM\"\n\ncurl -sS --get 'https:\u002F\u002Fwww.googleapis.com\u002Ftasks\u002Fv1\u002Flists\u002FLIST_ID\u002Ftasks' \\\n  -H \"Authorization: Bearer $VAULT_TOKEN_WWW_GOOGLEAPIS_COM\" \\\n  --data-urlencode \"showCompleted=false\" \\\n  --data-urlencode \"maxResults=100\"\n```\n\nBoth endpoints page (default 20 items): follow `nextPageToken` before treating a list\nas complete.\n\nCreating, completing, editing, or deleting a task is a write — treat it like any other\nwrite below. Example creation after approval:\n\n```bash\ncurl -sS -X POST 'https:\u002F\u002Fwww.googleapis.com\u002Ftasks\u002Fv1\u002Flists\u002FLIST_ID\u002Ftasks' \\\n  -H \"Authorization: Bearer $VAULT_TOKEN_WWW_GOOGLEAPIS_COM\" \\\n  -H 'content-type: application\u002Fjson' \\\n  --data '{\"title\":\"...\",\"notes\":\"...\",\"due\":\"2026-07-20T00:00:00.000Z\"}'\n```\n\n## Writes require approval\n\nCreating drafts, sending mail, modifying labels, deleting mail, or editing calendar\nevents is a write. Prepare the exact action, show the user the exact text, and ask for\napproval before running it. `send-draft` only ever fires on an explicitly approved\ndraft.\n\nCalendar event creation after approval:\n\n```bash\ncurl -sS -X POST 'https:\u002F\u002Fwww.googleapis.com\u002Fcalendar\u002Fv3\u002Fcalendars\u002Fprimary\u002Fevents' \\\n  -H \"Authorization: Bearer $VAULT_TOKEN_WWW_GOOGLEAPIS_COM\" \\\n  -H 'content-type: application\u002Fjson' \\\n  --data @event.json\n```\n\nAlways show what changed and keep the IDs needed to undo or inspect later in your\nreply or in memory, not on the computer.\n",{"name":5,"description":7,"requiredCapabilities":24},[25,26],"egress:gmail.googleapis.com","egress:www.googleapis.com","main","5011257b95913c04ebb800ac7bc80415546ee6bc","skills-seed\u002Fgoogle-workspace",1960,"https:\u002F\u002Fgithub.com\u002Fyc-software\u002Fqm","https:\u002F\u002Flabs.ycombinator.com\u002Fqm","https:\u002F\u002Fgithub.com\u002Fyc-software","ycombinator.com","2026-11-15 01:58:49",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add yc-software\u002Fqm --skill google-workspace",{"tool":42,"command":43},"bunx","bunx skills add yc-software\u002Fqm --skill google-workspace",{"tool":45,"command":46},"pnpm","pnpm dlx skills add yc-software\u002Fqm --skill google-workspace","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fyc-software\u002Fqm\u002Fblob\u002Fmain\u002Fskills-seed\u002Fgoogle-workspace\u002FSKILL.md",true,[50],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"scripts\u002Fgmail.py","SCRIPT","脚本",20435,"https:\u002F\u002Fgithub.com\u002Fyc-software\u002Fqm\u002Fblob\u002Fmain\u002Fskills-seed\u002Fgoogle-workspace\u002Fscripts\u002Fgmail.py",[57,64,71,78,85,93],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M79VXTEATDTE0X6SZRD4J75X","zoom","Find, create, reschedule, and cancel the user's Zoom meetings through their own Zoom connection.","https:\u002F\u002Fgithub.com\u002Fyc-software\u002Fqm\u002Fblob\u002Fmain\u002Fskills-seed\u002Fzoom\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M79VXKJ50M6G24Q11A3806R5","use-shared-credential","When you need to call a service the org has a SHARED credential for (a SERP\u002Fsearch key, a paid-API key, a data-vendor feed, a Git remote) — and the platform has told you that credential is available to this conversation — make the call BY PROXY through the credential broker. You never see the secret; the core stamps it onto the outbound request for you.","https:\u002F\u002Fgithub.com\u002Fyc-software\u002Fqm\u002Fblob\u002Fmain\u002Fskills-seed\u002Fuse-shared-credential\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M79VXERKP52PBXTQ7KAX82S4","ui-state","See what the person is looking at in the QM web UI right now — the whole page (sidebar, every multiview pane, open dialogs) as raw HTML, the app's state as JSON, optionally the CSS and a screenshot. Use when they ask about something on their screen, want help with the UI, or you need to check what a canvas you wrote actually rendered.","https:\u002F\u002Fgithub.com\u002Fyc-software\u002Fqm\u002Fblob\u002Fmain\u002Fskills-seed\u002Fui-state\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M79VXASHJ1WX4J68T3MBHZEK","ui-canvas","Draw your own HTML\u002FCSS\u002FJS as a full-window overlay on top of the QM web UI — a dashboard, a form, a visualization, controls that message you back. Write, update, replace, pin or dismiss it. Use when an interactive or visual result beats a chat reply.","https:\u002F\u002Fgithub.com\u002Fyc-software\u002Fqm\u002Fblob\u002Fmain\u002Fskills-seed\u002Fui-canvas\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M79VX53549EYHNJBHD3PCFSG","taste-skill","Design taste and process for anything a person will look at in a browser — landing page, dashboard, prototype, deck. The default design driver for a browsable artifact, with an anti-slop playbook for the visual language.","https:\u002F\u002Fgithub.com\u002Fyc-software\u002Fqm\u002Fblob\u002Fmain\u002Fskills-seed\u002Ftaste-skill\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fyc-software\u002Fqm\u002Fblob\u002Fmain\u002Fskills-seed\u002Ftaste-skill\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M79VX1DEE1BZZBK66NNCD238","slack-drafts","Create Slack message drafts in the user's own composer, as the user, through their per-user Slack OAuth. Drafting only — the user reviews and sends from Slack.","https:\u002F\u002Fgithub.com\u002Fyc-software\u002Fqm\u002Fblob\u002Fmain\u002Fskills-seed\u002Fslack-drafts\u002FSKILL.md",[],[]]