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. If status=error, follow
action and stop.
Tier. base for a small, single-purpose skill; pro for 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 OUT dir; the finished skill lands at
OUT/<skill-name>/, and the script prints its exact skill_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, follow reason / action.
Note: the run takes ~10 minutes. Run the task in the background once submitted.
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.
1---2name: skillscake-23description: 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".4---56# SkillsCake78A skill is a directory containing one SKILL.md and a number of supporting files.910Send a skill to SkillsCake; it bakes a perfect version. You are the thin client:11package the input, call the API, write the result back. The hard work is server-side.12You should only need to pause on error, tier choice, and apply gate.1314## Flow1516Two scripts: `scripts/check.sh` and `scripts/skillscake.sh`. Both print `key=value`17lines; on error, follow `reason` and `action`.18191. **Mode.** *Upgrade* an existing skill folder, including useful sanitized conversation20 context, or *create* one from a workflow the user just completed and wants to reuse.21 For upgrade, you need to know the location of the skill now. Surface to the user if22 needed. Read all files in the skill quickly.23242. **Check** your connection and account. `bash scripts/check.sh`. If `status=error`, follow25 `action` and stop.26273. **Tier.** `base` for a small, single-purpose skill; `pro` for a28 substantial one (long, scripted, or multi-file). Pause here to ask the user, giving29 your recommendation, if they did not specify a tier when calling for SkillsCake. If30 they don't have the run credit they need, suggest they visit31 https://skillscake.com/account/plan.32334. **Write `notes.txt`, sanitized.** Describe the workflow. If context exists, consider34 steps, real inputs/outputs, and where judgment matters. Consider specific quotes from35 your work. You are the sanitizer: strip secrets,credentials, and customer PII; keep only36 what the skill needs to work.37 Note: between the skill and notes.txt you cannot exceed 30,000 characters.38395. **Run** (choose or make a tmp `OUT` dir; the finished skill lands at40 `OUT/<skill-name>/`, and the script prints its exact `skill_dir`):41 - Upgrade: `bash scripts/skillscake.sh --tier T --out OUT --skill DIR --notes notes.txt --label "<name>"`42 - Create: `bash scripts/skillscake.sh --tier T --out OUT --notes notes.txt --label "<name>"`43 On failure, follow `reason` / `action`.44 Note: the run takes ~10 minutes. Run the task in the background once submitted.45466. **Review.** Do a fast review of the new skill at `skill_dir`. Surface the47 skill and benefits to the user before moving to apply.48497. **Apply** the skill to the original live location, if approved by the user. For50 create, correctly add the skill to the user's skills depending on the harness.5152## Don't5354- Don't write or edit the skill yourself.55- Don't handle signup, cards, or plans; route the user to the website.
skillscake