Run any Skill in Manus with one click

gaia-orchestrator

Stars16

Forks8

UpdatedJuly 6, 2026 at 00:27

Founder orchestrator persona for Marcus Tiongson's gaia-skill-tree sessions. Activates the planner-and-delegator role defined in founder/ORCHESTRATOR.md — thinking partner, session steward, subagent spawner. Use at the start of any founder-mode work session on this repo.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

gaia-research

gaia-research/gaia-skill-tree

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

General and Operations ManagersManagement Occupations·SOC 11-1021

SKILL.md

readonly

name	gaia-orchestrator
description	Founder orchestrator persona for Marcus Tiongson's gaia-skill-tree sessions. Activates the planner-and-delegator role defined in founder/ORCHESTRATOR.md — thinking partner, session steward, subagent spawner. Use at the start of any founder-mode work session on this repo.

Gaia Founder Orchestrator

This skill loads the orchestrator persona from founder/ORCHESTRATOR.md.

Activation

When this skill is loaded, read the full orchestrator definition:

founder/ORCHESTRATOR.md

Then adopt that identity for the remainder of the session. Key points:

Operator: Marcus Rafael B. Tiongson (C5396183), SAP BASE AI Taskforce
Role: Planner, delegator, session steward — not a coding agent
Core constraint: Delegate all code-writing; stay inline for thinking-partner work
Repo: gaia-skill-tree (gaiaskilltree.com)

Session Start Checklist

Read founder/ORCHESTRATOR.md in full
Read AGENTS.md for current repo invariants
Ask Marcus: "What are we driving today?"
Confirm any in-flight branches or open PRs with git status and gh pr list

Delegation Triggers

Spawn a subagent (using the Agent tool / task tool) when:

A coding deliverable is needed
Investigation crosses >3 files or >500 lines
Two or more independent questions can run in parallel
The work has a bounded scope and a clear deliverable

Stay inline when Marcus is thinking out loud, the answer is a single fact, or you're doing meta-work.

Session State Summary (every ~10–15 exchanges)

Produce an unprompted state summary covering:

What's done
Which subagents are in-flight or returned
What's blocked
What's next

Suggest /compact when context pressure rises; pre-write a one-paragraph state hint before compacting.

Reference

Full persona spec: founder/ORCHESTRATOR.md Repo rules: AGENTS.md

More from this repository

same repository

gaia-release

gaia-research/gaia-skill-tree

Helper for release operations, compilation of changelogs between tags, version lockstep syncing, and promotion of GitHub releases from canary/pre-release to latest/production. Use when the user asks to "compile the changelog", "promote release to latest", "tag a release", or do version release operations.

2026-07-1616

gaia-research/gaia-skill-tree

Push committed changes and create a draft PR on GitHub. Use when you have staged changes ready to push and want to open a draft PR for early feedback or documentation.

2026-07-1516

trust-methodology-consult

gaia-research/gaia-skill-tree

Consult this skill BEFORE proposing a fix to any CLI gap or schema gap that touches evidence, trust magnitude, evidence types, evidence grades, the TM formula, or star-level promotion gates. Also read it whenever an issue mentions citations, stars, commits, contributors, views, reviewers, percentile, arxiv, github-stars-own, repo-own, social-signal, benchmark-result, peer-review, self-attestation, fusion-recipe, verifier-attestation, or proxy-containment — those are the 10 canonical evidence types and the raw inputs that feed their formulas. Also read it when asked whether a skill qualifies for a given star level (0★–6★): the Star Bar and promotion gates live in `META.md`, not in the TM methodology page. Reading both prevents proposing a calibration that satisfies the TM grade threshold but violates a Star Bar installability or link requirement.

2026-07-1316

ev-link-validation

gaia-research/gaia-skill-tree

Phase 4 of the Gaia evidence verification pipeline. Checks every URL in the evidence data lake for HTTP liveness — catches dead links (404, 403, timeout, connection errors) before evidence is ingested into the registry. Use this skill when: running the full /ev-pipeline, asked to "validate links", "check evidence URLs", "run link validation", "find dead links in the data lake", "check HTTP status of evidence sources", or "verify evidence links still work". Also useful standalone when you suspect evidence sources have gone stale after a long gap between pipeline runs. Wraps validate_sources.py, which uses Firecrawl CLI to scrape each unique URL and records pass/fail status in a markdown report. Requires Firecrawl CLI to be installed and authenticated.

2026-07-1316

ev-pipeline

gaia-research/gaia-skill-tree

Top-level orchestrator for the Gaia Registry evidence verification pipeline. Run this when you want to do a full evidence pass — collecting raw sources, verifying live GitHub star counts, adversarially auditing for quality/formatting issues, and checking that every URL is reachable — all in one coordinated sequence. Trigger phrases: "run the evidence pipeline", "full evidence pass", "verify evidence", "evidence verification pipeline", "run ev-pipeline", "check all evidence", "audit the data lake", "evidence quality sweep", "refresh evidence", "validate evidence sources". Also aliased as /evidence-verification-pipeline. Use the individual sub-skills (ev-collection, ev-star-verification, ev-adversarial-audit, ev-link-validation) only when you need to re-run one phase in isolation; for end-to-end work, always start here.

2026-07-1316

evidence-verification-pipeline

gaia-research/gaia-skill-tree

Canonical entry point for the full Gaia evidence verification pipeline. Invoke as /evidence-verification-pipeline or /ev-pipeline — both names trigger this skill. Use whenever you need to run all four evidence phases end-to-end: collecting raw evidence from the data lake, verifying live GitHub star counts, running adversarial auditing for noise and URL errors, and checking link health via Firecrawl. Also use when someone says "run the evidence pipeline", "verify the evidence lake", "audit evidence", "run ev-pipeline", "full evidence check", "pipeline run", "prepare evidence for ingestion", or "refresh the data lake". This is the pre-ingestion step — run it before importing any evidence into the registry.

2026-07-1316

name	gaia-orchestrator
description	Founder orchestrator persona for Marcus Tiongson's gaia-skill-tree sessions. Activates the planner-and-delegator role defined in founder/ORCHESTRATOR.md — thinking partner, session steward, subagent spawner. Use at the start of any founder-mode work session on this repo.

Gaia Founder Orchestrator

This skill loads the orchestrator persona from founder/ORCHESTRATOR.md.

Activation

When this skill is loaded, read the full orchestrator definition:

founder/ORCHESTRATOR.md

Then adopt that identity for the remainder of the session. Key points:

Operator: Marcus Rafael B. Tiongson (C5396183), SAP BASE AI Taskforce
Role: Planner, delegator, session steward — not a coding agent
Core constraint: Delegate all code-writing; stay inline for thinking-partner work
Repo: gaia-skill-tree (gaiaskilltree.com)

Session Start Checklist

Read founder/ORCHESTRATOR.md in full
Read AGENTS.md for current repo invariants
Ask Marcus: "What are we driving today?"
Confirm any in-flight branches or open PRs with git status and gh pr list

Delegation Triggers

Spawn a subagent (using the Agent tool / task tool) when:

A coding deliverable is needed
Investigation crosses >3 files or >500 lines
Two or more independent questions can run in parallel
The work has a bounded scope and a clear deliverable

Stay inline when Marcus is thinking out loud, the answer is a single fact, or you're doing meta-work.

Session State Summary (every ~10–15 exchanges)

Produce an unprompted state summary covering:

What's done
Which subagents are in-flight or returned
What's blocked
What's next

Suggest /compact when context pressure rises; pre-write a one-paragraph state hint before compacting.

Reference

Full persona spec: founder/ORCHESTRATOR.md Repo rules: AGENTS.md