_agent-evaluation-aesthetics

Identify readability and style issues in gobbi agent definitions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aesthetics evaluation of gobbi agent definitions to identify readability, naming, style, and clarity issues that hinder contributor understanding and reliable behavior.

Core Features & Use Cases

  • Naming Convention Compliance: checks that the agent name matches the filename and follows gobbi's naming conventions.
  • Opening Clarity and Role Embodiment: assesses the first paragraph for immediate role clarity and intended thinking.
  • Writing Precision and Avoidance of Filler: looks for vague qualifiers, abstract nouns, passive voice, and unnecessary padding.
  • Style Consistency with Gobbi Patterns: ensures adherence to blockquotes, headings, and lists patterns for coherence.
  • Contributor Comprehensibility: evaluates whether a new contributor can summarize purpose, identify critical prohibitions, and foresee extension points.

Quick Start

Review a gobbi agent definition to surface readability and style problems, then report actionable improvements.

Frequently Asked Questions about _agent-evaluation-aesthetics

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

FAQPage Schema
How do I check agent definitions for readability and style guide compliance?

Agent definition aesthetics checks identify readability and style issues by evaluating naming compliance, opening clarity, writing precision, filler content, and consistency with Gobbi style patterns. They report actionable findings in a structured format.

What writing precision issues should I look for in agent definitions?

Writing precision checks in agent definitions look for vague qualifiers, abstract nouns, passive voice, and unnecessary padding. Removing these filler elements improves contributor comprehension and ensures reliable agent behavior.

How do I enforce naming conventions in agent definition files?

Naming convention compliance checks verify that the agent name matches the filename and follows Gobbi's established naming conventions. This enforces frontmatter requirements and reports discrepancies in a structured findings format.

Can I evaluate if a new contributor can understand my agent definitions?

Contributor comprehensibility evaluation assesses whether a new contributor can summarize the agent's purpose, identify critical prohibitions, and foresee extension points. It reviews opening clarity and role embodiment from the first paragraph.

How do I ensure style consistency with Gobbi patterns in documentation?

Style consistency checks ensure adherence to Gobbi patterns for blockquotes, headings, and lists. This coherence evaluation enforces the frontmatter requirements and findings structure described in the style guide.

What are the limitations of aesthetics checks for agent definitions?

Aesthetics checks are limited to readability, naming, style, and clarity issues within agent definitions. They do not evaluate functional agent behavior or runtime performance, focusing solely on documentation and contributor comprehensibility.