skill-capture-proposal

You can automate recurring tasks by detecting repeated command sequences and stable question-answer exchanges, then drafting a formal skill proposal that awaits your explicit approval before activation.

Pattern recognition for capturing repetitive workflows works by detecting repeated command sequences and stable question-answer exchanges within your active sessions, then triggering a draft proposal for formalization.

Yes, you can prevent unauthorized automated skill creation because the system uses a ratification workflow that surfaces a confirmation prompt, ensuring skills are registered only upon your explicit approval.

Drafting and ratifying a formal skill proposal involves generating a SKILL.md file in a sandbox location, followed by a user confirmation step where explicit approval is required before structured skill registration occurs.

No, this workflow automation requires no external dependencies, operating solely based on workspace configuration and user intent to facilitate structured skill registration.

A limitation of automatic skill capture is that it relies entirely on explicit user ratification, meaning no skills are created silently, which requires manual confirmation for every detected pattern.