Skill Creator
Azure/azqr
Create new skills, modify and improve existing skills, and measure skill performance.
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…
Install Skill Development
$ npx skills add Galaxy-Dawn/claude-scholar --skill skill-development -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Galaxy-Dawn/claude-scholar skill-development --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Galaxy-Dawn/claude-scholar.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/skill-development .claude/skills/skill-development && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "skill-development" agent skill from https://github.com/Galaxy-Dawn/claude-scholar/tree/main/skills/skill-development into .claude/skills/skill-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-development", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Galaxy-Dawn/claude-scholar/tree/main/skills/skill-developmentType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Galaxy-Dawn/claude-scholar --skill skill-development -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Galaxy-Dawn/claude-scholar skill-development --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Galaxy-Dawn/claude-scholar.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/skill-development .agents/skills/skill-development && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "skill-development" agent skill from https://github.com/Galaxy-Dawn/claude-scholar/tree/main/skills/skill-development into .agents/skills/skill-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-development", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Galaxy-Dawn/claude-scholar --skill skill-development -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Galaxy-Dawn/claude-scholar skill-development --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Galaxy-Dawn/claude-scholar.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/skill-development .cursor/skills/skill-development && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "skill-development" agent skill from https://github.com/Galaxy-Dawn/claude-scholar/tree/main/skills/skill-development into .cursor/skills/skill-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-development", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Galaxy-Dawn/claude-scholar.git --path skills/skill-development--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Galaxy-Dawn/claude-scholar --skill skill-development -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Galaxy-Dawn/claude-scholar skill-development --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Galaxy-Dawn/claude-scholar.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/skill-development .gemini/skills/skill-development && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "skill-development" agent skill from https://github.com/Galaxy-Dawn/claude-scholar/tree/main/skills/skill-development into .gemini/skills/skill-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-development", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Galaxy-Dawn/claude-scholar skill-developmentInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Galaxy-Dawn/claude-scholar --skill skill-development -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Galaxy-Dawn/claude-scholar.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/skill-development .github/skills/skill-development && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "skill-development" agent skill from https://github.com/Galaxy-Dawn/claude-scholar/tree/main/skills/skill-development into .github/skills/skill-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-development", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Galaxy-Dawn/claude-scholar --skill skill-development -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Galaxy-Dawn/claude-scholar skill-development --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Galaxy-Dawn/claude-scholar.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/skill-development .opencode/skills/skill-development && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "skill-development" agent skill from https://github.com/Galaxy-Dawn/claude-scholar/tree/main/skills/skill-development into .opencode/skills/skill-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-development", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
skill-development- GitHub stars
- 5.7k
- Used in
- 1 other repo
- Token cost
- ~1.1k tokens
- SKILL.md length
- 576 words
- Files
- 4 (incl. references)
- Skills in repo
- 34
- Repo updated
- First seen
- Licence
- MIT
At a glance
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…
- Works in 6 steps: Inspect the current environment first → Lock the skill contract → Write or repair the frontmatter → …
- Asks to create a new skill
- SKILL.md covers Goal, Core rules, Default workflow and Typical repair patterns, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Skill Development is an agent skill from Galaxy-Dawn/claude-scholar. 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.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/checklist.md`, `references/integrity-checks.md` and `references/skill-creator-original.md`).
It sits in Agent Workflows, covering Skill authoring. The repository describes itself as: Semi-automated research assistant for academic research and software development. Supports Claude Code, Codex CLI, Kimi Code CLI, and OpenCode across ideation, coding… The licence is MIT.
When your agent uses it
- Asks to create a new skill
- Repair an existing skill
- Improve trigger descriptions
- Reorganize skill structure
Example prompts
- “/skill-development”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 9037873. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Skill Development loads about 1.1k tokens when it runs, and up to ~4.3k if it reads all its reference files. Until then it costs about 58 tokens; SKILL.md has 576 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Galaxy-Dawn/claude-scholar at commit 9037873, republished under its MIT licence (© Galaxy-Dawn). 576 words, ~1,117 tokens.
Download SKILL.mdSave it as
.claude/skills/skill-development/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- skill-development
- 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.
- version
- 0.2.0
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.mdlayer, - backed by real
references/,examples/, andscripts/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.mdfocused on workflow and boundaries. - Move detailed catalogs, templates, and long explanations into
references/orexamples/. - 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:
- what the skill does,
- what triggers it,
- what it explicitly does not do,
- 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:
---
name: skill-name
description: This skill should be used when the user asks to "...", "...", or needs help with ....
---4. Keep the main file lean
A good SKILL.md should usually contain:
- a short goal section,
- role boundaries,
- a default workflow,
- safety or quality rules,
- a short list of additional resources.
Move these out of the main file when they get long:
- templates,
- exhaustive checklists,
- edge-case catalogs,
- sample outputs,
- long examples.
5. Add only real bundled resources
Use bundled resources deliberately:
references/for detailed guidance that may be loaded selectively,examples/for real example outputs or scaffolds,scripts/for deterministic helper logic.
If a resource is mentioned in SKILL.md, it must exist.
If a resource exists but is never referenced or used, delete it.
Show full SKILL.md (207 more words)Show less
6. Run integrity checks before closing
At minimum, verify:
- frontmatter parses,
- referenced local files exist,
- sibling skill or agent references are real,
SKILL.mdis not overloaded with material that belongs in references,- temporary logs, caches, and editor artifacts are not left inside the skill directory.
Typical repair patterns
When the skill is too long
- keep the trigger and workflow in
SKILL.md, - move catalogs and deep detail into
references/, - keep a short read order so another model knows what to load first.
When the skill is too thin
- add a default workflow,
- add at least one concrete example or checklist,
- make the boundaries explicit so the skill is not just a slogan.
When the skill has stale references
- remove dead paths immediately,
- replace historical names with current local names,
- re-check neighboring agents/commands/skills against the live directory.
Recommended output shape
When creating or repairing a skill, prefer ending with:
- what changed,
- which files were created or updated,
- what integrity checks were run,
- what still needs manual follow-up, if anything.
References
Load only what is needed:
references/checklist.md- compact quality checklist before closing a skill editreferences/integrity-checks.md- concrete local checks for missing files, dead references, and driftreferences/skill-creator-original.md- legacy background reference; use for context, not as the live source of truth
© Galaxy-Dawn, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (references) in skills/skill-development of Galaxy-Dawn/claude-scholar.
- SKILL.md
- references/checklist.md
- references/integrity-checks.md
- references/skill-creator-original.md
Open the folder on GitHubat commit 9037873
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in Galaxy-Dawn/claude-scholar, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Skill Development next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Skill Development this skillGalaxy-Dawn/claude-scholar | 5.7k | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Skill CreatorAzure/azqr | 795 | 89 repos | ~8.2k | Automated safety check: Pass | Apache-2.0 | |
| Claude Code Skill Developer Guidediet103/claude-code-infrastructure-showcase | 10k | 11 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Darwin Skill Optimizeralchaincyf/darwin-skill | 6.2k | 1 repos | ~4.7k | Automated safety check: Pass | MIT | |
| Claude Code Command Developmentanthropics/claude-plugins-official | 38k | 10 repos | ~4.8k | Automated safety check: Pass | Apache-2.0 | |
| Claude Code Plugin Structureanthropics/claude-plugins-official | 38k | 10 repos | ~3.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Claude Code Skill Developer Guide
diet103/claude-code-infrastructure-showcase
A guide to creating and managing Claude Code skills with auto-activation: skill-rules.json triggers, hooks, enforcement levels, YAML frontmatter and progressive disclosure.
Darwin Skill Optimizer
alchaincyf/darwin-skill
Scores SKILL.md files on a nine-dimension rubric, then improves them in a keep-or-revert loop with independent judge agents, test prompts, git history and human checkpoints.
- Official
Claude Code Command Development
anthropics/claude-plugins-official
Explains how to write Claude Code slash commands: Markdown files with YAML frontmatter, arguments, file references, bash context and interactive prompts.
- Official
Claude Code Plugin Structure
anthropics/claude-plugins-official
Explains the directory layout, plugin.json manifest and component organization of a Claude Code plugin, including auto-discovery and portable paths.
Skill Release Gate
rohitg00/ai-engineering-from-scratch
Evaluates an Agent Skill bundle before release for structure, trigger quality, artifact improvement, script correctness, safety, installed-tree integrity and host portability.
More from Galaxy-Dawn/claude-scholar
All 34 skills in this repoCitation Verification Guide
Galaxy-Dawn/claude-scholar
Reference guidance for checking every citation in academic writing against canonical sources such as DOI, arXiv, CrossRef and Semantic Scholar, to catch fake or wrong references.
Skill Improvement Plan Executor
Galaxy-Dawn/claude-scholar
Reads an improvement-plan file from a companion quality-review skill and applies its suggested fixes to a Claude Skill, backing up first.
Skill Quality Reviewer
Galaxy-Dawn/claude-scholar
Scores a skill across description, content organization, writing style and structure, then produces letter grades and a prioritized improvement plan.
UI/UX Design System Advisor
Galaxy-Dawn/claude-scholar
Turns a vague UI request into a concrete design system with style, palette, typography and layout guidance from a search script, plus stack-specific implementation advice.
Daily Paper Digest
Galaxy-Dawn/claude-scholar
Finds recent arXiv and bioRxiv papers on a topic, narrows them in stages to one pick per field, and writes bilingual Chinese and English summaries.
Nature Data
Galaxy-Dawn/claude-scholar
Prepare, audit, or revise Nature-ready Data Availability statements, data repository plans, dataset citations, and FAIR metadata checklists for manuscripts.
Related
Categories
Questions about Skill Development
What does Skill Development do?
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…. Skill Development is an agent skill from Galaxy-Dawn/claude-scholar. 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.
When should I use Skill Development?
Skill Development fits situations like: asks to create a new skill; repair an existing skill; improve trigger descriptions; reorganize skill structure.
How do I install Skill Development in Claude Code?
Run `npx skills add Galaxy-Dawn/claude-scholar --skill skill-development -a claude-code`. Or copy the skill folder (skills/skill-development in Galaxy-Dawn/claude-scholar) into .claude/skills/skill-development in your project. Claude Code loads it when a task matches its description.
How do I install Skill Development in Codex?
Run `npx skills add Galaxy-Dawn/claude-scholar --skill skill-development -a codex`. Or copy the skill folder (skills/skill-development in Galaxy-Dawn/claude-scholar) into .agents/skills/skill-development in your project. Codex loads it when a task matches its description.
Can I use Skill Development in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Galaxy-Dawn/claude-scholar --skill skill-development -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/skill-development, .gemini/skills/skill-development, .github/skills/skill-development and .opencode/skills/skill-development in your project.
What does Skill Development need to run?
SKILL.md names no scripts, command-line tools or credentials: Skill Development is instructions for the agent only.
Does Skill Development access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Skill Development safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Skill Development use?
Skill Development is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Skill Development use?
About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.2k tokens, read only when the agent opens those files.
What are the alternatives to Skill Development?
Skills that share tags, products or a category with Skill Development: Skill Creator (Azure/azqr, 795 stars), Claude Code Skill Developer Guide (diet103/claude-code-infrastructure-showcase, 10k stars), Darwin Skill Optimizer (alchaincyf/darwin-skill, 6.2k stars) and Claude Code Command Development (anthropics/claude-plugins-official, 38k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Skill Development?
Galaxy-Dawn (a GitHub user) maintains it in Galaxy-Dawn/claude-scholar, which has 5,703 GitHub stars. The repository holds 34 skills in this directory. The repository was last updated on September 23, 2026.
Source: Galaxy-Dawn/claude-scholar on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.