Skip to content
TakoAPI
Back to skills

subskill-generation-rule

by kenera

Coding Agents & IDEs
432Downloads reported by clawskills.sh
2Stars
0Views
0 likesSign in to like this skill
—Not yet rated
Your rating

Brief

Define and enforce project orgnization rules for generating subskills. put generated recommendation outputs.

Description

What This Skill Does

Defines file placement conventions for skills that contain multiple features or generate output artifacts. Artifacts go in `data/`, feature scripts in `subskills/<feature>/`, and each feature folder can optionally include its own `SKILL.md`. Keeps the main skill root free of one-off scripts and generated files.

A shared layout convention means contributors always know where generated outputs and feature scripts live without reading each skill individually.

When to Use It

  • Deciding where to place a newly generated recommendation file
  • Structuring a skill that has grown into multiple distinct features
  • Adding a SKILL.md to document a specific subskill's behavior
  • Auditing an existing skill folder for layout compliance
  • Onboarding contributors to a skill's file organization conventions

Example Workflow

INPUT

User asks: 'I'm adding a new recommendation feature to my skill — where should the script and its output go?'

AGENT
  1. 1

    Check if a subskills/ directory exists in the skill root

  2. 2

    Create subskills/<feature-name>/ for the new feature script

  3. 3

    Place the feature script inside that folder

  4. 4

    Create data/ at the skill root for generated output artifacts

  5. 5

    Optionally add SKILL.md inside the feature folder to document its behavior

OUTPUT

A clean skill layout with the feature script under `subskills/<feature-name>/` and generated outputs under `data/`, with no clutter in the skill root.

Installation

clawhub install kenera/subskill-generation-rule

Run the CLI command, or paste the prompt into Claude Code, Cursor, Codex or whichever coding agent you use.

Links