CtrlK
BlogDocsLog inGet started
Tessl Logo

voice-note-ingest

Ingest a voice note with exact-phrasing preservation (never paraphrased). Routes content to originals/, concepts/, people/, companies/, ideas/, personal/, or voice-notes/ based on a decision tree. The user's exact words are the signal.

64

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/voice-note-ingest/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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 body with a clear pipeline and decision tree, weakened by test-conformance filler that hurts conciseness and a lack of explicit verification checkpoints in the workflow.

Suggestions

Remove or relocate the 'Contract' and 'Output Format' sections that only exist for the conformance test, or fold their guarantees into the existing body sections to remove non-guidance padding.

Add an explicit verification step to the pipeline (e.g., 'VERIFY: confirm every mentioned person/company now has a back-link to this page') so workflow clarity is not capped at 2.

Tighten the Iron Law section so it does not repeat the exact-phrasing claim already stated in the description.

DimensionReasoningScore

Conciseness

The body is mostly efficient, but the trailing 'Contract' and 'Output Format' sections are explicit test-harness filler ('this section exists for the conformance test') and the Iron Law reiterates the description's exact-phrasing point, so it could be tightened.

2 / 3

Actionability

Provides concrete executable guidance: a 5-step pipeline with named commands ('gbrain transcription'), a first-match-wins decision tree with exact directory targets, a copy-paste brain-page skeleton, and precise citation/naming formats.

3 / 3

Workflow Clarity

The STORE→TRANSCRIBE→ROUTE→WRITE→CROSS-LINK sequence is clearly ordered, but there is no explicit verification checkpoint (e.g., confirm cross-links exist); correctness is only implied via the anti-patterns list, matching the 'sequence present but checkpoints implicit' anchor.

2 / 3

Progressive Disclosure

Well-organized into focused sections with clearly signaled, one-level-deep references (top blockquotes to conventions/quality.md and _brain-filing-rules.md, plus a Related skills section); no nested reference chains and no bundle files to verify.

3 / 3

Total

10

/

12

Passed

Description

82%

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 with good natural trigger coverage and a clear niche, held back only by the absence of an explicit 'Use when...' usage clause in the description string itself.

Suggestions

Add an explicit 'Use when...' clause to the description string (e.g., 'Use when the user sends an audio or voice message to be captured and filed'), so completeness is not capped at 2.

Consider leading with a third-person verb form ('Ingests voice notes...') to align with the 'Processes files' anchor style and avoid the imperative 'Ingest' opening.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Ingest a voice note with exact-phrasing preservation', 'Routes content to originals/, concepts/, people/, companies/, ideas/, personal/, or voice-notes/'), matching the anchor for listing several specific actions rather than vague language.

3 / 3

Completeness

The 'what' is clear, but the description string lacks an explicit 'Use when...' clause; per the judging guidelines a missing explicit trigger clause caps completeness at 2 even though the frontmatter carries a separate triggers list.

2 / 3

Trigger Term Quality

The triggers field supplies natural phrasings a user would actually say ('voice note', 'save this audio note', 'audio message', 'ingest this voice memo'), giving good coverage rather than technical jargon.

3 / 3

Distinctiveness Conflict Risk

The exact-phrasing voice-capture niche plus routing to a specific set of brain directories is a clear, narrow scope unlikely to fire for the wrong skill, matching the distinct-niche anchor.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 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: 1 missing, 2 suspicious

Warning

Total

14

/

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.