[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AACEMTQQRFTYMF5EHRM2ZB":3,"skill-same:01M7AACEMTQQRFTYMF5EHRM2ZB":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":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7AACEMTQQRFTYMF5EHRM2ZB","update-compass",null,"Update a private compass fork by merging upstream compass into it and opening a sync PR. Use when asked to \"update compass\", \"sync from upstream\", \"pull in the latest compass\".","ibrahimsaleem\u002Fcompass","ibrahimsaleem","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F27896839?v=4","01M7AABSBMTHXGZH3XCN8AZNKS","Mohammad Ibrahim Saleem","01M7AABSCASDTKQV8ZYRDN2Z77",1,"MIT","https:\u002F\u002Fgithub.com\u002Fibrahimsaleem\u002Fcompass\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fupdate-compass\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: update-compass\ndescription: Update a private compass fork by merging upstream compass into it and opening a sync PR. Use when asked to \"update compass\", \"sync from upstream\", \"pull in the latest compass\".\n---\n\n# update-compass\n\nAn organization customizes compass from a private fork: a standalone private repository whose\nhistory begins as a clone of compass, with everything organization-specific confined to\n`deploy\u002Flayers\u002F\u003Corg>\u002F` and the rest of the tree identical to upstream. That rest is what\nthis skill means by core: every file outside the organization's layer directory,\nincluding the plugins, the CLI, the docs, and CI, not just the runtime under `src\u002F`.\nThis skill keeps a private fork current. It merges upstream compass in and opens the\nresulting sync PR.\n\nSee [`deploy\u002Flayers\u002FREADME.md`](..\u002F..\u002F..\u002Fdeploy\u002Flayers\u002FREADME.md) for the layer boundary,\nand the `upstream-pr` skill for sending changes the other direction.\n\n## Check that there is anything to sync\n\n```bash\ngit remote -v\n```\n\nIf `origin` is `ibrahimsaleem\u002Fcompass`, stop: you are in upstream compass, and a repository\ncannot merge from itself. Never merge an organization's private fork into compass.\n\nOtherwise proceed. Judge by where `origin` points, not by the repository's name.\n\nIf the clone has no `upstream` remote, add it:\n\n```bash\ngit remote add upstream git@github.com:ibrahimsaleem\u002Fcompass\n```\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 sync-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\nA merge conflict needs both histories to change the same path, and upstream has no files\nunder `deploy\u002Flayers\u002F\u003Corg>\u002F`, so an organization's layer cannot conflict with a sync.\nUpstream changing the layer contract does not conflict either; it surfaces as a `compass check`\nfailure, covered below. Every conflict in a sync therefore means the private fork edited a\nfile that exists in upstream compass, which the layer boundary exists to prevent. For each such\nfile, decide which happened:\n\n- The edit is organization-specific and should never have been in core. Take upstream's\n  side, then move the customization into `deploy\u002Flayers\u002F\u003Corg>\u002F`.\n- The edit belongs in core compass for everyone. Resolve in whichever direction keeps the tree\n  working, then use the `upstream-pr` skill to send it to compass so the next sync stops\n  conflicting on it.\n\nList these files in the PR description either way. A private fork that accumulates core edits\ngets more expensive to sync each time, and the sync PR is where that cost should be\nvisible.\n\n## Verify before opening the PR\n\nA sync changes the runtime, the CLI, and possibly the deployment contract at once, so run\neverything. The root suite does not cover the CLI, and the CLI is where a contract change\nlands:\n\n```bash\nnpm install\nnpm run typecheck\nnpm run lint\nnpm test\nnpm --prefix cli test\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 compass` does not\nwork in a source checkout; the workspace symlink points at `cli\u002F`, which is unbuilt):\n\n```bash\nnode cli\u002Fbin\u002Fcompass.ts check --config deploy\u002Flayers\u002F\u003Corg>\u002Fcompass.config.jsonc\n```\n\nIf that reports an unsupported contract major, updating the layer config to the new shape\nis part of this sync.\n\n## Open the PR\n\n```bash\ngit push -u origin sync-upstream-\u003Cyyyy-mm-dd>\ngh pr create --repo \u003Cprivate-fork> --base main \\\n  --title \"Sync upstream compass 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 compass, 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\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 private fork runs upstream's CI workflows in the organization's 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 an existing private fork. It deletes refs the destination has and the\n  source does not, discarding the organization's own branches. It is safe only for the\n  first population of an empty repository.\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-compass\n\nAn organization customizes compass from a private fork: a standalone private repository whose\nhistory begins as a clone of compass, with everything organization-specific confined to\n`deploy\u002Flayers\u002F\u003Corg>\u002F` and the rest of the tree identical to upstream. That rest is what\nthis skill means by core: every file outside the organization's layer directory,\nincluding the plugins, the CLI, the docs, and CI, not just the runtime under `src\u002F`.\nThis skill keeps a private fork current. It merges upstream compass in and opens the\nresulting sync PR.\n\nSee [`deploy\u002Flayers\u002FREADME.md`](..\u002F..\u002F..\u002Fdeploy\u002Flayers\u002FREADME.md) for the layer boundary,\nand the `upstream-pr` skill for sending changes the other direction.\n\n## Check that there is anything to sync\n\n```bash\ngit remote -v\n```\n\nIf `origin` is `ibrahimsaleem\u002Fcompass`, stop: you are in upstream compass, and a repository\ncannot merge from itself. Never merge an organization's private fork into compass.\n\nOtherwise proceed. Judge by where `origin` points, not by the repository's name.\n\nIf the clone has no `upstream` remote, add it:\n\n```bash\ngit remote add upstream git@github.com:ibrahimsaleem\u002Fcompass\n```\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 sync-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\nA merge conflict needs both histories to change the same path, and upstream has no files\nunder `deploy\u002Flayers\u002F\u003Corg>\u002F`, so an organization's layer cannot conflict with a sync.\nUpstream changing the layer contract does not conflict either; it surfaces as a `compass check`\nfailure, covered below. Every conflict in a sync therefore means the private fork edited a\nfile that exists in upstream compass, which the layer boundary exists to prevent. For each such\nfile, decide which happened:\n\n- The edit is organization-specific and should never have been in core. Take upstream's\n  side, then move the customization into `deploy\u002Flayers\u002F\u003Corg>\u002F`.\n- The edit belongs in core compass for everyone. Resolve in whichever direction keeps the tree\n  working, then use the `upstream-pr` skill to send it to compass so the next sync stops\n  conflicting on it.\n\nList these files in the PR description either way. A private fork that accumulates core edits\ngets more expensive to sync each time, and the sync PR is where that cost should be\nvisible.\n\n## Verify before opening the PR\n\nA sync changes the runtime, the CLI, and possibly the deployment contract at once, so run\neverything. The root suite does not cover the CLI, and the CLI is where a contract change\nlands:\n\n```bash\nnpm install\nnpm run typecheck\nnpm run lint\nnpm test\nnpm --prefix cli test\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 compass` does not\nwork in a source checkout; the workspace symlink points at `cli\u002F`, which is unbuilt):\n\n```bash\nnode cli\u002Fbin\u002Fcompass.ts check --config deploy\u002Flayers\u002F\u003Corg>\u002Fcompass.config.jsonc\n```\n\nIf that reports an unsupported contract major, updating the layer config to the new shape\nis part of this sync.\n\n## Open the PR\n\n```bash\ngit push -u origin sync-upstream-\u003Cyyyy-mm-dd>\ngh pr create --repo \u003Cprivate-fork> --base main \\\n  --title \"Sync upstream compass 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 compass, 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\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 private fork runs upstream's CI workflows in the organization's 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 an existing private fork. It deletes refs the destination has and the\n  source does not, discarding the organization's own branches. It is safe only for the\n  first population of an empty repository.\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","fc42b47b4c200c9faffb09cf6036570ab80a5855",".codex\u002Fskills\u002Fupdate-compass",0,"https:\u002F\u002Fgithub.com\u002Fibrahimsaleem\u002Fcompass","https:\u002F\u002Fgithub.com\u002Fibrahimsaleem","https:\u002F\u002Fibrahimsaleem-portfolio.web.app\u002F","Hi Everyone, I am Mohammad Ibrahim Saleem from Houston, USA.\r\nAI Security Engineer @AT&T and Master's in Cybersecurity from University of Houston.","2026-08-09 17:04:40",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add ibrahimsaleem\u002Fcompass --skill update-compass",{"tool":39,"command":40},"bunx","bunx skills add ibrahimsaleem\u002Fcompass --skill update-compass",{"tool":42,"command":43},"pnpm","pnpm dlx skills add ibrahimsaleem\u002Fcompass --skill update-compass","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fibrahimsaleem\u002Fcompass\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fupdate-compass\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"agents\u002Fopenai.yaml","REFERENCE","参考文档",223,"https:\u002F\u002Fgithub.com\u002Fibrahimsaleem\u002Fcompass\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fupdate-compass\u002Fagents\u002Fopenai.yaml",[54,61,69,76,83,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},"01M7AAEBY6ERY8Y6T0RP07NJP9","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\u002Fibrahimsaleem\u002Fcompass\u002Fblob\u002Fmain\u002Fskills-seed\u002Fuse-shared-credential\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":65,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7AAE990JVBGXHY2CHFK1045","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\u002Fibrahimsaleem\u002Fcompass\u002Fblob\u002Fmain\u002Fskills-seed\u002Ftaste-skill\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fibrahimsaleem\u002Fcompass\u002Fblob\u002Fmain\u002Fskills-seed\u002Ftaste-skill\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7AAE60K1ZTPMG69PT7XHTXK","publish","Publish a long-lived internal web app, site, or dashboard from the agent computer. Scope-bound (only the owner's scope, plus whoever you share it with, can reach it), immutable versions with rollback, a stable friendly link. No public URL.","https:\u002F\u002Fgithub.com\u002Fibrahimsaleem\u002Fcompass\u002Fblob\u002Fmain\u002Fskills-seed\u002Fpublish\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7AAE2QR7QHS1GXANGEQ4AM8","popular-web-designs","54 real-world design systems (Stripe, Linear, Vercel, Notion, Apple…) as ready-to-paste HTML\u002FCSS — exact colors, typography, components, and spacing for styling a page after a known brand.","https:\u002F\u002Fgithub.com\u002Fibrahimsaleem\u002Fcompass\u002Fblob\u002Fmain\u002Fskills-seed\u002Fpopular-web-designs\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7AADY6N8BKFFCWG2VS5199D","morning-digest","Assemble and deliver one short morning digest for the person who owns the cron — what changed overnight in the sources they already connected, and what it means for their day.","https:\u002F\u002Fgithub.com\u002Fibrahimsaleem\u002Fcompass\u002Fblob\u002Fmain\u002Fskills-seed\u002Fmorning-digest\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},"01M7AADV19RN7RQZM88DWFJE9D","memory","Deliberately search, add to, or curate your long-term memory with the `memory` tool — beyond the automatic recall\u002Fcapture every turn already does. Use when asked who someone is or what they're working on, when you learn a durable fact worth keeping now, or when your notebook holds stale or wrong entries you should clean up.","https:\u002F\u002Fgithub.com\u002Fibrahimsaleem\u002Fcompass\u002Fblob\u002Fmain\u002Fskills-seed\u002Fmemory\u002FSKILL.md",[],[]]