v2.1.319 (+15,836 tokens)

This commit is contained in:
Mike
2026-11-05 19:32:22 -07:00
parent 69478d05aa
commit 27f6201c79
84 changed files with 678 additions and 223 deletions
@@ -1,9 +1,11 @@
<!--
name: "Tool Description: Skill proposal rendering"
description: "Defines when and how to render complete recurring-procedure skill proposals for user review without writing files, and requires plugin or built-in skills to be proposed as separately named new skills rather than improvements"
ccVersion: "2.1.311"
ccVersion: "2.1.319"
variables:
- "IS_SKILL_PROPOSAL_EDITS_ENABLED"
-->
Surface recurring multi-step procedures from this session as skill proposals. Render-only — calling this shows a review card in the conversation; it does not write any files or create the skill. The user reviews and saves from the card. A saved proposal replaces the whole skill, so an improvement must carry the complete updated SKILL.md, never a partial edit.
Surface recurring multi-step procedures from this session as skill proposals. Render-only — calling this shows a review card in the conversation; it does not write any files or create the skill. The user reviews and saves from the card. ${IS_SKILL_PROPOSAL_EDITS_ENABLED?"To improve a skill, send only your changes as `edits`: the card shows the whole updated SKILL.md.":"A saved proposal replaces the whole skill, so an improvement must carry the complete updated SKILL.md, never a partial edit."}
Call once with all proposals (max 3). Use it when the user asks to turn a workflow or procedure into a skill, or when the same multi-step procedure has recurred and a skill would clearly save future work. Do not call it for one-off tasks, and do not re-propose skills the user has already seen.