publish fix, GitHub and LinkedIn site definitions

setup-node's registry-url writes an npmrc auth-token line with a
placeholder token, which npm used instead of OIDC and got a 404 from
the registry. Dropping registry-url lets trusted publishing work.

New clis: github.com (repo, user, search, trending, issues) and
linkedin.com (profile, company, jobs; public guest views work through
the Chrome fingerprint). Both verified live before shipping.

.github/workflows/publish.yml

@@ -34,10 +34,12 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v7
-      - uses: actions/setup-node@v4
+      # No registry-url here: it writes an .npmrc auth-token line with a
+      # placeholder value, and npm then authenticates with that instead of
+      # falling through to OIDC trusted publishing.
+      - uses: actions/setup-node@v7
         with:
           node-version: 24
-          registry-url: https://registry.npmjs.org
       # Trusted publishing needs npm 11.5.1 or newer.
       - run: npm install -g npm@latest
       - run: npm ci

README.md

@@ -59,6 +59,8 @@ only-cli works on any mostly-static website with no per-site setup: news sites,
 | --- | --- | --- |
 | Hacker News | news.ycombinator.com | `top`, `new`, `item <id>`, `user <name>` |
 | Reddit | reddit.com (via old.reddit.com) | `sub <name>`, `post <id>`, `user <name>`, `search <query>` |
+| GitHub | github.com | `repo <owner> <name>`, `user <name>`, `search <query>`, `trending`, `issues <owner> <name>` |
+| LinkedIn | linkedin.com | `profile <name>`, `company <name>`, `jobs <query>` (public guest views) |
 | DuckDuckGo | duckduckgo.com | `search <query>`, `lite <query>` |
 | Bing | bing.com | `search <query>`, `news <query>` |
 

clis/github.com.json

@@ -0,0 +1,10 @@
+{
+  "domain": "github.com",
+  "commands": {
+    "repo": { "open": "https://github.com/{owner}/{repo}", "args": ["owner", "repo"] },
+    "user": { "open": "https://github.com/{name}", "args": ["name"] },
+    "search": { "open": "https://github.com/search?q={query}&type=repositories", "args": ["query"] },
+    "trending": { "open": "https://github.com/trending" },
+    "issues": { "open": "https://github.com/{owner}/{repo}/issues", "args": ["owner", "repo"] }
+  }
+}

clis/linkedin.com.json

@@ -0,0 +1,8 @@
+{
+  "domain": "linkedin.com",
+  "commands": {
+    "profile": { "open": "https://www.linkedin.com/in/{name}", "args": ["name"] },
+    "company": { "open": "https://www.linkedin.com/company/{name}", "args": ["name"] },
+    "jobs": { "open": "https://www.linkedin.com/jobs/search?keywords={query}", "args": ["query"] }
+  }
+}

llms.txt

@@ -8,7 +8,7 @@ Key facts:
 - Commands: `oc open <url>` (compact view with numbered actions), `oc raw <url>` (whole page as markdown, `--html` for cleaned HTML), `oc --help` for the full surface
 - Default output budget is 500 tokens per page; `--budget <n>` adjusts it
 - Benchmarked at roughly 45x fewer tokens than reading raw HTML, with per-task numbers at https://github.com/only-cli/benchmarks
-- Works on any mostly-static website; tuned shortcuts ship for Hacker News, Reddit, DuckDuckGo, and Bing
+- Works on any mostly-static website; tuned shortcuts ship for Hacker News, Reddit, GitHub, LinkedIn (public guest views), DuckDuckGo, and Bing
 - Requests impersonate Chrome, so pages that block plain scripts often still work
 - Claude Code skill included: `npx skills add only-cli/oc`
 - No JavaScript rendering yet and no login sessions yet (both on the roadmap)