CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

typesafe-ai

Build AI-powered software with TypeSafe: small units of AI intelligence you can use like programming primitives. Its System One models, including Jev, turn natural language and application state into typed judgments and probabilities that code can combine. Use when a feature needs programmable common sense, when brainstorming what AI could make possible in an app, or when an LLM prompt-and-parse step could become a structured decision. Applications include routing, ranking, extraction, verification, and interactive experiences; these are starting points, not the limits. Read live docs and cookbooks to find useful patterns and discover new combinations.

Quality

73%

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 ./.claude/skills/typesafe-ai/SKILL.md

The canonical home for this skill is typesafe-ai in phatblat/dotfiles

SKILL.md
Quality
Evals
Security

Quality

Content

51%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 pure redirect that delegates everything to an external file outside the bundle. While maximally token-efficient and unambiguous as an instruction, it provides no actionable guidance, no workflow, and no in-bundle overview or references, so the skill functions only in environments where the external path happens to exist.

Suggestions

Inline a minimal quick-start in the body (e.g. one code snippet showing a TypeSafe judgment call and where to find the SDK) so the skill provides actionable guidance even when the shared external skill file is not present.

Replace or supplement the absolute external path with bundle-relative references (e.g. references/cookbook.md) inside the skill directory, so progressive disclosure works without environment assumptions.

Add a brief fallback or validation step (e.g. 'If that path does not exist, read references/README.md') so the workflow has a checkpoint instead of a single fragile delegation.

DimensionReasoningScore

Conciseness

The body is two lines — a generator comment and a single delegation instruction — with zero padding and no explanation of concepts Claude already knows. Every token present does work; this matches the 'lean and efficient, every token earns its place' anchor.

5 / 5

Actionability

The only guidance is 'Load and follow the shared skill at ~/.agents/skills/typesafe-ai/SKILL.md' — a single directive with a specific path, but no concrete steps, commands, or examples for the skill's actual task. This is minimal concrete guidance missing the specifics of execution; a 3 would require some substantive actionable content, and a 1 would mean even the directive were vague.

2 / 5

Workflow Clarity

There is a rough first step (load the external skill file) but the entire workflow beyond it is undefined in the body, with no sequence, checkpoints, or fallback if the external path is absent. The simple-skill exception does not apply because the skill's task domain (building AI features) is not single-step, so this sits at 'rough sequence present but many gaps' rather than 1 (the one instruction given is at least coherent and unambiguous).

2 / 5

Progressive Disclosure

The single reference is clearly signaled and one level deep, but the main file contains no overview content at all, and the reference points to an absolute home-directory path outside the skill bundle rather than to organized bundle files (no references/, scripts/, or assets/ exist). Structure exists only in a degenerate form — a pure redirect — which falls short of 'good structure' (4) but is not buried or nested (2).

3 / 5

Total

12

/

20

Passed

Description

83%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.

A strong description: third-person, concrete, and explicit about both what the skill does and when to use it, with specific application areas and named triggers. The only weaknesses are a slightly conceptual opening frame and a few missing natural synonyms in the trigger terms.

DimensionReasoningScore

Specificity

Lists several specific actions and application areas — 'turn natural language and application state into typed judgments and probabilities', 'routing, ranking, extraction, verification, and interactive experiences' — though the core framing ('units of AI intelligence you can use like programming primitives') stays conceptual, leaving minor gaps versus the comprehensive top anchor.

4 / 5

Completeness

Explicitly answers both questions: the 'what' ('turn natural language and application state into typed judgments and probabilities that code can combine') and a concrete 'Use when...' clause naming three trigger conditions. Matches the top anchor; a 4 would require the 'when' to be less explicit or specific, which it is not.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'routing', 'ranking', 'extraction', 'verification', 'brainstorming what AI could make possible in an app', 'prompt-and-parse step'. A few natural terms users would say are missing (e.g. 'classification', 'moderation', 'structured output', 'scoring'), so it falls just short of the comprehensive synonym coverage of the top anchor.

4 / 5

Distinctiveness Conflict Risk

Brand-specific vocabulary (TypeSafe, System One, Jev) and a distinct niche (typed LLM judgments as composable primitives) with targeted triggers minimize conflict. Minor overlap risk remains with general LLM-application-building skills due to the broad opening 'Build AI-powered software' and the brainstorming trigger.

4 / 5

Total

17

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

phatblat/dotfiles

Path

.claude/skills/typesafe-ai/SKILL.md

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.