> ## Documentation Index
> Fetch the complete documentation index at: https://docs.glood.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Install the skills

> Two skills that teach your assistant how to operate Glood well

The MCP server gives your assistant the tools. The skills teach it **how** to
use them: call `whoami` first, never guess which organization a phrase meant,
check what a report is called before running it, and quote the window with every
number.

```bash theme={null}
npx skills add LoopClub/glood-agent-skills
```

One command for Claude, Codex, Gemini CLI, opencode — anything that reads
`SKILL.md`. Copying the files out of the repository does the same without the
CLI.

<Note>
  The skills teach a model how to operate Glood, but they carry no tools of their
  own. Until you [add the MCP server](/platform/connect) there is nothing for them
  to drive.
</Note>

## The two skills

| Skill         | What it teaches                                                                                                                                                                                                                         |
| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `glood`       | **How to use the tools.** Call `whoami` first. Never guess which organization a phrase meant. Check `describe_reports` before `run_report`. Cite the report and the window with every number. Read back the review sentence on a write. |
| `glood-query` | **The query language.** Every measure and dimension by name, which pairs may be combined, the operators and window enums, the refusals, and the traps that make a valid query answer a different question than the one asked.           |

They are split on purpose. A client loads a skill's body only when its
description fires, and most sessions ask for a named report and never compose a
query — those sessions should not carry the vocabulary for one.

## Claude Code gets both at once

The plugin carries the server **and** the skills, so neither step above applies:

```bash theme={null}
/plugin marketplace add LoopClub/glood-claude-plugin
/plugin install glood
```

## claude.ai and ChatGPT need nothing installed

Neither surface loads `SKILL.md` files. **The server sends both skill bodies
itself** when the connection opens, in the MCP `instructions` field, so the same
guidance arrives with nothing installed.

This is why there is no "install the skills" step for a connector — only for a
CLI.

## Keeping them current

Nothing in the skills is configuration. The organization list, the report
catalogue, each agent's instructions and every permission come from the server
at call time — so a change you make in the dashboard reaches your next
conversation with no reinstall, and nothing you installed can go stale in a way
that matters.

## Checking they loaded

Ask:

> "What Glood organizations can you see?"

If the assistant does not recognise `whoami`, the server is connected but the
skills are not loaded. Re-run `npx skills add LoopClub/glood-agent-skills` and
start a new session.