[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79VSF4CZPPAPM6T4JTK8BM5":3,"skill-same:01M79VSF4CZPPAPM6T4JTK8BM5":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},"01M79VSF4CZPPAPM6T4JTK8BM5","upstream-pr",null,"Send a change to upstream qm without leaking organization-specific context. Use when asked to \"upstream this\", \"open a PR against qm\", \"contribute this back\", or when explicitly asked to contribute a downstream change.","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\u002F.codex\u002Fskills\u002Fupstream-pr\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: upstream-pr\ndescription: Send a change to upstream qm without leaking organization-specific context. Use when asked to \"upstream this\", \"open a PR against qm\", \"contribute this back\", or when explicitly asked to contribute a downstream change.\n---\n\n# upstream-pr\n\nSource forks may change core freely. This skill applies only when an upstream\ncontribution is requested; maintaining a local change does not require contributing it.\nKeep private deployment material in `deploy\u002Flayers\u002F\u003Corg>\u002F` in a private source fork or\nin a separate private deployment repository for public source. Core means the runtime,\nplugins, CLI, docs, and CI, and may also contain private details that must be scrubbed.\n\nUpstream qm is shared with organizations other than yours, and anything pushed there is\npermanent: it stays reachable by SHA in every clone and fork even after a deleted branch or\na force-push. Treat a leak as unrecoverable and spend the effort before the push.\n\nSee [`deploy\u002Flayers\u002FREADME.md`](..\u002F..\u002F..\u002Fdeploy\u002Flayers\u002FREADME.md) for the boundary, and the\n`update-qm` skill for syncing the other direction.\n\n## Where the branch will go\n\n`git remote -v`, the source tree, and repository metadata identify the situation. This decides the push\ntarget only; the scrub steps below run in every case.\n\n- `origin` is `yc-software\u002Fqm`: you are in upstream qm. Push the branch to `origin`\n  and open the PR there.\n- `origin` is a GitHub fork of qm, meaning a repository created with GitHub's fork\n  feature and living inside qm's fork network: push to `origin` and open a normal\n  cross-repo PR.\n- A standalone source fork: assume it may hold private material even if\n  `deploy\u002Flayers\u002F` looks empty, and read \"Pushing from a private fork\" below.\n- A package deployment or unrelated repository: prepare the contribution in a separate\n  clean upstream checkout; never push its history to upstream.\n\nJudge by where `origin` points, not by the repository's name. A repository named\n`\u003Corg>\u002Fqm-\u003Csomething>` in the same GitHub organization as the source may still be a\nseparate downstream repository.\n\n## Decide whether the change belongs upstream\n\nAsk what the change would mean to an organization that is not yours. It belongs upstream\nwhen it is a fix or capability in core qm that any deployment would want. It does not\nbelong upstream when it only makes sense given how your organization is set up: its tools,\nits vocabulary, its providers, its process. Keep that change downstream: deployment\nmaterial belongs in the layer or private deployment repository, while source behavior\nmay remain a local core modification.\n\nA change that is generic in substance but written against org-specific fixtures needs its\nfixtures rewritten first. Model them on the account-neutral fixtures under `deploy\u002Fstacks\u002F`\nrather than inventing values from your own deployment.\n\n## Start from a clean tree and a clean branch\n\nA branch cut from a private fork's `main` carries every organization commit in its history, and a\nPR from it exposes all of them. Cut from upstream instead.\n\n`git switch -c` carries modified and untracked files onto the new branch, where a later\n`git add -A` sweeps them into the PR. So first require a clean tree; this must print\nnothing:\n\n```bash\ngit status --porcelain\n```\n\nUse `upstream` below for the verified upstream remote; in an upstream checkout use\n`origin` instead throughout these commands and the history checks.\n\nThen:\n\n```bash\ngit fetch upstream\ngit switch -c \u003Ctopic> upstream\u002Fmain\ngit cherry-pick \u003Csha> [\u003Csha>...]\n```\n\nIf the change is entangled with organization commits and will not cherry-pick cleanly,\nreimplement it on the clean branch. That is faster than auditing a messy history, and it\nfails safe.\n\n## Scrub\n\nRun all four checks against the final branch state, and again after any amend or rebase.\n\nThe scans walk every commit rather than the net diff, because two ordinary moves defeat a\nnet diff. Moving a file out of `deploy\u002Flayers\u002F` with `git mv` is recorded as a rename, so\nthe diff never shows its contents. Adding a layer file in one commit and deleting it in a\nlater one leaves the net diff empty, but the file still ships in the branch's history.\n`git log -p --no-renames` sees both.\n\nCapture the outgoing history once, into the gitignored `.generated\u002F`:\n\n```bash\nmkdir -p .generated\u002Fupstream-pr\ngit log -p --no-renames \\\n  --format='commit %H%nauthor %an \u003C%ae>%ncommitter %cn \u003C%ce>%n%s%n%b' \\\n  upstream\u002Fmain..HEAD > .generated\u002Fupstream-pr\u002Foutgoing.txt\n```\n\n**1. No layer paths in any commit.**\n\n```bash\ngit log --name-status --no-renames --format='' upstream\u002Fmain..HEAD \\\n  | grep -E 'deploy\u002Flayers\u002F[^\u002F]+\u002F' || echo \"PASS: no layer paths\"\n```\n\nOn any hit, stop and rebuild the branch. No PR to upstream legitimately touches an\norganization's layer directory. The shared `deploy\u002Flayers\u002FREADME.md` is core and may\nchange, which is why the pattern matches only paths inside an organization's\nsubdirectory.\n\n**2. No private organization identifiers in content, messages, or authorship.** Build the\nterm list from the private deployment and local core changes, wherever they live: `qm.config.jsonc` has the org slug and public URL host,\n`.env.example` has the computed secret names, `.env` has the secret values,\n`slack-app-manifest.yml` has workspace and app names, `infra\u002Fterraform.tfvars` has cloud\naccount and repository coordinates, and `sandbox\u002F` has internal tool and system names. Add\nyour email domains, teammates' names, and any customer or partner names.\n\nAuthorship is scanned because a clone configured with an internal `user.email` stamps it on\nevery commit, and it stays visible on the upstream PR.\n\n```bash\ncat > .generated\u002Fupstream-pr\u002Fterms.txt \u003C\u003C'TERMS'\nacme\nacme.example.com\n123456789012\nTERMS\n\ntest -s .generated\u002Fupstream-pr\u002Fterms.txt || echo \"REFUSING: term list is empty\"\ngrep -inFf .generated\u002Fupstream-pr\u002Fterms.txt .generated\u002Fupstream-pr\u002Foutgoing.txt \\\n  || echo \"PASS: no identifier hits\"\n```\n\nReplace the example terms with real ones. If the placeholders are left in, the grep matches\nnothing and looks like a pass.\n\n**3. Account for every binary.** A diff shows a binary as one line with no content, so the\nidentifier scan cannot see inside it. Screenshots, `sandbox\u002Ftools\u002F\u003Cid>\u002F\u003Cbinary>`, state\nsnapshots, and PDFs all land here.\n\n```bash\ngrep '^Binary files' .generated\u002Fupstream-pr\u002Foutgoing.txt || echo \"PASS: no binaries\"\n```\n\nJustify each hit individually or drop it from the branch.\n\n**4. The surfaces git cannot see.** None of these appear in any diff:\n\n- the branch name\n- the PR title and description, including pasted error output or stack traces, which\n  routinely carry internal hostnames, account IDs, and real user identifiers\n- screenshots attached to the PR. This repository requires one for any change an operator\n  or user sees rendered, and a screenshot of your instance shows your organization's data,\n  channels, and people. Reproduce the surface against synthetic data and say that you did.\n- reproduction steps that name an internal system, and test data derived from real records\n\nThe title and description also carry no provenance. Write them from upstream's point of\nview and describe what the change does, never where it came from. That the change\noriginated in a private fork, was cherry-picked from other branches, passed your fork's\nCI, or was prepared with this skill is process, not content, and naming your fork points\nreaders at a repository they cannot see. Mention private forks only when the fork model\nitself is the subject of the change.\n\n## Pushing from a private fork\n\nA private fork is a standalone repository outside GitHub's fork network, so it cannot\nopen a cross-repo pull request.\n\nIf you have write access to upstream qm, push the topic branch there and open the PR inside\nthat repository:\n\n```bash\ngit push upstream \u003Ctopic>\ngh pr create --repo yc-software\u002Fqm --base main --head \u003Ctopic> \\\n  --title \"\u003Ctitle>\" --body-file .generated\u002Fupstream-pr\u002Fbody.md\n```\n\nIf you do not, keep a separate public GitHub fork of qm for contributions and push the\nbranch there from a different clone. Do not add that GitHub fork as a remote in the\nprivate fork's clone, where a mistyped push target would send private history to a\npublic repository.\n\nAlways pass `--title` and `--body-file`; without them `gh` prompts, which fails in a\nnon-interactive run. Pass `--head` explicitly, because `gh` otherwise infers the head\nrepository from local remotes, and a private fork's `origin` is the private repository. For the\nsame reason, pass `--repo` to every `gh` command you run in a private fork: without it,\n`gh pr edit 1` can silently overwrite PR #1 of the source repository. If that happens, the\nprior body is recoverable through the GraphQL `userContentEdits` field.\n\nAfter the PR merges, bring it downstream through `update-qm`. Preserve any existing local\nimplementation while reconciling it with the merged version; do not blindly apply the\npatch again.\n\n## If something leaked\n\nSay so immediately rather than quietly force-pushing. A deleted branch or amended commit\nstays reachable by SHA on GitHub and in every clone. Rotate whatever was exposed\n(credentials, tokens, URLs that act as capabilities) and tell whoever owns the affected\nsystem. The disclosure is the fix; rewriting history is not.\n","# upstream-pr\n\nSource forks may change core freely. This skill applies only when an upstream\ncontribution is requested; maintaining a local change does not require contributing it.\nKeep private deployment material in `deploy\u002Flayers\u002F\u003Corg>\u002F` in a private source fork or\nin a separate private deployment repository for public source. Core means the runtime,\nplugins, CLI, docs, and CI, and may also contain private details that must be scrubbed.\n\nUpstream qm is shared with organizations other than yours, and anything pushed there is\npermanent: it stays reachable by SHA in every clone and fork even after a deleted branch or\na force-push. Treat a leak as unrecoverable and spend the effort before the push.\n\nSee [`deploy\u002Flayers\u002FREADME.md`](..\u002F..\u002F..\u002Fdeploy\u002Flayers\u002FREADME.md) for the boundary, and the\n`update-qm` skill for syncing the other direction.\n\n## Where the branch will go\n\n`git remote -v`, the source tree, and repository metadata identify the situation. This decides the push\ntarget only; the scrub steps below run in every case.\n\n- `origin` is `yc-software\u002Fqm`: you are in upstream qm. Push the branch to `origin`\n  and open the PR there.\n- `origin` is a GitHub fork of qm, meaning a repository created with GitHub's fork\n  feature and living inside qm's fork network: push to `origin` and open a normal\n  cross-repo PR.\n- A standalone source fork: assume it may hold private material even if\n  `deploy\u002Flayers\u002F` looks empty, and read \"Pushing from a private fork\" below.\n- A package deployment or unrelated repository: prepare the contribution in a separate\n  clean upstream checkout; never push its history to upstream.\n\nJudge by where `origin` points, not by the repository's name. A repository named\n`\u003Corg>\u002Fqm-\u003Csomething>` in the same GitHub organization as the source may still be a\nseparate downstream repository.\n\n## Decide whether the change belongs upstream\n\nAsk what the change would mean to an organization that is not yours. It belongs upstream\nwhen it is a fix or capability in core qm that any deployment would want. It does not\nbelong upstream when it only makes sense given how your organization is set up: its tools,\nits vocabulary, its providers, its process. Keep that change downstream: deployment\nmaterial belongs in the layer or private deployment repository, while source behavior\nmay remain a local core modification.\n\nA change that is generic in substance but written against org-specific fixtures needs its\nfixtures rewritten first. Model them on the account-neutral fixtures under `deploy\u002Fstacks\u002F`\nrather than inventing values from your own deployment.\n\n## Start from a clean tree and a clean branch\n\nA branch cut from a private fork's `main` carries every organization commit in its history, and a\nPR from it exposes all of them. Cut from upstream instead.\n\n`git switch -c` carries modified and untracked files onto the new branch, where a later\n`git add -A` sweeps them into the PR. So first require a clean tree; this must print\nnothing:\n\n```bash\ngit status --porcelain\n```\n\nUse `upstream` below for the verified upstream remote; in an upstream checkout use\n`origin` instead throughout these commands and the history checks.\n\nThen:\n\n```bash\ngit fetch upstream\ngit switch -c \u003Ctopic> upstream\u002Fmain\ngit cherry-pick \u003Csha> [\u003Csha>...]\n```\n\nIf the change is entangled with organization commits and will not cherry-pick cleanly,\nreimplement it on the clean branch. That is faster than auditing a messy history, and it\nfails safe.\n\n## Scrub\n\nRun all four checks against the final branch state, and again after any amend or rebase.\n\nThe scans walk every commit rather than the net diff, because two ordinary moves defeat a\nnet diff. Moving a file out of `deploy\u002Flayers\u002F` with `git mv` is recorded as a rename, so\nthe diff never shows its contents. Adding a layer file in one commit and deleting it in a\nlater one leaves the net diff empty, but the file still ships in the branch's history.\n`git log -p --no-renames` sees both.\n\nCapture the outgoing history once, into the gitignored `.generated\u002F`:\n\n```bash\nmkdir -p .generated\u002Fupstream-pr\ngit log -p --no-renames \\\n  --format='commit %H%nauthor %an \u003C%ae>%ncommitter %cn \u003C%ce>%n%s%n%b' \\\n  upstream\u002Fmain..HEAD > .generated\u002Fupstream-pr\u002Foutgoing.txt\n```\n\n**1. No layer paths in any commit.**\n\n```bash\ngit log --name-status --no-renames --format='' upstream\u002Fmain..HEAD \\\n  | grep -E 'deploy\u002Flayers\u002F[^\u002F]+\u002F' || echo \"PASS: no layer paths\"\n```\n\nOn any hit, stop and rebuild the branch. No PR to upstream legitimately touches an\norganization's layer directory. The shared `deploy\u002Flayers\u002FREADME.md` is core and may\nchange, which is why the pattern matches only paths inside an organization's\nsubdirectory.\n\n**2. No private organization identifiers in content, messages, or authorship.** Build the\nterm list from the private deployment and local core changes, wherever they live: `qm.config.jsonc` has the org slug and public URL host,\n`.env.example` has the computed secret names, `.env` has the secret values,\n`slack-app-manifest.yml` has workspace and app names, `infra\u002Fterraform.tfvars` has cloud\naccount and repository coordinates, and `sandbox\u002F` has internal tool and system names. Add\nyour email domains, teammates' names, and any customer or partner names.\n\nAuthorship is scanned because a clone configured with an internal `user.email` stamps it on\nevery commit, and it stays visible on the upstream PR.\n\n```bash\ncat > .generated\u002Fupstream-pr\u002Fterms.txt \u003C\u003C'TERMS'\nacme\nacme.example.com\n123456789012\nTERMS\n\ntest -s .generated\u002Fupstream-pr\u002Fterms.txt || echo \"REFUSING: term list is empty\"\ngrep -inFf .generated\u002Fupstream-pr\u002Fterms.txt .generated\u002Fupstream-pr\u002Foutgoing.txt \\\n  || echo \"PASS: no identifier hits\"\n```\n\nReplace the example terms with real ones. If the placeholders are left in, the grep matches\nnothing and looks like a pass.\n\n**3. Account for every binary.** A diff shows a binary as one line with no content, so the\nidentifier scan cannot see inside it. Screenshots, `sandbox\u002Ftools\u002F\u003Cid>\u002F\u003Cbinary>`, state\nsnapshots, and PDFs all land here.\n\n```bash\ngrep '^Binary files' .generated\u002Fupstream-pr\u002Foutgoing.txt || echo \"PASS: no binaries\"\n```\n\nJustify each hit individually or drop it from the branch.\n\n**4. The surfaces git cannot see.** None of these appear in any diff:\n\n- the branch name\n- the PR title and description, including pasted error output or stack traces, which\n  routinely carry internal hostnames, account IDs, and real user identifiers\n- screenshots attached to the PR. This repository requires one for any change an operator\n  or user sees rendered, and a screenshot of your instance shows your organization's data,\n  channels, and people. Reproduce the surface against synthetic data and say that you did.\n- reproduction steps that name an internal system, and test data derived from real records\n\nThe title and description also carry no provenance. Write them from upstream's point of\nview and describe what the change does, never where it came from. That the change\noriginated in a private fork, was cherry-picked from other branches, passed your fork's\nCI, or was prepared with this skill is process, not content, and naming your fork points\nreaders at a repository they cannot see. Mention private forks only when the fork model\nitself is the subject of the change.\n\n## Pushing from a private fork\n\nA private fork is a standalone repository outside GitHub's fork network, so it cannot\nopen a cross-repo pull request.\n\nIf you have write access to upstream qm, push the topic branch there and open the PR inside\nthat repository:\n\n```bash\ngit push upstream \u003Ctopic>\ngh pr create --repo yc-software\u002Fqm --base main --head \u003Ctopic> \\\n  --title \"\u003Ctitle>\" --body-file .generated\u002Fupstream-pr\u002Fbody.md\n```\n\nIf you do not, keep a separate public GitHub fork of qm for contributions and push the\nbranch there from a different clone. Do not add that GitHub fork as a remote in the\nprivate fork's clone, where a mistyped push target would send private history to a\npublic repository.\n\nAlways pass `--title` and `--body-file`; without them `gh` prompts, which fails in a\nnon-interactive run. Pass `--head` explicitly, because `gh` otherwise infers the head\nrepository from local remotes, and a private fork's `origin` is the private repository. For the\nsame reason, pass `--repo` to every `gh` command you run in a private fork: without it,\n`gh pr edit 1` can silently overwrite PR #1 of the source repository. If that happens, the\nprior body is recoverable through the GraphQL `userContentEdits` field.\n\nAfter the PR merges, bring it downstream through `update-qm`. Preserve any existing local\nimplementation while reconciling it with the merged version; do not blindly apply the\npatch again.\n\n## If something leaked\n\nSay so immediately rather than quietly force-pushing. A deleted branch or amended commit\nstays reachable by SHA on GitHub and in every clone. Rotate whatever was exposed\n(credentials, tokens, URLs that act as capabilities) and tell whoever owns the affected\nsystem. The disclosure is the fix; rewriting history is not.\n",{"name":5,"description":7},"main","5011257b95913c04ebb800ac7bc80415546ee6bc",".codex\u002Fskills\u002Fupstream-pr",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 upstream-pr",{"tool":39,"command":40},"bunx","bunx skills add yc-software\u002Fqm --skill upstream-pr",{"tool":42,"command":43},"pnpm","pnpm dlx skills add yc-software\u002Fqm --skill upstream-pr","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fyc-software\u002Fqm\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fupstream-pr\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"agents\u002Fopenai.yaml","REFERENCE","参考文档",196,"https:\u002F\u002Fgithub.com\u002Fyc-software\u002Fqm\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fupstream-pr\u002Fagents\u002Fopenai.yaml",[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",[],[]]