Skip to content

ericrisco/rsc-harness / skills/whatsapp-telegram

whatsapp-telegram

Verified

Use when wiring an app or agent to message customers over the WhatsApp Cloud API or a Telegram bot — order updates, OTP codes, reminders, alerts and broadcasts — or when debugging undelivered messages, 24-hour-window errors, rejected templates, webhook signature verification, or rate limits and their retry headers. NOT the reply content you send (that is `customer-support`).

FileKindSize
SKILL.mdskill md11.6 KB
evals/README.mdmarkdown804 B
evals/cases.yamlconfig3.0 KB
references/telegram-bot-api.mdmarkdown3.4 KB
references/whatsapp-cloud-api.mdmarkdown4.5 KB
scripts/verify.shexecutablescript3.8 KB

evals/README.md

View on GitHub
# Evals — whatsapp-telegram

These cases are LLM-graded. `should_trigger` / `should_not_trigger` check that the skill's
description and body route correctly: each `should_trigger` prompt (including a Catalan and a
non-obvious error-code phrasing) must select this skill, while each `should_not_trigger` prompt
must defer to the named sibling (`route_to`). The `capability` case is scored against its
`must_include` rubric — a grader reads the skill body + references and confirms each bullet is
satisfiable (pinned `v25.0` endpoint, env-sourced token, `messaging_product` body, 24h-window
branch with #131047, captured message id). Run them with the repo's eval runner pointed at this
skill directory; there is no live API call — grading is on the produced guidance, not on sending a
real message.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall