home / skills / bizshuk / llm_plugin / skill_generator

skill_generator skill

/skills/skill_generator

This skill helps generate a new LLM capability using a template and creates an organized folder structure for seamless agent enhancement.

npx playbooks add skill bizshuk/llm_plugin --skill skill_generator

Review the files below or copy the command above to add this skill to your agents.

Files (3)
SKILL.md
1.1 KB
---
name: Skill Generator
description: Use template with LLM to generate a new skill for LLM model
user-invocable: true
auto-invoke: true
version: "1.0.0"
capabilities: ["mcp", "terminal"]
---

# Skill Generator

Read @assets/skill.template.md and use it as template.  

Interactive mode to ask question below one by one.

1. Answer what the skill name is? <skill_name>.  
2. What role will use this skill? <role>.  
3. Descibe this skill. <skill_description>.  
4. Bsaed on given role and skill description, Generate skill details. <detail>.  
5. Based on the skill folder structure save it to ~/.agent/skill/<skill_name_without_space>/SKILL.md.  
If any other reference, it needs to be saved to sub folder accordingly.  
~/.agent/skill/<skill_name_without_space>.  
├─── SKILL.md       # Main.  
├─── scripts/       # Executable scripts (bash, python, node) the agent can run.  
├─── references/    # Static documentation, schemas, or example data for the agent to consult.  
└─── assets/        # Code templates, boilerplate, or binary resources.

Overview

This skill generates new skills for an LLM-based agent using a reusable template and an interactive prompt flow. It guides the user through concise questions to capture name, role, description, and implementation details, then scaffolds a standardized folder with scripts, references, and assets. The result is a ready-to-edit skill package following the agent's expected layout.

How this skill works

The generator asks the user a sequence of targeted questions to collect the skill name, intended role, descriptive summary, and technical details. It fills a template with those answers and writes a structured skill folder into the agent workspace under ~/.agent/skill/<skill_name_without_spaces> with a main skill file, executable scripts, supporting references, and assets. It validates folder placement and creates subfolders when external references are required.

When to use it

  • You need to bootstrap a new LLM skill quickly using a consistent template.
  • When multiple contributors must follow the same folder and file conventions.
  • To convert a concept or requirement into a ready-to-edit skill package.
  • When automating repetitive skill-scaffolding tasks for agents.
  • For onboarding new roles with standardized skill structure.

Best practices

  • Provide concise, accurate answers during the interactive prompts to ensure the generated content is focused.
  • Use short, descriptive skill names without spaces or special characters to avoid path issues.
  • Review and customize the generated main skill file and scripts before running the skill in production.
  • Add concrete example data to the references folder to improve agent reliability.
  • Version-control the generated folder and document any deviations from the template.

Example use cases

  • Create a data-extraction skill that a data analyst role will run to fetch and normalize CSVs.
  • Scaffold a customer-support responder skill for a support agent role, including example templates in references.
  • Generate a monitoring skill for an SRE role, with executable health-check scripts in scripts/.
  • Produce a content-generation skill for a marketing role, with prompt templates stored in assets/.

FAQ

Can I overwrite an existing skill folder?

Yes, but confirm backups first. The generator can replace files in the target folder; use version control to avoid data loss.

What naming rules should I follow for the skill folder?

Use lowercase letters, hyphens or underscores instead of spaces, and avoid special characters to ensure cross-platform compatibility.

Which files are populated automatically?

The main skill file, a basic scripts directory with example executables, an empty references directory, and an assets directory with template resources are created and populated based on your answers.