CtrlK
BlogDocsLog inGet started
Tessl Logo

personwise/personwise-partner-training

Partners repeat what your materials say — to their customers, in public. Turn your approved partner program materials into an interactive digital-human partner training course that teaches the product story, the deal flow, and the rules exactly as approved, and answers partner questions on demand. Commissions, territories, and earnings are never promised beyond what you have approved.

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

Quality

Content

77%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.

The body is a highly actionable, well-sequenced governed-CLI workflow with strong validation and feedback loops, but it is verbose in places and packs operational detail inline rather than splitting it into one-level reference files.

Suggestions

Deduplicate the awaiting_sources / no-op behavior: state the rule once and reference it from the upload, conflict, and recovery sections instead of re-explaining it three times.

Move the long update-check freshness and error-handling matrix (the "Keep the CLI and this Skill current" section) into a separate reference file and keep SKILL.md as a quick-start overview with a clear pointer.

Consolidate the scattered safety prohibitions (sudo/PATH/credential handling) into one short list rather than restating them across the bootstrap, auth, and source-upload sections.

DimensionReasoningScore

Conciseness

The guidance is operational and assumes Claude's competence, but it restates the same invariants several times — the awaiting_sources no-op behavior is explained in three places (the source-upload section, the conflict section, and finish/recover), and the safety prohibitions are repeated across sections — so it is mostly efficient but could be tightened.

3 / 5

Actionability

Fully executable, copy-paste-ready commands with exact flags are given throughout — `personwise version --json`, `course readiness --json`, `course create --input <blueprint.json> --json`, `source add/status/retry/detach`, `run wait/get/advance` — covering the common cases concretely.

5 / 5

Workflow Clarity

A clearly sequenced workflow (version → bootstrap → auth → update check → readiness → blueprint → sources → checkpoints → publish) with explicit validation checkpoints and feedback loops, e.g. "Do not call run advance while any source is pending", CONFLICT→`read_current_state` handling, and retry-only-when-freshly-allowed recovery for a long-running batch operation.

5 / 5

Progressive Disclosure

Referenced bundle paths are real one-level-deep files (`assets/bootstrap.sh`, `assets/bootstrap.ps1`, both present), but the SKILL.md itself is a ~330-line monolith that inlines operational detail which could live in separate reference files, with no quick-start-then-reference split.

3 / 5

Total

16

/

20

Passed

Description

100%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.

The description is a strong, third-person trigger-rich statement that concretely states what the skill does and when to invoke it, with an explicit scope boundary. It avoids fluff and over-claims while naming specific capabilities and natural trigger phrases.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Produce a grounded interactive digital-human course learners can interrupt with voice questions", "install or update the official PersonWise CLI", "uses browser OAuth" — with comprehensive coverage rather than generic phrasing.

5 / 5

Completeness

Explicitly answers both what ("Produce a grounded interactive digital-human course") and when ("Use when the user asks for Partner Training") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Provides an explicit trigger-language block — "partner training; partner onboarding; channel partner training; reseller training" — covering the natural variations a user would say.

5 / 5

Distinctiveness Conflict Risk

A clear partner/reseller-training niche with an explicit boundary clause ("Other course-creation requests are handled only when the user explicitly asks for them") that minimizes conflict with adjacent course skills.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents