create-extension

Scaffold Flare TEE extensions with SKILL.md and HTTP interfaces.

Updated Apr 3, 2026

Search Tags:#solidity #smart-contracts #extension-development #flare #tee-extension #secure-computation

Ready to run

npx skills add https://github.com/emmatekulova/flex_prover --skill create-extension-emmatekulova

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-extension
Source: https://github.com/emmatekulova/flex_prover/tree/main/.claude/commands/fce
Command: npx skills add https://github.com/emmatekulova/flex_prover --skill create-extension-emmatekulova

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Building Flare TEE extensions can be complex, requiring coordinated architecture, protocol definitions, and on-chain integration. This Skill provides a clear blueprint to scaffold a secure, interoperable extension workflow.

Core Features & Use Cases

Architectural scaffolding for a Flare TEE extension (TEE node, extension server, InstructionSender contract, and registry).
Guidance on handler registration, state management, testing, and deployment considerations.
Use Case: Teams can quickly prototype a secure extension that receives off-chain instructions, performs attestation, and posts results on-chain.

Quick Start

Follow the scaffold to implement a minimal Flare TEE extension with a sample handler and corresponding on-chain registration.

Frequently Asked Questions about create-extension

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

FAQPage Schema

How do I scaffold a Flare TEE extension architecture end-to-end?▼

A Flare TEE extension architecture requires coordinating a TEE node, extension server, and on-chain InstructionSender contract with a registry to handle off-chain instructions, perform attestation, and post results securely to the blockchain.

What components are needed for a secure Flare TEE extension deployment workflow?▼

A secure Flare TEE extension deployment workflow requires a TEE node for secure computation, an extension server exposing HTTP endpoints, an InstructionSender contract, and a registry for handler registration and on-chain integration.

Can I use this to build smart contracts for Flare TEE extensions in a CI environment?▼

Yes, the scaffold supports end-to-end development, testing, and deployment of TEE-backed extensions and smart contracts across multiple languages in both local and CI environments.

How does state management work for Flare TEE extension servers?▼

State management for Flare TEE extension servers relies on a defined HTTP interface utilizing GET /state to retrieve current conditions and POST /action to process instructions, supported by handler registration and versioning schemas.

What is the best way to structure a Flare TEE extension project for interoperability?▼

Structure a Flare TEE extension by defining a frontmatter schema, creating a SKILL.md entry point, organizing optional resources directories, and specifying a defined extension workflow to ensure secure interoperability.

Do I need specific dependencies to develop TEE-backed extensions on Flare?▼

No specific dependencies are required to start developing TEE-backed extensions on Flare, as the scaffold provides the functional requirements and architectural blueprint for teams to prototype across various languages.