_skills-evaluation-architecture

Evaluate skill definitions for structural soundness and clean composition.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture perspective for evaluating gobbi skill definitions to ensure sound structure and clean composition.

Core Features & Use Cases

  • Evaluate hierarchy, abstraction, and coupling across skills
  • Verify navigability and extension paths via SKILL.md
  • Identify potential decomposition or over-splitting issues in skills

Quick Start

Evaluate a candidate skill by loading its SKILL.md and reporting on structure and extensibility.

Frequently Asked Questions about _skills-evaluation-architecture

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

FAQPage Schema
How do I evaluate skill architecture for clean decomposition and modularity?

Evaluating skill architecture involves assessing hierarchy, abstraction, coupling, and extension paths to verify structural soundness. You load a candidate SKILL.md and report on its structure and extensibility to identify potential decomposition or over-splitting issues.

What is structural soundness in skill definitions and how is it verified?

Structural soundness in skill definitions means clean composition where a skill can be loaded selectively and extended. It is verified by checking clear frontmatter with name, description, and allowed-tools, and ensuring SKILL.md documents navigation and provides a navigate table.

How to check if a SKILL.md supports navigability and extensibility?

To check SKILL.md navigability and extensibility, verify it documents navigation, provides a navigate table, and defines an extensible structure. This confirms the skill can be properly loaded selectively and extended across the repository.

When do I need to assess hierarchy and coupling across skills in a repository?

Assess hierarchy and coupling across skills when you need to identify potential decomposition or over-splitting issues. This architecture evaluation ensures clean composition and verifies how well each skill can be loaded selectively and extended.

Does evaluating skill definitions require specific frontmatter fields?

Evaluating skill definitions requires clear frontmatter with name, description, and allowed-tools. This prerequisite metadata allows the architecture evaluation to properly assess structural soundness, hierarchy, abstraction, and coupling across the skills.

Can this architecture evaluation identify over-splitting issues in skills?

Architecture evaluation can identify potential decomposition or over-splitting issues in skills. By assessing hierarchy, abstraction, and coupling, it verifies structural soundness and determines how well a skill can be loaded selectively and extended.