meta-lab-extention

Generates language-specific lab module specification skills for programming learning projects.

3|1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/ZHLX2005/sl --skill meta-lab-extention-zhlx2005
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meta-lab-extention
Source: https://github.com/ZHLX2005/sl/tree/main/skills/meta-lab-extention
Command: npx skills add https://github.com/ZHLX2005/sl --skill meta-lab-extention-zhlx2005

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When learning a new programming language, developers need consistent lab directory structures and module conventions, but manually writing a specification skill for each language is repetitive and error-prone. This Skill automates the creation of language-specific lab extension skills tailored to each language's toolchain and conventions. ## Core Features & Use Cases - Language and Toolchain Detection: Identifies the target language (Rust, Java, Go, Python, C++, TypeScript) and maps it to the correct build tool such as Cargo, Maven, Go Modules, uv, CMake, or npm. - Lab Layering Specification: Defines per-language lab directory structures, including module layout, test file conventions, and build tool registration rules like Cargo workspace members. - Skill Generation with Quality Gates: Produces a complete SKILL.md under .claude/skills/ with YAML frontmatter, trigger-based description, error case tables, and a success checklist. - Use Case: You tell the assistant "I'm learning Rust, create a lab spec skill for me" and it generates a rust-lab-extender skill defining workspace-based module structure, extension workflows, and common pitfalls. ## Quick Start Ask the assistant to create a lab module specification skill for the programming language you are learning, such as Rust or Go.

Frequently Asked Questions about meta-lab-extention

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

FAQPage Schema
How do I create a skill for managing lab code in a new programming language?

Ask the assistant to generate a lab specification skill for your target language. It detects the language and build tool, defines the lab directory layering rules, and writes a complete SKILL.md into .claude/skills/{language}-lab-extender/.

Which languages and build tools does the lab skill generator support?

It covers Rust with Cargo, Java with Maven or Gradle, Go with Go Modules, Python with uv, C++ with CMake or Meson, and TypeScript with npm or pnpm. Each language gets conventions matched to its toolchain.

Where should the generated skill file be placed?

The generated SKILL.md must be written to .claude/skills/{language}-lab-extender/SKILL.md. Placing it in the current directory instead means the system cannot recognize or trigger the skill.

Why is my generated skill not being triggered?

The most common cause is a description field written as a content summary instead of trigger conditions. The description must state when the skill activates, such as phrases the user would say, and the file must include valid YAML frontmatter with name and description.

Can the same lab structure be reused across different languages?

No, each language needs its own conventions. For example, Rust modules use Cargo workspace members while Python modules use __init__.py, so applying one language's rules to another produces broken specifications.