CtrlK
BlogDocsLog inGet started
Tessl Logo

personwise/personwise-report-briefing

Reports get skimmed for one chart and misquoted forever. Turn your whitepaper or benchmark report into an interactive digital-human briefing course that teaches the findings with the method and the limits attached — and answers audience questions the PDF cannot. No causal leaps, no predictions beyond what the report states.

71

Quality

89%

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

81%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 highly actionable with a clearly sequenced, validation-rich workflow and concrete CLI commands. Its main weakness is verbosity from repeated passages and a monolithic structure that leans heavily on inline detail rather than progressive file splits.

Suggestions

Deduplicate the awaiting_sources no-op explanation (currently restated in 'Build and submit the blueprint' and 'Finish, recover, and report') into a single canonical passage and reference it.

Consolidate the repeated 'never create a replacement run/course' injunctions into one stated rule to reduce token cost.

Move the lengthy CLI/Skill freshness and update-protocol detail into a referenced file (e.g. UPDATES.md) to keep SKILL.md a leaner overview.

DimensionReasoningScore

Conciseness

Mostly efficient for a complex governed-CLI workflow, but the awaiting_sources no-op behavior is restated nearly verbatim in two sections and 'never create a replacement run' is repeated several times; these duplications could be tightened without losing clarity.

3 / 5

Actionability

Provides fully executable, copy-paste-ready commands with flags and placeholders throughout — 'personwise version --json', 'personwise --account <alias> course create --input <blueprint.json> --json', 'run wait --run-id <run-id> --timeout-seconds 1800 --json' — covering the common cases concretely.

5 / 5

Workflow Clarity

The workflow is clearly sequenced (readiness → blueprint → sources → checkpoints → review → publish) with explicit validation checkpoints and feedback loops: 'If a source fails ... retry ... if the same error returns, stop', and conflict handling via 'read_current_state' with bounded retry then stop.

5 / 5

Progressive Disclosure

Well-structured with clear section headers and one-level-deep, well-signaled references to real bundle files (assets/bootstrap.sh, assets/bootstrap.ps1), but the doc is largely monolithic with extensive inline protocol detail that could be split into referenced files.

4 / 5

Total

17

/

20

Passed

Description

95%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 strong: it explicitly states what the skill produces, when to use it, lists natural trigger terms, and scopes itself to avoid conflicts. Its only weakness is a degree of verbosity from embedded safety/constraint clauses that dilute the action list.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'Produce a grounded interactive digital-human presentation', 'interrupt with voice questions', 'install or update the official PersonWise CLI', 'uses browser OAuth' — though much of the text is constraint/safety language rather than action coverage, leaving minor gaps versus a fully comprehensive action list.

4 / 5

Completeness

Clearly answers both 'when' ('Use when the user asks for Report Briefing from supplied source materials') and 'what' ('Produce a grounded interactive digital-human presentation ... delivered as an askable course') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Explicitly enumerates natural trigger phrases a user would say — 'report briefing; research presentation; whitepaper summary; benchmark report; interactive presentation' — giving comprehensive coverage with synonyms.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (report-briefing courses) and explicitly bounds scope ('Other course-creation requests are handled only when the user explicitly asks'), minimizing overlap with other skills.

5 / 5

Total

19

/

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