[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74FPMPDVWZAPJMFZCYH874W":3,"skill-same:01M74FPMPDVWZAPJMFZCYH874W":69},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":13,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M74FPMPDVWZAPJMFZCYH874W","github-auth",null,"GitHub auth setup: HTTPS tokens, SSH keys, gh CLI login.","lzy18001500226\u002FMoSim","lzy18001500226","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F152623587?v=4","01M71ZMEX36NK05B642131DEEK","01M71ZMEXSMX72KPVNJ572G0CM",0,"MIT","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FPlatforms\u002Fhermes-agent\u002Fskills\u002Fgithub\u002Fgithub-auth\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: github-auth\ndescription: \"GitHub auth setup: HTTPS tokens, SSH keys, gh CLI login.\"\nversion: 1.1.0\nauthor: Hermes Agent\nlicense: MIT\nplatforms: [linux, macos, windows]\nmetadata:\n  hermes:\n    tags: [GitHub, Authentication, Git, gh-cli, SSH, Setup]\n    related_skills: [github-pr-workflow, github-code-review, github-issues, github-repo-management]\n---\n\n# GitHub Authentication Setup\n\nThis skill sets up authentication so the agent can work with GitHub repositories, PRs, issues, and CI. It covers two paths:\n\n- **`git` (always available)** — uses HTTPS personal access tokens or SSH keys\n- **`gh` CLI (if installed)** — richer GitHub API access with a simpler auth flow\n\n## Detection Flow\n\nWhen a user asks you to work with GitHub, run this check first:\n\n```bash\n# Check what's available\ngit --version\ngh --version 2>\u002Fdev\u002Fnull || echo \"gh not installed\"\n\n# Check if already authenticated\ngh auth status 2>\u002Fdev\u002Fnull || echo \"gh not authenticated\"\ngit config --global credential.helper 2>\u002Fdev\u002Fnull || echo \"no git credential helper\"\n```\n\n**Decision tree:**\n1. If `gh auth status` shows authenticated → you're good, use `gh` for everything\n2. If `gh` is installed but not authenticated → use \"gh auth\" method below\n3. If `gh` is not installed → use \"git-only\" method below (no sudo needed)\n\n---\n\n## Method 1: Git-Only Authentication (No gh, No sudo)\n\nThis works on any machine with `git` installed. No root access needed.\n\n### Option A: HTTPS with Personal Access Token (Recommended)\n\nThis is the most portable method — works everywhere, no SSH config needed.\n\n**Step 1: Create a personal access token**\n\nTell the user to go to: **https:\u002F\u002Fgithub.com\u002Fsettings\u002Ftokens**\n\n- Click \"Generate new token (classic)\"\n- Give it a name like \"hermes-agent\"\n- Select scopes:\n  - `repo` (full repository access — read, write, push, PRs)\n  - `workflow` (trigger and manage GitHub Actions)\n  - `read:org` (if working with organization repos)\n- Set expiration (90 days is a good default)\n- Copy the token — it won't be shown again\n\n**Step 2: Configure git to store the token**\n\n```bash\n# Set up the credential helper to cache credentials\n# \"store\" saves to ~\u002F.git-credentials in plaintext (simple, persistent)\ngit config --global credential.helper store\n\n# Now do a test operation that triggers auth — git will prompt for credentials\n# Username: \u003Ctheir-github-username>\n# Password: \u003Cpaste the personal access token, NOT their GitHub password>\ngit ls-remote https:\u002F\u002Fgithub.com\u002F\u003Ctheir-username>\u002F\u003Cany-repo>.git\n```\n\nAfter entering credentials once, they're saved and reused for all future operations.\n\n**Alternative: cache helper (credentials expire from memory)**\n\n```bash\n# Cache in memory for 8 hours (28800 seconds) instead of saving to disk\ngit config --global credential.helper 'cache --timeout=28800'\n```\n\n**Alternative: set the token directly in the remote URL (per-repo)**\n\n```bash\n# Embed token in the remote URL (avoids credential prompts entirely)\ngit remote set-url origin https:\u002F\u002F\u003Cusername>:\u003Ctoken>@github.com\u002F\u003Cowner>\u002F\u003Crepo>.git\n```\n\n**Step 3: Configure git identity**\n\n```bash\n# Required for commits — set name and email\ngit config --global user.name \"Their Name\"\ngit config --global user.email \"their-email@example.com\"\n```\n\n**Step 4: Verify**\n\n```bash\n# Test push access (this should work without any prompts now)\ngit ls-remote https:\u002F\u002Fgithub.com\u002F\u003Ctheir-username>\u002F\u003Cany-repo>.git\n\n# Verify identity\ngit config --global user.name\ngit config --global user.email\n```\n\n### Option B: SSH Key Authentication\n\nGood for users who prefer SSH or already have keys set up.\n\n**Step 1: Check for existing SSH keys**\n\n```bash\nls -la ~\u002F.ssh\u002Fid_*.pub 2>\u002Fdev\u002Fnull || echo \"No SSH keys found\"\n```\n\n**Step 2: Generate a key if needed**\n\n```bash\n# Generate an ed25519 key (modern, secure, fast)\nssh-keygen -t ed25519 -C \"their-email@example.com\" -f ~\u002F.ssh\u002Fid_ed25519 -N \"\"\n\n# Display the public key for them to add to GitHub\ncat ~\u002F.ssh\u002Fid_ed25519.pub\n```\n\nTell the user to add the public key at: **https:\u002F\u002Fgithub.com\u002Fsettings\u002Fkeys**\n- Click \"New SSH key\"\n- Paste the public key content\n- Give it a title like \"hermes-agent-\u003Cmachine-name>\"\n\n**Step 3: Test the connection**\n\n```bash\nssh -T git@github.com\n# Expected: \"Hi \u003Cusername>! You've successfully authenticated...\"\n```\n\n**Step 4: Configure git to use SSH for GitHub**\n\n```bash\n# Rewrite HTTPS GitHub URLs to SSH automatically\ngit config --global url.\"git@github.com:\".insteadOf \"https:\u002F\u002Fgithub.com\u002F\"\n```\n\n**Step 5: Configure git identity**\n\n```bash\ngit config --global user.name \"Their Name\"\ngit config --global user.email \"their-email@example.com\"\n```\n\n---\n\n## Method 2: gh CLI Authentication\n\nIf `gh` is installed, it handles both API access and git credentials in one step.\n\n### Interactive Browser Login (Desktop)\n\n```bash\ngh auth login\n# Select: GitHub.com\n# Select: HTTPS\n# Authenticate via browser\n```\n\n### Token-Based Login (Headless \u002F SSH Servers)\n\n```bash\necho \"\u003CTHEIR_TOKEN>\" | gh auth login --with-token\n\n# Set up git credentials through gh\ngh auth setup-git\n```\n\n### Verify\n\n```bash\ngh auth status\n```\n\n---\n\n## Using the GitHub API Without gh\n\nWhen `gh` is not available, you can still access the full GitHub API using `curl` with a personal access token. This is how the other GitHub skills implement their fallbacks.\n\n### Setting the Token for API Calls\n\n```bash\n# Option 1: Export as env var (preferred — keeps it out of commands)\nexport GITHUB_TOKEN=\"\u003Ctoken>\"\n\n# Then use in curl calls:\ncurl -s -H \"Authorization: token $GITHUB_TOKEN\" \\\n  https:\u002F\u002Fapi.github.com\u002Fuser\n```\n\n### Extracting the Token from Git Credentials\n\nIf git credentials are already configured (via credential.helper store), the token can be extracted:\n\n```bash\n# Read from git credential store\ngrep \"github.com\" ~\u002F.git-credentials 2>\u002Fdev\u002Fnull | head -1 | sed 's|https:\u002F\u002F[^:]*:\\([^@]*\\)@.*|\\1|'\n```\n\n### Helper: Detect Auth Method\n\nUse this pattern at the start of any GitHub workflow:\n\n```bash\n# Try gh first, fall back to git + curl\nif command -v gh &>\u002Fdev\u002Fnull && gh auth status &>\u002Fdev\u002Fnull; then\n  echo \"AUTH_METHOD=gh\"\nelif [ -n \"$GITHUB_TOKEN\" ]; then\n  echo \"AUTH_METHOD=curl\"\nelif [ -f ~\u002F.hermes\u002F.env ] && grep -q \"^GITHUB_TOKEN=\" ~\u002F.hermes\u002F.env; then\n  export GITHUB_TOKEN=$(grep \"^GITHUB_TOKEN=\" ~\u002F.hermes\u002F.env | head -1 | cut -d= -f2 | tr -d '\\n\\r')\n  echo \"AUTH_METHOD=curl\"\nelif grep -q \"github.com\" ~\u002F.git-credentials 2>\u002Fdev\u002Fnull; then\n  export GITHUB_TOKEN=$(grep \"github.com\" ~\u002F.git-credentials | head -1 | sed 's|https:\u002F\u002F[^:]*:\\([^@]*\\)@.*|\\1|')\n  echo \"AUTH_METHOD=curl\"\nelse\n  echo \"AUTH_METHOD=none\"\n  echo \"Need to set up authentication first\"\nfi\n```\n\n---\n\n## Troubleshooting\n\n| Problem | Solution |\n|---------|----------|\n| `git push` asks for password | GitHub disabled password auth. Use a personal access token as the password, or switch to SSH |\n| `remote: Permission to X denied` | Token may lack `repo` scope — regenerate with correct scopes |\n| `fatal: Authentication failed` | Cached credentials may be stale — run `git credential reject` then re-authenticate |\n| `ssh: connect to host github.com port 22: Connection refused` | Try SSH over HTTPS port: add `Host github.com` with `Port 443` and `Hostname ssh.github.com` to `~\u002F.ssh\u002Fconfig` |\n| Credentials not persisting | Check `git config --global credential.helper` — must be `store` or `cache` |\n| Multiple GitHub accounts | Use SSH with different keys per host alias in `~\u002F.ssh\u002Fconfig`, or per-repo credential URLs |\n| `gh: command not found` + no sudo | Use git-only Method 1 above — no installation needed |\n","# GitHub Authentication Setup\n\nThis skill sets up authentication so the agent can work with GitHub repositories, PRs, issues, and CI. It covers two paths:\n\n- **`git` (always available)** — uses HTTPS personal access tokens or SSH keys\n- **`gh` CLI (if installed)** — richer GitHub API access with a simpler auth flow\n\n## Detection Flow\n\nWhen a user asks you to work with GitHub, run this check first:\n\n```bash\n# Check what's available\ngit --version\ngh --version 2>\u002Fdev\u002Fnull || echo \"gh not installed\"\n\n# Check if already authenticated\ngh auth status 2>\u002Fdev\u002Fnull || echo \"gh not authenticated\"\ngit config --global credential.helper 2>\u002Fdev\u002Fnull || echo \"no git credential helper\"\n```\n\n**Decision tree:**\n1. If `gh auth status` shows authenticated → you're good, use `gh` for everything\n2. If `gh` is installed but not authenticated → use \"gh auth\" method below\n3. If `gh` is not installed → use \"git-only\" method below (no sudo needed)\n\n---\n\n## Method 1: Git-Only Authentication (No gh, No sudo)\n\nThis works on any machine with `git` installed. No root access needed.\n\n### Option A: HTTPS with Personal Access Token (Recommended)\n\nThis is the most portable method — works everywhere, no SSH config needed.\n\n**Step 1: Create a personal access token**\n\nTell the user to go to: **https:\u002F\u002Fgithub.com\u002Fsettings\u002Ftokens**\n\n- Click \"Generate new token (classic)\"\n- Give it a name like \"hermes-agent\"\n- Select scopes:\n  - `repo` (full repository access — read, write, push, PRs)\n  - `workflow` (trigger and manage GitHub Actions)\n  - `read:org` (if working with organization repos)\n- Set expiration (90 days is a good default)\n- Copy the token — it won't be shown again\n\n**Step 2: Configure git to store the token**\n\n```bash\n# Set up the credential helper to cache credentials\n# \"store\" saves to ~\u002F.git-credentials in plaintext (simple, persistent)\ngit config --global credential.helper store\n\n# Now do a test operation that triggers auth — git will prompt for credentials\n# Username: \u003Ctheir-github-username>\n# Password: \u003Cpaste the personal access token, NOT their GitHub password>\ngit ls-remote https:\u002F\u002Fgithub.com\u002F\u003Ctheir-username>\u002F\u003Cany-repo>.git\n```\n\nAfter entering credentials once, they're saved and reused for all future operations.\n\n**Alternative: cache helper (credentials expire from memory)**\n\n```bash\n# Cache in memory for 8 hours (28800 seconds) instead of saving to disk\ngit config --global credential.helper 'cache --timeout=28800'\n```\n\n**Alternative: set the token directly in the remote URL (per-repo)**\n\n```bash\n# Embed token in the remote URL (avoids credential prompts entirely)\ngit remote set-url origin https:\u002F\u002F\u003Cusername>:\u003Ctoken>@github.com\u002F\u003Cowner>\u002F\u003Crepo>.git\n```\n\n**Step 3: Configure git identity**\n\n```bash\n# Required for commits — set name and email\ngit config --global user.name \"Their Name\"\ngit config --global user.email \"their-email@example.com\"\n```\n\n**Step 4: Verify**\n\n```bash\n# Test push access (this should work without any prompts now)\ngit ls-remote https:\u002F\u002Fgithub.com\u002F\u003Ctheir-username>\u002F\u003Cany-repo>.git\n\n# Verify identity\ngit config --global user.name\ngit config --global user.email\n```\n\n### Option B: SSH Key Authentication\n\nGood for users who prefer SSH or already have keys set up.\n\n**Step 1: Check for existing SSH keys**\n\n```bash\nls -la ~\u002F.ssh\u002Fid_*.pub 2>\u002Fdev\u002Fnull || echo \"No SSH keys found\"\n```\n\n**Step 2: Generate a key if needed**\n\n```bash\n# Generate an ed25519 key (modern, secure, fast)\nssh-keygen -t ed25519 -C \"their-email@example.com\" -f ~\u002F.ssh\u002Fid_ed25519 -N \"\"\n\n# Display the public key for them to add to GitHub\ncat ~\u002F.ssh\u002Fid_ed25519.pub\n```\n\nTell the user to add the public key at: **https:\u002F\u002Fgithub.com\u002Fsettings\u002Fkeys**\n- Click \"New SSH key\"\n- Paste the public key content\n- Give it a title like \"hermes-agent-\u003Cmachine-name>\"\n\n**Step 3: Test the connection**\n\n```bash\nssh -T git@github.com\n# Expected: \"Hi \u003Cusername>! You've successfully authenticated...\"\n```\n\n**Step 4: Configure git to use SSH for GitHub**\n\n```bash\n# Rewrite HTTPS GitHub URLs to SSH automatically\ngit config --global url.\"git@github.com:\".insteadOf \"https:\u002F\u002Fgithub.com\u002F\"\n```\n\n**Step 5: Configure git identity**\n\n```bash\ngit config --global user.name \"Their Name\"\ngit config --global user.email \"their-email@example.com\"\n```\n\n---\n\n## Method 2: gh CLI Authentication\n\nIf `gh` is installed, it handles both API access and git credentials in one step.\n\n### Interactive Browser Login (Desktop)\n\n```bash\ngh auth login\n# Select: GitHub.com\n# Select: HTTPS\n# Authenticate via browser\n```\n\n### Token-Based Login (Headless \u002F SSH Servers)\n\n```bash\necho \"\u003CTHEIR_TOKEN>\" | gh auth login --with-token\n\n# Set up git credentials through gh\ngh auth setup-git\n```\n\n### Verify\n\n```bash\ngh auth status\n```\n\n---\n\n## Using the GitHub API Without gh\n\nWhen `gh` is not available, you can still access the full GitHub API using `curl` with a personal access token. This is how the other GitHub skills implement their fallbacks.\n\n### Setting the Token for API Calls\n\n```bash\n# Option 1: Export as env var (preferred — keeps it out of commands)\nexport GITHUB_TOKEN=\"\u003Ctoken>\"\n\n# Then use in curl calls:\ncurl -s -H \"Authorization: token $GITHUB_TOKEN\" \\\n  https:\u002F\u002Fapi.github.com\u002Fuser\n```\n\n### Extracting the Token from Git Credentials\n\nIf git credentials are already configured (via credential.helper store), the token can be extracted:\n\n```bash\n# Read from git credential store\ngrep \"github.com\" ~\u002F.git-credentials 2>\u002Fdev\u002Fnull | head -1 | sed 's|https:\u002F\u002F[^:]*:\\([^@]*\\)@.*|\\1|'\n```\n\n### Helper: Detect Auth Method\n\nUse this pattern at the start of any GitHub workflow:\n\n```bash\n# Try gh first, fall back to git + curl\nif command -v gh &>\u002Fdev\u002Fnull && gh auth status &>\u002Fdev\u002Fnull; then\n  echo \"AUTH_METHOD=gh\"\nelif [ -n \"$GITHUB_TOKEN\" ]; then\n  echo \"AUTH_METHOD=curl\"\nelif [ -f ~\u002F.hermes\u002F.env ] && grep -q \"^GITHUB_TOKEN=\" ~\u002F.hermes\u002F.env; then\n  export GITHUB_TOKEN=$(grep \"^GITHUB_TOKEN=\" ~\u002F.hermes\u002F.env | head -1 | cut -d= -f2 | tr -d '\\n\\r')\n  echo \"AUTH_METHOD=curl\"\nelif grep -q \"github.com\" ~\u002F.git-credentials 2>\u002Fdev\u002Fnull; then\n  export GITHUB_TOKEN=$(grep \"github.com\" ~\u002F.git-credentials | head -1 | sed 's|https:\u002F\u002F[^:]*:\\([^@]*\\)@.*|\\1|')\n  echo \"AUTH_METHOD=curl\"\nelse\n  echo \"AUTH_METHOD=none\"\n  echo \"Need to set up authentication first\"\nfi\n```\n\n---\n\n## Troubleshooting\n\n| Problem | Solution |\n|---------|----------|\n| `git push` asks for password | GitHub disabled password auth. Use a personal access token as the password, or switch to SSH |\n| `remote: Permission to X denied` | Token may lack `repo` scope — regenerate with correct scopes |\n| `fatal: Authentication failed` | Cached credentials may be stale — run `git credential reject` then re-authenticate |\n| `ssh: connect to host github.com port 22: Connection refused` | Try SSH over HTTPS port: add `Host github.com` with `Port 443` and `Hostname ssh.github.com` to `~\u002F.ssh\u002Fconfig` |\n| Credentials not persisting | Check `git config --global credential.helper` — must be `store` or `cache` |\n| Multiple GitHub accounts | Use SSH with different keys per host alias in `~\u002F.ssh\u002Fconfig`, or per-repo credential URLs |\n| `gh: command not found` + no sudo | Use git-only Method 1 above — no installation needed |\n",{"name":5,"author":23,"license":14,"version":24,"metadata":25,"platforms":39,"description":7},"Hermes Agent","1.1.0",{"hermes":26},{"tags":27,"related_skills":34},[28,29,30,31,32,33],"GitHub","Authentication","Git","gh-cli","SSH","Setup",[35,36,37,38],"github-pr-workflow","github-code-review","github-issues","github-repo-management",[40,41,42],"linux","macos","windows","main","e0ec177d00f087cb04e90206b2f7d3aa2f5a1350","References\u002FAgent\u002FPlatforms\u002Fhermes-agent\u002Fskills\u002Fgithub\u002Fgithub-auth","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim","https:\u002F\u002Fgithub.com\u002Flzy18001500226","2026-08-31 23:29:00",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add lzy18001500226\u002FMoSim --skill github-auth",{"tool":55,"command":56},"bunx","bunx skills add lzy18001500226\u002FMoSim --skill github-auth",{"tool":58,"command":59},"pnpm","pnpm dlx skills add lzy18001500226\u002FMoSim --skill github-auth","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FPlatforms\u002Fhermes-agent\u002Fskills\u002Fgithub\u002Fgithub-auth\u002FSKILL.md",true,[63],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"scripts\u002Fgh-env.sh","SCRIPT","脚本",2574,"https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FPlatforms\u002Fhermes-agent\u002Fskills\u002Fgithub\u002Fgithub-auth\u002Fscripts\u002Fgh-env.sh",[70,80,88,96,104,112],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":74,"licenseFileUrl":75,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":79},"01M78RK6JGRPTD3TDSMTQWDQ9P","skill-installer","Install Codex skills into $CODEX_HOME\u002Fskills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fskill-installer\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fskill-installer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":74,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":79},"01M78RK29KVRDQXSMVZX1GQTJN","skill-creator","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fskill-creator\u002Flicense.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":74,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":79},"01M78RJPF3210Y5DA9VJ6JMMG6","openai-docs","Use for Codex models\u002Fpricing, scheduled tasks, skills, settings, setup, troubleshooting, customization, automations, and self-knowledge—including 'you,' 'your,' 'this app,' or 'this coding agent' when they refer to Codex—and for OpenAI APIs\u002Fproducts and ChatGPT Work. Also use for model choice\u002Fmigration, prompting, SDKs, Responses, Realtime, agents, evals, and Chat\u002FWork\u002FCodex comparisons. Do not use for generic app\u002Fsoftware tasks that merely mention Codex.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fopenai-docs\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fopenai-docs\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":74,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":79},"01M78RJH7X67C5AY8ZVS7RQNWJ","imagegen","Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG\u002Fvector\u002Fcode-native assets, extending an established icon or logo system, or building the visual directly in HTML\u002FCSS\u002Fcanvas.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fimagegen\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fimagegen\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":74,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":79},"01M78RBBAYMJ6T3ZMAYHCFM6G7","skill-creator-cc","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FWorkflow\u002Fokwinds\u002Fmiscellany\u002Fagent\u002Fskills\u002Fskill-creator-cc\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FWorkflow\u002Fokwinds\u002Fmiscellany\u002Fagent\u002Fskills\u002Fskill-creator-cc\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":116,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":120},"01M76VV9V2R9FZTVGMJZV7Y996","prd-writing-guide","Write complete, unambiguous PRDs that development teams can implement without guesswork. Includes requirement discovery framework, structured documentation methodology, completeness checklists, and common pitfall avoidance. Use when: writing new PRDs, reviewing PRD drafts, validating requirement completeness, preparing for engineering handoff. Triggers: 'write PRD', '写PRD', '产品需求文档', '需求文档', '需求规格', '需求评审', '完善需求', 'create requirements doc', 'product requirements', 'feature spec', 'requirements document'. Anti-triggers: 'technical design doc', 'architecture design', 'implementation plan', 'API design', '架构设计', '技术方案', '实现方案', '接口设计'.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FWorkflow\u002Fokwinds\u002Fmiscellany\u002Fagent\u002Fskills\u002Fprd-writing-guide\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FWorkflow\u002Fokwinds\u002Fmiscellany\u002Fagent\u002Fskills\u002Fprd-writing-guide\u002FSKILL.md",[],[],"2026-11-12 13:55:43"]