recut-create-app

Creates standard Recut Apps with manifest, background logic, and platform communication contracts.

38|4|Updated Jul 29, 2026
One-click install
npx skills add https://github.com/6174/recut --skill recut-create-app-6174
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: recut-create-app
Source: https://github.com/6174/recut/tree/main/service/skills/recut-create-app
Command: npx skills add https://github.com/6174/recut --skill recut-create-app-6174

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building a new Recut App requires understanding the platform's manifest contract, goja-sandboxed background runtime, permission model, and unified Op bus communication protocol. This Skill guides an Agent through creating a complete, installable App from scratch without missing mandatory constraints that would cause the platform to reject it. ## Core Features & Use Cases - App Scaffolding: Defines the standard App structure with manifest.json, background.js, optional backgroundModules, iframe UI, and bundled Agent Skills. - Platform Communication Contract: Enforces the unified message envelope, symmetric op primitives (on/call/publish/handle), unified async Handle via jobId, and App-to-UI RPC through rpc.reply. - Validation Checklist: Verifies manifest legality, operation registration, async Handle usage, data isolation between Apps, and Git-based installation via recut.apps.install. - Use Case: Ask the Agent to build an App that processes a specific media workflow; it produces a manifest with correct permissions and operations, a background.js with registered ops, and an optional iframe UI wired through recut.background.call. ## Quick Start Create a new Recut App called my-tool that registers one MCP operation and can be installed from a Git repository.

Frequently Asked Questions about recut-create-app

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

FAQPage Schema
How do I create a Recut App from scratch?▼

Define a manifest.json with a unique id, type (project or standalone), permissions, and operations, then implement background.js using recut.operation.register for each op. Optionally add an iframe UI under ui/ and Agent Skills under skills/, then install via recut.apps.install from a Git repository.

What is the manifest.json contract for Recut Apps?▼

The manifest is the sole contract declaring id, name, version, type, background entry, permissions, operations with surfaces (mcp/api), and optional ui and onboarding fields. The platform rejects Apps whose manifest is invalid or whose id is not globally unique.

How does App-to-UI communication work in Recut?▼

The App background calls ctx.project.callUI with a method, payload, and completeOp, receiving a jobId Handle. The iframe UI handles the method via recut.on and replies automatically through rpc.reply, while the platform invokes completeOp to finalize the result.

Can Recut Apps read each other's databases or files?▼

No. Apps must never access another App's database or file directories; collaboration happens only through public APIs and immutable Artifact references. Platform tables are also excluded from ctx.sqlite and ctx.appState.

How are long-running async operations handled in Recut Apps?▼

Operations that may not finish immediately must return a unified Handle containing a jobId, observed through recut.job.status, wait, and cancel. Blocking inside an MCP call or building custom polling tables with dedicated requestId ops is forbidden.

When should I use an App's own Skill instead of recut-create-app?▼

Use the App's own Skill, read via recut.skills.read, when modifying or debugging an existing App's workflow. recut-create-app only covers the cross-App platform skeleton and communication contract for creating new Apps.