CtrlK
BlogDocsLog inGet started
Tessl Logo

voice-persona-venus

Route to Venus (sharp executive-assistant voice persona). Used for logistics — calendar, tasks, recent messages, brain lookups — at sub-second phone-call latency. The default voice persona unless DEFAULT_PERSONA=mars is set.

59

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./recipes/agent-voice/skills/voice-persona-venus/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 tight, actionable overview that routes detail to the persona prompt, tool allow-list, and sister skills with clear navigation. It is strong on conciseness and actionability, with only minor organization and validation-loop gaps typical of a behavioral skill.

DimensionReasoningScore

Conciseness

The body is lean and opinionated ("Speed is the signal", "SHUT UP. Wait.") and assumes competence, with only minor trimmable asides such as the Output Format rationalization.

4 / 5

Actionability

Concrete guidance abounds — the exact `/call?persona=venus&topicId=...` URL, the `^[a-z0-9][a-z0-9-]*$` slug, named tool ops, and exact file paths — but it is instruction/behavior-oriented rather than copy-paste code, leaving minor gaps.

4 / 5

Workflow Clarity

The topic-summoning flow and conversation-timing rules are clearly sequenced with an explicit safety checkpoint ("Never put topic content in the URL"), though behavioral skills lack formal validate→fix→retry loops.

4 / 5

Progressive Disclosure

Well-organized sections push detail to one-level-deep targets (persona prompt in venus.mjs, allow-list in tools.mjs, sister skills linked), but there is no in-bundle references/ structure and links point to code outside the skill.

4 / 5

Total

16

/

20

Passed

Description

66%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 specific and distinct, naming concrete logistics capabilities and a clear persona niche, but it lacks an explicit "Use when..." trigger clause, capping completeness. Trigger terms are present but not comprehensive.

Suggestions

Add an explicit "Use when the operator says calendar, tasks, schedule, or asks for a quick logistics answer" clause to raise completeness above 3.

Expand trigger-term coverage in the description with synonyms like "schedule" and "reminders" so natural phrases are not split between description and frontmatter.

State the routing trigger surface (voice or text input matching the triggers) explicitly to reduce ambiguity about when Venus activates.

DimensionReasoningScore

Specificity

"Used for logistics — calendar, tasks, recent messages, brain lookups" lists several concrete capabilities alongside the routing action, though coverage of the persona's full behavior is implied rather than enumerated.

4 / 5

Completeness

The "what" is clear (route to Venus for logistics at sub-second latency) but there is no explicit "Use when..." trigger clause — "Used for logistics" only weakly implies when, so completeness is capped at 3 per the guidelines.

3 / 5

Trigger Term Quality

Natural user terms like "calendar", "tasks", and "recent messages" appear, but common synonyms (e.g. "schedule", "reminders") and the explicit trigger phrases live in the frontmatter triggers rather than the description.

4 / 5

Distinctiveness Conflict Risk

"sharp executive-assistant voice persona" with a logistics niche and a default-unless-DEFAULT_PERSONA=mars carve-out is mostly distinct, with minor overlap risk against the sister mars persona.

4 / 5

Total

15

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 4 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

13

/

16

Passed

Repository
garrytan/gbrain
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.