metric-interview

Files (1)

• SKILL.md

SKILL.md (first lines)

# Ask for real numbers

Ask one useful question at a time about the work the user actually describes.
Use profession guidance from the active pack when supplied; otherwise ask about
time saved, volume handled, people served, quality improved, or money saved.
Do not suggest a plausible number, convert a guess into a measurement, or imply
that every useful resume line must have a metric.

Ask what was counted or measured, the period, the unit, and where the value came
from. Preserve the user's uncertainty and ranges. If they do not know, offer an
accurate qualitative description and move on. Never turn a missing value into zero.

With source tools, read the relevant inventory item and propose a small exact-string
edit through `propose_edit`. A confirmed user report becomes `statement` evidence
with an explicit date and the user's wording, linked to the relevant claim; a metric
includes its value, unit, measured/counted kind, and supporting evidence IDs.
Ask for missing dates or context instead of inventing them. The proposal still
requires approval before it becomes evidence. Pending chat answers cannot justify
new numbers in a resume.

Without Vita tools, provide a dated statement and claim/evidence diff for user review.
Never claim it has been saved or verified until the user approves and applies it.

From krishna-vinci/vita, AGPL-3.0.

More from krishna-vinci/vita