Claude SG Community Event · May 29, 2026
Yingtell
SEA
What happens when your message meets a panel of brutally honest AI advisors?
The Problem
You left the meeting excited.
They went quiet.
The follow-up message felt right.
The silence that followed did not.
Indonesia
They said "very interesting." You never heard back.
Thailand
The meeting was warm. The proposal died in silence.
Philippines
Strong first call. Follow-up email — no reply.
?
The message was the problem.
You just didn't know it.
The Build
"I built my own critic.
And it has opinions."
Yingtell SEA
A multi-agent ASEAN message review tool
built entirely in a single HTML file.
1
HTML file
3
Parallel agents
0
Frameworks
Built by someone who cannot spell JavaScript.
Meet the Agents
Your panel of brutally honest advisors
K
KAIA
Cultural Sensitivity
Reads what your message signals culturally — face, status, relationship, timing.
R
REX
Relationship Intel
Reads the relationship dynamic. Are you moving too fast? Too transactional?
V
VERA
Value & Risk
Reads what you're offering — and what you're accidentally risking.
J
THE JUDGE
— Final Grader
Reviews all three agents. Renders a verdict.
PASS
HOLD
REWRITE
How It Works
Multi-agent orchestration with a harness and grader
YOUR
MESSAGE
Your message
+ context
→
KAIA
REX
VERA
3 agents run
in parallel
→
JUDGE
Grades &
synthesizes
→
VERDICT
PASS / HOLD
/ REWRITE
Agentic Vocabulary
Harness:
The control layer that stops agents — and developers — from doing dangerous things. The harness protects the deal.
Grader:
The Judge. An agent whose only job is to evaluate the other agents' outputs and assign a verdict.
Orchestration:
Running multiple agents in parallel, then combining their reasoning into one coherent answer.
Live Demo
DEMO
TIME
Let's submit something…
questionable.
1
Flip the Demo toggle (top right of the app)
2
Bad follow-up message auto-fills
3
Hit Submit — all 3 agents run live
4
Watch the Judge arrive
Demo Mode · No API key needed · Fully scripted result
yingtell-sea.html ↗
Security Architecture
This is not vibe coding.
This is vibe coding
WITH BRAKES.
🔑 Runtime only
API key is entered at runtime. Never hardcoded into the file. Never baked in.
🚫 Never stored
No localStorage. No cookies. No file. Close the tab — the key is gone. That is intentional. That is architecture.
→ Browser to Anthropic directly
Goes straight from your browser to Anthropic's servers. No middleman storing it anywhere.
🛡 For production
Always use a backend proxy so the API key never touches the client at all.
"The harness protects the deal. The security architecture protects the key. Same mindset."
The question is no longer:
"Can you build it?"
The question is:
"Do you know
what to ask for?"
— Li Yingying, Yingfluence
Yingfluence
Let's talk about what you're building.
Influence begins with clarity.
Depth before visibility.
Structure before noise.
www.yingfluence.com
Founder: Li Yingying
Try it yourself
→
Flip to Demo Mode — no key needed
→
Paste your own message for a live read
→
Try different markets and relationship stages
→
Fork it. Build your own version.
github.com/Yingfluencer/yingtell-sea
Scan to connect
←
1 / 9
→
Press → or click to advance