optimize

Cluster open misses from threads_skill_learnings.log into sub_skill and category groups.

262|179|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/akseolabs-seo/AK-Threads-booster --skill optimize-akseolabs-seo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: optimize
Source: https://github.com/akseolabs-seo/AK-Threads-booster/tree/main/skills/optimize
Command: npx skills add https://github.com/akseolabs-seo/AK-Threads-booster --skill optimize-akseolabs-seo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Optimize skill converts repeated misses captured in threads_skill_learnings.log into concrete, reviewable sub-skill rule edits, ensuring changes are proposed with evidence and require explicit user approval.

Core Features & Use Cases

  • Cluster open misses by sub_skill and category to surface actionable improvement areas.
  • Draft concrete edits with exact file locations, before/after text, and supporting quotes.
  • Require explicit user approval before applying any change, with safe backups and version bumps.
  • Maintain a changelog-like trace of addressed entries and superseded items for auditability.
  • Anchor edits to shared knowledge and rules to maintain consistency across sub-skills.

Quick Start

Review threads_skill_learnings.log, draft proposals, and await your approval to apply edits.

Frequently Asked Questions about optimize

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

FAQPage Schema
How do I turn workflow log analysis misses into actionable rule edits?

Turn log analysis misses into actionable rule edits by clustering open entries from threads_skill_learnings.log into sub_skill and category groups. The process drafts concrete edits with exact file locations, before/after text, and supporting evidence quotes for review.

What is the best way to propose sub-skill rule changes from captured log data?

The best way to propose sub-skill rule changes from captured log data is to anchor edits to shared knowledge and rules, maintaining consistency across sub-skills. Proposals include exact file locations, before/after text, and supporting quotes for reviewer approval.

How do I apply versioning and backups when updating sub-skill rules?

Apply versioning and backups when updating sub-skill rules by requiring explicit user approval before applying any change. The system manages safe backups, performs version bumps, and maintains a changelog-like trace of addressed entries and superseded items for auditability.

Can I review and group log misses by category before modifying workflow files?

Yes, you can review and group log misses by category before modifying workflow files. The optimization process surfaces actionable improvement areas by clustering open misses by sub_skill and category, drafting proposals that await explicit approval before any edits are applied.

Why does updating sub-skill rules require explicit user approval?

Updating sub-skill rules requires explicit user approval to ensure changes are proposed with evidence and applied safely. This requirement guarantees that safe backups and version bumps are executed intentionally, maintaining traceable records of superseded entries.