[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79VTX2FRPZB46WQKNQHDJFT":3,"skill-same:01M79VTX2FRPZB46WQKNQHDJFT":53},{"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":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M79VTX2FRPZB46WQKNQHDJFT","email-voice-profile",null,"Build (or refresh) a voice profile of how the user writes email, from their own sent Gmail. The profile is what email-draft-in-voice consumes to ghostwrite email that sounds like them.","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\u002Femail-voice-profile\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: email-voice-profile\ndescription: Build (or refresh) a voice profile of how the user writes email, from their own sent Gmail. The profile is what email-draft-in-voice consumes to ghostwrite email that sounds like them.\n---\n\n# Email voice profile\n\nUse this when the user asks you to learn how they write email — \"learn my voice\",\n\"build my email voice profile\", \"study my sent mail so you can draft for me\" — or when\n`email-draft-in-voice` needs a profile that doesn't exist yet.\n\n**Personal DMs only.** Sent mail is private; refuse to run this from a channel or group\nand offer to continue in the user's DM. The profile you produce is published to their\npersonal Files, so only their own conversations and their own Inbox drafting can read it.\n\n## 0. Check Files first\n\nComputers are replaced without notice, so nothing durable lives on one. Before building,\nsearch memory for \"email voice profile\" and `GET $AGENT_API_URL\u002Fv1\u002Ffiles?q=email-voice-profile`\n(header `x-agent-capability: $AGENT_API_TOKEN`). An existing profile is refreshed, not\nrebuilt blind: download it with `GET $AGENT_API_URL\u002Fv1\u002Ffiles\u002F\u003Cid>\u002Fcontent` and carry its\nvalidated hard rules forward unless the new corpus contradicts them.\n\n## 1. Pull the corpus\n\nUse the selected email access skill to retrieve up to 300 of the user's sent messages.\nStrip quoted replies and `--`-delimited signatures, drop automated and trivial messages,\nand write one JSON line per email to `voice\u002Fcorpus\u002Fcorpus.jsonl`, tagged `internal` or\n`external` by recipient domain. Record corpus stats; if fewer than ~50 usable emails\nsurvive, tell the user the profile will be rough and ask whether to continue.\n\n## 2. Study it\n\nRead a deliberate spread, not just the top of the file: oldest and newest, internal\nand external, one-liners and long emails. You are looking for what is _distinctive_ —\npatterns a generic professional emailer would not share.\n\nWatch for a signature block: only `--`-delimited signatures are stripped, so a plain\nsignature (name \u002F title \u002F phone) survives at the end of many bodies. Treat a verbatim\nrecurring trailing block as the mail client's signature, not a chosen sign-off — note\nit in the profile so drafts never include it (Gmail appends it on send).\n\n## 3. Write the profile\n\nWrite `email-voice-profile.md` (that exact name; the Inbox drafting loop looks it up by\nname) with exactly these sections,\nevery claim backed by observed frequency (\"uses 'Best,' in 80% of external mail\"),\nwith 2–3 verbatim example lines each:\n\n- **Register map** — how tone shifts by audience (internal vs external, familiar vs\n  cold), and how their length tracks the situation.\n- **Openers & sign-offs** — actual greetings and closings with rough frequencies,\n  including when they use none.\n- **Rhythm** — sentence length, paragraph shape, how they open and end a body, use of\n  fragments, lists, links.\n- **Vocabulary & phrases** — recurring words, pet phrases, how they hedge, how they say\n  yes and no.\n- **Punctuation & formatting quirks** — dashes, ellipses, casing, emoji, bolding.\n- **Hard rules** — things true of nearly every email (\"never opens with 'I hope this\n  finds you well'\", \"always lowercase to teammates\").\n- **Anti-patterns** — what they never do, plus the generic-AI tells to avoid\n  (enthusiastic adjectives, \"I'd be happy to\", bullet-point answers to plain questions).\n\n## 4. Validate before declaring done\n\nHold out 3 real threads the profile wasn't built from. For each, draft the user's\nreply using only the profile, then compare with what they actually sent. Where the\nreal email diverges, tighten the profile — usually a missing hard rule or register\ndistinction. Record `validated: \u003Cdate>` at the top of the profile once the drafts read\nas plausibly theirs.\n\nShow the user the finished profile and ask what feels wrong; their corrections go in\nas hard rules.\n\n## 5. Publish it\n\nUpload the finished file to Files: `curl -fsS \"$AGENT_API_URL\u002Fv1\u002Ffiles\u002Fupload-client\"\n-H \"x-agent-capability: $AGENT_API_TOKEN\" -o \u002Ftmp\u002Fqm-upload.py && python3 \u002Ftmp\u002Fqm-upload.py\nemail-voice-profile.md`, then record one memory fact: \"Email voice profile is Files\n\u003Cid> (built \u003Cdate>)\". The Inbox drafting loop reads the newest `email-voice-profile.md`\nin the user's Files on every pass, so publishing is what makes drafts sound like them.\nThe corpus stays on the computer; only the profile is durable. Re-run this skill any\ntime they want it refreshed — publish the new version and update the memory fact.\n","# Email voice profile\n\nUse this when the user asks you to learn how they write email — \"learn my voice\",\n\"build my email voice profile\", \"study my sent mail so you can draft for me\" — or when\n`email-draft-in-voice` needs a profile that doesn't exist yet.\n\n**Personal DMs only.** Sent mail is private; refuse to run this from a channel or group\nand offer to continue in the user's DM. The profile you produce is published to their\npersonal Files, so only their own conversations and their own Inbox drafting can read it.\n\n## 0. Check Files first\n\nComputers are replaced without notice, so nothing durable lives on one. Before building,\nsearch memory for \"email voice profile\" and `GET $AGENT_API_URL\u002Fv1\u002Ffiles?q=email-voice-profile`\n(header `x-agent-capability: $AGENT_API_TOKEN`). An existing profile is refreshed, not\nrebuilt blind: download it with `GET $AGENT_API_URL\u002Fv1\u002Ffiles\u002F\u003Cid>\u002Fcontent` and carry its\nvalidated hard rules forward unless the new corpus contradicts them.\n\n## 1. Pull the corpus\n\nUse the selected email access skill to retrieve up to 300 of the user's sent messages.\nStrip quoted replies and `--`-delimited signatures, drop automated and trivial messages,\nand write one JSON line per email to `voice\u002Fcorpus\u002Fcorpus.jsonl`, tagged `internal` or\n`external` by recipient domain. Record corpus stats; if fewer than ~50 usable emails\nsurvive, tell the user the profile will be rough and ask whether to continue.\n\n## 2. Study it\n\nRead a deliberate spread, not just the top of the file: oldest and newest, internal\nand external, one-liners and long emails. You are looking for what is _distinctive_ —\npatterns a generic professional emailer would not share.\n\nWatch for a signature block: only `--`-delimited signatures are stripped, so a plain\nsignature (name \u002F title \u002F phone) survives at the end of many bodies. Treat a verbatim\nrecurring trailing block as the mail client's signature, not a chosen sign-off — note\nit in the profile so drafts never include it (Gmail appends it on send).\n\n## 3. Write the profile\n\nWrite `email-voice-profile.md` (that exact name; the Inbox drafting loop looks it up by\nname) with exactly these sections,\nevery claim backed by observed frequency (\"uses 'Best,' in 80% of external mail\"),\nwith 2–3 verbatim example lines each:\n\n- **Register map** — how tone shifts by audience (internal vs external, familiar vs\n  cold), and how their length tracks the situation.\n- **Openers & sign-offs** — actual greetings and closings with rough frequencies,\n  including when they use none.\n- **Rhythm** — sentence length, paragraph shape, how they open and end a body, use of\n  fragments, lists, links.\n- **Vocabulary & phrases** — recurring words, pet phrases, how they hedge, how they say\n  yes and no.\n- **Punctuation & formatting quirks** — dashes, ellipses, casing, emoji, bolding.\n- **Hard rules** — things true of nearly every email (\"never opens with 'I hope this\n  finds you well'\", \"always lowercase to teammates\").\n- **Anti-patterns** — what they never do, plus the generic-AI tells to avoid\n  (enthusiastic adjectives, \"I'd be happy to\", bullet-point answers to plain questions).\n\n## 4. Validate before declaring done\n\nHold out 3 real threads the profile wasn't built from. For each, draft the user's\nreply using only the profile, then compare with what they actually sent. Where the\nreal email diverges, tighten the profile — usually a missing hard rule or register\ndistinction. Record `validated: \u003Cdate>` at the top of the profile once the drafts read\nas plausibly theirs.\n\nShow the user the finished profile and ask what feels wrong; their corrections go in\nas hard rules.\n\n## 5. Publish it\n\nUpload the finished file to Files: `curl -fsS \"$AGENT_API_URL\u002Fv1\u002Ffiles\u002Fupload-client\"\n-H \"x-agent-capability: $AGENT_API_TOKEN\" -o \u002Ftmp\u002Fqm-upload.py && python3 \u002Ftmp\u002Fqm-upload.py\nemail-voice-profile.md`, then record one memory fact: \"Email voice profile is Files\n\u003Cid> (built \u003Cdate>)\". The Inbox drafting loop reads the newest `email-voice-profile.md`\nin the user's Files on every pass, so publishing is what makes drafts sound like them.\nThe corpus stays on the computer; only the profile is durable. Re-run this skill any\ntime they want it refreshed — publish the new version and update the memory fact.\n",{"name":5,"description":7},"main","5011257b95913c04ebb800ac7bc80415546ee6bc","skills-seed\u002Femail-voice-profile",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":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add yc-software\u002Fqm --skill email-voice-profile",{"tool":39,"command":40},"bunx","bunx skills add yc-software\u002Fqm --skill email-voice-profile",{"tool":42,"command":43},"pnpm","pnpm dlx skills add yc-software\u002Fqm --skill email-voice-profile","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fyc-software\u002Fqm\u002Fblob\u002Fmain\u002Fskills-seed\u002Femail-voice-profile\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"scripts\u002Ffetch_sent.py","SCRIPT","脚本",7654,"https:\u002F\u002Fgithub.com\u002Fyc-software\u002Fqm\u002Fblob\u002Fmain\u002Fskills-seed\u002Femail-voice-profile\u002Fscripts\u002Ffetch_sent.py",[54,61,68,75,82,90],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"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":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"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":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"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":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"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",[],[]]