CtrlK
BlogDocsLog inGet started
Tessl Logo

voice-transcription

Framework-wide voice dictation in the agent sidebar composer. Use when changing composer microphone UX, the transcribe-voice route, or the Voice Transcription settings section. Covers transcription-source routing, cleanup routing, Google realtime gating, and the voice transcription application-state keys.

67

Quality

82%

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

65%

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 and well-structured with concrete framework symbols, but it is long, retains some non-instructional rationale, omits validation checkpoints in the batch workflow, and keeps all detail inline rather than splitting into referenced files.

Suggestions

Tighten conciseness by trimming design-rationale asides (e.g., the Cursor/Lovable comparison in the mic-visibility rule) so every line is directly instructional.

Add an explicit validation/verification checkpoint to the batch transcription routing workflow (e.g., confirm a non-empty transcript and a successful provider response before returning) to satisfy the batch-operations feedback-loop expectation.

Move the detailed realtime-speech-mode spec and the provider preference table into a reference file linked one level deep from SKILL.md, keeping the body as a concise overview, to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The ~210-line body is mostly dense, framework-specific guidance with no basic-concept padding, but it carries rationale asides (e.g., the Cursor/Lovable comparison, "more forgiving in a sidebar") and notable length that could be tightened.

2 / 3

Actionability

It supplies exact file paths, route names (/_agent-native/transcribe-voice, /_agent-native/transcribe-stream/session), function symbols (executeAgentToolCall, parseVoiceContextPack, readAppSecret({...})), state keys, and a copy-ready code snippet, giving concrete executable guidance.

3 / 3

Workflow Clarity

Sequences are present (numbered batch routing, the realtime manifest handling with a session.updated checkpoint), but the batch transcription workflow lacks an explicit validate/verify feedback loop, which caps batch-operation workflows at 2.

2 / 3

Progressive Disclosure

Sections and the "Where the pieces live" navigation table are well organized, but the skill is a single ~210-line monolithic SKILL.md with no bundle references and content (realtime spec, provider table) that could be split out one level deep.

2 / 3

Total

9

/

12

Passed

Description

100%

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, third-person, and answers both what and when with an explicit Use-when clause tied to concrete framework entry points. It is concise without fluff and clearly distinguishable from other skills.

DimensionReasoningScore

Specificity

Names multiple concrete framework concerns — "transcription-source routing, cleanup routing, Google realtime gating, and the voice transcription application-state keys" — rather than vague abstractions, matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly states both what ("Framework-wide voice dictation in the agent sidebar composer") and when via a clear "Use when" clause, satisfying the explicit-trigger requirement that allows a 3.

3 / 3

Trigger Term Quality

The "Use when changing composer microphone UX, the transcribe-voice route, or the Voice Transcription settings section" triggers are the exact concrete terms a framework developer would say when reaching for this skill.

3 / 3

Distinctiveness Conflict Risk

The niche is narrowly scoped to voice transcription in a specific framework with distinct route/section triggers (transcribe-voice route, Voice Transcription settings), making conflict with other skills unlikely.

3 / 3

Total

12

/

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

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository
BuilderIO/agent-native
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.