I built sift because keeping up with the internet started feeling like a second job.
Choose what you care about. sift reads the feeds, threads, newsletters, and search results — then turns them into one weekly issue you can actually finish.
sift.day
2
1
7
The goal isn’t to help people consume more.
It’s to replace the endless feed with something finite: one issue, linked sources, and a clear ending.
You can read a real sample before downloading:
sift.day
6
Shipped 5 MCP Skills for GroundAPI this week — one config line in Claude/Cursor, and your AI gets real-world data.
Thread 🧵👇
#buildinpublic #MCP #indiehackers
1
1
31
🌤️ Context-Aware Assistant
Auto-detect location via IP, real-time weather + 7-day forecast, package tracking.
🌐 Web Researcher
Multi-angle search, full-page scraping, structured reports with sources.
1
17
All powered by GroundAPI MCP Server. 14 data tools, one API key.
GitHub: github.com/qingkongzhiqian/g…
Setup: groundapi.net/documentation/…
Free 500 calls/month. No credit card needed.
1
34
Every SaaS will eventually ship a CLI. Not for devs — for AI agents.
Feishu just open-sourced theirs. Messages, docs, spreadsheets, approvals — all callable by Claude Code in one command.
GUI for humans. CLI for agents. Both will coexist. #buildinpublic #AI
16
Feishu (Lark) just open-sourced their entire product as a CLI tool.
This is huge. Your AI Agent can now control Feishu directly — messages, docs, spreadsheets, calendar, approvals. All via command line.
Thread on why this matters 🧵
#buildinpublic #AI
1
31
The smartest part: Feishu's CLI returns human-readable error messages.
Not just "404" or "502", but: which parameter failed, what went wrong, what command to run to fix it.
This lets AI self-retry and self-correct. Every API should do this.
1
11
The future of software: every product will have two interfaces.
GUI — for humans.
CLI — for AI agents.
github.com/larksuite/cli
#buildinpublic #opensource #AI
1
13





