eval-writing-styles

Sweeps prompt writing styles over shared eval cases and reports a quality-versus-token Pareto frontier.

Updated Jun 20, 2026
One-click install
npx skills add https://github.com/ensj/skill-eval-framework --skill eval-writing-styles-ensj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eval-writing-styles
Source: https://github.com/ensj/skill-eval-framework/tree/main/.claude/skills/eval-writing-styles
Command: npx skills add https://github.com/ensj/skill-eval-framework --skill eval-writing-styles-ensj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing a writing style for a prompt (caveman, terse, formal, bullet) is usually guesswork, and shorter prompts trade quality for token savings in unknown ways. This Skill measures that tradeoff empirically so you can pick a style based on data instead of intuition. ## Core Features & Use Cases - Style rewriting: Rewrites a base prompt into each style defined in src/styles/index.ts (baseline, caveman, terse, formal, bullet) via the patterns/restyle.js workflow. - Adaptive sweep: Runs all style variants over shared eval cases with patterns/eval-sweep.js, using adaptive seed batches up to n_max with a variance ceiling. - Cost-join and Pareto frontier: Joins quality scores with token costs via dist/styles/cost-join.js and computes a Pareto frontier and quality_per_cost winner through dist/compose-eval/cli.js. - Use Case: You suspect a terse version of your classify-text prompt would cut token spend. Run this Skill to get a report showing each style's quality mean, token cost, tokens saved versus baseline, and which styles dominate baseline. ## Quick Start Ask the agent to test writing styles for the classify-text skill using src/skills/classify-text/variants/v1-baseline.md as the base prompt and show the Pareto frontier.

Frequently Asked Questions about eval-writing-styles

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

FAQPage Schema
How do I test which prompt writing style performs best?▼

Provide a base prompt file and a skill id whose evals and output schema drive scoring. The Skill rewrites the prompt into each style, sweeps all variants over shared eval cases, and reports quality means, token costs, and a Pareto frontier.

How do I measure token cost savings from a terse or caveman prompt style?▼

The cost-join step combines the sweep leaderboard with per-artifact token counts, then the report computes tokens saved versus baseline for each style. It also states which styles dominate baseline on both quality and cost.

What setup is required before running a writing style evaluation?▼

Run npm run build from the skill-eval-framework root first. This emits patterns/restyle.js, patterns/eval-sweep.js, the skill output schemas, and the dist CLI bundles for variants, cost-join, scorer, and compose-eval.

Can I pass a fixed seeds argument to the style sweep?▼

No. The adaptive sweep ignores a seeds argument and decides seed count itself using seed_batch, n_max, and variance_ceiling. For the cost-join step, derive seeds as n_final divided by the number of cases.

What are the limitations of style-based prompt evaluation?▼

Results depend on the discriminating power of the eval cases; saturated evals can yield inconclusive outcomes. The comparison is also scoped to the styles defined in src/styles/index.ts and the single skill whose cases and schema drive scoring.