stripe

Name: stripe
Availability: InStock
Author: HybridAI

Investigate Stripe customers, subscriptions, payments, and webhook events across test and live modes.

126|11|Updated Feb 24, 2026

Search Tags:#debugging #subscriptions #billing #payments #stripe #webhooks #stripe cli

Ready to run

npx skills add https://github.com/HybridAIOne/hybridclaw --skill stripe-hybridaione

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: stripe
Source: https://github.com/HybridAIOne/hybridclaw/tree/main/skills/stripe
Command: npx skills add https://github.com/HybridAIOne/hybridclaw --skill stripe-hybridaione

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stripe billing teams need fast, reliable answers about customer/payment state and webhook behavior without risking accidental changes, especially across test vs live environments.

Core Features & Use Cases

Customer and subscription investigation: Locate and inspect customers, products, prices, subscriptions, payment intents, and checkout sessions to explain what happened.
Webhook and event troubleshooting: Debug local forwarding and webhook delivery by correlating specific event IDs and object IDs with app processing and endpoint outcomes.
Safe operational workflow planning: Draft read-first steps and confirm exact identifiers before any mutation, using Stripe CLI/API/Dashboard as the source of truth.

Quick Start

Forward Stripe events to your local webhook endpoint, then ask which specific event and object ID are failing and whether the issue is test or live mode.

Frequently Asked Questions about stripe

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

FAQPage Schema

How do I debug Stripe webhook delivery issues using the CLI?▼

Debug Stripe webhook delivery by using the CLI to forward events to your local endpoint, then correlating specific event IDs and object IDs with app processing and endpoint outcomes to trace failures end-to-end.

Why is my Stripe subscription billing outcome unexpected?▼

Stripe subscription billing outcomes require investigating customers, products, prices, and payment intents to explain what happened, ensuring you confirm exact identifiers and determine whether the issue is in test or live mode first.

What is the safest workflow for inspecting Stripe payment intents before making changes?▼

Safe Stripe inspection requires a read-first approach to locate and inspect payment intents and checkout sessions, confirming exact identifiers and determining test-vs-live status before planning any mutations or changes.

Can I use Stripe CLI to troubleshoot both test and live mode integrations?▼

Yes, Stripe CLI supports troubleshooting integrations across both test and live modes, requiring correct test-vs-live determination and identifier confirmation before tracing specific events or attempting any safe operational workflow planning.

What should I do when Stripe webhook events are not reaching my local endpoint?▼

When Stripe webhook events fail to reach your local endpoint, forward events via Stripe CLI, then trace one concrete event ID and object ID end-to-end to correlate app processing with endpoint delivery outcomes.

Does investigating Stripe billing require authenticated API access?▼

Yes, investigating Stripe billing state and webhook behavior requires authenticated Stripe API workflows, using the Dashboard, CLI, or API as the source of truth to inspect customers, subscriptions, and payments safely.