Help us improve
Share bugs, ideas, or general feedback.
From claude-scholar
Creates, repairs, and refactors Claude skills by inspecting the local environment, locking skill contracts, and keeping SKILL.md files lean with real bundled resources.
npx claudepluginhub galaxy-dawn/claude-scholar --plugin claude-scholarHow this skill is triggered — by the user, by Claude, or both
Slash command
/claude-scholar:skill-developmentThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill to create or repair Claude skills in the **current local environment**, not in an abstract plugin template.
Create, improve, and test SKILL.md files to extend Claude Code with project-specific knowledge and reusable workflows.
Guides creating and refining skills for Claude Code, covering intent capture, structure, writing patterns, and progressive-disclosure organization.
Guides development of Claude Code SKILL.md files with best practices, structure, YAML frontmatter rules, categories, patterns, references, and testing.
Share bugs, ideas, or general feedback.
Use this skill to create or repair Claude skills in the current local environment, not in an abstract plugin template.
Produce a skill that is:
SKILL.md layer,references/, examples/, and scripts/ files when they are mentioned,SKILL.md focused on workflow and boundaries.references/ or examples/.Before writing anything:
Use the local inventory as the authority. Do not write guidance against an imagined plugin layout.
Define four things before editing:
If the skill only needs a short workflow, keep it short. Do not create references/, examples/, or scripts/ just because the directories are conventional.
The frontmatter should:
name,Prefer descriptions of this form:
---
name: skill-name
description: This skill should be used when the user asks to "...", "...", or needs help with ....
---
A good SKILL.md should usually contain:
Move these out of the main file when they get long:
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.
At minimum, verify:
SKILL.md is not overloaded with material that belongs in references,SKILL.md,references/,When creating or repairing a skill, prefer ending with:
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