appeal-score

Analyze technical documentation prose defects and generate prioritized improvement lists.

30|12|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/anthony-chaudhary/fak --skill appeal-score
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: appeal-score
Source: https://github.com/anthony-chaudhary/fak/tree/main/.claude/skills/appeal-score
Command: npx skills add https://github.com/anthony-chaudhary/fak --skill appeal-score

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the issue of machine-generated prose that feels robotic, repetitive, and difficult for human readers to engage with, ensuring your documentation sounds authentic and trustworthy.

Core Features & Use Cases

  • Prose Scorecard: Analyzes text for specific defects like em-dash floods, overlong sentences, and LLM-scaffolding phrases.
  • Debt Burndown: Provides a repeatable, metric-driven workflow to reduce appeal-debt without altering the underlying claims or technical accuracy.
  • Use Case: Use this to audit your README or technical guides before a release to ensure they land effectively with human readers and answer engines.

Quick Start

Run the appeal score tool on the README file to identify prose defects and generate a prioritized list of human-voice improvements.

Frequently Asked Questions about appeal-score

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

FAQPage Schema
How do I make technical documentation sound less robotic and more human?

To make technical documentation sound less robotic, you can run a prose scorecard that analyzes text for specific LLM-tells like em-dash floods, overlong sentences, and scaffolding phrases. This process generates a prioritized list of human-voice improvements.

What are common LLM-tells in README files and how do I audit them?

Common LLM-tells in README files include em-dash floods, overlong sentences, and repetitive LLM-scaffolding phrases. You can audit these prose defects using a metric-driven scorecard that identifies readability issues while maintaining strict factual and link integrity.

Can I improve the readability of technical guides without changing technical accuracy?

You can improve the readability of technical guides without altering technical accuracy by applying a debt burndown workflow. This approach provides a repeatable, metric-driven process to reduce prose defects while strictly maintaining the underlying claims and factual integrity.

Do I need Python to run readability audits on reader-facing prose?

Yes, you need Python installed to execute the scorecard logic for readability audits. The Python environment is required to analyze reader-facing prose, identify machine-generated defects, and generate actionable improvement lists.

When should I audit my documentation for machine-generated prose defects?

You should audit your documentation for machine-generated prose defects before a release to ensure the content lands effectively with human readers and answer engines. This guarantees your technical guides sound authentic and trustworthy without robotic repetition.