[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73GGEB67BWP0X5BZDREVMHT":3,"skill-same:01M73GGEB67BWP0X5BZDREVMHT":49},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M73GGEB67BWP0X5BZDREVMHT","uncloud",null,"Use when managing an Uncloud cluster — deploying services, configuring Caddy ingress, adding static proxy routes for non-cluster devices, publishing ports, scaling, inspecting logs, or managing machines and volumes with the `uc` CLI.","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Funcloud\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: uncloud\ndescription: Use when managing an Uncloud cluster — deploying services, configuring Caddy ingress, adding static proxy routes for non-cluster devices, publishing ports, scaling, inspecting logs, or managing machines and volumes with the `uc` CLI.\norigin: ECC\n---\n\n# Uncloud Cluster Management\n\nReference for the `uc` CLI — a decentralised self-hosting platform using Docker containers, WireGuard mesh networking, and Caddy reverse proxy.\n\n## When to Activate\n\nUse this skill when working with Uncloud clusters, especially when:\n- Bootstrapping or joining machines with `uc machine`\n- Deploying services from Compose files with `uc deploy`\n- Publishing HTTP, HTTPS, TCP, or UDP ports through Uncloud\n- Configuring Caddy ingress with `x-caddy`, `x-ports`, or `--caddyfile`\n- Routing external LAN devices through the cluster proxy\n- Inspecting logs, service state, volumes, DNS, or machine placement\n\n## How It Works\n\nUncloud runs Docker services across peer machines connected by a WireGuard mesh. Each machine is an equal cluster member; services communicate on the overlay network and Caddy runs globally to terminate public HTTP\u002FHTTPS traffic. Compose files can use Uncloud extensions for ingress, placement, and generated Caddy configuration, while the `uc` CLI handles image distribution, scheduling, scaling, logs, and cluster state.\n\n## Examples\n\n```bash\nuc machine init user@host --name machine-1\nuc service run --name web -p app.example.com:8080\u002Fhttps nginx:latest\nuc deploy\n```\n\n## Core Concepts\n\n- **No central control plane** — all machines are equal peers connected by WireGuard\n- **Caddy** runs as a global service on every machine; auto-obtains TLS from Let's Encrypt\n- **Overlay network** — services communicate via `10.210.0.0\u002F16` by default; DNS provided inside the mesh\n- **Caddyfile is autogenerated** — never edit it directly; use `x-caddy` \u002F `--caddyfile` instead\n\n---\n\n## CLI Quick Reference\n\n### Machines\n\n| Command | Purpose |\n|---------|---------|\n| `uc machine init user@host` | Bootstrap first machine \u002F new cluster |\n| `uc machine add user@host` | Join machine to existing cluster |\n| `uc machine ls` | List machines |\n| `uc machine update NAME --public-ip IP` | Update public IP for ingress |\n| `uc machine rm NAME` | Remove machine |\n\nKey `init` flags: `--name`, `--network 10.210.0.0\u002F16`, `--no-caddy`, `--no-dns`, `--public-ip auto\\|IP\\|none`\n\n### Services\n\n| Command | Purpose |\n|---------|---------|\n| `uc service ls` \u002F `uc ls` | List services |\n| `uc service run IMAGE` | Run a single container service |\n| `uc deploy` | Deploy from `compose.yaml` |\n| `uc deploy --no-build` | Deploy already-pushed images without rebuilding |\n| `uc deploy --recreate` | Force service recreation |\n| `uc scale SERVICE N` | Set replica count |\n| `uc service logs SERVICE` | View logs |\n| `uc service exec SERVICE` | Shell into container |\n| `uc service inspect SERVICE` | Detailed info |\n| `uc service rm SERVICE` | Remove service (keeps named volumes) |\n| `uc ps` | All containers across cluster |\n\n### Images\n\n```bash\nuc image push myapp:latest                    # Push local image to all machines\nuc image push myapp:latest -m machine1,machine2  # Push to specific machines\nuc images                                     # List images in cluster\n```\n\n### Volumes\n\n```bash\nuc volume ls                  # All volumes\nuc volume ls -m machine1      # On specific machine\nuc volume create NAME -m MACHINE\nuc volume rm NAME\n```\n\n### Caddy\n\n```bash\nuc caddy config    # Show current generated Caddyfile (read-only)\nuc caddy deploy    # Deploy\u002Fupgrade Caddy across cluster\n```\n\n### DNS & Context\n\n```bash\nuc dns show        # Show reserved *.uncld.dev domain\nuc dns reserve     # Reserve a new domain\nuc ctx ls          # List cluster contexts\nuc ctx use prod    # Switch context\n```\n\n---\n\n## Port Publishing\n\n### HTTP\u002FHTTPS (via Caddy reverse proxy)\n\n```\n-p [hostname:]container_port[\u002Fprotocol]\n```\n\n| Example | Meaning |\n|---------|---------|\n| `-p 8080\u002Fhttps` | HTTPS with auto `service-name.cluster-domain` hostname |\n| `-p app.example.com:8080\u002Fhttps` | HTTPS with custom hostname |\n| `-p 8080\u002Fhttp` | HTTP only, no TLS |\n\n### TCP\u002FUDP (host-bound, bypasses Caddy)\n\n```\n-p [host_ip:]host_port:container_port[\u002Fprotocol]@host\n```\n\n| Example | Meaning |\n|---------|---------|\n| `-p 5432:5432@host` | TCP 5432 on all interfaces |\n| `-p 127.0.0.1:5432:5432@host` | TCP 5432 loopback only |\n| `-p 53:5353\u002Fudp@host` | UDP |\n\n---\n\n## Compose File Extensions\n\nUncloud adds these extensions on top of Docker Compose:\n\n### `x-ports` — publish ports with domains\n\n```yaml\nservices:\n  app:\n    image: app:latest\n    x-ports:\n      - example.com:8000\u002Fhttps\n      - www.example.com:8000\u002Fhttps\n      - api.example.com:9000\u002Fhttps\n```\n\n### `x-caddy` — custom Caddy config for service\n\n```yaml\nservices:\n  app:\n    image: app:latest\n    x-caddy: |\n      example.com {\n        redir https:\u002F\u002Fwww.example.com{uri} permanent\n      }\n      www.example.com {\n        reverse_proxy {{upstreams 8000}} {\n          import common_proxy\n        }\n        basic_auth \u002Fadmin\u002F* {\n          admin $2a$14$...\n        }\n      }\n```\n\nTemplate functions available inside `x-caddy`:\n- `{{upstreams [service] [port]}}` — healthy container IPs\n- `{{.Name}}` — service name\n- `{{.Upstreams}}` — map of all services → IPs\n\n### `x-machines` — placement constraints\n\n```yaml\nservices:\n  db:\n    image: postgres:18\n    x-machines: db-machine          # Single machine name\n  app:\n    image: app:latest\n    x-machines:\n      - machine-1\n      - machine-2\n```\n\n### Full multi-service example\n\n```yaml\nservices:\n  api:\n    build: .\u002Fapi\n    x-ports:\n      - api.example.com:3000\u002Fhttps\n    environment:\n      DATABASE_URL: postgres:\u002F\u002Fdb:5432\u002Fmydb\n\n  web:\n    build: .\u002Fweb\n    x-ports:\n      - example.com:8000\u002Fhttps\n      - www.example.com:8000\u002Fhttps\n    environment:\n      API_URL: http:\u002F\u002Fapi:3000\n\n  db:\n    image: postgres:18\n    environment:\n      POSTGRES_PASSWORD: ${DB_PASSWORD}\n    volumes:\n      - db-data:\u002Fvar\u002Flib\u002Fpostgresql\u002Fdata\n    x-machines: db-machine\n\nvolumes:\n  db-data:\n```\n\n---\n\n## Routing to External (Non-Cluster) Devices\n\nTo expose an external device (e.g. BMC, NAS, router UI) via Caddy without running a real container:\n\n**1. Create a Caddyfile snippet** (e.g. `~\u002Fdevice.caddyfile`):\n\n```caddyfile\nhttps:\u002F\u002Fdevice.example.com {\n    reverse_proxy https:\u002F\u002F192.168.1.x {\n        transport http {\n            tls_insecure_skip_verify   # needed for self-signed BMC certs\n        }\n    }\n    log\n}\n```\n\nFor plaintext upstream: `reverse_proxy http:\u002F\u002F192.168.1.x:port`\n\n**2. Register as a named service with no-op container:**\n\n```bash\nuc service run \\\n  --name device-bmc \\\n  --caddyfile ~\u002Fdevice.caddyfile \\\n  registry.k8s.io\u002Fpause:3.9\n```\n\n`pause` is a minimal no-op container — it does nothing, but gives Uncloud a service entry to attach the Caddyfile to.\n\n**3. Verify:**\n\n```bash\nuc caddy config   # device.example.com block should appear\n```\n\n> `--caddyfile` cannot be combined with non-`@host` published ports.\n\n**DNS tip:** A wildcard record (`*.yourdomain.com → cluster-public-ip`) means any new subdomain works immediately — no DNS change needed per service.\n\n---\n\n## Service DNS (Internal)\n\nServices inside the cluster resolve each other by name:\n\n| DNS name | Resolves to |\n|----------|------------|\n| `service-name` | Any healthy container |\n| `service-name.internal` | Same |\n| `rr.service-name.internal` | Round-robin |\n| `nearest.service-name.internal` | Machine-local first |\n\n---\n\n## Scaling & Global Services\n\n```bash\nuc scale web 5    # 5 replicas (spread across machines)\nuc scale web 1    # Scale down\n```\n\n```yaml\nservices:\n  caddy:\n    deploy:\n      mode: global   # One container on every machine\n```\n\n---\n\n## Image Tag Templates (in compose.yaml)\n\n```yaml\nimage: myapp:{{gitdate \"20060102\"}}.{{gitsha 7}}\nimage: myapp:{{gitsha 7}}.${GITHUB_RUN_ID:-local}\n```\n\n| Function | Output |\n|----------|--------|\n| `{{gitsha N}}` | First N chars of commit SHA |\n| `{{gitdate \"format\"}}` | Git commit date in Go format |\n| `{{date \"format\"}}` | Current date |\n\n---\n\n## Common Workflows\n\n**Deploy from source:**\n```bash\nuc deploy                          # Build + push + deploy\nuc build --push && uc deploy --no-build   # Separate steps\n```\n\n**Inspect a service:**\n```bash\nuc inspect web\nuc logs -f web\nuc logs --since 1h web\nuc exec web                        # Opens shell\nuc exec web \u002Fbin\u002Fsh -c \"env\"       # Run specific command\n```\n\n**Zero-downtime deploys** happen automatically; Uncloud waits for health checks before terminating old containers.\n\n**Force recreate:**\n```bash\nuc deploy --recreate\n```\n\n---\n\n## Common Mistakes\n\n| Mistake | Fix |\n|---------|-----|\n| Editing the Caddyfile directly | Use `x-caddy` in compose or `--caddyfile` on `uc service run` |\n| Proxying an HTTPS upstream with self-signed cert | Add `transport http { tls_insecure_skip_verify }` |\n| `uc caddy config` shows no user-defined blocks | Caddy admin socket unreachable — check `uc inspect caddy` and `uc logs caddy` |\n| Service can't reach external LAN IP from container | Verify Caddy container's host can route to target network |\n| Volumes lost after `uc service rm` | Named volumes persist; only anonymous volumes are auto-removed |\n","# Uncloud Cluster Management\n\nReference for the `uc` CLI — a decentralised self-hosting platform using Docker containers, WireGuard mesh networking, and Caddy reverse proxy.\n\n## When to Activate\n\nUse this skill when working with Uncloud clusters, especially when:\n- Bootstrapping or joining machines with `uc machine`\n- Deploying services from Compose files with `uc deploy`\n- Publishing HTTP, HTTPS, TCP, or UDP ports through Uncloud\n- Configuring Caddy ingress with `x-caddy`, `x-ports`, or `--caddyfile`\n- Routing external LAN devices through the cluster proxy\n- Inspecting logs, service state, volumes, DNS, or machine placement\n\n## How It Works\n\nUncloud runs Docker services across peer machines connected by a WireGuard mesh. Each machine is an equal cluster member; services communicate on the overlay network and Caddy runs globally to terminate public HTTP\u002FHTTPS traffic. Compose files can use Uncloud extensions for ingress, placement, and generated Caddy configuration, while the `uc` CLI handles image distribution, scheduling, scaling, logs, and cluster state.\n\n## Examples\n\n```bash\nuc machine init user@host --name machine-1\nuc service run --name web -p app.example.com:8080\u002Fhttps nginx:latest\nuc deploy\n```\n\n## Core Concepts\n\n- **No central control plane** — all machines are equal peers connected by WireGuard\n- **Caddy** runs as a global service on every machine; auto-obtains TLS from Let's Encrypt\n- **Overlay network** — services communicate via `10.210.0.0\u002F16` by default; DNS provided inside the mesh\n- **Caddyfile is autogenerated** — never edit it directly; use `x-caddy` \u002F `--caddyfile` instead\n\n---\n\n## CLI Quick Reference\n\n### Machines\n\n| Command | Purpose |\n|---------|---------|\n| `uc machine init user@host` | Bootstrap first machine \u002F new cluster |\n| `uc machine add user@host` | Join machine to existing cluster |\n| `uc machine ls` | List machines |\n| `uc machine update NAME --public-ip IP` | Update public IP for ingress |\n| `uc machine rm NAME` | Remove machine |\n\nKey `init` flags: `--name`, `--network 10.210.0.0\u002F16`, `--no-caddy`, `--no-dns`, `--public-ip auto\\|IP\\|none`\n\n### Services\n\n| Command | Purpose |\n|---------|---------|\n| `uc service ls` \u002F `uc ls` | List services |\n| `uc service run IMAGE` | Run a single container service |\n| `uc deploy` | Deploy from `compose.yaml` |\n| `uc deploy --no-build` | Deploy already-pushed images without rebuilding |\n| `uc deploy --recreate` | Force service recreation |\n| `uc scale SERVICE N` | Set replica count |\n| `uc service logs SERVICE` | View logs |\n| `uc service exec SERVICE` | Shell into container |\n| `uc service inspect SERVICE` | Detailed info |\n| `uc service rm SERVICE` | Remove service (keeps named volumes) |\n| `uc ps` | All containers across cluster |\n\n### Images\n\n```bash\nuc image push myapp:latest                    # Push local image to all machines\nuc image push myapp:latest -m machine1,machine2  # Push to specific machines\nuc images                                     # List images in cluster\n```\n\n### Volumes\n\n```bash\nuc volume ls                  # All volumes\nuc volume ls -m machine1      # On specific machine\nuc volume create NAME -m MACHINE\nuc volume rm NAME\n```\n\n### Caddy\n\n```bash\nuc caddy config    # Show current generated Caddyfile (read-only)\nuc caddy deploy    # Deploy\u002Fupgrade Caddy across cluster\n```\n\n### DNS & Context\n\n```bash\nuc dns show        # Show reserved *.uncld.dev domain\nuc dns reserve     # Reserve a new domain\nuc ctx ls          # List cluster contexts\nuc ctx use prod    # Switch context\n```\n\n---\n\n## Port Publishing\n\n### HTTP\u002FHTTPS (via Caddy reverse proxy)\n\n```\n-p [hostname:]container_port[\u002Fprotocol]\n```\n\n| Example | Meaning |\n|---------|---------|\n| `-p 8080\u002Fhttps` | HTTPS with auto `service-name.cluster-domain` hostname |\n| `-p app.example.com:8080\u002Fhttps` | HTTPS with custom hostname |\n| `-p 8080\u002Fhttp` | HTTP only, no TLS |\n\n### TCP\u002FUDP (host-bound, bypasses Caddy)\n\n```\n-p [host_ip:]host_port:container_port[\u002Fprotocol]@host\n```\n\n| Example | Meaning |\n|---------|---------|\n| `-p 5432:5432@host` | TCP 5432 on all interfaces |\n| `-p 127.0.0.1:5432:5432@host` | TCP 5432 loopback only |\n| `-p 53:5353\u002Fudp@host` | UDP |\n\n---\n\n## Compose File Extensions\n\nUncloud adds these extensions on top of Docker Compose:\n\n### `x-ports` — publish ports with domains\n\n```yaml\nservices:\n  app:\n    image: app:latest\n    x-ports:\n      - example.com:8000\u002Fhttps\n      - www.example.com:8000\u002Fhttps\n      - api.example.com:9000\u002Fhttps\n```\n\n### `x-caddy` — custom Caddy config for service\n\n```yaml\nservices:\n  app:\n    image: app:latest\n    x-caddy: |\n      example.com {\n        redir https:\u002F\u002Fwww.example.com{uri} permanent\n      }\n      www.example.com {\n        reverse_proxy {{upstreams 8000}} {\n          import common_proxy\n        }\n        basic_auth \u002Fadmin\u002F* {\n          admin $2a$14$...\n        }\n      }\n```\n\nTemplate functions available inside `x-caddy`:\n- `{{upstreams [service] [port]}}` — healthy container IPs\n- `{{.Name}}` — service name\n- `{{.Upstreams}}` — map of all services → IPs\n\n### `x-machines` — placement constraints\n\n```yaml\nservices:\n  db:\n    image: postgres:18\n    x-machines: db-machine          # Single machine name\n  app:\n    image: app:latest\n    x-machines:\n      - machine-1\n      - machine-2\n```\n\n### Full multi-service example\n\n```yaml\nservices:\n  api:\n    build: .\u002Fapi\n    x-ports:\n      - api.example.com:3000\u002Fhttps\n    environment:\n      DATABASE_URL: postgres:\u002F\u002Fdb:5432\u002Fmydb\n\n  web:\n    build: .\u002Fweb\n    x-ports:\n      - example.com:8000\u002Fhttps\n      - www.example.com:8000\u002Fhttps\n    environment:\n      API_URL: http:\u002F\u002Fapi:3000\n\n  db:\n    image: postgres:18\n    environment:\n      POSTGRES_PASSWORD: ${DB_PASSWORD}\n    volumes:\n      - db-data:\u002Fvar\u002Flib\u002Fpostgresql\u002Fdata\n    x-machines: db-machine\n\nvolumes:\n  db-data:\n```\n\n---\n\n## Routing to External (Non-Cluster) Devices\n\nTo expose an external device (e.g. BMC, NAS, router UI) via Caddy without running a real container:\n\n**1. Create a Caddyfile snippet** (e.g. `~\u002Fdevice.caddyfile`):\n\n```caddyfile\nhttps:\u002F\u002Fdevice.example.com {\n    reverse_proxy https:\u002F\u002F192.168.1.x {\n        transport http {\n            tls_insecure_skip_verify   # needed for self-signed BMC certs\n        }\n    }\n    log\n}\n```\n\nFor plaintext upstream: `reverse_proxy http:\u002F\u002F192.168.1.x:port`\n\n**2. Register as a named service with no-op container:**\n\n```bash\nuc service run \\\n  --name device-bmc \\\n  --caddyfile ~\u002Fdevice.caddyfile \\\n  registry.k8s.io\u002Fpause:3.9\n```\n\n`pause` is a minimal no-op container — it does nothing, but gives Uncloud a service entry to attach the Caddyfile to.\n\n**3. Verify:**\n\n```bash\nuc caddy config   # device.example.com block should appear\n```\n\n> `--caddyfile` cannot be combined with non-`@host` published ports.\n\n**DNS tip:** A wildcard record (`*.yourdomain.com → cluster-public-ip`) means any new subdomain works immediately — no DNS change needed per service.\n\n---\n\n## Service DNS (Internal)\n\nServices inside the cluster resolve each other by name:\n\n| DNS name | Resolves to |\n|----------|------------|\n| `service-name` | Any healthy container |\n| `service-name.internal` | Same |\n| `rr.service-name.internal` | Round-robin |\n| `nearest.service-name.internal` | Machine-local first |\n\n---\n\n## Scaling & Global Services\n\n```bash\nuc scale web 5    # 5 replicas (spread across machines)\nuc scale web 1    # Scale down\n```\n\n```yaml\nservices:\n  caddy:\n    deploy:\n      mode: global   # One container on every machine\n```\n\n---\n\n## Image Tag Templates (in compose.yaml)\n\n```yaml\nimage: myapp:{{gitdate \"20060102\"}}.{{gitsha 7}}\nimage: myapp:{{gitsha 7}}.${GITHUB_RUN_ID:-local}\n```\n\n| Function | Output |\n|----------|--------|\n| `{{gitsha N}}` | First N chars of commit SHA |\n| `{{gitdate \"format\"}}` | Git commit date in Go format |\n| `{{date \"format\"}}` | Current date |\n\n---\n\n## Common Workflows\n\n**Deploy from source:**\n```bash\nuc deploy                          # Build + push + deploy\nuc build --push && uc deploy --no-build   # Separate steps\n```\n\n**Inspect a service:**\n```bash\nuc inspect web\nuc logs -f web\nuc logs --since 1h web\nuc exec web                        # Opens shell\nuc exec web \u002Fbin\u002Fsh -c \"env\"       # Run specific command\n```\n\n**Zero-downtime deploys** happen automatically; Uncloud waits for health checks before terminating old containers.\n\n**Force recreate:**\n```bash\nuc deploy --recreate\n```\n\n---\n\n## Common Mistakes\n\n| Mistake | Fix |\n|---------|-----|\n| Editing the Caddyfile directly | Use `x-caddy` in compose or `--caddyfile` on `uc service run` |\n| Proxying an HTTPS upstream with self-signed cert | Add `transport http { tls_insecure_skip_verify }` |\n| `uc caddy config` shows no user-defined blocks | Caddy admin socket unreachable — check `uc inspect caddy` and `uc logs caddy` |\n| Service can't reach external LAN IP from container | Verify Caddy container's host can route to target network |\n| Volumes lost after `uc service rm` | Named volumes persist; only anonymous volumes are auto-removed |\n",{"name":5,"origin":24,"description":7},"ECC","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Funcloud",1,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-11 23:56:26",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill uncloud",{"tool":41,"command":42},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill uncloud",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill uncloud","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Funcloud\u002FSKILL.md",true,[],[50,58,65,73,81,89],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":54,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":69,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":77,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]