edgion-skills

Route developer tasks to minimal Edgion knowledge subtrees via SKILL.md frontmatter.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Pandaala/Edgion --skill edgion-skills
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: edgion-skills
Source: https://github.com/Pandaala/Edgion/tree/main/skills
Command: npx skills add https://github.com/Pandaala/Edgion --skill edgion-skills

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly find the right Edgion docs and operational guidance for understanding architecture, using configuration features, and following code-level conventions when debugging or implementing changes.

Core Features & Use Cases

  • Progressive discovery navigation: start from the root skill and then load only the smallest relevant subtree (architecture, features, or coding) to reduce noise.
  • Architecture → features → coding workflow: supports cross-domain tasks by guiding you through internal processing flow, external schemas/config contracts, and code constraints in the right order.
  • Task and symptom locators: provides entry points for common developer workflows (plugin development, Controller↔Gateway sync debugging) and symptom-based triage (Unknown kind, routing failures).

Quick Start

Use the edgion-skills skill to locate the smallest subtree for your current task, then jump to the specific entry point for architecture, features/config schema, or coding conventions.

Frequently Asked Questions about edgion-skills

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

FAQPage Schema
How do I navigate Edgion architecture docs to troubleshoot Controller and Gateway sync issues?

To troubleshoot Controller↔Gateway sync issues, you navigate the Edgion architecture subtree from the root skill to locate internal processing flows, routing behavior details, and relevant coding standards for fast debugging and resolution.

What is the best way to find Edgion configuration schema references for implementing new plugins?

The best way to find Edgion configuration schema references for plugin development is by routing from the root skill into the feature and config reference subtree, ensuring you load only the minimal relevant documentation needed.

How does progressive discovery help reduce noise when debugging Edgion routing failures?

Progressive discovery reduces noise during Edgion routing failure debugging by loading only the smallest relevant knowledge subtree—such as architecture or coding conventions—instead of surfacing unrelated operational guidance or configuration schemas.

Do I need a specific SKILL.md YAML frontmatter format to use Edgion knowledge navigation?

Yes, Edgion knowledge navigation requires a mandatory SKILL.md YAML frontmatter containing name and description fields, which enables the internal directory locators and task entry points to function correctly for documentation discovery.

Can I use symptom-based triage to locate coding standards for unknown kind errors in Edgion?

Yes, you can use symptom-based triage entry points to locate Edgion coding standards and architecture constraints specifically for unknown kind errors, guiding you directly to the correct code-level conventions for resolution.

When should I not use the Edgion root skill for finding operational guidance?

You should not use the Edgion root skill when you need full documentation access, as it applies progressive discovery to load only the minimal relevant subtree, intentionally excluding unrelated architecture or feature schemas to reduce noise.