Issue No. 01
Week 45 — five repos, one homelab, no drama
Eight things worth keeping and a quiet week on the box. Skim the bold lines, open the one that bugs you.

Right. Two minutes, that is the whole ask. Read the bold line under each card, open the one you want, close the tab. Nothing here needs a decision today.
Start with these three
GitHub - pablostanley/yoinks: yoink any video from your terminal. no shady ads.yoink any video from your terminal. no shady ads. Contribute to pablostanley/yoinks development by creating an account on GitHub.A terminal downloader for 1,800+ sites, no ads, no redirects. Under the hood it is a wrapper over yt-dlp — which is fine, that is the point. Install it if you ever grab video from a terminal.
A headless browser written from scratch in Zig, not a Chromium fork. Claims 16x less memory than headless Chrome and dumps pages as Markdown, PNG or PDF. Worth a look if a browser is the thing eating your RAM.
GitHub - smicallef/spiderfoot: SpiderFoot automates OSINT for threat intelligence and mapping your attack surface.SpiderFoot automates OSINT for threat intelligence and mapping your attack surface. - smicallef/spiderfootSelf-hosted OSINT scan of your own footprint. Point it at your own domain, see what the internet already knows. Run it once on your own name; the result is usually boring and that is the good outcome.
The rest of the pile
GitHub - shiyu-coder/Kronos: Kronos: A Foundation Model for the Language of Financial MarketsKronos: A Foundation Model for the Language of Financial Markets - shiyu-coder/KronosOpen foundation model for financial K-lines (OHLCV). Only if you already have an opinion about candlesticks.
GitHub - Motionsites-AI/claude-skill: Free Claude skill: make Claude build award-level, cinematic landing pages. By MotionSites.Free Claude skill: make Claude build award-level, cinematic landing pages. By MotionSites. - Motionsites-AI/claude-skillA Claude skill for cinematic landing pages. You were looking at this one for the newsletter build. Open it when we do the UI pass.
Try this
Try this
Point a memory-hungry browser at your own pages
The Zig browser above is the interesting one, because the constraint it solves is real: a headless Chrome will happily eat 2 GB to render one page.
- Install it, then run it against a page you already know renders badly.
- Compare the dump against what Chrome produces. If the Markdown is close, you have a cheap scraper.
- Keep it if it holds up. Delete it if it does not — it costs nothing to find out.
The honest caveat: it is young software, and “renders like Chrome” is the claim to test, not the claim to trust.
Prompt worth stealing
This is the one that made the difference this week. Paste it into your model of choice and change the bracketed parts.
Read this repository and tell me whether I should install it:
[repo URL]
Answer in this order, and keep it under 200 words:
1. What it does, in one sentence a non-programmer would follow.
2. What it replaces or improves on. Name the incumbent.
3. The honest cost: dependencies, maintenance, and what breaks if the maintainer walks away.
4. One reason NOT to install it.
Do not summarise the README. If the repo is a wrapper around something else, say so in the first sentence.Homelab: the boring week
Nothing caught fire. That is worth writing down, because the two weeks before it were not quiet.
- The NAS held steady. No scrub errors, no alerts.
- The hypervisor logged no task failures this week.
- The agent box stayed up for the whole window. No OOM, no restart.
- The reverse proxy served every internal hostname without a renewal hiccup.
Next week
Same time, Sunday. If nothing interesting turned up, the issue will say so rather than pad itself out.