_agents

Define and validate gobbi agent definitions with frontmatter structure.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/HahyeonJeon/gobbi --skill agents-hahyeonjeon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: _agents
Source: https://github.com/HahyeonJeon/gobbi/tree/main/plugins/gobbi/skills/_agents
Command: npx skills add https://github.com/HahyeonJeon/gobbi --skill agents-hahyeonjeon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured reference and interactive guide for defining, reviewing, and modifying .claude/agents/ files within gobbi. It ensures agent definitions follow a consistent frontmatter structure, establish clear identity and boundaries, and align with the universal lifecycle.

Core Features & Use Cases

  • Reference and guide for agent definitions, including required frontmatter fields (name, description, tools, model) and the recommended lifecycle (Study, Plan, Execute, Verify, Memorize).
  • Guided navigation to related documentation (pi.md, executor.md, researcher.md, evaluator.md, evaluation.md) to help auditors and creators find the correct patterns and examples.
  • Enforces project-specific domain knowledge by distinguishing project agents from gobbi's built-in agents and promoting explicit boundary definitions.
  • Supports onboarding and auditing workflows by outlining delegation patterns, suggested outputs, and quality expectations for agent definitions.

Quick Start

Review the agent-definitions structure and begin drafting a new agent using the frontmatter, identity, and lifecycle guidance.

Frequently Asked Questions about _agents

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define agent definitions for the gobbi framework using frontmatter?

To define agent definitions for the gobbi framework, create a file in `.claude/agents/` with valid SKILL.md frontmatter specifying name, description, tools, and model to ensure proper identity and tool scoping.

What frontmatter fields are required for a valid gobbi agent file?

A valid gobbi agent file requires frontmatter fields for name, description, tools, and model to establish clear identity, define tool scoping, and align with the universal agent lifecycle.

When do I need to use the Study Plan Execute Verify Memorize lifecycle for agents?

Use the Study Plan Execute Verify Memorize lifecycle when establishing agent definitions to guide delegation patterns, structure suggested outputs, and maintain quality expectations during onboarding and auditing workflows.

How do I distinguish project-specific agents from built-in gobbi agents?

To distinguish project-specific agents from built-in gobbi agents, establish explicit boundary definitions within the agent frontmatter to enforce domain expertise and prevent overlap with the framework's native tools.

Can I use this agent reference guide to audit existing delegation patterns?

Yes, you can use this agent reference guide to audit delegation patterns by navigating the provided documentation links to verify frontmatter structure, tool scoping, and lifecycle alignment.

What are the limitations of defining project agents without explicit boundaries in gobbi?

Defining project agents without explicit boundaries in gobbi causes tool scoping conflicts and identity overlap with built-in agents, degrading the framework's delegation patterns and lifecycle execution.