CtrlK
BlogDocsLog inGet started
Tessl Logo

map-personas

Use when mapping supplied roles or stakeholder evidence into buyer, user, champion, and blocker personas for an offer or account.

73

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

93%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, actionable instruction skill with concrete rules, statuses, and an output template. The only minor gap is the absence of an explicit error-recovery feedback loop, though the task does not demand one.

DimensionReasoningScore

Conciseness

The body is lean and well-sectioned with no padding and no explanation of concepts Claude already knows; every section (Purpose, Required inputs, Workflow, Output format, Guardrails, Quality check) earns its place.

5 / 5

Actionability

Guidance is concrete and executable: exact statuses (Fact/Hypothesis/Missing), exact functions (Buyer/User/Champion/Blocker), explicit fact-vs-hypothesis rules, and a copy-paste output table template. Absence of code is appropriate for this instruction-only skill.

5 / 5

Workflow Clarity

A clear six-step sequence is paired with a "Quality check" validation checkpoint, but there is no explicit validate→fix→retry feedback loop; this is an analytical (non-destructive) task so the destructive cap does not apply, leaving it just below the top anchor.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references and no bundle files present, the body is well-organized into clear sections, satisfying the simple-skill exception for the top score.

5 / 5

Total

19

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description with an explicit "Use when" trigger and a distinctive niche. Keyword coverage and action breadth are the only mild areas, both already solid.

DimensionReasoningScore

Specificity

The description names the domain and concrete output categories — "mapping supplied roles or stakeholder evidence into buyer, user, champion, and blocker personas" — listing several specific persona types, but the core action remains a single verb (mapping), so it falls just below comprehensive multi-action coverage.

4 / 5

Completeness

It explicitly answers both what ("mapping supplied roles or stakeholder evidence into ... personas") and when ("Use when mapping ... for an offer or account") with a concrete trigger phrase, matching the top anchor.

5 / 5

Trigger Term Quality

Natural sales/account terms are well represented ("personas", "buyer", "champion", "blocker", "stakeholder", "roles", "offer", "account"), but a few natural synonyms a user might say (e.g. "stakeholder mapping", "role mapping", "decision-makers") are absent.

4 / 5

Distinctiveness Conflict Risk

The four-function persona model for offers/accounts is a clear, narrow niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
llaskin/AI-SDR-Skill-Pack
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.