[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M781SSXA28P6180EKD42PMEX":3,"skill-same:01M781SSXA28P6180EKD42PMEX":74},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M781SSXA28P6180EKD42PMEX","proximo",null,"proximo makes local Docker containers reachable at https:\u002F\u002F\u003Cname>.test with trusted HTTPS and local DNS. Use when bringing up a project's containers, exposing a container through proximo.* labels or giving a service a local hostname, when calling or testing a containerized service (curl, wget, a test suite), when a .test host does not resolve, does not answer (ERR_CONNECTION_REFUSED) or returns 502\u002F503, when a browser rejects a local certificate (ERR_CERT_AUTHORITY_INVALID, ERR_CERT_COMMON_NAME_INVALID), when a page loads and then breaks in the browser, when a request through a .test host fails and you need what the container itself wrote, when the developer says something is not progressing — a queue not draining, a worker or job that keeps dying — and no page is broken, when a container cannot reach a VPN or tunnelled address the host reaches, or when sharing a route with a colleague over the team's mesh (proximo.share) or a colleague reports a shared link that times out, lands on .test, loses its login, or fails at the certificate.","filippolmt\u002Fskills","filippolmt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F61194571?v=4","01M7808VK1A8QF8ZXGT2DWTKHS","Filippo Merante Caparrotta","01M7808VKN74HC3EZMK8EV35KS",1,"MIT","https:\u002F\u002Fgithub.com\u002Ffilippolmt\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fproximo\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ffilippolmt\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fproximo\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: proximo\ndescription: proximo makes local Docker containers reachable at https:\u002F\u002F\u003Cname>.test with trusted HTTPS and local DNS. Use when bringing up a project's containers, exposing a container through proximo.* labels or giving a service a local hostname, when calling or testing a containerized service (curl, wget, a test suite), when a .test host does not resolve, does not answer (ERR_CONNECTION_REFUSED) or returns 502\u002F503, when a browser rejects a local certificate (ERR_CERT_AUTHORITY_INVALID, ERR_CERT_COMMON_NAME_INVALID), when a page loads and then breaks in the browser, when a request through a .test host fails and you need what the container itself wrote, when the developer says something is not progressing — a queue not draining, a worker or job that keeps dying — and no page is broken, when a container cannot reach a VPN or tunnelled address the host reaches, or when sharing a route with a colleague over the team's mesh (proximo.share) or a colleague reports a shared link that times out, lands on .test, loses its login, or fails at the certificate.\nmetadata:\n  short-description: Expose a container at https:\u002F\u002F\u003Cname>.test, and diagnose one that is broken\n---\n\n# proximo\n\nA container carries `proximo.*` labels; proximo gives it a name, local DNS, a\ntrusted certificate, and a `Host`-based route. Reference:\n\u003Chttps:\u002F\u002Ffilippolmt.github.io\u002Fproximo\u002F>.\n\n## Before anything else\n\nRun `proximo version`.\n\n- **Not on PATH** — proximo is not in play here. Say so and stop.\n- **`.proximo-skill.json` sits beside this file and its version differs** — run\n  `proximo skill install` (add `--scope global` when this copy is under the\n  developer's home directory rather than in the repository), then ask the\n  developer to restart the session so the refreshed skill loads.\n- **No `.proximo-skill.json`** — this copy came from a marketplace rather than\n  from the CLI, so nothing keeps it level with the installed binary. Confirm\n  anything surprising against `proximo --help` before acting on it.\n\n## Triage\n\n`proximo status` is an inventory of routes, and it never prints a Remedy. Run it\nfirst: what it shows picks the branch.\n\n| `proximo status` shows | Read |\n| --- | --- |\n| A last line saying the proximo stack is not running or degraded | Run `proximo doctor`. A Remedy of `proximo up` is yours to run; any other is the developer's. Then run `proximo status` again: until the line is gone the routes listed may not answer, so no other row applies |\n| A line `⚠ Listening on 0.0.0.0:…` (or `[::]`) | The stack predates the loopback-only Traefik: `proximo up` is yours to run, and it narrows it. A developer who wants a route reachable from another host has no setting for it; only a shared route is, on the mesh ([sharing](https:\u002F\u002Ffilippolmt.github.io\u002Fproximo\u002Fsharing.html)) |\n| No route for the container, or a route flagged with a warning | [`references\u002Fexpose.md`](references\u002Fexpose.md) |\n| A route, but the host does not answer, answers 502\u002F503, or the browser distrusts the certificate | [`references\u002Frouting.md`](references\u002Frouting.md) |\n| A route, the host answers, and the page itself is wrong | [`references\u002Finspection.md`](references\u002Finspection.md) |\n| A route, the host answers, and a request fails on the server — a 500, or an API call that comes back wrong | [`references\u002Ftranscript.md`](references\u002Ftranscript.md) |\n| Nothing is visibly broken, and the developer says something is **not progressing** — a queue not draining, a job that never finishes, a worker that keeps dying | [`references\u002Ftranscript.md`](references\u002Ftranscript.md) — ask for **Incidents** |\n| Nothing about a route is wrong, and a call **from inside a container** to an address the host reaches — a host behind a VPN, a network over a tunnel — hangs until it times out | Run `proximo doctor` and read *The stack network is on the declared subnet*: the stack network can shadow that route. A Remedy of `proximo up` is yours to run. If the subnet it states overlaps the address, `proximo config subnet \u003Ccidr>` moves the stack: ask the developer for a free private range, since only they know which ones their VPN uses. Then [troubleshooting](https:\u002F\u002Ffilippolmt.github.io\u002Fproximo\u002Ftroubleshooting.html#a-container-cannot-reach-an-address-your-host-can) |\n| A route carries `proximo.share`, or a **colleague** reports a shared link that times out, lands on a `.test` address, loses its login, or fails at the certificate | The `PEER` column says whether the route is served on its peer names; then [sharing](https:\u002F\u002Ffilippolmt.github.io\u002Fproximo\u002Fsharing.html) and the matching section of [troubleshooting](https:\u002F\u002Ffilippolmt.github.io\u002Fproximo\u002Ftroubleshooting.html#a-shared-link-does-not-resolve-or-times-out). `proximo doctor` checks this machine's side (`peer-intermediate`, `peer-routes`, `peer-dns`, `peer-relay`, `mesh`); nothing here can see the colleague's |\n\nWhen the developer's account does not settle which row it is, ask the host\nitself and let the status code decide:\n\n```sh\ncurl -sS -o \u002Fdev\u002Fnull -w '%{http_code}\\n' https:\u002F\u002F\u003Chost>\n```\n\n## Rules, in every branch\n\n**A Remedy that changes the host is the developer's to run.** `proximo doctor`\nreports Checks, and every failed Check carries a Remedy — the exact command. Hand\nover the ones that install, trust, or ask for a password: proximo's contract is\nthat every mutation of a machine stays a command its owner typed. Run the\nread-only commands yourself, `proximo up` when the stack is down or degraded, and\n`proximo update` when a Remedy names it: both recreate only the stack's\ncontainers and change nothing on the host. Say which command you are running.\n\n**Recreating the stack empties the Exchange buffer.** Exchanges are held in\nmemory and bounded, so whatever recreates the `inspector` — `proximo down` then\n`up`, `proximo update`, `proximo config subnet`, or an `up` that brings a new\nstack image or moves the stack network — discards every\nClient report recorded before it. A label change needs no stack restart, and an\n`up` over an unchanged running stack keeps the buffer. Collect what you need\nbefore recreating, and reproduce the problem after; `proximo errors` says when the\nhop came up in the last ten minutes.\n\n**No Incident does not mean no problem.** `proximo errors` reports what the\n*runtime* declared about a container — an exit, a restart, an OOM kill — and\nnever what a container wrote. A worker that is alive and blocked on a slow query\ndeclares nothing, so an empty listing means *proximo saw nothing happen*, never\n*nothing is wrong*. Under `--service` the listing always ends with the\n**readings** — one per running container (running since when, healthcheck,\nrestarts, when its output last moved) — and deliberately draws no conclusion:\nidentical readings come from a consumer with nothing to do and one that is stuck.\nA scaled service gives you one reading per replica; do not generalise one\nreplica's reading to the service. Report the readings as readings, and read the\noutput for the window before concluding anything:\n`proximo errors transcript --service \u003Cservice> --since 30m`. To make a stuck\nworker visible next time, propose a healthcheck that fails when it stops\nadvancing — Docker then says *unhealthy*, and a healthcheck that was passing and\nstopped is an Incident. It has to pass once first — a check that never passed\ndeclares nothing when it fails — so propose a `start_period` with it, which keeps\na slow first job from being reported unhealthy on the way there.\n\n**A call to a local container goes through its route.** A request that checks a\nservice running in a local container — `curl`, `wget`, a test suite, a script —\nmade from the host, or from a dev container that pins proximo's names, goes to\n`https:\u002F\u002F\u003Cqualified host>`, resolved through proximo and verified against its CA:\nthe path the developer's browser takes, so the result covers the name, the\ncertificate, the router and the health gate. A name that does not resolve or a\ncertificate that is refused is itself the finding: run `proximo doctor`, read\n[`references\u002Frouting.md`](references\u002Frouting.md), and keep the call unchanged.\n`localhost:\u003Cport>`, the container's IP, `-k`, `--resolve` and a hand-written\n`\u002Fetc\u002Fhosts` entry each answer a different question and hide the one you were\nasked. Any other host — `google.com`, a staging API — is outside proximo: call it\nas it is. A call made from any other container follows that container's own\nnetworking.\n\n**A hostname is a proximo label.** When a service needs a name, declare it with\n`proximo.hosts` under the configured TLD (`proximo config tld`), or\n`proximo.tcp.port` for a TCP service: proximo issues the DNS record, the\ncertificate and the route together, and it owns the local zone. The host\nresolver, `\u002Fetc\u002Fhosts` and DNS containers stay as they are. How:\n[`references\u002Fexpose.md`](references\u002Fexpose.md). proximo routes HTTP(S) and\nTLS-with-SNI TCP. UDP, plain TCP, and a listener that a LAN device must reach\n(syslog from a firewall) stay outside it: publish the port with `ports:` on the\naddress that device reaches.\n\n**Ask the binary.** For anything about proximo — routes and their names, the CA\n(`proximo config ca-path`), the inventory (`proximo config inventory-dir`), what a\ncontainer wrote (`proximo errors`) — the `proximo` CLI is the interface, and\n`proximo --help` lists what this binary runs. The files under `~\u002F.proximo` and\nthe stack's containers are its implementation. Inside a toolbox container it is a\nbridge shim, and `config` stays on the host. There the TLD is the one of the\n`traefik.\u003Ctld>` route in `proximo status`, the CA is already trusted\n(`$TOOLBOX_PROXIMO_CA` names it), the inventory directory is\n`\u002Fetc\u002Ftoolbox\u002Fproximo`, and a `config` change is the developer's to run.\n\n**Ask on the qualified host.** Every route answers on two names, and only the\nqualified one stays put: a Collision can move the bare host to another\ncontainer. Put the qualified host in `--host` and in `curl`, and read it from\n`proximo status --json` (`qualified`) rather than out of the table. A route\nwithout `qualified` (the stack's own `traefik.\u003Ctld>`, a container outside a\nCompose project) has only its bare host: use `bare`. A tool that\nmust follow routes without running the CLI — a dev container's hosts sync — reads\nthe same document from `routes.json` in `proximo config inventory-dir`.\n","# proximo\n\nA container carries `proximo.*` labels; proximo gives it a name, local DNS, a\ntrusted certificate, and a `Host`-based route. Reference:\n\u003Chttps:\u002F\u002Ffilippolmt.github.io\u002Fproximo\u002F>.\n\n## Before anything else\n\nRun `proximo version`.\n\n- **Not on PATH** — proximo is not in play here. Say so and stop.\n- **`.proximo-skill.json` sits beside this file and its version differs** — run\n  `proximo skill install` (add `--scope global` when this copy is under the\n  developer's home directory rather than in the repository), then ask the\n  developer to restart the session so the refreshed skill loads.\n- **No `.proximo-skill.json`** — this copy came from a marketplace rather than\n  from the CLI, so nothing keeps it level with the installed binary. Confirm\n  anything surprising against `proximo --help` before acting on it.\n\n## Triage\n\n`proximo status` is an inventory of routes, and it never prints a Remedy. Run it\nfirst: what it shows picks the branch.\n\n| `proximo status` shows | Read |\n| --- | --- |\n| A last line saying the proximo stack is not running or degraded | Run `proximo doctor`. A Remedy of `proximo up` is yours to run; any other is the developer's. Then run `proximo status` again: until the line is gone the routes listed may not answer, so no other row applies |\n| A line `⚠ Listening on 0.0.0.0:…` (or `[::]`) | The stack predates the loopback-only Traefik: `proximo up` is yours to run, and it narrows it. A developer who wants a route reachable from another host has no setting for it; only a shared route is, on the mesh ([sharing](https:\u002F\u002Ffilippolmt.github.io\u002Fproximo\u002Fsharing.html)) |\n| No route for the container, or a route flagged with a warning | [`references\u002Fexpose.md`](references\u002Fexpose.md) |\n| A route, but the host does not answer, answers 502\u002F503, or the browser distrusts the certificate | [`references\u002Frouting.md`](references\u002Frouting.md) |\n| A route, the host answers, and the page itself is wrong | [`references\u002Finspection.md`](references\u002Finspection.md) |\n| A route, the host answers, and a request fails on the server — a 500, or an API call that comes back wrong | [`references\u002Ftranscript.md`](references\u002Ftranscript.md) |\n| Nothing is visibly broken, and the developer says something is **not progressing** — a queue not draining, a job that never finishes, a worker that keeps dying | [`references\u002Ftranscript.md`](references\u002Ftranscript.md) — ask for **Incidents** |\n| Nothing about a route is wrong, and a call **from inside a container** to an address the host reaches — a host behind a VPN, a network over a tunnel — hangs until it times out | Run `proximo doctor` and read *The stack network is on the declared subnet*: the stack network can shadow that route. A Remedy of `proximo up` is yours to run. If the subnet it states overlaps the address, `proximo config subnet \u003Ccidr>` moves the stack: ask the developer for a free private range, since only they know which ones their VPN uses. Then [troubleshooting](https:\u002F\u002Ffilippolmt.github.io\u002Fproximo\u002Ftroubleshooting.html#a-container-cannot-reach-an-address-your-host-can) |\n| A route carries `proximo.share`, or a **colleague** reports a shared link that times out, lands on a `.test` address, loses its login, or fails at the certificate | The `PEER` column says whether the route is served on its peer names; then [sharing](https:\u002F\u002Ffilippolmt.github.io\u002Fproximo\u002Fsharing.html) and the matching section of [troubleshooting](https:\u002F\u002Ffilippolmt.github.io\u002Fproximo\u002Ftroubleshooting.html#a-shared-link-does-not-resolve-or-times-out). `proximo doctor` checks this machine's side (`peer-intermediate`, `peer-routes`, `peer-dns`, `peer-relay`, `mesh`); nothing here can see the colleague's |\n\nWhen the developer's account does not settle which row it is, ask the host\nitself and let the status code decide:\n\n```sh\ncurl -sS -o \u002Fdev\u002Fnull -w '%{http_code}\\n' https:\u002F\u002F\u003Chost>\n```\n\n## Rules, in every branch\n\n**A Remedy that changes the host is the developer's to run.** `proximo doctor`\nreports Checks, and every failed Check carries a Remedy — the exact command. Hand\nover the ones that install, trust, or ask for a password: proximo's contract is\nthat every mutation of a machine stays a command its owner typed. Run the\nread-only commands yourself, `proximo up` when the stack is down or degraded, and\n`proximo update` when a Remedy names it: both recreate only the stack's\ncontainers and change nothing on the host. Say which command you are running.\n\n**Recreating the stack empties the Exchange buffer.** Exchanges are held in\nmemory and bounded, so whatever recreates the `inspector` — `proximo down` then\n`up`, `proximo update`, `proximo config subnet`, or an `up` that brings a new\nstack image or moves the stack network — discards every\nClient report recorded before it. A label change needs no stack restart, and an\n`up` over an unchanged running stack keeps the buffer. Collect what you need\nbefore recreating, and reproduce the problem after; `proximo errors` says when the\nhop came up in the last ten minutes.\n\n**No Incident does not mean no problem.** `proximo errors` reports what the\n*runtime* declared about a container — an exit, a restart, an OOM kill — and\nnever what a container wrote. A worker that is alive and blocked on a slow query\ndeclares nothing, so an empty listing means *proximo saw nothing happen*, never\n*nothing is wrong*. Under `--service` the listing always ends with the\n**readings** — one per running container (running since when, healthcheck,\nrestarts, when its output last moved) — and deliberately draws no conclusion:\nidentical readings come from a consumer with nothing to do and one that is stuck.\nA scaled service gives you one reading per replica; do not generalise one\nreplica's reading to the service. Report the readings as readings, and read the\noutput for the window before concluding anything:\n`proximo errors transcript --service \u003Cservice> --since 30m`. To make a stuck\nworker visible next time, propose a healthcheck that fails when it stops\nadvancing — Docker then says *unhealthy*, and a healthcheck that was passing and\nstopped is an Incident. It has to pass once first — a check that never passed\ndeclares nothing when it fails — so propose a `start_period` with it, which keeps\na slow first job from being reported unhealthy on the way there.\n\n**A call to a local container goes through its route.** A request that checks a\nservice running in a local container — `curl`, `wget`, a test suite, a script —\nmade from the host, or from a dev container that pins proximo's names, goes to\n`https:\u002F\u002F\u003Cqualified host>`, resolved through proximo and verified against its CA:\nthe path the developer's browser takes, so the result covers the name, the\ncertificate, the router and the health gate. A name that does not resolve or a\ncertificate that is refused is itself the finding: run `proximo doctor`, read\n[`references\u002Frouting.md`](references\u002Frouting.md), and keep the call unchanged.\n`localhost:\u003Cport>`, the container's IP, `-k`, `--resolve` and a hand-written\n`\u002Fetc\u002Fhosts` entry each answer a different question and hide the one you were\nasked. Any other host — `google.com`, a staging API — is outside proximo: call it\nas it is. A call made from any other container follows that container's own\nnetworking.\n\n**A hostname is a proximo label.** When a service needs a name, declare it with\n`proximo.hosts` under the configured TLD (`proximo config tld`), or\n`proximo.tcp.port` for a TCP service: proximo issues the DNS record, the\ncertificate and the route together, and it owns the local zone. The host\nresolver, `\u002Fetc\u002Fhosts` and DNS containers stay as they are. How:\n[`references\u002Fexpose.md`](references\u002Fexpose.md). proximo routes HTTP(S) and\nTLS-with-SNI TCP. UDP, plain TCP, and a listener that a LAN device must reach\n(syslog from a firewall) stay outside it: publish the port with `ports:` on the\naddress that device reaches.\n\n**Ask the binary.** For anything about proximo — routes and their names, the CA\n(`proximo config ca-path`), the inventory (`proximo config inventory-dir`), what a\ncontainer wrote (`proximo errors`) — the `proximo` CLI is the interface, and\n`proximo --help` lists what this binary runs. The files under `~\u002F.proximo` and\nthe stack's containers are its implementation. Inside a toolbox container it is a\nbridge shim, and `config` stays on the host. There the TLD is the one of the\n`traefik.\u003Ctld>` route in `proximo status`, the CA is already trusted\n(`$TOOLBOX_PROXIMO_CA` names it), the inventory directory is\n`\u002Fetc\u002Ftoolbox\u002Fproximo`, and a `config` change is the developer's to run.\n\n**Ask on the qualified host.** Every route answers on two names, and only the\nqualified one stays put: a Collision can move the bare host to another\ncontainer. Put the qualified host in `--host` and in `curl`, and read it from\n`proximo status --json` (`qualified`) rather than out of the table. A route\nwithout `qualified` (the stack's own `traefik.\u003Ctld>`, a container outside a\nCompose project) has only its bare host: use `bare`. A tool that\nmust follow routes without running the CLI — a dev container's hosts sync — reads\nthe same document from `routes.json` in `proximo config inventory-dir`.\n",{"name":5,"metadata":25,"description":7},{"short-description":26},"Expose a container at https:\u002F\u002F\u003Cname>.test, and diagnose one that is broken","main","e63612d78f9099c1970584ea3faef109f42d20bb","skills\u002Fproximo",0,"https:\u002F\u002Fgithub.com\u002Ffilippolmt\u002Fskills","https:\u002F\u002Fgithub.com\u002Ffilippolmt","2026-11-14 22:46:00",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add filippolmt\u002Fskills --skill proximo",{"tool":40,"command":41},"bunx","bunx skills add filippolmt\u002Fskills --skill proximo",{"tool":43,"command":44},"pnpm","pnpm dlx skills add filippolmt\u002Fskills --skill proximo","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffilippolmt\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fproximo\u002FSKILL.md",true,[48,52,58,62,66,70],{"path":49,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":16},"LICENSE","许可证",1083,{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fexpose.md","REFERENCE","参考文档",7474,"https:\u002F\u002Fgithub.com\u002Ffilippolmt\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fproximo\u002Freferences\u002Fexpose.md",{"path":59,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Finspection.md",5237,"https:\u002F\u002Fgithub.com\u002Ffilippolmt\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fproximo\u002Freferences\u002Finspection.md",{"path":63,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Frouting.md",5220,"https:\u002F\u002Fgithub.com\u002Ffilippolmt\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fproximo\u002Freferences\u002Frouting.md",{"path":67,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Ftranscript.md",8299,"https:\u002F\u002Fgithub.com\u002Ffilippolmt\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fproximo\u002Freferences\u002Ftranscript.md",{"path":71,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":72,"sourceHtmlUrl":73},"SOURCE.md",387,"https:\u002F\u002Fgithub.com\u002Ffilippolmt\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fproximo\u002FSOURCE.md",[75,83,92,100,108,116],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":79,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":20},"01M781ZJN9KDK0YY8EAQ8WXPRQ","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Ffilippolmt\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-for-agents\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ffilippolmt\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-for-agents\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":87,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":20},"01M781ZDZ8CQ30GRY5XNT1RF91","wrangler","Run or troubleshoot Wrangler CLI commands in projects that have a wrangler.jsonc, wrangler.json, or wrangler.toml file, including local development, Previews, deployment, and resource management. For new projects and projects without a Wrangler configuration file, use the cf CLI instead.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Ffilippolmt\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwrangler\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ffilippolmt\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwrangler\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":96,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":20},"01M781ZA1MB7E7T1R1TE0BTTJS","workers-profiling","Profile or debug CPU usage and memory allocation in deployed Cloudflare Workers and Durable Objects. Then use this information to optimize your code.","https:\u002F\u002Fgithub.com\u002Ffilippolmt\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fworkers-profiling\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ffilippolmt\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fworkers-profiling\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":104,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":20},"01M781Z52Q7PBMDA2YBC3SCTYM","workers-development","Run, inspect, and debug Cloudflare Workers during local development with cf dev, wrangler dev, or the Cloudflare Vite plugin, using Local Explorer to read and seed binding data and query local traces and logs. Also routes production debugging to Workers observability. Use for debugging requests whether or not the project uses Wrangler.","https:\u002F\u002Fgithub.com\u002Ffilippolmt\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fworkers-development\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ffilippolmt\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fworkers-development\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":112,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":20},"01M781Z193MG7SHF4DSD1WK583","workers-best-practices","Cloudflare Workers best practices for production applications. Use when writing, reviewing, or configuring Workers.","https:\u002F\u002Fgithub.com\u002Ffilippolmt\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fworkers-best-practices\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ffilippolmt\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fworkers-best-practices\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":120,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":20},"01M781YT0JB3GVA1HTFZ9QJHM7","wordpress-pro","Develops custom WordPress themes and plugins, creates and registers Gutenberg blocks and block patterns, configures WooCommerce stores, implements WordPress REST API endpoints, applies security hardening (nonces, sanitization, escaping, capability checks), and optimizes performance through caching and query tuning. Use when building WordPress themes, writing plugins, customizing Gutenberg blocks, extending WooCommerce, working with ACF, using the WordPress REST API, applying hooks and filters, or improving WordPress performance and security.","https:\u002F\u002Fgithub.com\u002Ffilippolmt\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwordpress-pro\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ffilippolmt\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwordpress-pro\u002FSKILL.md",[],[]]