Skip to content

Skill Types

Jump to bottom
mbtiongson1 edited this page Jun 22, 2026 · 4 revisions

Skill Types

Every skill in Gaia belongs to one of four classification types. The type determines its position in the DAG graph, prerequisite thresholds, and the evidence requirements for its named implementations.

Overview

Symbol Schema Value Display Name Graph Position / Rule
○ basic Basic Skill Primitive, indivisible capability — no prerequisites.
◇ extra Extra Skill Emergent pipeline — requires $\ge$ 2 prerequisites.
◉ unique Unique Skill Specialized basic capability — no prerequisites, 0 derivatives (graph-isolated).
◆ ultimate Ultimate Skill Complex capstone — requires $\ge$ 5 prerequisites and Origin Fusion.

Important

Under the G7 framework, all generic skill nodes in the registry (registry/nodes/**/*.json) are starless (rank-less). They define abstract capabilities and prerequisites in the DAG. Star ratings (levels 2★ to 6★, or 1★ for demoted status) are only held by named implementations (registry/named/**/*.md) representing concrete codebases and artifacts.

Basic — Basic Skill ○

Basic skills are the primitive building blocks of the registry. They represent irreducible capabilities that an agent either possesses or does not.

Rules:

  • Must have no prerequisites (prerequisites must be empty).
  • Can be a prerequisite for extra or ultimate skills.
  • Generic basic skill nodes are starless.
  • Named implementations can be claimed at levels 2★ through 6★ depending on their trust magnitude.

Examples:

  • web-search: Issues queries to a search engine.
  • code-generation: Produces source code from a natural-language description.
  • parse-html: Extracts elements from raw markup.

Extra — Extra Skill ◇

Extra skills represent pipeline integrations, emerging when multiple basic or extra skills work in concert to achieve a specific workflow.

Rules:

  • Must have 2 or more prerequisites.
  • The combination must plausibly produce the claimed emergent capability.
  • Generic extra skill nodes are starless.
  • Named implementations can be claimed at levels 2★ through 6★.

Examples:

  • web-scrape (requires web-search · parse-html · extract-entities).
  • rag-pipeline (requires retrieve · chunk-document · embed-text · score-relevance · tokenize · rank).
  • autonomous-debug (requires code-generation · code-execution · error-interpretation).

Unique — Unique Skill ◉

Unique skills are specialized basic capabilities that have achieved a high degree of implementation isolation.

Rules:

  • Must have no prerequisites (prerequisites must be empty).
  • Must be graph-isolated (has 0 derivatives referenced as prerequisites by any other nodes in the graph).
  • Generic unique skill nodes are starless.
  • Named implementations require a level of 4★ (Hardened) or above.

There are currently no unique generic skill nodes defined on disk in the registry.

Ultimate — Ultimate Skill ◆

Ultimate skills represent the absolute apex of agent capability. They are complex capstones bundling dozens of generic skills.

Rules:

  • Must have 5 or more prerequisites.
  • Requires Origin Fusion: The proposing contributor must hold origin: true status on at least 1 of the prerequisite skills in the registry.
  • Requires a minimum of 3 evidence sources of grade A or B (such as arxiv papers, verified benchmarks, or major github-stars-own repositories).
  • Generic ultimate skill nodes are starless.
  • Named implementations are typically graded at level 5★ (Transcendent) or 6★ (Apex).
  • Requires 2 verifier approvals from distinct organizations before merge.
  • Must have status: "validated" at merge (cannot be merged as provisional).

Canonical examples:

  • founder-mode-orchestration
  • multi-topology-orchestration
  • superpowers

Adding a New Skill

  • New Basic: The definition must be indivisible. If it can be decomposed into separate capabilities, it must be modeled as an extra skill.
  • New Extra: List all prerequisites; the combination must produce emergent behavior that no single prerequisite alone provides.
  • New Ultimate: Ensure you satisfy the 5-prerequisite floor and Origin Fusion rule, and compile at least 3 high-grade evidence sources.

→ See Contributing for the submission and review process.

Clone this wiki locally