Skip to content

voyager67/Pixelcraft / skills/pricing-page-slop-repair

pricing-page-slop-repair

Verified

Finds generic SaaS pricing-table slop: arbitrary plan tiers, feature-checkmark walls, misleading savings, fake popularity, and unclear billing terms.

FileKindSize
SKILL.mdskill md2.5 KB
agents/openai.yamlconfig343 B
---
name: pricing-page-slop-repair
description: "Finds generic SaaS pricing-table slop: arbitrary plan tiers, feature-checkmark walls, misleading savings, fake popularity, and unclear billing terms."
license: CC-BY-NC-4.0
---

# Pricing Page Slop Repair

## Workflow

1. Confirm actual plans, billing intervals, included limits, add-ons, and cancellation terms from supplied source data.
2. Audit plan names and descriptions for vague labels and undifferentiated tiers.
3. Remove invented “Most popular”, crossed-out prices, savings claims, and customer counts unless substantiated.
4. Group features by buyer decision rather than showing a giant undifferentiated checklist.
5. Clarify units, overages, seat limits, annual/monthly billing, taxes, and trial terms.
6. Make plan comparison accessible on mobile and via keyboard.
7. Use explicit CTA labels and explain what happens after selection.

## Output

Pricing truth audit, comparison fixes, claims needing evidence, and mobile/keyboard checks.

## Non-negotiable rules

- Judge the interface that exists, not assumptions about who or what produced it. AI authorship cannot be reliably inferred from generic visual patterns alone.
- Treat “AI slop” as a shorthand for observable quality problems: generic patterns, weak hierarchy, arbitrary decoration, vague copy, fabricated-looking content, inconsistent systems, or incomplete states.
- A pattern is a signal, not proof. Record evidence, confidence, and plausible benign explanations. Do not label a screen “AI-generated” as a factual finding.
- Preserve user goals, factual content, product behavior, existing brand assets, and working accessibility unless the evidence supports a change.
- Never invent metrics, reviews, customer logos, endorsements, product claims, features, integrations, or data to make a screen look more convincing.
- Inspect rendered output when tools allow it. If you only inspect source code or a screenshot, state that limitation.
- Make the smallest effective change first. Do not replace an existing coherent visual language just to make the result look different.
- Never expose secrets or private information found in a repository. If a secret is detected, do not repeat its value; report only the file and line, stop short of publishing it, and recommend revocation/rotation.

## Completion report

State the signals found, evidence and confidence, fixes made, files changed, checks actually run, and unresolved issues. Distinguish visual review, code review, and runtime testing.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 196kUpdated Claude CodeCodexVerifiedInstall