skills.rest
orchestra-mcp
orchestra-mcpOFFICIAL
Explore all skills by this author →
WebsiteGitHub

native-extensions

Develop native Orchestra IDE extensions with a TypeScript API and JSON manifest.

3|1|Updated Feb 27, 2026
Search Tags:#typescript#api#sdk#ide#native#extension development
One-click install
npx skills add https://github.com/orchestra-mcp/framework --skill native-extensions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: native-extensions
Source: https://github.com/orchestra-mcp/framework/tree/main/.claude/skills/native-extensions
Command: npx skills add https://github.com/orchestra-mcp/framework --skill native-extensions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides the comprehensive API and framework for developing native extensions, enabling deep integration and full platform access within the Orchestra IDE.

Core Features & Use Cases

  • Full Platform Access: Develop extensions with direct access to filesystem, network, AI, and UI APIs.
  • Extension Development: Design, build, and manage complex IDE extensions using TypeScript and a familiar manifest format.
  • Use Case: Create a custom code linter extension that uses AI to suggest refactors and integrates directly with the editor's UI to display warnings and errors.

Quick Start

Use the native-extensions skill to register a new command that displays a notification.

Frequently Asked Questions about native-extensions

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

FAQPage Schema
How do I build native extensions for the Orchestra IDE?▼

To build native extensions for the Orchestra IDE, use the TypeScript API to define custom commands and UI panels through a JSON manifest. This framework facilitates deep integration, granting full platform access for filesystem and AI operations.

What is the best way to integrate an AI code linter directly into the IDE?▼

The best way to integrate an AI code linter is by developing a native extension using the TypeScript API. This allows your custom linter to interact directly with the editor's UI to display warnings and suggest refactors.

Do I need a JSON manifest to develop IDE extensions with TypeScript?▼

Yes, you need a JSON manifest to develop IDE extensions with TypeScript. Defining your extension capabilities through this manifest is required to adhere to the strict permission system and access platform features.

Can I access the filesystem and network when developing custom commands?▼

Yes, you can access the filesystem and network when developing custom commands. Native extensions provide full platform access via the TypeScript API, facilitating operations like filesystem interactions and network requests.

How does the permission system work for Orchestra native extensions?▼

The permission system requires declaring extension capabilities in a JSON manifest. This strict system ensures native extensions developed via the TypeScript API only access explicitly defined filesystem, network, AI, and UI APIs.

What are the limitations when creating UI panels and AI integrations in Orchestra?▼

Limitations for creating UI panels and AI integrations stem from the strict permission system defined in your JSON manifest. Extensions must explicitly declare capabilities, restricting access to only the approved TypeScript APIs.

Related Skills

Explore More Software Engineering Skills→
kraftvaerkkraftvaerk

umbraco-entity-actions

Create custom entity actions in the Umbraco backoffice using manifest files and TypeScript classes.

Official
Intermediate
kraftvaerkkraftvaerk

umbraco-package-view

Create custom package views in the Umbraco backoffice.

Official
Intermediate
Moliboy5000Moliboy5000

mcp-setup

Configure MCP servers like Context7, Exa, Filesystem, and GitHub via CLI.

Community
Intermediate
minhtri2710minhtri2710

cli-builder

Build TypeScript command-line interfaces with Bun.

Community
Advanced