Writing skills readme first
Before creating any new skill, check the user's personal skills repo if they have one. Use the write-a-skill skill for the template. This is the mandatory starting point for all skill creation work.From its SKILL.md
npx -y skills add ceilidhboy/skills --skill writing-skills-readme-firstAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, 304 tokens by cl100k_base, as published. Nobody here has run it
Writing Skills — Read Me First
Activate this skill whenever skill creation, writing, or authoring is discussed.
Rule
Before creating or modifying any skill, check whether the user has a personal skills repo configured.
Process
-
Check for a local config — Look for
~/.config/skills/config.json. If it exists, read theskillsRepofield.- If found → you know where their skills repo is.
- If not found → ask the user: "Do you have a personal skills repo you'd like new skills created in?"
-
If the user provides a path — Save it for next time:
- Create
~/.config/skills/config.json(and theskillsdirectory if needed) with:{ "skillsRepo": "/path/to/repo" }
- Create
-
Read the repo's conventions — Navigate to the skills repo and read:
README.md— for the available skills and overviewCONTRIBUTING.md— for the exact process to add or update skills
-
Use
write-a-skill— Follow thewrite-a-skillskill for the SKILL.md template and structure. -
If no repo exists — Skip steps 1-3 and just use
write-a-skilldirectly. The skill will go wherever the project or user context suggests.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.