agentsclimarketplace

Push notification tester

Skill team-telnyx/ai/skills/push-notification-tester

Test VoIP push notifications for Telnyx WebRTC iOS (APNs) and Android (FCM) apps. Use when debugging push notification delivery, validating certificate/credential setup, or testing that a device receives VoIP pushes correctly.From its SKILL.md

Install
npx -y skills add team-telnyx/ai --skill push-notification-tester

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

2.1 KB, 516 tokens by cl100k_base, as published. Nobody here has run it

Push Notification Tester

Send test VoIP push notifications to iOS (APNs) and Android (FCM) devices.

iOS (APNs)

node {baseDir}/scripts/send-ios-push.js \
  --token=<device_token> \
  --bundle-id=<bundle_id> \
  --cert=<path/to/cert.pem> \
  --key=<path/to/key.pem> \
  [--env=sandbox|production] \
  [--caller-name="Test Caller"] \
  [--caller-number="+1234567890"]

Required args

  • --token — 64-char hex APNs device token
  • --bundle-id — App bundle ID (e.g. com.telnyx.webrtc)
  • --cert — Path to certificate PEM file
  • --key — Path to private key PEM file

Optional args

  • --envsandbox (default) or production
  • --caller-name — Display name (default: "Test Caller")
  • --caller-number — Phone number (default: "+1234567890")

Android (FCM)

node {baseDir}/scripts/send-android-push.js \
  --token=<fcm_token> \
  --project-id=<firebase_project_id> \
  --service-account=<path/to/service-account.json> \
  [--caller-name="Test Caller"] \
  [--caller-number="+1234567890"]

Required args

  • --token — FCM device token
  • --project-id — Firebase project ID
  • --service-account — Path to service account JSON file

Optional args

  • --caller-name — Display name (default: "Test Caller")
  • --caller-number — Phone number (default: "+1234567890")

Output

Both scripts output JSON to stdout:

{"success": true, "message": "Push notification sent successfully", "details": {...}}
{"success": false, "error": "Description of what went wrong"}

Exit code 0 on success, 1 on failure.

Dependencies

Run npm install in the scripts/ directory, or the scripts will auto-install on first run.

  • @parse/node-apn — APNs client for iOS
  • google-auth-library — Google OAuth for FCM
  • axios — HTTP client for FCM API

What ships with it: 3 files

6.6 KB alongside SKILL.md, 2 of them executable

scripts/

Gives 0 of the 12 instructions most test skills give in 516 tokens

Counted across 1,201 of the 2,096 authors here whose files we hold, read 2026-09-06

  • Write a failing test before writing codein 43 of 1201, across 36 files
  • Run the full test suitein 36 of 1201, across 35 files
  • Test only one variable per experimentin 34 of 1201, across 17 files
  • Read product marketing context before asking questionsin 34 of 1201, across 14 files
  • Mock external dependenciesin 34 of 1201, across 30 files
  • Define primary, secondary, and guardrail metricsin 33 of 1201, across 16 files
  • Pre-determine sample size before startingin 31 of 1201, across 14 files
  • Test behavior rather than implementationin 31 of 1201, across 29 files
  • Formulate a hypothesis before designing a testin 30 of 1201, across 13 files
  • Document every test hypothesis, variant, and resultin 29 of 1201, across 11 files
  • Use descriptive test function namesin 25 of 1201, across 21 files
  • Commit to the methodology without stopping earlyin 24 of 1201, across 8 files

Said here and by no other author read

  • Run iOS push script with required tokens and certificates

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.