prompt-analyzer

Analyze Task and Phase Briefs to generate insights and improvement recommendations.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/zero-rehq/opencode-kit --skill prompt-analyzer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prompt-analyzer
Source: https://github.com/zero-rehq/opencode-kit/tree/main/.opencode/skill/prompt-analyzer
Command: npx skills add https://github.com/zero-rehq/opencode-kit --skill prompt-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analysts and teams often struggle to extract actionable insights from Task Briefs and Phase Briefs. The Prompt Analyzer consolidates analysis, highlights patterns of success and anti-patterns, and guides iterative prompt improvements.

Core Features & Use Cases

  • Insight Generation: derives actionable insights, comparisons, and improvement recommendations from briefs.
  • Pattern Detection: identifies successful and problematic brief patterns across multiple tasks.
  • Auto & Manual Triggers: supports auto-trigger after brief generation and manual prompts like /analyze-brief and /compare-briefs.

Quick Start

Use the prompt-analyzer to analyze a Task Brief by providing the path to the brief, e.g. worklog/2026-01-15_task.md, and request insights or improvements.

Frequently Asked Questions about prompt-analyzer

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

FAQPage Schema
How do I analyze Task Briefs to extract actionable insights and improvement recommendations?

To analyze Task Briefs, provide the brief file path and request insights or improvements. The analyzer derives actionable recommendations, highlights patterns, and outputs Markdown-ready results for iterative prompt enhancement.

What is the best way to compare multiple Phase Briefs for successful and problematic patterns?

Comparing multiple Phase Briefs is done using the /compare-briefs command. This identifies successful and anti-patterns across tasks to guide iterative prompt improvements and output Markdown-compatible comparisons.

Can I auto-trigger brief analysis immediately after brief generation in OpenCode?

Brief analysis supports auto-trigger after brief generation within the OpenCode workflow. It also supports manual prompts like /analyze-brief for on-demand analysis of single or multiple briefs.

Does the prompt analyzer work without external dependencies or components?

The analyzer operates with no external dependencies or components. It implements five analysis modes, quality metrics, and pattern detection internally, ensuring self-contained brief evaluation.

How do I integrate brief analysis results with an orchestrator and supermemory?

Brief analysis outputs Markdown-ready results compatible with orchestrator and supermemory integration. This ensures derived insights and improvement recommendations flow seamlessly into downstream workflows.