skill-development
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.
Profile →npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill skill-development --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 jo
What does the skill-development skill 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 internally consistent.
How do I install it?
Run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill skill-development --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Auto-Empirical-Research-Skills, a repository with 3,244 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.