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.
This commit is contained in:
only-cli
2026-08-18 09:48:04 -04:00
parent 96873e4b8f
commit b536cc2ccf
5 changed files with 25 additions and 3 deletions
+1 -1
View File
@@ -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)