Gaia Harness Engineering

OrganizationPopular

amd

gaia-harness-engineering

Help a developer report a GAIA TUI, WebUI or agent problem, explicitly share a snapshot with Claude Code or Codex through MCP, and validate isolated worktree fixes.

Overview

Publisher	amd
Repository	`gaia`
Skill name	`gaia-harness-engineering`
Stars	1.6K
Forks	176
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by amd on GitHub. Read the source before you install it.

Installation

Install the Gaia Harness Engineering AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/amd/gaia/tree/main/hub/agents/gaia/python/gaia_agent/skills/gaia-harness-engineering
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/amd/gaia/tree/main/hub/agents/gaia/python/gaia_agent/skills/gaia-harness-engineering

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/amd/gaia.git /tmp/gaia
mkdir -p .claude/skills
cp -r /tmp/gaia/hub/agents/gaia/python/gaia_agent/skills/gaia-harness-engineering .claude/skills/gaia-harness-engineering

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Gaia Harness Engineering in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Gaia Harness Engineering on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Gaia Harness Engineering is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Developer handoff

This skill is enabled by the host only in developer mode. Start only when the developer reports a problem or requests an improvement. Do not automatically assess friction or start coding. Keep GAIA available for daily work.

Clarify expected and observed behavior. Use engineering_status without a job ID to inspect source-cache initialization and coding-app setup. Surface failures and connection instructions; do not claim connection or task launch merely because the app exists.
Select claude or codex with the developer. Prepare a concise summary and selected evidence. Do not collect entire histories, unrelated files or credentials. share_engineering_context shows the exact summary and context and requests fresh approval before the selected coding app can read them. The app may use a cloud provider; its existing filesystem permissions remain independent of this bridge. Never use shell, file tools or another MCP tool to bypass this approval. Bypass-permissions mode cannot approve sharing.
Give the developer the job ID and connection instructions. Use open_engineering_app only when asked to open the app. An opened app or prefilled composer is not a submitted or running task. The developer may interact directly in their existing coding app. For Codex specifically, opening only brings the app forward: it does not create a task, select a folder or prefill a composer. Say this explicitly, then show the returned directory and exact prompt to paste into a new task. Never say "posted to Codex", "sent", or "look for the prefilled composer". A generated MCP config is not an installed or verified client connection.
Diagnose before editing: reproduce safely using synthetic or read-only inputs, inspect configuration/model limits and actual build identities, check releases and existing issues/PRs. Do not replay destructive tools or external sends. Recommend a model/configuration change when evidence supports it; ask before changing the user's model. Unknown root cause stays unknown.
After diagnosis, use approve_engineering_code to request worktree scope. All edits must be in an isolated worktree from the managed GAIA cache. Private snapshots stay outside Git; they must not become fixtures or commits.
Have the coding app launch a separate agent/TUI/WebUI preview with isolated writable state, ports and explicit build revision. A worktree is not a security sandbox. Let the developer test and iterate. Share additional feedback only through append_engineering_context, which asks again.
Use engineering_status for reported progress and preview details. Clearly distinguish app-reported results from locally verified checks. Native app conversations and detailed coding remain in that app.
Review all outgoing public text, code and commit history. Generalize private examples. Workflow approval does not make raw context safe to publish. Follow repository contribution/review requirements; maintainers own merge.
revoke_engineering_context stops future bridge reads. Already delivered data cannot be recalled. Stable release updates are a separate feature; never replace the running GAIA installation from a preview worktree.

Frequently asked questions

What does the Gaia Harness Engineering AI skill do?

Help a developer report a GAIA TUI, WebUI or agent problem, explicitly share a snapshot with Claude Code or Codex through MCP, and validate isolated worktree fixes.

Why use Gaia Harness Engineering on TypingMind?

Because you install it once and use it with any model. Gaia Harness Engineering is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Gaia Harness Engineering in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/amd/gaia/tree/main/hub/agents/gaia/python/gaia_agent/skills/gaia-harness-engineering. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Gaia Harness Engineering?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Gaia Harness Engineering?

As many as you like. As long as a model supports skills, you can use Gaia Harness Engineering with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Gaia Harness Engineering AI skill free?

Yes. It is published on GitHub by amd under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Discord Clawd

openclaw

OrganizationPopular

Use to talk to the Discord-backed OpenClaw agent/session; not for archive search.

Discrawl

Discord archive: search, sync freshness, DMs, summaries, TUI, repo/release work.

Gitcrawl

GitHub archive: issue/PR search, sync freshness, duplicate clusters, current GitHub handoff, and Gitcrawl repo work.

Graincrawl

Granola archive: search, sync freshness, notes, transcripts, panels, SQL counts, and Graincrawl repo work.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Developer handoff

Frequently asked questions

Related AI Skills

Set up your own AI workspace now