prompt-optimizer

Analyzes draft prompts and generates optimized, ready-to-paste versions.

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/KanakMalpani/General-Private-Skills --skill prompt-optimizer-kanakmalpani
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prompt-optimizer
Source: https://github.com/KanakMalpani/General-Private-Skills/tree/main/skills/prompt-optimizer
Command: npx skills add https://github.com/KanakMalpani/General-Private-Skills --skill prompt-optimizer-kanakmalpani

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes draft prompts, identifies intent and gaps, matches ECC components (skills/commands/agents/hooks), and outputs a ready-to-paste optimized prompt. It operates in advisory mode only — never executes tasks itself.

Core Features & Use Cases

  • Intent detection and gap analysis to align prompts with ECC primitives
  • Mapping to ECC components for consistent prompt orchestration
  • Generation of a complete, paste-ready optimized prompt with workflow guidance

Quick Start

Paste a draft prompt into the ECC optimizer and receive a ready-to-paste optimized prompt.

Frequently Asked Questions about prompt-optimizer

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

FAQPage Schema
How do I optimize a draft prompt for software engineering tasks?

To optimize a draft prompt, paste it into the prompt optimizer which analyzes intent, identifies gaps, and maps requirements to produce a ready-to-paste prompt with acceptance criteria and verification steps.

What is prompt engineering gap analysis for bug fixes and refactoring?

Prompt engineering gap analysis detects missing intent and scope boundaries in draft prompts, mapping them to workflow components to generate complete prompts for bug fixes, refactoring, and new features.

Can I use prompt optimization for research and documentation scopes?

Yes, prompt optimization supports research and documentation scopes by adapting to the detected tech stack and generating prompts that follow a six-phase workflow with clear scope boundaries.

Does the prompt optimizer execute tasks or generate workflow guidance?

The prompt optimizer operates in advisory mode only, meaning it never executes tasks itself but instead produces ready-to-paste optimized prompts with workflow guidance and verification steps.

What's the best way to structure prompts for testing and code review?

The best way to structure testing and code review prompts is mapping them to ECC components, ensuring outputs follow the six-phase workflow and include explicit acceptance criteria and scope boundaries.