skill-development

Create or repair Claude skills with structured SKILL.md validation.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/EmaRimoldi/Claude-scholar-extended --skill skill-development-emarimoldi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-development
Source: https://github.com/EmaRimoldi/Claude-scholar-extended/tree/main/skills/skill-development
Command: npx skills add https://github.com/EmaRimoldi/Claude-scholar-extended --skill skill-development-emarimoldi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides structured guidance to create or repair Claude skills inside the current local environment, ensuring consistent frontmatter, clear boundaries, and lean core instructions.

Core Features & Use Cases

  • Define a clear skill contract: purpose, triggers, and boundaries, with lean SKILL.md and detailed guidance moved to references when needed.
  • Enforce resource discipline: promote appropriate use of references/, scripts/, and assets/ to support reusable workflows.
  • Support iterative repair and improvement: guide updates to SKILL.md and bundled resources based on real tasks and feedback.

Quick Start

Inspect the current skill directory, lock the skill contract, and implement reusable resources to finalize the skill.

Frequently Asked Questions about skill-development

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

FAQPage Schema
How do I create a Claude skill with proper frontmatter and directory structure?

To create a Claude skill, define its purpose, triggers, and boundaries, then validate frontmatter integrity and ensure SKILL.md exists alongside optional directories like references, scripts, and assets for lean organization.

What is the best way to repair a broken skill layout in my local environment?

Repairing a skill layout involves inspecting the current directory, validating frontmatter integrity, enforcing skill boundaries, and reorganizing resources into references, scripts, and assets to restore consistent structure.

How do I organize references and scripts when updating skill triggers?

Organize references and scripts by moving detailed guidance into the references directory, placing executable tools in scripts, and maintaining a lean SKILL.md to support reusable workflows during trigger updates.

Can I refactor a skill contract to improve modularity without breaking existing workflows?

Refactoring a skill contract requires locking the purpose, triggers, and boundaries, then migrating detailed instructions to bundled resources to maintain modularity without disrupting existing local workflows.

Why does my skill validation fail when the frontmatter is misconfigured?

Skill validation fails when frontmatter is misconfigured because the structure enforces strict integrity checks on metadata fields to ensure clear boundaries and proper resource organization within the local environment.

When do I need to move detailed instructions to the references directory during skill development?

Move detailed instructions to the references directory during skill development when the core SKILL.md becomes overly complex, ensuring the main file remains lean while preserving comprehensive guidance for iterative repair.