[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79VSC2DVVBY9A8R2YSCVD78":3,"skill-same:01M79VSC2DVVBY9A8R2YSCVD78":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},"01M79VSC2DVVBY9A8R2YSCVD78","update-qm",null,"Update a QM source fork by merging upstream, or upgrade a package deployment dependency, and open a PR. Use when asked to \"update qm\", \"sync from upstream\", \"pull in the latest qm\".","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\u002Fupdate-qm\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: update-qm\ndescription: Update a QM source fork by merging upstream, or upgrade a package deployment dependency, and open a PR. Use when asked to \"update qm\", \"sync from upstream\", \"pull in the latest qm\".\n---\n\n# update-qm\n\nDetermine whether this is a source fork or a package deployment before choosing the\nupdate procedure. Source forks may intentionally change core; preserve those changes.\nContributing them upstream is optional.\n\n## Identify the checkout\n\nRun `git remote -v` and inspect the files and ancestry. If `origin` is `yc-software\u002Fqm`,\nthis is upstream itself, not a downstream sync target. A different origin alone does\nnot prove a source fork. A source fork has the QM source tree and shared upstream\nhistory; a package deployment has a deployment config and a pinned `@yc-software\u002Fqm`\ndependency. In a source fork with nested deployment directories, update source unless\nthe request specifically targets a nested package pin.\n\nFor a package deployment, work on a topic branch and install the requested release with\n`npm install --save-exact @yc-software\u002Fqm@\u003Cversion>`. If no version is specified, resolve\nthe current published release first. Review the package and lockfile diff, contract\nchanges, and image overrides that could keep workloads on older images. Package updates\ndo not refresh generated runbooks, skills, or vendored Terraform: compare the release's\nscaffold in a separate temporary directory and reconcile required changes without\nreinitializing or overwriting the existing deployment. Run the installed CLI's `check`,\n`doctor`, and `plan`, then open a PR in the deployment repository. Deploy only within\nthe user's requested scope, following its deployment runbook and live checks. Do not\nadd an upstream source remote or merge source into a package deployment.\n\nFor a source fork, check the `upstream` remote points to `yc-software\u002Fqm`; if absent, add\n`git remote add upstream git@github.com:yc-software\u002Fqm`. Confirm shared history before\nmerging. Never merge downstream history into upstream. Use `--repo` on every `gh`\ncommand. Inspect the actual default branch; the examples below assume `main` and must\nbe adapted if the fork deliberately uses another name. If a mirror-seeded repository\nhas a stale feature branch as its default, identify the intended base before syncing;\ndo not silently merge into the stale branch or delete existing refs.\n\n## Merge, never rebase\n\n`origin\u002Fmain` is published history that deploys and other clones track. Rebasing it onto\nupstream rewrites those commits, so always merge.\n\n```bash\ngit switch main\ngit pull --ff-only origin main\ngit fetch upstream\ngit switch -c codex\u002Fsync-upstream-\u003Cyyyy-mm-dd>\ngit log --oneline main..upstream\u002Fmain\ngit merge upstream\u002Fmain\n```\n\nRecord the commit range before resolving anything so the PR can state it. If the merge\nreports \"Already up to date\", delete the branch and report that instead of opening an empty\nPR.\n\n## Resolving conflicts\n\nRead both sides and the local commits that explain the customization. Preserve\nintentional local behavior while integrating upstream fixes; a core conflict is expected\nmaintenance, not a policy violation. Keep deployment data in the layer or separate\nprivate deployment repository where practical. Do not discard a core modification just\nbecause it is organization-specific or insist it be contributed upstream.\n\nDocument conflicts, resolutions, and remaining divergence in the sync PR. When intent\ncannot be recovered from code, tests, or history, ask the operator before choosing a\nbehavior. Review inherited CI and publishing changes for the fork's own accounts and\nregistries rather than enabling upstream workflows blindly.\n\n## Verify before opening the PR\n\nDetermine affected tests from the merged range and conflict resolutions. Run those\nlocally plus typecheck and lint; include CLI tests for CLI or deployment-contract changes.\nUse the full local suite only when the affected scope cannot be determined; otherwise\nlet CI run it. Install the locked dependencies first:\n\n```bash\nnpm ci\nnpm run typecheck\nnpm run lint\n```\n\nA sync can raise the deployment contract major, and the CLI rejects a layer config written\nfor the old one. Check each organization layer with the in-tree CLI (`npm exec qm` does not\nwork in a source checkout; the workspace symlink points at `cli\u002F`, which is unbuilt):\n\n```bash\nnode cli\u002Fbin\u002Fqm.ts check --config deploy\u002Flayers\u002F\u003Corg>\u002Fqm.config.jsonc\n```\n\nFor deployments outside the checkout, substitute their config paths. If a config reports\nan unsupported contract major, adapting it is part of the sync. Verify non-trivial behavior\nchanges in a live dev instance before opening the PR, per AGENTS.md. Production service\nbuilds must use `--build-from` against this checkout (or deliberately published custom\nimages); merging source does not update published runtime images. See the README source\ndeployment procedure.\n\n## Open the PR\n\n```bash\ngit push -u origin codex\u002Fsync-upstream-\u003Cyyyy-mm-dd>\ngh pr create --repo \u003Csource-fork> --base main \\\n  --title \"Sync upstream qm through \u003Cshort-sha>\" \\\n  --body-file .generated\u002Fsync-body.md\n```\n\nPass `--repo` to every `gh` command you run in a private fork. Without it, `gh` picks a base\nrepository from the clone's remotes and may choose `upstream`: the sync PR gets opened\nagainst qm, and `gh pr edit 1` overwrites whatever PR is number 1 in the source repository.\nThe same applies to `gh pr view`, `gh pr list`, and `gh issue`.\n\nThe description should state the upstream commit range merged, any file outside\n`deploy\u002Flayers\u002F` that conflicted and how it was resolved, and the results of the checks\nabove.\n\nWhen authorized to land a source-sync PR, preserve the upstream ancestry with a merge\ncommit (`gh pr merge --repo \u003Csource-fork> \u003Cpr> --merge`) or an ancestry-preserving\nfast-forward. Never squash or rebase a source-sync PR, even if the repository's usual\nshipping workflow uses squash: that loses the upstream merge and causes later syncs to\nrevisit already-integrated history. If repository settings prohibit merge commits,\nresolve that policy before landing; do not fall back to squash. Package dependency PRs\ncan follow the deployment repository's ordinary merge policy.\n\nIf the private fork deploys from `main`, merging this PR ships upstream's changes to production,\nso merge when someone can watch it.\n\nA source fork runs its enabled CI workflows in its own account. A sync that\nadds or changes CI changes what runs on the next PR, and workflows that need secrets the\nfork never received will fail until those are supplied.\n\n## Never do these\n\n- `git push --mirror` to seed or update a source fork. It copies unrelated branches and\n  tags, leaves initial default-branch selection implicit, and can delete destination-only\n  refs. Seed only `main` and explicitly set the default branch as the README shows.\n- Pushing a branch whose history contains organization commits to upstream. The\n  `upstream-pr` skill pushes upstream only from branches cut fresh from `upstream\u002Fmain`\n  and scrubbed.\n- Rebasing `main` onto `upstream\u002Fmain`, or force-pushing a private fork's `main`.\n- Resolving a conflict by deleting the upstream side wholesale to quiet the merge. That\n  silently diverges core from upstream, and the divergence returns as a larger conflict in\n  the next sync.\n","# update-qm\n\nDetermine whether this is a source fork or a package deployment before choosing the\nupdate procedure. Source forks may intentionally change core; preserve those changes.\nContributing them upstream is optional.\n\n## Identify the checkout\n\nRun `git remote -v` and inspect the files and ancestry. If `origin` is `yc-software\u002Fqm`,\nthis is upstream itself, not a downstream sync target. A different origin alone does\nnot prove a source fork. A source fork has the QM source tree and shared upstream\nhistory; a package deployment has a deployment config and a pinned `@yc-software\u002Fqm`\ndependency. In a source fork with nested deployment directories, update source unless\nthe request specifically targets a nested package pin.\n\nFor a package deployment, work on a topic branch and install the requested release with\n`npm install --save-exact @yc-software\u002Fqm@\u003Cversion>`. If no version is specified, resolve\nthe current published release first. Review the package and lockfile diff, contract\nchanges, and image overrides that could keep workloads on older images. Package updates\ndo not refresh generated runbooks, skills, or vendored Terraform: compare the release's\nscaffold in a separate temporary directory and reconcile required changes without\nreinitializing or overwriting the existing deployment. Run the installed CLI's `check`,\n`doctor`, and `plan`, then open a PR in the deployment repository. Deploy only within\nthe user's requested scope, following its deployment runbook and live checks. Do not\nadd an upstream source remote or merge source into a package deployment.\n\nFor a source fork, check the `upstream` remote points to `yc-software\u002Fqm`; if absent, add\n`git remote add upstream git@github.com:yc-software\u002Fqm`. Confirm shared history before\nmerging. Never merge downstream history into upstream. Use `--repo` on every `gh`\ncommand. Inspect the actual default branch; the examples below assume `main` and must\nbe adapted if the fork deliberately uses another name. If a mirror-seeded repository\nhas a stale feature branch as its default, identify the intended base before syncing;\ndo not silently merge into the stale branch or delete existing refs.\n\n## Merge, never rebase\n\n`origin\u002Fmain` is published history that deploys and other clones track. Rebasing it onto\nupstream rewrites those commits, so always merge.\n\n```bash\ngit switch main\ngit pull --ff-only origin main\ngit fetch upstream\ngit switch -c codex\u002Fsync-upstream-\u003Cyyyy-mm-dd>\ngit log --oneline main..upstream\u002Fmain\ngit merge upstream\u002Fmain\n```\n\nRecord the commit range before resolving anything so the PR can state it. If the merge\nreports \"Already up to date\", delete the branch and report that instead of opening an empty\nPR.\n\n## Resolving conflicts\n\nRead both sides and the local commits that explain the customization. Preserve\nintentional local behavior while integrating upstream fixes; a core conflict is expected\nmaintenance, not a policy violation. Keep deployment data in the layer or separate\nprivate deployment repository where practical. Do not discard a core modification just\nbecause it is organization-specific or insist it be contributed upstream.\n\nDocument conflicts, resolutions, and remaining divergence in the sync PR. When intent\ncannot be recovered from code, tests, or history, ask the operator before choosing a\nbehavior. Review inherited CI and publishing changes for the fork's own accounts and\nregistries rather than enabling upstream workflows blindly.\n\n## Verify before opening the PR\n\nDetermine affected tests from the merged range and conflict resolutions. Run those\nlocally plus typecheck and lint; include CLI tests for CLI or deployment-contract changes.\nUse the full local suite only when the affected scope cannot be determined; otherwise\nlet CI run it. Install the locked dependencies first:\n\n```bash\nnpm ci\nnpm run typecheck\nnpm run lint\n```\n\nA sync can raise the deployment contract major, and the CLI rejects a layer config written\nfor the old one. Check each organization layer with the in-tree CLI (`npm exec qm` does not\nwork in a source checkout; the workspace symlink points at `cli\u002F`, which is unbuilt):\n\n```bash\nnode cli\u002Fbin\u002Fqm.ts check --config deploy\u002Flayers\u002F\u003Corg>\u002Fqm.config.jsonc\n```\n\nFor deployments outside the checkout, substitute their config paths. If a config reports\nan unsupported contract major, adapting it is part of the sync. Verify non-trivial behavior\nchanges in a live dev instance before opening the PR, per AGENTS.md. Production service\nbuilds must use `--build-from` against this checkout (or deliberately published custom\nimages); merging source does not update published runtime images. See the README source\ndeployment procedure.\n\n## Open the PR\n\n```bash\ngit push -u origin codex\u002Fsync-upstream-\u003Cyyyy-mm-dd>\ngh pr create --repo \u003Csource-fork> --base main \\\n  --title \"Sync upstream qm through \u003Cshort-sha>\" \\\n  --body-file .generated\u002Fsync-body.md\n```\n\nPass `--repo` to every `gh` command you run in a private fork. Without it, `gh` picks a base\nrepository from the clone's remotes and may choose `upstream`: the sync PR gets opened\nagainst qm, and `gh pr edit 1` overwrites whatever PR is number 1 in the source repository.\nThe same applies to `gh pr view`, `gh pr list`, and `gh issue`.\n\nThe description should state the upstream commit range merged, any file outside\n`deploy\u002Flayers\u002F` that conflicted and how it was resolved, and the results of the checks\nabove.\n\nWhen authorized to land a source-sync PR, preserve the upstream ancestry with a merge\ncommit (`gh pr merge --repo \u003Csource-fork> \u003Cpr> --merge`) or an ancestry-preserving\nfast-forward. Never squash or rebase a source-sync PR, even if the repository's usual\nshipping workflow uses squash: that loses the upstream merge and causes later syncs to\nrevisit already-integrated history. If repository settings prohibit merge commits,\nresolve that policy before landing; do not fall back to squash. Package dependency PRs\ncan follow the deployment repository's ordinary merge policy.\n\nIf the private fork deploys from `main`, merging this PR ships upstream's changes to production,\nso merge when someone can watch it.\n\nA source fork runs its enabled CI workflows in its own account. A sync that\nadds or changes CI changes what runs on the next PR, and workflows that need secrets the\nfork never received will fail until those are supplied.\n\n## Never do these\n\n- `git push --mirror` to seed or update a source fork. It copies unrelated branches and\n  tags, leaves initial default-branch selection implicit, and can delete destination-only\n  refs. Seed only `main` and explicitly set the default branch as the README shows.\n- Pushing a branch whose history contains organization commits to upstream. The\n  `upstream-pr` skill pushes upstream only from branches cut fresh from `upstream\u002Fmain`\n  and scrubbed.\n- Rebasing `main` onto `upstream\u002Fmain`, or force-pushing a private fork's `main`.\n- Resolving a conflict by deleting the upstream side wholesale to quiet the merge. That\n  silently diverges core from upstream, and the divergence returns as a larger conflict in\n  the next sync.\n",{"name":5,"description":7},"main","5011257b95913c04ebb800ac7bc80415546ee6bc",".codex\u002Fskills\u002Fupdate-qm",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 update-qm",{"tool":39,"command":40},"bunx","bunx skills add yc-software\u002Fqm --skill update-qm",{"tool":42,"command":43},"pnpm","pnpm dlx skills add yc-software\u002Fqm --skill update-qm","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fyc-software\u002Fqm\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fupdate-qm\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"agents\u002Fopenai.yaml","REFERENCE","参考文档",210,"https:\u002F\u002Fgithub.com\u002Fyc-software\u002Fqm\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fupdate-qm\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",[],[]]