capture-skill

Capture conversation knowledge, patterns, and workflows into reusable skills.

Updated Nov 10, 2018
One-click install
npx skills add https://github.com/GLaDO8/dotfiles --skill capture-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: capture-skill
Source: https://github.com/GLaDO8/dotfiles/tree/main/claude/backup/skills/capture-skill
Command: npx skills add https://github.com/GLaDO8/dotfiles --skill capture-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture knowledge, patterns, and workflows from the current conversation into a new or existing skill.

Core Features & Use Cases

  • Capture ongoing learnings: Persist insights, decisions, and best practices from chats as reusable skills.
  • Update or create skills: Extend or compose skills by adding new learnings with minimal friction.
  • Guided workflow: Follow a structured process to identify, validate, and distill content before saving.

Quick Start

Use the capture-skill to save the current conversation learnings into a new skill named 'my-skill' or update an existing one.

Frequently Asked Questions about capture-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save conversation learnings into a reusable skill?

You can capture conversation learnings into a reusable skill by following a structured workflow that validates and distills content before saving it with frontmatter-driven metadata and optional assets.

How can I update an existing skill with new knowledge from a chat?

You update an existing skill by extending or composing it with new learnings from the current conversation, adding fresh patterns and workflows with minimal friction.

What is the best way to automate capturing workflows from conversations?

The best way to automate workflow capture from conversations is using a structured capture workflow that distills knowledge and patterns, persisting them as reusable skills with frontmatter-driven metadata.

Does creating skills from conversations require YAML frontmatter?

Creating skills from conversations relies on frontmatter-driven metadata to structure and persist the captured knowledge, ensuring workflows and patterns are properly stored for future sessions.

Can I store optional assets under a skill directory when capturing knowledge?

Yes, you can store optional assets under a skill directory when you capture knowledge and patterns from conversations, supporting the frontmatter-driven metadata for the reusable skill.