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/cases.yaml

View on GitHub
skill: whatsapp-telegram

should_trigger:
  - prompt: "Send an order-confirmation WhatsApp message to a customer via the Cloud API"
    why: Core WhatsApp Cloud API send — the central job of this skill.
  - prompt: "My WhatsApp sends return error 131047, how do I re-engage the user?"
    why: Non-obvious — #131047 is the closed-24h-window error; the fix is sending an approved template.
  - prompt: "Build a Telegram bot that broadcasts alerts to subscribers and handle 429 retry_after"
    why: Telegram send plus the rate-limit/backoff rule this skill owns.
  - prompt: "Vull enviar una plantilla de WhatsApp d'avis de cita als clients"
    why: Catalan phrasing for a WhatsApp template send (appointment-reminder template).
  - prompt: "Set up the WhatsApp inbound webhook and verify the X-Hub-Signature-256 header"
    why: Non-obvious WhatsApp-specific webhook setup (verify token + HMAC signature).
  - prompt: "Should I use setWebhook or getUpdates for my Telegram bot?"
    why: Telegram inbound decision — the two modes are mutually exclusive, a known footgun.
  - prompt: "Why are my WhatsApp template blasts being billed per message now instead of per conversation?"
    why: Non-obvious — pricing changed to per-message on 2025-07-01; agent must know the current model.

should_not_trigger:
  - prompt: "Write the actual support reply text and triage this angry customer"
    route_to: customer-support
    why: Content/tone and triage of the reply, not the transport pipe.
  - prompt: "Plan our week's posts across LinkedIn, Instagram and TikTok"
    route_to: social-publisher
    why: Social content calendar and multi-platform posting, not 1:1 messaging APIs.
  - prompt: "Write a cold first-touch DM sequence to prospects who never replied"
    route_to: cold-outreach
    why: First-touch outreach copy and cadence, not message delivery plumbing.
  - prompt: "Design a generic webhook receiver with retries and idempotency for any provider"
    route_to: webhooks
    why: Abstract receiver design; this skill covers only WhatsApp/Telegram-specific setup.
  - prompt: "When a Stripe payment succeeds, message the customer on WhatsApp — orchestrate the whole flow"
    route_to: automation-flows
    why: Cross-tool multi-step orchestration, not a single send implementation.

capability:
  - scenario: "Implement a function that messages a WhatsApp customer: send a free-form text if they messaged within the last 2 hours, otherwise send an approved template. Use the Cloud API."
    must_include:
      - "Endpoint pins the Graph version, e.g. https://graph.facebook.com/v25.0/{PHONE_NUMBER_ID}/messages"
      - "Bearer token read from env (e.g. process.env.WA_TOKEN), never hardcoded"
      - 'Body includes messaging_product: "whatsapp", to, and type'
      - "Branches on the 24-hour window: in-window -> free-form text, out-of-window -> template"
      - "Explains that out-of-window free-form fails with error #131047"
      - "Captures the response message id (messages[0].id) for delivery tracing"
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