takt-optimize

Analyze TAKT piece YAML and facet maps to generate optimized file sets.

1|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/j5ik2o/dotfiles --skill takt-optimize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: takt-optimize
Source: https://github.com/j5ik2o/dotfiles/tree/main/.agent/skills/takt-optimize
Command: npx skills add https://github.com/j5ik2o/dotfiles --skill takt-optimize

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

TAKT workflows often become bloated with fragmented pieces, duplicated facets, and manual optimization effort. takt-optimize automates the identification and consolidation of patterns, reducing token usage, unifying movements, simplifying rules, reusing facets, improving loop control, and proposing parallelization. When execution logs are available (e.g., .takt/logs/*.jsonl), it can base optimization on real runtime data.

Core Features & Use Cases

  • Analyze existing TAKT piece YAML and facet maps.
  • Generate an optimized file set with minimal token cost and streamlined structure.
  • Create an actionable optimization plan and, if logs are provided, justify changes with data-driven metrics.
  • Replace custom facets with built-in references when possible to reduce complexity and maintenance.

Quick Start

Provide your TAKT piece and optional logs, and the optimizer will output an optimized file set ready for deployment.

Frequently Asked Questions about takt-optimize

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

FAQPage Schema
How do I optimize TAKT workflow YAML to reduce token usage?

TAKT workflow optimization analyzes existing piece YAML and facet maps to consolidate patterns, unify movements, and reduce token usage. It generates an optimized file set with streamlined structure and minimal token cost ready for deployment.

Can I use execution logs to justify TAKT workflow optimizations?

Execution logs from .takt/logs/*.jsonl can be used to justify TAKT workflow optimizations with data-driven metrics. When logs are provided, the optimizer bases its actionable optimization plan on real runtime data rather than static analysis.

What is the best way to consolidate duplicated facets in a TAKT workflow?

Consolidating duplicated facets in a TAKT workflow is best handled by replacing custom facets with built-in references to reduce complexity and maintenance. This automated approach simplifies rules and reuses existing facet structures effectively.

How do I streamline TAKT piece structures and improve loop control?

Streamlining TAKT piece structures involves analyzing facet maps to unify movements, simplify rules, and improve loop control. The optimizer proposes concrete optimizations across patterns, policies, and iterations to create a minimal structure.

Do I need execution logs to run TAKT workflow optimization?

Execution logs are not required to run TAKT workflow optimization. The optimizer can analyze existing piece YAML and facet maps independently, but providing logs from .takt/logs/*.jsonl enables data-driven metrics to justify proposed changes.

Why does my TAKT workflow have bloated pieces and fragmented facets?

TAKT workflows often become bloated due to fragmented pieces, duplicated facets, and manual optimization effort. Automated optimization identifies and consolidates these patterns, unifying movements and proposing parallelization to reduce overall token usage.