Skillscake
Claude and Codex plugins plus a public skill to use SkillsCake with your agents
npx -y skills add skillscake/use-skillscake --skill skillscakeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 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.
What its author says it does
Copied from the file, not written here
Create or upgrade an agent skill with SkillsCake. Use when the user wants to improve a skill using SkillsCake, create a skill based on a completed workflow, or says "use SkillsCake".
SKILL.md
2.7 KB, as published. Nobody here has run it
SkillsCake
A skill is a directory containing one SKILL.md and a number of supporting files.
Send a skill to SkillsCake; it bakes a perfect version. You are the thin client: package the input, call the API, write the result back. The hard work is server-side. You should only need to pause on error, tier choice, and apply gate.
Flow
Two scripts: scripts/check.sh and scripts/skillscake.sh. Both print key=value
lines; on error, follow reason and action.
-
Mode. Upgrade an existing skill folder, including useful sanitized conversation context, or create one from a workflow the user just completed and wants to reuse. For upgrade, you need to know the location of the skill now. Surface to the user if needed. Read all files in the skill quickly.
-
Check your connection and account.
bash scripts/check.sh. Ifstatus=error, followactionand stop. -
Tier.
basefor a small, single-purpose skill;profor a substantial one (long, scripted, or multi-file). Pause here to ask the user, giving your recommendation, if they did not specify a tier when calling for SkillsCake. If they don't have the run credit they need, suggest they visit https://skillscake.com/account/plan. -
Write
notes.txt, sanitized. Describe the workflow. If context exists, consider steps, real inputs/outputs, and where judgment matters. Consider specific quotes from your work. You are the sanitizer: strip secrets,credentials, and customer PII; keep only what the skill needs to work. Note: between the skill and notes.txt you cannot exceed 30,000 characters. -
Run (choose or make a tmp
OUTdir; the finished skill lands atOUT/<skill-name>/, and the script prints its exactskill_dir):- Upgrade:
bash scripts/skillscake.sh --tier T --out OUT --skill DIR --notes notes.txt --label "<name>" - Create:
bash scripts/skillscake.sh --tier T --out OUT --notes notes.txt --label "<name>"On failure, followreason/action. Note: the run takes ~10 minutes. Run the task in the background once submitted.
- Upgrade:
-
Review. Do a fast review of the new skill at
skill_dir. Surface the skill and benefits to the user before moving to apply. -
Apply the skill to the original live location, if approved by the user. For create, correctly add the skill to the user's skills depending on the harness.
Don't
- Don't write or edit the skill yourself.
- Don't handle signup, cards, or plans; route the user to the website.