Name: personwise/personwise-product-first-success
Rating: 66.4 (1 reviews)
Author: personwise

personwise/personwise-product-first-success

New users stall before their first success, and every stalled setup costs activation. Turn your setup guides and manuals into an interactive digital-human quick start guide that walks users to first successful use and answers their questions along the way. High-risk steps always point back to qualified on-site confirmation — the course guides, it never certifies.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

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.

A highly actionable, well-sequenced operational skill body with strong command examples and validation checkpoints. Its main weaknesses are repeated explanations of the same no-op behavior and a monolithic structure that would benefit from offloading detail into reference files.

Suggestions

Consolidate the three explanations of the 'awaiting_sources' 200-no-op / source-ready behavior into one authoritative paragraph and reference it, removing the repetition around lines 213-218, 220-226, and 300-304.

Move the detailed CLI command reference and the authorization/update-handling matrix into a separate references/ file (one level deep) and link to it from SKILL.md, keeping the body as an overview.

Dedupe the 'running and waiting are normal in-progress states, not failures' guidance that appears both in the run-wait section (~line 260) and the finish/recover section (~line 286).

Dimension	Reasoning	Score
Conciseness	The body is dense and operationally efficient, but the 'awaiting_sources' 200-no-op behavior is restated in three places (around lines 213-218, 220-226, and 300-304) and 'running/waiting are not failures' repeats, so it could be tightened.	3 / 5
Actionability	Concrete, copy-paste-ready commands with explicit placeholders cover the common cases — e.g. 'personwise --account <alias> course readiness --json' and 'course create --input <blueprint.json> --json'.	5 / 5
Workflow Clarity	The workflow is clearly sequenced (version check, bootstrap, auth, update check, readiness, create, source, wait, review, publish) with explicit validation checkpoints and error-recovery feedback loops (source retry, CONFLICT read-then-retry).	5 / 5
Progressive Disclosure	Structure is present and asset references (assets/bootstrap.sh, bootstrap.ps1, service-descriptor.signed.json) are real and signaled, but the bulk operational reference is inlined in one ~320-line SKILL.md rather than split into one-level-deep reference files.	3 / 5
	Total	16 / 20 Passed

Description

83%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, third-person description that concretely states capabilities and gives explicit trigger language for when to invoke the skill. It is largely distinct and complete, with only minor room to add synonyms and tighten coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and several 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 only minor coverage gaps.	4 / 5
Completeness	Explicitly answers both 'what' (produce the interactive course, install the CLI, OAuth) and 'when' via a 'Use when...' clause plus concrete trigger phrases.	5 / 5
Trigger Term Quality	'Trigger language: product setup; getting started; quick start guide; first successful use' gives good natural-term coverage, though a few common synonyms are absent.	4 / 5
Distinctiveness Conflict Risk	The 'Product First-Success Guide' niche with distinct triggers is mostly separable, with only minor overlap risk against broader course-creation skills.	4 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Reviewed

21 days ago

Table of Contents

Discovery Implementation Validation