[BUG] When creating a new skill from RooCode settings, it is possible to create broken one

[Olegas]

Problem (one or two sentences)

Try to create a skill, which is having a colon symbol (:) in it's description
Example:

---
name: test-skill
description: do something useful. Keywords: useful, skill, foo, bar
---

Such skill will not be displayed in UI

Context (who is affected and when)

Happens when user creates a skill with specially crafted description text

Reproduction steps

1. create a new skill with RooCode UI (scope does not matter)
2. in description field write something with a colon symbol (:)

Expected result

User can see a new skill in settings UI

Actual result

Skill is not visible (even after app restart)

Variations tried (optional)

No response

App Version

3.53.0 (44f6bba)

API Provider (optional)

None

Model Used (optional)

No response

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

[Olegas]

I think the root cause is here: https://github.com/RooCodeInc/Roo-Code/blob/main/src/services/skills/SkillsManager.ts#L398
Description string is not enclosed in quotes so, if it is having a : symbol, resulting YAML will be incorrect

[roomote-v0]

I've analyzed this issue and here's my proposed implementation plan:

Root Cause: In src/services/skills/SkillsManager.ts, the createSkill method builds YAML frontmatter via manual string concatenation (line 398):

const frontmatterLines = [`name: ${name}`, `description: ${trimmedDescription}`]

When the description contains a colon followed by a space (e.g., Keywords: useful), YAML interprets the colon as a key-value separator, producing invalid frontmatter. The gray-matter parser then fails to extract the description field correctly, causing the skill to be silently skipped during loading (lines 112-114).

Proposed Fix:

1. Quote the description value in YAML frontmatter in the createSkill method in src/services/skills/SkillsManager.ts. Change the frontmatter generation to wrap the description in double quotes and escape any internal double quotes/backslashes:

   const escapedDescription = trimmedDescription.replace(/\\/g, "\\\\").replace(/"/g, "\\\"")
   const frontmatterLines = [`name: ${name}`, `description: "${escapedDescription}"`]

   This ensures colons, hash symbols, and other YAML-special characters in descriptions are treated as literal text.

2. Add a test case in src/services/skills/__tests__/SkillsManager.spec.ts to verify that skills with colons in their description are created correctly and can be loaded back.

This is the minimal, targeted fix. The reading side already uses gray-matter which handles quoted YAML strings correctly, so no changes are needed there.

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.