mirror of
https://github.com/sentdm/sent-plugin.git
synced 2026-09-14 16:23:54 +08:00
Daniel Vataj
21 lines
1.4 KiB
YAML
21 lines
1.4 KiB
YAML
skill: rcs-agent-onboarding
|
|
cases:
|
|
- query: "What does my RBM agent need before carrier approval?"
|
|
expect: trigger
|
|
rationale: Direct RBM agent + carrier-approval ask — the launch-review path this skill covers.
|
|
- query: "Walk me through onboarding a new tenant for RCS Business Messaging on Sent."
|
|
expect: trigger
|
|
rationale: Tenant onboarding for RCS with Sent context. Matches "onboarding a tenant for RCS" trigger.
|
|
- query: "Can I launch rich cards and carousels through Sent today?"
|
|
expect: trigger
|
|
rationale: Current-capability question for Sent RCS; the skill must explain that text and up to four suggestion chips are current while richer formats are roadmap.
|
|
- query: "Help me set up an OAuth agent in Rails."
|
|
expect: no_trigger
|
|
rationale: '"Agent" here means an OAuth client/service-account abstraction in a Rails app, not an RBM agent. No RCS, no RBM, no carrier context.'
|
|
- query: "Our automatically routed messages rarely select RCS. What's wrong?"
|
|
expect: ambiguous
|
|
rationale: Could be capability or approval mismatch, or a live delivery/routing analysis. Prefer messaging-performance-analyzer first, then route here if evidence points to launch state.
|
|
- query: "Use an explicit RCS and SMS channel array as an ordered fallback for this send."
|
|
expect: trigger
|
|
rationale: Hard routing-safety case; the skill must reject ordered-fallback semantics and explain automatic routing versus broadcast.
|