About this skill

Problem Addressed

Formbricks Wrap has a narrow focus: it wraps Formbricks for use in TypeScript projects and fits github and automation style workflows. The available metadata lists tags and a version, but does not expose concrete APIs, form fields, authentication methods, or deployment steps, so it should be read as a thin wrapper rather than a full business component.

How It Is Presented

The metadata identifies the author as q15004040209-creator, the version as 1.0.0, and the main signal as wrap. The implied usage is to package Formbricks-related capabilities into TypeScript-callable forms and then invoke them from scripts, CI tasks, or GitHub workflows. Because the body does not specify initialization, error handling, event callbacks, or configuration options, readers should first confirm which functions are exported, what their parameters are, and how external triggers are configured.

Boundaries

If a project already uses a TypeScript stack and only needs a lightweight wrapper layer to connect to Formbricks, this skill can be a candidate. For production use, verify authentication, secret configuration, retries, timeouts, callback signatures, and logging; when the documentation is incomplete, do not assume these capabilities are already implemented.

Screenshots

Use Cases

A TypeScript project needs to call Formbricks-related capabilities from scripts and verify whether the wrapper interface is sufficient.
A GitHub workflow needs to integrate Formbricks automation tasks and evaluate whether this wrap is a suitable entry layer.
A team maintains a TypeScript toolchain and needs to package Formbricks-related calls into a reusable module.

Best For

Engineers maintaining TypeScript services or scripts who need to call Formbricks-related capabilities in code
Engineers responsible for GitHub automation workflows who need to connect an external form tool to CI/CD scripts
Technical leads evaluating third-party wrap packages to decide whether one can replace hand-written Formbricks calls