CtrlK
BlogDocsLog inGet started
Tessl Logo

voice-persona-mars

Route to Mars (introspective thought partner / demo showman voice persona). Used when the operator wants depth, meaning, or impressive social demos rather than logistics. Mars handles SOLO mode (philosophy, presence, patterns) and DEMO mode (tool-driven showmanship) automatically.

68

Quality

85%

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

85%

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

A well-structured, actionable skill body with clear routing workflows, enforcement checkpoints, and clean one-level references. Minor conciseness gains are available by trimming repeated justifications around the Iron Law and Venus-redirect logic.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes competence, but there is some explanatory padding (e.g., elaborated rationale behind the Iron Law and repeated explanations of the Venus redirect) that could be tightened without losing clarity.

2 / 3

Actionability

Provides concrete, executable guidance: specific endpoints ('?persona=mars', '/session'), an exact call-link example with regex slug pattern, named tools per mode, and named enforcement scripts/tests.

3 / 3

Workflow Clarity

Routing and mode-detection flows are clearly sequenced (resolver routes session, mode-switch happens inside persona), with explicit validation/feedback via re-route to Venus on drift and named conformance tests acting as checkpoints.

3 / 3

Progressive Disclosure

Well-organized sections with one-level-deep, clearly signaled references to sister skills (voice-persona-venus, voice-post-call) and code paths; no nested-reference indirection and no bundle files are needed for a skill of this size.

3 / 3

Total

11

/

12

Passed

Description

85%

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 that clearly states both capability and invocation conditions with a clear niche. Trigger-term naturalness is slightly more dependent on the skill name 'Mars' than fully self-evident keywords, but the included phrases are reasonable.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: 'Route to Mars', handles 'SOLO mode (philosophy, presence, patterns)' and 'DEMO mode (tool-driven showmanship)', with explicit contrast against logistics routing.

3 / 3

Completeness

Explicitly answers both what ('Route to Mars... introspective thought partner / demo showman voice persona') and when ('Used when the operator wants depth, meaning, or impressive social demos rather than logistics'), with an explicit 'Used when' clause.

3 / 3

Trigger Term Quality

Includes natural phrases a user might say ('thought partner', 'what's on my mind', 'introspective'), but the body's frontmatter triggers carry the bulk of trigger coverage and the description leans on the skill-name 'Mars' rather than fully natural standalone keywords.

2 / 3

Distinctiveness Conflict Risk

The niche is distinct (introspection/showmanship vs logistics handled by the sister 'Venus' persona), and the explicit contrast makes conflict with other skills unlikely.

3 / 3

Total

11

/

12

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.