Bundle Integration Steer

Integrate scenarios into the LPBS Business Suite bundle with JWT validation, entitlements, and credit metering.

54|7|Updated Sep 19, 2021
One-click install
npx skills add https://github.com/Vrooli/Vrooli --skill bundle-integration-steer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Bundle Integration Steer
Source: https://github.com/Vrooli/Vrooli/tree/main/scenarios/prompt-manager/store/skills/packs/core/bundle-integration-steer
Command: npx skills add https://github.com/Vrooli/Vrooli --skill bundle-integration-steer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures every app in the Business Suite bundle stops reinventing authentication, entitlements, and credit metering so subscribers receive consistent gating, shared credits, and authenticated downloads from LPBS.

Core Features & Use Cases

  • JWT Authentication Middleware: Validates LPBS-issued tokens via Authorization header or access_token cookie, checks issuer, expiry, and signing secret, then sets user context without storing credentials.
  • Entitlements & Credit Consumption: Calls the LPBS entitlements endpoint with short caching, handles authorized/forbidden responses, consumes credits before expensive work, includes scenario metadata, and maps errors to the standard LPBS shape.
  • LPBS Registration & Audit: Registers the app and platform assets in download_apps/download_assets with requires_entitlement flags, documents integration findings, and uses visited-tracker plus internal docs to keep the bundle auditable.

Quick Start

Use the bundle integration steer to audit the scenario, confirm JWT middleware, entitlement checks, and LPBS registration before releasing the app.

Frequently Asked Questions about Bundle Integration Steer

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

FAQPage Schema
How do I enforce shared JWT authentication and credit metering across bundled applications?

LPBS JWT authentication validates tokens via the Authorization header or access_token cookie, checking the issuer, expiry, and signing secret. It sets the user context securely without storing credentials, ensuring consistent subscription gating across bundled apps.

What is the best way to consume LPBS credits before running expensive operations?

The best way to consume LPBS credits is by calling the entitlements endpoint with short caching before expensive work begins. This checks authorization, includes scenario metadata, consumes the required credits, and maps errors to the standard LPBS shape.

How do I register platform assets for authenticated downloads in the LPBS bundle?

Register platform assets by adding them to download_apps and download_assets with requires_entitlement flags. This LPBS registration process ensures downloads are gated by entitlement checks and keeps the bundle auditable via visited-tracker and internal docs.

Does LPBS subscription gating work across different platforms and supported app environments?

LPBS subscription gating works across supported platforms by applying JWT validation, entitlement checks, and credit metering consistently. The integration ensures registration metadata matches LPBS contracts so every platform receives identical gating and shared credits.

Why does my app need entitlement error mapping when integrating with the LPBS Business Suite?

Entitlement error mapping is needed to ensure forbidden or failed credit consumption responses match the standard LPBS error shape. This maintains consistent error handling and subscription gating behavior across every app in the Business Suite bundle.