skill-capture

# skill-capture - recurring workflow becomes a reusable skill When the same ordered, multi-step workflow keeps recurring in a session, that repetition is a signal: the workflow is worth capturing once as a Claude Code skill so it need not be re-derived every time. This skill governs how credo notices that repetition and, only with the right permission, turns it into a discoverable skill - without inventing any new infrastructure. ## Detection heuristic (in-session, no backend) Detection is purely heuristic and lives entirely in the current session's context. There is NO persistent counter, NO tracking file that increments, NO new infrastructure. You notice the pattern the same way a person would: - A candidate is the SAME multi-step sequence - the same ordered steps or commands, small variation allowed (different arguments, paths, or names) - that you have carried out about three times in the running session. - One-off actions and trivial single commands are not candidates. The value is in a multi-step ordered sequence that you would otherwise reconstruct from scratch each time. - Detection resets with the session. This skill does not try to remember across sessions via a counter; cross-session memory lives only in the two `.credo/` files below, which are written when a pattern is actually noted or built, never as a running tally. ## Mode gating (hard guarantee) How you act on a detected candidate depends strictly on the session mode, mirroring the audit skill...