[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AYD8QQ0AHM65CG5DTCB3MB":3,"skill-same:01M7AYD8QQ0AHM65CG5DTCB3MB":61},{"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":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":38,"ownerDescription":39,"updatedAt":40,"install":41,"resources":54},"01M7AYD8QQ0AHM65CG5DTCB3MB","homelab-management",null,"Homelab infrastructure management — server audits, security hardening, Docker stack setup, Cloudflare Tunnel, Tailscale, monitoring, backups. For remote server assessment against checklists, use the audit workflow below.","oat431\u002Fhermes_config_backup","oat431","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54722120?v=4","01M7AYD07EH8SYPMYY8CGZKS22","Oralita","01M7AYD0816QDF77E3TWCRSQC9",1,"Unlicense","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Farchived\u002Fhomelab-management\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: homelab-management\ndescription: \"Homelab infrastructure management — server audits, security hardening, Docker stack setup, Cloudflare Tunnel, Tailscale, monitoring, backups. For remote server assessment against checklists, use the audit workflow below.\"\ntriggers:\n  - homelab audit or checklist\n  - remote server health check\n  - server security review\n  - infrastructure planning or architecture\n  - Docker stack setup on a server\n  - Cloudflare Tunnel or Tailscale setup\n  - self-hosted services management\n---\n\n# Homelab Management\n\n## Audit Workflow\n\nWhen the user asks to check\u002Faudit a remote server against a checklist:\n\n1. **Read the checklist first** — load the full checklist file before SSH-ing anywhere\n2. **Gather in parallel batches** — group SSH commands by concern (hardware, Docker, security, networking) and run them concurrently. SSH timeouts are common with sudo-heavy commands — break those into smaller calls\n3. **Handle `sudo` carefully** — SSH commands with `sudo` hang waiting for a password prompt. Options: (a) ask the user to set up `NOPASSWD` sudoers entry, (b) use the user's own permissions and note what needs root, (c) pipe password via `sudo -S` if the tool allows it\n4. **Compile findings in section-by-section tables** — match the checklist structure, one table per section with ✅\u002F⚠️\u002F❌\u002F❓ status indicators\n5. **Prioritize findings** — use 🔴 Critical, ⚠️ Priority, ✅ OK severity levels\n6. **End with a ranked action list** — top 5 actions, numbered by priority, with concrete next steps\n\n## Report Format\n\nThe user prefers:\n- **Status tables** per checklist section (| Item | Status | Notes |)\n- **Emoji indicators**: ✅ pass, ⚠️ needs attention, ❌ fail, ❓ cannot verify from SSH\n- **Priority callouts** before each section's critical findings\n- **Code blocks** for exact fixes (SSH config, compose YAML, commands)\n- **Top N actions list** at the end — concrete, numbered, actionable\n- **Concise notes** — no fluff, just what's wrong and how to fix it\n\n## Common Findings Reference\n\nLoad `references\u002Fssh-audit-commands.md` for the SSH command patterns used for server audits. These cover hardware info, Docker inspection, security config, networking, and backup status checks.\n\n## Architecture Diagrams\n\nWhen the user wants a visual architecture plan for their homelab:\n- Use **Mermaid** format (Obsidian-compatible)\n- Structure: `flowchart TB` with subgraphs for layers (Edge, Infrastructure, Applications, Data, Backup)\n- Use cylinder shapes `[(...)]` for databases, standard shapes for services\n- Include emoji in subgraph labels for visual clarity\n- Append to the relevant checklist\u002Fnote file, not a separate file\n\n## Security Hardening Checklist\n\nCommon issues found in homelab audits:\n\n| Finding | Why it's bad | Fix |\n|---------|-------------|-----|\n| SSH `PasswordAuthentication` commented out | Defaults to `yes` on Ubuntu — brute-forceable | Set explicit `no` in sshd_config.d\u002F |\n| Containers bound to `0.0.0.0` | Bypasses reverse proxy, directly accessible from LAN\u002Finternet | Bind to `127.0.0.1` in compose ports |\n| No firewall (UFW not configured) | All ports open by default | `ufw default deny incoming`, allow 22\u002F80\u002F443 only |\n| No backups | Data loss on disk failure | Compose files in git + DB dumps + rclone to B2 |\n| No UPS | Filesystem corruption on power loss | Small APC UPS + auto-shutdown script |\n| `fail2ban` not installed\u002Factive | No brute-force protection | `apt install fail2ban`, enable service |\n| Containers with no restart policy | Don't survive reboots | `restart: unless-stopped` in compose |\n| No resource limits on containers | One bad container OOM-kills everything | `mem_limit` and `cpus` in compose |\n| Nginx proxying HTTP to HTTPS service | \"Client sent HTTP request to HTTPS server\" error | Use `proxy_pass https:\u002F\u002F` + `proxy_ssl_verify off` |\n\n## Adding New Services (Nginx + Cloudflare Tunnel)\n\nNo DNS changes needed — wildcard `*.domain.com` in tunnel config catches all subdomains. Just add Nginx config and reload.\n\n### HTTP services (most common)\n\n```nginx\nserver {\n    server_name service.panomete.com;\n    location \u002F {\n        proxy_pass http:\u002F\u002F127.0.0.1:PORT;\n        proxy_set_header Host $host;\n        proxy_set_header X-Real-IP $remote_addr;\n        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;\n        proxy_set_header X-Forwarded-Proto $scheme;\n    }\n}\n```\n\n### HTTPS services (Portainer, Keycloak, etc.)\n\nWhen a service runs on HTTPS internally (self-signed cert):\n\n```nginx\nserver {\n    server_name container.panomete.com;\n    location \u002F {\n        proxy_pass https:\u002F\u002F127.0.0.1:PORT;\n        proxy_ssl_verify off;\n        proxy_set_header Host $host;\n        proxy_set_header X-Real-IP $remote_addr;\n        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;\n        proxy_set_header X-Forwarded-Proto $scheme;\n    }\n}\n```\n\n**Pitfall:** \"Client sent an HTTP request to an HTTPS server\" → add `proxy_pass https:\u002F\u002F` and `proxy_ssl_verify off`.\n\n## Key Decisions Pattern\n\nWhen the user wants to \"set zero\" and rebuild infra:\n1. Understand what they're building (read project specs)\n2. Propose a target architecture diagram (Mermaid)\n3. Ask clarifying questions (hardware, DB needs, backup preferences)\n4. Let them confirm before building anything\n5. Don't rush to implementation — planning first is the user's stated preference\n\n## SSH from Windows (Git Bash \u002F MSYS2)\n\nWhen `sshpass` is not available on Windows, use the `SSH_ASKPASS` trick for password-based SSH:\n\n```bash\n# Create password script (clean up after key-based auth is set up!)\ncat > \u002Ftmp\u002Fssh_pass.sh \u003C\u003C 'SCRIPT'\n#!\u002Fbin\u002Fbash\necho 'PASSWORD_HERE'\nSCRIPT\nchmod +x \u002Ftmp\u002Fssh_pass.sh\n\n# Connect using SSH_ASKPASS\nexport SSH_ASKPASS=\"\u002Ftmp\u002Fssh_pass.sh\" SSH_ASKPASS_REQUIRE=\"force\" DISPLAY=\":0\"\nssh -o StrictHostKeyChecking=no user@host \"command\" \u003C \u002Fdev\u002Fnull\n```\n\n**Critical pitfalls:**\n- **stdin must be `\u002Fdev\u002Fnull`** — otherwise SSH tries to read password from stdin instead of ASKPASS\n- **`DISPLAY=:0` is required** — SSH_ASKPASS only activates when DISPLAY is set (even on Windows\u002FMSYS2)\n- **Clean up the password script** after switching to key-based auth: `rm \u002Ftmp\u002Fssh_pass.sh`\n\n### ed25519 Key Failure (Windows OpenSSH 9.9 ↔ Ubuntu 26.04 OpenSSH 10.2)\n\nWindows Git Bash ships OpenSSH 9.9 which uses `publickey-hostbound-v00@openssh.com` extension. Ubuntu 26.04's OpenSSH 10.2 accepts the key but the signing step fails silently (\"we did not send a packet, disable method\").\n\n**Symptoms:** `ssh -vvv` shows \"Server accepts key\" followed by \"Permission denied\"\n\n**Workaround:** Generate and use an **RSA 4096** key instead of ed25519:\n```bash\nssh-keygen -t rsa -b 4096 -f ~\u002F.ssh\u002Fid_rsa -N \"\" -C \"description\"\n```\n\n### Sudo over Non-Interactive SSH\n\n`sudo` requires a TTY for password prompt. Non-interactive SSH (`ssh user@host \"sudo ...\"`) hangs or fails with \"A terminal is required to authenticate\".\n\n**Fix:** Ask the user to set up NOPASSWD sudo on the server:\n```bash\necho 'username ALL=(ALL) NOPASSWD:ALL' | sudo tee \u002Fetc\u002Fsudoers.d\u002Fusername\n```\n\nThis is needed for audit workflows that probe root-only configs (`ufw status`, `sshd -T`, `iptables -L`). Revoke after the task with `sudo rm \u002Fetc\u002Fsudoers.d\u002Fusername`.\n\n## Anonymization for Team-Shared Diagrams\n\nWhen the user shares architecture diagrams in a **team knowledge base** (not their private vault):\n- Replace project code names with generic labels: **Service A, Service B, ...**\n- Replace personal microservice names (e.g. \"Flowero Gate\") with generic terms: **API Gateway, Service Discovery, Load Balancer**\n- Add a ⚠️ note: \"Service names are anonymized — replace with actual project names in your private vault\"\n- Keep infrastructure tool names (Keycloak, Nginx, PostgreSQL) as-is — those are generic\n\n## Infrastructure Stack Preferences (Panomete)\n\n- **No public IP** — Cloudflare Tunnel for web, Tailscale for SSH\u002Fmanagement\n- **Multiple DBs** — PostgreSQL, MongoDB, Redis (possibly more)\n- **Docker Compose** for service management (not Proxmox\u002FVMs)\n- **Nginx** as reverse proxy (already established)\n- **Organized compose layout**: `application\u002F`, `database\u002F`, `storage\u002F`, `mq\u002F`\n- **Certbot not needed with Cloudflare Tunnel** — TLS terminates at Cloudflare edge, Nginx listens on localhost HTTP only\n- **OS: Ubuntu Server LTS** — user chose this over Debian for familiarity\n","# Homelab Management\n\n## Audit Workflow\n\nWhen the user asks to check\u002Faudit a remote server against a checklist:\n\n1. **Read the checklist first** — load the full checklist file before SSH-ing anywhere\n2. **Gather in parallel batches** — group SSH commands by concern (hardware, Docker, security, networking) and run them concurrently. SSH timeouts are common with sudo-heavy commands — break those into smaller calls\n3. **Handle `sudo` carefully** — SSH commands with `sudo` hang waiting for a password prompt. Options: (a) ask the user to set up `NOPASSWD` sudoers entry, (b) use the user's own permissions and note what needs root, (c) pipe password via `sudo -S` if the tool allows it\n4. **Compile findings in section-by-section tables** — match the checklist structure, one table per section with ✅\u002F⚠️\u002F❌\u002F❓ status indicators\n5. **Prioritize findings** — use 🔴 Critical, ⚠️ Priority, ✅ OK severity levels\n6. **End with a ranked action list** — top 5 actions, numbered by priority, with concrete next steps\n\n## Report Format\n\nThe user prefers:\n- **Status tables** per checklist section (| Item | Status | Notes |)\n- **Emoji indicators**: ✅ pass, ⚠️ needs attention, ❌ fail, ❓ cannot verify from SSH\n- **Priority callouts** before each section's critical findings\n- **Code blocks** for exact fixes (SSH config, compose YAML, commands)\n- **Top N actions list** at the end — concrete, numbered, actionable\n- **Concise notes** — no fluff, just what's wrong and how to fix it\n\n## Common Findings Reference\n\nLoad `references\u002Fssh-audit-commands.md` for the SSH command patterns used for server audits. These cover hardware info, Docker inspection, security config, networking, and backup status checks.\n\n## Architecture Diagrams\n\nWhen the user wants a visual architecture plan for their homelab:\n- Use **Mermaid** format (Obsidian-compatible)\n- Structure: `flowchart TB` with subgraphs for layers (Edge, Infrastructure, Applications, Data, Backup)\n- Use cylinder shapes `[(...)]` for databases, standard shapes for services\n- Include emoji in subgraph labels for visual clarity\n- Append to the relevant checklist\u002Fnote file, not a separate file\n\n## Security Hardening Checklist\n\nCommon issues found in homelab audits:\n\n| Finding | Why it's bad | Fix |\n|---------|-------------|-----|\n| SSH `PasswordAuthentication` commented out | Defaults to `yes` on Ubuntu — brute-forceable | Set explicit `no` in sshd_config.d\u002F |\n| Containers bound to `0.0.0.0` | Bypasses reverse proxy, directly accessible from LAN\u002Finternet | Bind to `127.0.0.1` in compose ports |\n| No firewall (UFW not configured) | All ports open by default | `ufw default deny incoming`, allow 22\u002F80\u002F443 only |\n| No backups | Data loss on disk failure | Compose files in git + DB dumps + rclone to B2 |\n| No UPS | Filesystem corruption on power loss | Small APC UPS + auto-shutdown script |\n| `fail2ban` not installed\u002Factive | No brute-force protection | `apt install fail2ban`, enable service |\n| Containers with no restart policy | Don't survive reboots | `restart: unless-stopped` in compose |\n| No resource limits on containers | One bad container OOM-kills everything | `mem_limit` and `cpus` in compose |\n| Nginx proxying HTTP to HTTPS service | \"Client sent HTTP request to HTTPS server\" error | Use `proxy_pass https:\u002F\u002F` + `proxy_ssl_verify off` |\n\n## Adding New Services (Nginx + Cloudflare Tunnel)\n\nNo DNS changes needed — wildcard `*.domain.com` in tunnel config catches all subdomains. Just add Nginx config and reload.\n\n### HTTP services (most common)\n\n```nginx\nserver {\n    server_name service.panomete.com;\n    location \u002F {\n        proxy_pass http:\u002F\u002F127.0.0.1:PORT;\n        proxy_set_header Host $host;\n        proxy_set_header X-Real-IP $remote_addr;\n        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;\n        proxy_set_header X-Forwarded-Proto $scheme;\n    }\n}\n```\n\n### HTTPS services (Portainer, Keycloak, etc.)\n\nWhen a service runs on HTTPS internally (self-signed cert):\n\n```nginx\nserver {\n    server_name container.panomete.com;\n    location \u002F {\n        proxy_pass https:\u002F\u002F127.0.0.1:PORT;\n        proxy_ssl_verify off;\n        proxy_set_header Host $host;\n        proxy_set_header X-Real-IP $remote_addr;\n        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;\n        proxy_set_header X-Forwarded-Proto $scheme;\n    }\n}\n```\n\n**Pitfall:** \"Client sent an HTTP request to an HTTPS server\" → add `proxy_pass https:\u002F\u002F` and `proxy_ssl_verify off`.\n\n## Key Decisions Pattern\n\nWhen the user wants to \"set zero\" and rebuild infra:\n1. Understand what they're building (read project specs)\n2. Propose a target architecture diagram (Mermaid)\n3. Ask clarifying questions (hardware, DB needs, backup preferences)\n4. Let them confirm before building anything\n5. Don't rush to implementation — planning first is the user's stated preference\n\n## SSH from Windows (Git Bash \u002F MSYS2)\n\nWhen `sshpass` is not available on Windows, use the `SSH_ASKPASS` trick for password-based SSH:\n\n```bash\n# Create password script (clean up after key-based auth is set up!)\ncat > \u002Ftmp\u002Fssh_pass.sh \u003C\u003C 'SCRIPT'\n#!\u002Fbin\u002Fbash\necho 'PASSWORD_HERE'\nSCRIPT\nchmod +x \u002Ftmp\u002Fssh_pass.sh\n\n# Connect using SSH_ASKPASS\nexport SSH_ASKPASS=\"\u002Ftmp\u002Fssh_pass.sh\" SSH_ASKPASS_REQUIRE=\"force\" DISPLAY=\":0\"\nssh -o StrictHostKeyChecking=no user@host \"command\" \u003C \u002Fdev\u002Fnull\n```\n\n**Critical pitfalls:**\n- **stdin must be `\u002Fdev\u002Fnull`** — otherwise SSH tries to read password from stdin instead of ASKPASS\n- **`DISPLAY=:0` is required** — SSH_ASKPASS only activates when DISPLAY is set (even on Windows\u002FMSYS2)\n- **Clean up the password script** after switching to key-based auth: `rm \u002Ftmp\u002Fssh_pass.sh`\n\n### ed25519 Key Failure (Windows OpenSSH 9.9 ↔ Ubuntu 26.04 OpenSSH 10.2)\n\nWindows Git Bash ships OpenSSH 9.9 which uses `publickey-hostbound-v00@openssh.com` extension. Ubuntu 26.04's OpenSSH 10.2 accepts the key but the signing step fails silently (\"we did not send a packet, disable method\").\n\n**Symptoms:** `ssh -vvv` shows \"Server accepts key\" followed by \"Permission denied\"\n\n**Workaround:** Generate and use an **RSA 4096** key instead of ed25519:\n```bash\nssh-keygen -t rsa -b 4096 -f ~\u002F.ssh\u002Fid_rsa -N \"\" -C \"description\"\n```\n\n### Sudo over Non-Interactive SSH\n\n`sudo` requires a TTY for password prompt. Non-interactive SSH (`ssh user@host \"sudo ...\"`) hangs or fails with \"A terminal is required to authenticate\".\n\n**Fix:** Ask the user to set up NOPASSWD sudo on the server:\n```bash\necho 'username ALL=(ALL) NOPASSWD:ALL' | sudo tee \u002Fetc\u002Fsudoers.d\u002Fusername\n```\n\nThis is needed for audit workflows that probe root-only configs (`ufw status`, `sshd -T`, `iptables -L`). Revoke after the task with `sudo rm \u002Fetc\u002Fsudoers.d\u002Fusername`.\n\n## Anonymization for Team-Shared Diagrams\n\nWhen the user shares architecture diagrams in a **team knowledge base** (not their private vault):\n- Replace project code names with generic labels: **Service A, Service B, ...**\n- Replace personal microservice names (e.g. \"Flowero Gate\") with generic terms: **API Gateway, Service Discovery, Load Balancer**\n- Add a ⚠️ note: \"Service names are anonymized — replace with actual project names in your private vault\"\n- Keep infrastructure tool names (Keycloak, Nginx, PostgreSQL) as-is — those are generic\n\n## Infrastructure Stack Preferences (Panomete)\n\n- **No public IP** — Cloudflare Tunnel for web, Tailscale for SSH\u002Fmanagement\n- **Multiple DBs** — PostgreSQL, MongoDB, Redis (possibly more)\n- **Docker Compose** for service management (not Proxmox\u002FVMs)\n- **Nginx** as reverse proxy (already established)\n- **Organized compose layout**: `application\u002F`, `database\u002F`, `storage\u002F`, `mq\u002F`\n- **Certbot not needed with Cloudflare Tunnel** — TLS terminates at Cloudflare edge, Nginx listens on localhost HTTP only\n- **OS: Ubuntu Server LTS** — user chose this over Debian for familiarity\n",{"name":5,"triggers":24,"description":7},[25,26,27,28,29,30,31],"homelab audit or checklist","remote server health check","server security review","infrastructure planning or architecture","Docker stack setup on a server","Cloudflare Tunnel or Tailscale setup","self-hosted services management","main","2988869c5a7d7be2225c9ea7a54a4a56a59b0d45","workflow\u002Farchived\u002Fhomelab-management",0,"https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup","https:\u002F\u002Fgithub.com\u002Foat431","https:\u002F\u002Fpanomete.com\u002F","Hope and Luck is not a part of the strategy, \r\n\r\nSoftskill produces plan Hard skill produce product.","2026-11-03 00:43:08",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add oat431\u002Fhermes_config_backup --skill homelab-management",{"tool":47,"command":48},"bunx","bunx skills add oat431\u002Fhermes_config_backup --skill homelab-management",{"tool":50,"command":51},"pnpm","pnpm dlx skills add oat431\u002Fhermes_config_backup --skill homelab-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Farchived\u002Fhomelab-management\u002FSKILL.md",true,[55],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fssh-audit-commands.md","REFERENCE","参考文档",3861,"https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Farchived\u002Fhomelab-management\u002Freferences\u002Fssh-audit-commands.md",[62,70,77,84,91,98],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AYZ2JY3NFKAPQSC39N5F3F","project-spec-docs","Fill\u002Fupdate project_spec docs (templates, MM handoffs).","MIT","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fui-ux\u002Fproject-spec-docs\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AYYRZPE7HQX7778558X52S","penpot-mcp","Penpot MCP: connect, verify, and fix streaming via nginx.","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fui-ux\u002Fpenpot-mcp\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AYYNKP61CN2281VMJDXMB5","nginx-streaming-proxy","Configure nginx for streaming endpoints (SSE, MCP, WS).","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fui-ux\u002Fnginx-streaming-proxy\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7AYYJP0MDV1D3WVEEZB3SGA","branding-ci","Use for brand\u002FCI identity, style guides, and brand docs.","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fui-ux\u002Fbranding-ci\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7AYYGCXVT97DDTCM0ZJT6F6","yuanbao","Yuanbao (元宝) groups: @mention users, query info\u002Fmembers.","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fshared-skills\u002Fyuanbao\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M7AYYC2Y65NMGMD4GQXAZMMS","slidev","Create and present web-based slidedecks for developers using Slidev with Markdown, Vue components, code highlighting, animations, and interactive features. Use when building technical presentations, conference talks, code walkthroughs, teaching materials, or developer decks.","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fshared-skills\u002Fslidev\u002FSKILL.md",[],[]]