Skip to content
Back to search

otp-widget-builder

MarketplaceWorks with Claude CodeGitHub

A Claude skill that helps you build or customize your own OTP verification widget.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/saurabh186--otp-widget-builder/badge.svg)](/listings/saurabh186--otp-widget-builder)

HTML

<a href="/listings/saurabh186--otp-widget-builder"><img src="/api/listings/saurabh186--otp-widget-builder/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Claude Code (recommended)

In a Claude Code session:

/plugin marketplace add Saurabh186/otp-widget-builder
/plugin install otp-widget-builder@otp-widget-builder

Or from your shell:

claude plugin marketplace add Saurabh186/otp-widget-builder
claude plugin install otp-widget-builder@otp-widget-builder

Then ask Claude for an OTP widget, e.g. *"Create an OTP login widget for our React app"*, or run `/otp-widget-builder:otp-widget-builder`.

**Manual install (no plugin system):** download `otp-widget-builder.zip` from [Releases](https://github.com/Saurabh186/otp-widget-builder/releases) and unzip it into `~/.claude/skills/` (just you) or `<your-repo>/.claude/skills/` (shared with your team via git). It then runs as `/otp-widget-builder`.

Claude.ai and Claude Desktop

1. Download `otp-widget-builder.zip` from [Releases](https://github.com/Saurabh186/otp-widget-builder/releases). 2. Turn on **Settings → Capabilities → Code execution and file creation** (newer layouts may call it "Create and edit files"). 3. Go to **Customize → Skills**, upload the ZIP, and make sure the skill is switched on. 4. Ask for an OTP widget in any chat.

On claude.ai, Claude runs code in a sandbox that may not have network or browser access. The skill tells you which checks it couldn't run and gives you the commands to run locally.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 14 lines
  1. {
  2. "name": "otp-widget-builder",
  3. "description": "A Claude skill that helps you build or customize your own OTP verification widget.",
  4. "owner": {
  5. "name": "Saurabh186"
  6. },
  7. "plugins": [
  8. {
  9. "name": "otp-widget-builder",
  10. "source": "./plugins/otp-widget-builder",
  11. "description": "Interactively build or customize a production-ready OTP verification widget on your own APIs, in any frontend stack, with branding, tests and docs."
  12. }
  13. ]
  14. }
README.md · README · 75 lines
  1. # OTP Widget Builder: a Claude skill
  2. A Claude skill that walks you through building your own **OTP verification widget**, or customizing an existing one. Claude asks you questions one at a time, shows a plan for your approval, then writes the code, tests and docs.
  3. - **Any stack:** vanilla TypeScript Web Component, React, Angular, Vue, and others. Claude recommends one based on where the widget will run.
  4. - **Your APIs:** it uses your own send / verify / resend endpoints. It never invents API details and never puts secrets in frontend code.
  5. - **Your design:** the reference layout, your screenshots or Figma, or a generated design, all themed with your brand colours, logo and text.
  6. - **Delivery formats:** embeddable `<script>`, npm package, standalone page, or a component inside your existing app. It builds only the ones you need.
  7. - **Tested and documented:** unit, integration and E2E tests, plus README, API, configuration, integration, customization, architecture, testing and deployment docs and a working demo page. Test results are labelled as mocked or real API.
  8. The OTP flow (timers, resend limits, channel retry, error handling, embedding) is based on the [`production-js` branch](https://github.com/Walkover-Web-Solution/OTP-widget-web/tree/production-js) of Walkover-Web-Solution/OTP-widget-web, the vanilla JavaScript SDK in `core-js/`. The widgets it generates are independent projects with no runtime dependency on that repo.
  9. ## Install
  10. ### Claude Code (recommended)
  11. In a Claude Code session:
  12. ```
  13. /plugin marketplace add Saurabh186/otp-widget-builder
  14. /plugin install otp-widget-builder@otp-widget-builder
  15. ```
  16. Or from your shell:
  17. ```bash
  18. claude plugin marketplace add Saurabh186/otp-widget-builder
  19. ```
  20. ```bash
  21. claude plugin install otp-widget-builder@otp-widget-builder
  22. ```
  23. Then ask Claude for an OTP widget, e.g. *"Create an OTP login widget for our React app"*, or run `/otp-widget-builder:otp-widget-builder`.
  24. **Manual install (no plugin system):** download `otp-widget-builder.zip` from [Releases](https://github.com/Saurabh186/otp-widget-builder/releases) and unzip it into `~/.claude/skills/` (just you) or `<your-repo>/.claude/skills/` (shared with your team via git). It then runs as `/otp-widget-builder`.
  25. ### Claude.ai and Claude Desktop
  26. 1. Download `otp-widget-builder.zip` from [Releases](https://github.com/Saurabh186/otp-widget-builder/releases).
  27. 2. Turn on **Settings → Capabilities → Code execution and file creation** (newer layouts may call it "Create and edit files").
  28. 3. Go to **Customize → Skills**, upload the ZIP, and make sure the skill is switched on.
  29. 4. Ask for an OTP widget in any chat.
  30. On claude.ai, Claude runs code in a sandbox that may not have network or browser access. The skill tells you which checks it couldn't run and gives you the commands to run locally.
  31. ## How a session goes
  32. 1. **Questions:** new or existing widget, where it runs, formats, identifiers and channels, your API contract (with real request/response examples), OTP rules, design, texts, and what your backend needs on success.
  33. 2. **Plan:** a summary, architecture, file list, dependencies and test plan. Nothing is built until you approve it.
  34. 3. **Build:** config, API client, state machine, UI and theming, entry points, and a demo page with a mock mode.
  35. 4. **Verify:** lint, type check, tests, production build, demo run and responsive checks.
  36. 5. **Docs and handoff:** the full documentation set, plus a final checklist covering open items and anything not verified.
  37. ## Repository layout
  38. ```
  39. .claude-plugin/marketplace.json marketplace definition
  40. plugins/otp-widget-builder/
  41. ├── .claude-plugin/plugin.json plugin manifest
  42. └── skills/otp-widget-builder/
  43. ├── SKILL.md workflow and rules
  44. ├── references/ reference-repo architecture, OTP flow, API/security, design, dev and testing guidelines
  45. ├── templates/ project structure, API docs, configuration docs
  46. └── examples/ new widget, API mapping, customization walkthroughs
  47. ```
  48. ## Security notes
  49. - The skill refuses to put private API keys in browser code and treats a successful verification in the widget as a signal only. Your backend must validate the returned token.
  50. - Never paste production secrets into a chat. Use test credentials or a staging environment for real-API testing.
  51. ## License
  52. [MIT](LICENSE). You're free to use, modify and share this skill.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.