1/ I built IntelliPlug, a support assistant that answers customers from each company's own documents, with every company's data kept separate.
Here's how it works, and what moved the needle. 🧵
Teachers spend evenings writing lesson plans and assessments.
Teacher Co-Pilot drafts curriculum-aligned lesson plans and assessment materials for secondary schools, and a second AI step checks each draft before the teacher sees it.
https://t.co/2ONqBRc3LF
@nishant_zk@SmartJellyAI I'd like to help. I build RAG and knowledge assistants: retrieval, evals, answers grounded in sources, which is close to what Jelly's memory does. Happy to start on a defined piece and show work. Sending you a DM.
A system can pass every test and still fail in its first week with real people: bad wifi, forgotten passwords, zero patience, sometimes bad intentions.
The spec describes an ideal world. Nobody lives there. My checks:
1. Why does this need to exist at all? Delete before you build.
2. Does it survive someone who never reads the docs?
3. Is a retry safe, or does it corrupt data?
4. If the complexity can't go, can I absorb it instead of handing it to the user?
4. You get a ranked list and a report to share with the hiring manager.
It doesn't replace the recruiter. It gives them a consistent first pass, so time goes on conversations.
Case study: https://t.co/xqNhZFk97s
A job ad goes up. By Friday the shared inbox is full of CVs. For small HR teams, the bottleneck isn't finding people. It's reading them.
I built CV Ranker for that. How it works:
1. It reads the CVs (PDFs too) and the job description.
2. It compares them by meaning, not only keywords.
3. A language model adds a reasoned view per candidate.
@adcock_brett Its great, easily the most impressive LLM product I have used since chatgpt first launched. I am left with 30+% of the monthly h3 allocation already and its been amazing
Every term, someone at a school loses days to a puzzle: one teacher in two rooms, the lab booked twice, fix one clash and two more appear.
I built a timetable scheduler for it. What worked, in 3 posts:
2. Then mutate where the clashes actually are. Conflict-directed mutation converged to schedules with zero clashes.
Lesson: in scheduling, a good starting point beats brute force.
Learn to create content.
Learn Problem solving.
Learn to sell.
Learn AI Leverage.
Learn to build with AI.
Learn Distribution.
These are the high end skills I recommend everyone learns in 2026. Did I miss anything? 👨🏾💻👀
A model in a notebook has no users, no uptime, and no way for another system to call it.
Value starts when it becomes a service: state, auth, streaming, background jobs.
That's backend work, and AI engineers need it.
https://t.co/flwE7QDYKb
Minutes from a sensitive meeting, without uploading the recording anywhere?
I built Sovereign Minute Maker for that. Transcription and personal-detail redaction run on your device. Only cleaned text reaches the LLM.
https://t.co/OzuMqGZyNc
@de_henne Nice result. Scope the MCP plugin to only the skills it needs and log the tool calls, so you can spot when a skill stops improving the click. The guardrails are what let automation compound.
@mardehaym Masking alone still leaks geography, so testing outcomes per release matters more than the prompt. What moves these builds: map sources before the model touches a file, then eval historical files to gate each deploy.