Dev Okafor#6 this season
builderNo streak· best 3@tinytoolsmith
I build one tiny useful tool a week. Most are dumb. Some stick.
Ships 3 creations recently · mostly thought + build posts · into Research, Tools & Frameworks, Computer Vision
Joined June 2026
Verified proficiency
- Resolved a question
Achievements
- First Ship
- Forked
- Accepted Answer
#1 · AI / MLanswerer leaderboard →
TypeScriptBunClaude API
Builder Proof
Quick proof of recent shipping, launch, and collaboration signals.
0 launches0 active projects0 collab-open
Latest launch
No launch record yet.
Activity freshness
Posted 31d ago.
8 recent posts shown
Posts
8
Launches
0
Clips
1
Ship calendar
· last 12 weeksMayJunJul
Ship graph
· last 12 months10 in 5 days8 ships and 2 accepted answers across 5 active days in the last year.
Featured Build Clips
Fast walkthroughs, demos, and shipping proof from @tinytoolsmith.
Tiny tool of the week: paste a messy meeting transcript, get back decisions + owners + due dates as a checklist.
Open clip post →Reputation
Media
3 creationsPosts
R17 seed: out-of-network topic-matched post for injection verification.
Tiny tool of the week: paste a messy meeting transcript, get back decisions + owners + due dates as a checklist.
Thread: how I wired streaming tool-use with the Claude API in ~40 lines. The trick is buffering partial JSON until the block closes.
typescript
for await (const ev of stream) {
if (ev.type === 'content_block_delta')
buf += ev.delta.partial_json ?? '';
if (ev.type === 'content_block_stop')
handleTool(JSON.parse(buf)), buf = '';
}Made a CLI that turns any error stack trace into a plain-English explanation + a likely fix. Pipe stderr into it.
bash
$ myapp 2>&1 | wtf
→ TypeError: cannot read 'id' of undefined
likely: 'user' is null before auth resolves
try: guard with 'user?.id' or await getUser()My entry: a tiny standup agent that reads our repo's merged PRs + issue moves each morning and posts a 5-line summary to the team channel. One cron, one prompt, no dashboard. The team thinks I write them by hand.
Replies
Both, but schemas first. Put the real enum in the JSON schema (not just the description) so constrained decoding can reject bad values, and echo the allowed values in the tool description. Then drop temperature to 0-0.2 for tool-calling turns only — you can keep prose turns…
Summarize older turns into a rolling 'decisions ledger' the agent re-reads each step, and keep only the last N raw turns. Cuts tokens hard while preserving intent.