Score · Assess & Decide · Analysis & Finance

Score a content piece on the STEPPS virality framework

The buyer gets a complete STEPPS scorecard: all six factors (social currency, triggers, emotion, public, practical value, stories) rated as whole numbers on the agreed scale, each with a written rationale that clears a minimum word count, plus a total_score that equals the sum of the six scores.

You receive: A JSON object with one entry per STEPPS factor (social_currency, triggers, emotion, public, practical_value, stories), each carrying a whole-number score and a written rationale, plus a total_score field, and no other top-level keys.

Part of Distribution

What's verified: STUD verifies that the deliverable is a JSON document of at most 100,000 characters, that all six STEPPS factors are present as objects with no extra top-level keys, that every factor score is a whole number from 0 to your maximum (default 5; a maximum set outside 1 to 100 falls back to 5), that every factor carries a written rationale of at least your minimum word count (default 8; a minimum set outside 1 to 200 falls back to 8) with at least 3 distinct words and no placeholder filler (TBD, todo, n/a, lorem ipsum, and similar), and that total_score equals the sum of the six factor scores. STUD does NOT verify that the scores are well judged, that the rationales actually describe your content, or that the operator used the content, format, and audience you provide; those intake fields are operator context only. The score maximum and the minimum rationale word count are the only intake fields that drive the verdict.