Individual skill

account-progression-staging

Use this skill when you want attribution that measures whether GTM activity actually moves accounts forward — not touchpoint "credit." It assigns each account a single current progression stage (Unaware → Aware → Engaged → Qualified → Sales Ready → Customer) from its full signal stack using deterministic, auditable rules, so the same inputs always produce the same stage and every assignment is explainable from the evidence that triggered it. Progression is measured at the account level with a buying-group gate — advancement requires multiple distinct contacts, never one power user — so a single loud champion can't fake momentum. Each run applies exactly one stage tag, records a stage-entry event with an evidence snapshot and time-in-prior-stage, updates the running stack in account memory, and routes a Sales-Ready alert with buying-group context and a recommended next action. Because it writes stage history, it turns attribution into delta-versus-baseline: conversion rate and velocity per stage transition, exposed cohort vs. control — so budget goes to what drives stage movement, not what drives clicks. Every threshold is exposed as a tunable default. Use it for stage assignment, progression tracking, "why is this account here?" explainability, stuck-account activation lists, and Sales-Ready routing.

skills/steve-armenti/account-progression-staging/SKILL.md

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD

Yes

Scanner rules are current

Yes

Repository scan complete

No

Skill scan complete

Yes

Observed behavior

Instructions only

Last checked

Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.