texter-subscription-pipeline

Coordinate phase-gated Texter webhook subscription workflows from JSON creation to Postman documentation.

1|Updated Jul 17, 2025
One-click install
npx skills add https://github.com/whatsper/texterdocs --skill texter-subscription-pipeline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: texter-subscription-pipeline
Source: https://github.com/whatsper/texterdocs/tree/main/.claude/skills/texter-subscription-pipeline
Command: npx skills add https://github.com/whatsper/texterdocs --skill texter-subscription-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines end-to-end setup and validation of subscribe-to-events workflows (SUB) for Texter, ensuring phase-gated delivery and consistent payloads across JSON, Postman, and marketplace.

Core Features & Use Cases

  • Phase-driven workflow with strict sequencing
  • Generates Phase 1 scenario JSON for Texter Scenarios UI
  • Provides Postman documentation template for API import
  • Supports gated progression through Phases 1-4 with explicit confirmations
  • Integrates with Texter marketplace for add-scenario deployment

Quick Start

Create and import Phase 1 Scene JSON for a new SUB scenario in Texter, then test the payload in the UI.

Frequently Asked Questions about texter-subscription-pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a webhook subscription workflow from scenario creation to Postman documentation?

A webhook subscription workflow is set up through strict phase-gated sequencing, starting with Phase 1 scenario JSON creation, then adjusting payloads, and finally generating Postman import blocks for validation before marketplace integration.

What is the correct phase sequence for creating a subscribe-to-events scenario in Texter?

The subscribe-to-events scenario requires strict phase sequencing: Phase 1 generates scenario JSON, Phase 2 handles adjustments, Phase 3 creates Postman description and import blocks, and Phase 4 marketplace deployment is gated until Phase 3 validation explicitly passes.

Can I skip to marketplace deployment before validating the Postman import for my webhook scenario?

Marketplace deployment for a webhook scenario is disallowed until Phase 3 validation is explicitly confirmed, enforcing gated progression to ensure payload consistency across JSON, Postman, and the marketplace before final deployment.

How do I generate Postman documentation for an API testing webhook payload?

Postman documentation for an API testing webhook payload is generated in Phase 3, providing a Postman description and import blocks specifically designed for API import, following Phase 1 JSON creation and Phase 2 adjustments.

Does this webhook subscription pipeline require any external dependencies to function?

The webhook subscription pipeline operates with no external dependencies, coordinating the end-to-end workflow internally to ensure phase-accurate outputs and consistent payloads across JSON, Postman, and marketplace integration.