Agent skill · software engineering · aiskillstore
blocklet-converter
Converts static web or Next.js projects into ArcBlock blocklets using provided DID. Analyzes project structure, generates configuration files, and validates setup. Requires blocklet DID as parameter.
Why this skill is useful
Adds a complete executable workflow for converting web projects into ArcBlock blocklets, including configuration generation and validation scripts.
What it needs
Requires blocklet, bun installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Blocklet Converter Converts static web projects and Next.js applications into ArcBlock blocklets with proper configuration and validation. Parameters did (required): Pre-generated blocklet DID (format: z8ia...) Example: "Convert this project to blocklet using DID z8ia4e5vAeDsQEE2P26bQqz9oWR1Lxg9qUMaV" If missing or invalid, exit immediately with error message: "Blocklet DID parameter is required." Workflow 1. Project Analysis Skip directories: nodemodules/, .pnpm/, .yarn/, .cache/, .turbo/, bowercomponents/ Verify Web Application Exists Check for ANY of: package.json with web-related dependencies index.html in root, public/, or src/ or common locations Web framework config (vite.config., webpack.config., next.config., etc.) If none found → EXIT with error message: "No web application detected." Detect Project Type Check package.json dependencies for: Next.js: next in dependencies → Next.js project Backend frameworks: express, koa, fastify, nest, etc. → EXIT with error: "Only static webapp and next.js projects are supported." Otherwise → Static webapp Extract & Emit Metadata (Early) Immediately after confirming project type, extract metadata from package.json: title: Human-friendly project name suitable for public display (e.g., my-cool-app → My Cool App) description: A clear, non-technical description for end users. If package.json description is too technical, rewrite it to be user-friendly. Emit using the protocol below, then continue with the workflow: Build (if build script exists) If either fails → EXIT with error output. Locate Output Directory For Next.js projects: Output directory is always .next — skip detection. For static webapps: Find index.html in: dist/ → build/ → out/ → public/ → ./, or any other common locations. If not found → EXIT with error message: "No index.html entry point found." Confirm Output Directory Verify the output directory exists and contains expected files before proceeding. 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/blocklet-converter