# Skill Development

Should be used when the user asks to create a new skill, repair an existing skill...

- Repository: https://github.com/Galaxy-Dawn/claude-scholar (5959 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-10-19
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Galaxy-Dawn/claude-scholar --skill skill-development -g -a claude-code -y`
Codex: `npx skills add Galaxy-Dawn/claude-scholar --skill skill-development -g -a codex -y`
Cursor: `npx skills add Galaxy-Dawn/claude-scholar --skill skill-development -g -a cursor -y`
Gemini CLI: `npx skills add Galaxy-Dawn/claude-scholar --skill skill-development -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add Galaxy-Dawn/claude-scholar`

## Description

This skill should be used when the user asks to create a new skill, repair an existing skill, improve trigger descriptions, reorganize skill structure, or make a Claude skill more reusable and internally consistent.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Skill Development

Use this skill to create or repair Claude skills in the **current local environment**, not in an abstract plugin template.

## Goal

Produce a skill that is:
- easy to trigger,
- lean at the `SKILL.md` layer,
- backed by real `references/`, `examples/`, and `scripts/` files when they are mentioned,
- free of dead local references.

## Core rules

- Keep **one skill = one durable job**.
- Treat the frontmatter description as the main trigger surface.
- Keep `SKILL.md` focused on workflow and boundaries.
- Move detailed catalogs, templates, and long explanations into `references/` or `examples/`.
- Do not mention files that do not exist.
- Do not inherit stale names, agents, or sibling skill references without verifying they exist locally.

## Default workflow

### 1. Inspect the current environment first

Before writing anything:
- inspect the target skill directory,
- inspect neighboring skills that already solve a similar problem,
- verify which agents, commands, and sibling skills actually exist,
- identify stale references before adding new ones.

Use the local inventory as the authority. Do not write guidance against an imagined plugin layout.

### 2. Lock the skill contract

Define four things before editing:
1. what the skill does,
2. what triggers it,
3. what it explicitly does **not** do,
4. which bundled resources are actually needed.

If the skill only needs a short workflow, keep it short. Do not create `references/`, `examples/`, or `scripts/` just because the directories are conventional.

### 3. Write or repair the frontmatter

The frontmatter should:
- use the real skill identifier in `name`,
- use a third-person trigger description,
- include concrete phrases a user would naturally say,
- stay short enough to scan quickly.

Prefer descriptions of this form:

```yaml
---
name: skill-name
description: This skill should be used when the user asks to "...", "...", or needs help with ....
---
```

### 4. Keep the main file lean

The rest: https://github.com/Galaxy-Dawn/claude-scholar/blob/HEAD/skills/skill-development/SKILL.md