Learn a Skill

Author a new SKILL.md from whatever the user points you at: a local directory or file, an online documentation page, a workflow you just walked through together in this conversation, or notes/a procedure the user describes or pastes in. You do the sourcing yourself, with whatever tools you already have — there is no separate ingestion engine.

This skill does not itself perform the task described by the source. It produces a new, separate skill file that captures how to do the task, for reuse in future sessions.

When to Use

• The user runs /learn <description> or says "turn this into a skill", "learn how to do X", "remember this workflow", "make this repeatable"
• The user points you at a directory, SDK, or API and asks you to learn it
• The user asks you to capture something you (the agent) just did successfully, so it can be repeated later
• The user pastes a described procedure and asks for it to become a skill

Procedure

1. Parse the request. It may mix two things, in any order: SOURCES to read (paths, URLs, "what we just did", pasted notes) and REQUIREMENTS that shape the skill (focus, scope, what to leave out, naming). Treat every part as load-bearing — text after a path or link is usually a requirement, not incidental. Never read only the first source and ignore the rest.