persona-score

To audit your repository for missing documentation and affordances, run the persona-score skill. It analyzes the file tree against a scorecard of hard requirements to calculate persona-debt and generates a prioritized work-list of missing items.

Persona-debt is the gap between what a target user needs, such as installation paths or deployment guides, and what is actually present in the repository tree. Accumulating this debt makes the project inaccessible to critical users like infra engineers.

You can prevent repository drift by using the persona-score skill as a regression sentinel. It acts as a gatekeeper to ensure future changes do not accidentally break the entry paths and affordances required by your top-10 defined personas.

Yes, you can use a scorecard to track onboarding readiness by evaluating the repository against hard requirements for defined user personas. The skill measures this readiness deterministically and provides a repeatable framework for maintaining user-experience standards.

Yes, you need Python installed to run a persona readiness audit. The skill depends on Python scripts to analyze the file tree, evaluate affordances against the scorecard, and generate the work-list for retiring project debt.

The best way to generate an actionable work-list for missing affordances is to run a persona-debt audit. The skill evaluates the file tree and outputs a prioritized list targeting the most critical missing requirements for your top-10 personas.