Skip to content

Tools

Tools extend goga with specialized capabilities. Each tool is a separate Python package that installs skills into your AI agent and provides CLI commands.

Installing a tool

Tools are distributed as Python packages with the goga-tool- prefix:

pip install goga-tool-<tool-name>

After installing, connect the tool to your agent:

goga connect <agent>

goga connect auto-discovers all installed goga_tool_* packages and copies their skills into the agent's skills directory. The tool becomes available both as an agent skill and as a CLI command.

Built-in tools

The following tools ship with goga out of the box — no separate install required. They are registered automatically once goga is installed and goga connect has been run.

Tool Description Docs GitHub
viewer Interactive dependency graph viewer for CODEMANIFEST cells Documentation Source
mkdocs Generate and maintain MkDocs documentation from CODEMANIFEST files Documentation Source
scriba The writer — translates texts between languages and reviews texts against prompt-engineering principles Documentation Source

Using a tool

Via CLI:

goga tool <name> [args...]

Via agent skill:

Invoke the /goga:tool <name> command in your agent session. The dispatcher routes the request to the matching skill.

Tool structure

Each tool package follows a standard layout:

goga_tool_<name>/
├── __init__.py        # main(args) entry point for CLI
└── skills/
    └── <skill>/
        └── SKILL.md   # Agent skill definition

A valid tool must:

  • Be named with the goga_tool_ prefix
  • Contain a skills/ directory with at least one skill
  • Each skill directory must include a SKILL.md file
  • Expose a main(args: list[str]) function for CLI execution

Skill naming

Each skill directory inside skills/ has a base name. When goga connect installs the tool, the prefix goga-tool-<skill-name>- is automatically added to every skill.

In package (skills/) After goga connect
mkdocs/SKILL.md goga-tool-mkdocs
mkdocs-discovery/SKILL.md goga-tool-mkdocs-discovery
mkdocs-writer/SKILL.md goga-tool-mkdocs-writer

The skill whose directory name matches the tool name becomes the entry point — the dispatcher invoked by /goga:tool <name>.

Naming rules

  • Use lowercase with hyphens as separators
  • Name the main skill directory exactly <tool-name> to serve as the dispatcher entry point
  • Name sub-skills descriptively using the <tool-name>-<purpose> pattern (e.g., mkdocs-discovery, mkdocs-validator)
  • Keep names concise and indicative of the skill's responsibility