# Plugin Skill Layout

> Plugin Skill Layout Review Pattern

- Skill: `kdcllc/plugin-skill-layout` (Agent Skill)
- Install (CLI): `npx skillmds@latest add kdcllc/plugin-skill-layout`
- Raw SKILL.md: https://api.skillmd.com/api/skills/kdcllc/plugin-skill-layout/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: kdcllc (https://skillmd.com/u/kdcllc)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/kdcllc/plugin-skill-layout

---

# Plugin Skill Layout Review Pattern

Use this pattern when a repo wants to follow another skill/plugin example repo without copying irrelevant internals.

## Rules

1. Copy the **outer packaging shell** first:
   - root `plugin.json`
   - `"skills": ["skills/"]`
   - one self-contained folder per skill under `skills/`
2. Keep each skill's **runtime assets, scripts, evals, and data** with that skill unless there is a functional reason to move them.
3. Do **not** copy example-specific folders (`template/`, `content-examples/`, UI assets) unless the target skill actually needs that capability.
4. Re-check docs so packaging changes do not imply broader product scope.
5. Re-run the skill-local validation and packaging commands after layout changes.

## Why

Example repos often mix reusable packaging patterns with product-specific implementation folders. This pattern separates the reusable shell from the example's business logic so a repo can align structurally without importing scope creep or path churn.

## Applied Here

- Example shell adopted: root `plugin.json` + `skills/`
- Internal RBAC shape preserved: `scripts/`, `references/data/`, `evals/`
- Guardrail: no broadening beyond offline built-in Azure RBAC role matching