skill-granularity-convention

Define and enforce single-purpose skill granularity with splitting and merging criteria.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/RevTechStudio/rts-plugins --skill skill-granularity-convention
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-granularity-convention
Source: https://github.com/RevTechStudio/rts-plugins/tree/main/rts-plugin-generator/skills/skill-granularity-convention
Command: npx skills add https://github.com/RevTechStudio/rts-plugins --skill skill-granularity-convention

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides clear guidelines for defining the optimal granularity of AI skills, ensuring each skill has a single, well-defined purpose. It helps users decide when to split or combine skills, leading to more maintainable and reusable AI components.

Core Features & Use Cases

  • Single-Purpose Principle: Defines what constitutes a single purpose for a skill, ensuring clarity in its objective and scope.
  • Splitting Criteria: Provides clear indicators (e.g., multiple objectives, complex workflows, excessive categories) for when a skill should be broken down.
  • Merging Criteria: Offers guidelines (e.g., overly small skills, strong inter-dependencies, high duplication) for when multiple skills should be combined.
  • Use Case: A user has a system-designer skill that covers architecture, database, and API design. This skill would advise splitting it into architecture-designer, database-schema-designer, and api-designer to adhere to the single-purpose principle.

Quick Start

Evaluate the granularity of a skill named 'system-designer' that currently covers architecture, database, and API design.

Frequently Asked Questions about skill-granularity-convention

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

FAQPage Schema
How do I decide if a skill has the right granularity or should be split into smaller skills?

Skill granularity should follow the single-purpose principle: each skill covers one clear objective. Split a skill when it has multiple distinct objectives, complex workflows across unrelated domains, or excessive categories. For example, a skill covering architecture, database design, and API design should split into three focused skills, each with 3–5 responsibilities and 2–5 workflow steps.

What are the standards for defining a well-scoped AI skill?

A well-scoped skill has a single-line description (about 50 characters), 3–5 clear responsibilities, and 2–5 workflow steps or categories. This structure ensures maintainability and reusability. Skills with overly broad descriptions, more than 5 responsibilities, or unclear purpose violate granularity conventions and should be redesigned.

When should I merge multiple skills into one instead of keeping them separate?

Merge skills when they are overly small with minimal responsibility, share strong inter-dependencies requiring frequent coordination, or contain high duplication in logic and workflows. Merging reduces maintenance overhead and improves reusability, but only if the combined skill maintains a single, coherent purpose.

How do skill granularity principles apply to AI skill design and governance?

Granularity principles govern skill design decisions, evaluation criteria, and governance policies. They standardize how to assess skill responsibility scope, categorization, splitting and merging decisions, and reuse patterns. This ensures consistency across skill portfolios and enables maintainable, composable AI components.

What's the difference between splitting decisions based on workflow phases versus categorical complexity?

Splitting by workflow phases separates skills across different stages of execution (e.g., planning, implementation, validation). Splitting by categorical complexity breaks apart skills where each category represents a distinct domain (e.g., database design vs. API design). Both signal a violation of single-purpose principle and warrant separate skills.

Can I reuse a skill across multiple workflows if it maintains single-purpose design?

Yes. Single-purpose design maximizes reusability: a focused skill with clear responsibility and minimal scope is easier to integrate into different workflows. However, maintain modularity through proper granularity—avoid combining unrelated responsibilities that limit where the skill can be applied.