fastedge-core

Routes FastEdge requests between docs retrieval and MCP-backed execution skills in Codex.

1|Updated Jul 23, 2026
One-click install
npx skills add https://github.com/G-Core/fastedge-plugin --skill fastedge-core-g-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fastedge-core
Source: https://github.com/G-Core/fastedge-plugin/tree/main/plugins/gcore-fastedge-codex/skills/fastedge-core
Command: npx skills add https://github.com/G-Core/fastedge-plugin --skill fastedge-core-g-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Working with Gcore FastEdge in Codex requires knowing whether a request needs documentation lookup or actual build/deploy execution, and which specialized skill should handle it. This core skill acts as the routing layer that directs each FastEdge request to the right task skill while enforcing a strict separation between local docs retrieval and MCP-backed execution. ## Core Features & Use Cases - Task Routing: Directs requests to specialized skills for scaffolding, deploying, managing, testing, debugging, live-testing, and documentation lookup. - Docs-First Retrieval: Uses a docs index with topic IDs, tags, and line ranges to answer FastEdge API and concept questions with minimal context loading. - MCP Execution Protocol: Coordinates build, deploy, and manage operations through the FastEdge MCP server, with clear diagnostics when MCP is unavailable. - Use Case: A developer asks to deploy a new Wasm edge app; the skill routes the request to the deploy skill, which uses MCP tools like build-wasm and upload-binary, while a separate question about FastEdge API concepts is answered from local indexed docs. ## Quick Start Ask to create and deploy a new FastEdge app, and the skill will route your request to the appropriate scaffold and deploy skills backed by the FastEdge MCP server.

Frequently Asked Questions about fastedge-core

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

FAQPage Schema
How do I deploy a FastEdge app from Codex?

Ask to build and deploy your app, and the core skill routes the request to the deploy skill, which uses the FastEdge MCP server tools build-wasm, upload-binary, and gcore_api. The MCP server must be configured with a valid GCORE_API_KEY for execution to work.

How does the FastEdge core skill decide which skill to use?

It routes by request type: new projects go to scaffold, build and deploy requests to deploy, lifecycle and secrets management to manage, test generation to test, and documentation questions to fastedge-docs. Each task skill mirrors the Claude plugin behavior.

What happens if the FastEdge MCP server is not configured?

The skill stops before any build, deploy, or manage execution and states that MCP is required. It helps diagnose the cause, such as Docker not running or GCORE_API_KEY not visible, while docs, scaffolding, and test work continue without MCP.

Can I use local toolchains instead of the FastEdge MCP server?

Local toolchains are an explicit opt-out, not a default path. They are only surfaced if you decline Docker, and the skill warns that this route is unsupported since the MCP server ships bundled with the plugin.

How are FastEdge documentation questions answered without loading full docs?

The skill reads the docs-index.json file, selects topics by id, tags, category, and language, then reads only the relevant line ranges from referenced markdown files. This keeps context usage minimal unless full docs are explicitly requested.