amend-skill

To improve prompt effectiveness, you analyze execution logs to identify failure patterns and propose targeted amendments to trigger conditions, steps, and payloads. This ensures your prompt logic remains effective by addressing recurring errors directly.

Failure analysis for debugging code analysis skills works by examining observation logs to pinpoint recurring errors. It identifies specific failure patterns in skill execution history and generates a unified diff to propose targeted improvements to the skill's logic.

The best way to fix a skill blocked by a WAF is to analyze the execution logs, identify the WAF pattern, and suggest adding a WAF bypass technique to the skill's instructions. This generates a targeted amendment to the skill's payload.

Yes, you need observation logs to analyze skill execution history. The analysis requires access to observation logs and skill markdown files to pinpoint recurring errors and propose targeted amendments for improving skill effectiveness.

Yes, you can use this to tighten trigger conditions and fix missing steps. It analyzes execution history and proposes targeted amendments addressing failure patterns in trigger conditions, steps, payloads, and output formats by generating a unified diff.

The limitation of automated skill improvement is that it requires existing observation logs and skill markdown files for analysis. It cannot propose amendments without prior execution history data to identify failure patterns and generate a unified diff for review.