save-skill

You can save conversation insights as reusable skills by extracting the latest assistant response or user content and writing it to a structured YAML-frontmatter Markdown file in a project-specific knowledge repository.

Saving a chat session procedure works by converting the discussed pattern into a focused skill file, creating the per-project skills directory if it is missing, and committing and pushing the Markdown file to the Git-backed knowledge repo.

Yes, you can capture debugging approaches and checklists from a chat by invoking the save command, which persists them as structured skill files that are automatically injected into future sessions for that project.

Yes, you need a Git-backed knowledge repository because the skill files are written to a per-project skills directory and the changes are committed and pushed to ensure they are versioned and shareable across collaborators.

The best way to persist actionable instructions is to save them as structured YAML-frontmatter Markdown files under a per-project knowledge repo, ensuring the knowledge is not lost between sessions and is available for reuse.

If a project skills directory is missing when saving a new skill, the tool automatically creates the required directories before writing the Markdown file and merging updates into existing skills.