ftm-capture

Extracts repeatable workflow patterns into routine, playbook, and reference documents.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/kkudumu/feed-the-machine --skill ftm-capture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ftm-capture
Source: https://github.com/kkudumu/feed-the-machine/tree/main/ftm-capture
Command: npx skills add https://github.com/kkudumu/feed-the-machine --skill ftm-capture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extracts patterns, routines, and reference docs from the current session so repeated work is captured and reused across future tasks.

Core Features & Use Cases

  • Capture workflows as Routine, Playbook, and Reference Doc.
  • Read session context (blackboard, daily log, tool history) and generate durable artifacts accessible to ftm-mind, ftm-routine, and ftm-ops.
  • Auto-suggest captures for recurring patterns and guide clarifications to ensure generalizability.
  • Update existing artifacts when the workflow already exists to keep knowledge fresh.

Quick Start

Initiate a capture after completing a repeatable workflow to save it as a routine, playbook, and reference document.

Frequently Asked Questions about ftm-capture

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

FAQPage Schema
How do I capture repeatable workflow steps into a reusable playbook?

Capture repeatable workflow steps by initiating a capture after completing a task. The tool reads session context and extracts patterns into a structured JSON playbook, YAML routine, and Markdown reference document for future reuse.

What is the best way to automate knowledge capture from routine tasks?

Automating knowledge capture from routine tasks involves extracting repeatable patterns from your session context and writing them into durable artifacts. This generates a YAML routine and Markdown reference complete with gotchas and decisions for future use.

Can I update existing routines and reference docs when a workflow changes?

Yes, you can update existing routines and reference docs. When a workflow already exists, the capture process updates the current artifacts to keep your knowledge layers fresh and ensure ongoing accuracy for future tasks.

Do I need session context like daily logs to generate automation routines?

Yes, generating automation routines requires access to session context such as the blackboard, daily log, and tool history. This context is necessary to accurately extract repeatable steps and write durable automation artifacts.

How does auto-suggest work for capturing recurring workflow patterns?

Auto-suggest for capturing recurring workflow patterns works by monitoring your session for repeatable steps and prompting a capture. It guides clarifications to ensure the extracted routine and playbook remain generalizable across future tasks.

What formats are produced when extracting workflow patterns into knowledge layers?

Extracting workflow patterns into knowledge layers produces a YAML routine, a JSON playbook, and a Markdown reference document. These durable artifacts capture repeatable steps, gotchas, and decisions for future automation tasks.