CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

distilly

Set up the owner profile so a personal agent knows who it works for (first-run setup, "get to know me"), or distill colleague, relationship, or celebrity source material into reusable Person Profiles for agents.

Quality

74%

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 ./SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary router-style SKILL.md: minimal, well-structured, with exact paths and deferred loading of flow files. The only meaningful weakness is that destructive routes (delete/rollback of generated skills) carry no validation or safety checkpoint in the body, capping workflow clarity.

Suggestions

Add a one-line validation rule for destructive manage operations, e.g. 'Before deleting or rolling back a generated skill, list the affected directory and confirm with the user.'

Include one fully resolved example invocation of tools/owner_profile.py (with a real path) to close the actionability gap for hosts without ${CLAUDE_SKILL_DIR}.

Trim the 'Skill Root' block by merging its three redundant negative instructions into one sentence to tighten token efficiency.

DimensionReasoningScore

Conciseness

The ~30-line body is lean and assumes Claude's competence: a routing table, three storage/write/credential rules, and host invocation details, with no explanation of concepts Claude already knows. The 'Skill Root' block slightly over-explains ("Do not assume the shell's current working directory... do not guess or hard-code an install path" repeats the same point), matching anchor 4 rather than the every-token-earns-its-place ideal of 5.

4 / 5

Actionability

Guidance is concrete: exact flow-file paths per request type, an executable command template (`python3 "{distilly_skill_root}/tools/owner_profile.py"`), specific flags (`--base-dir`, `--setup`, `--login`), and exact storage paths. It is an instruction-only router, so absent code is not penalized, but there are minor gaps (no worked example of a resolved command or output), fitting anchor 4 rather than the fully copy-paste-ready coverage of 5.

4 / 5

Workflow Clarity

The routing sequence is clear and unambiguous (request → matching flow file → follow it), but no validation checkpoints appear anywhere. The manage flow routes "roll back or delete a generated skill" — a destructive operation — with no verification step visible; per the rubric guideline this caps workflow clarity at 3 even though routing itself is crisp.

3 / 5

Progressive Disclosure

Textbook progressive disclosure: the body is a pure overview with a routing table to one-level-deep flow files (`prompts/flows/owner.md`, `create.md`, `evolve.md`, `manage.md`, `sources.md`, `celebrity_research.md`), each clearly signaled, with explicit deferred loading ("read those when the flow gets there, not up front"). No bundle files exist in references/scripts/assets to verify, but the structure as written matches anchor 5 exactly; it is not anchor 4 because there is no organization gap in the overview itself.

5 / 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.

A clear, concise third-person description that names both core functions and several natural trigger phrases, with a distinctive niche. Its main weakness is the absence of an explicit "Use when..." clause, leaving the "when" side only weakly implied and capping completeness.

Suggestions

Add an explicit 'Use when...' clause listing concrete triggers, e.g. 'Use when the user says "get to know me", wants to distill themselves or a colleague/friend/celebrity into an agent profile, or on first run with no owner profile.'

Include common user phrasings from the routing table ("create a skill for XX", "distill myself", "I have new files") as trigger terms to improve keyword coverage.

Clarify the output artifact early ("generates a reusable skill under ./skills/...") so the what explicitly states the deliverable, not just the activity.

DimensionReasoningScore

Specificity

The description names concrete actions — "Set up the owner profile", "distill colleague, relationship, or celebrity source material into reusable Person Profiles" — covering both of the skill's functions with only minor gaps. It sits between anchor 3 (1-2 concrete actions, not comprehensive) and anchor 5 (fully comprehensive action list), so 4 fits best.

4 / 5

Completeness

The "what" is clear (owner-profile setup; distilling source material into Person Profiles), but there is no "Use when..." clause; the parenthetical "(first-run setup, \"get to know me\")" only weakly implies timing and covers just one of the two functions. Per the judging guideline, a missing explicit trigger clause caps completeness at 3, and anchor 3 (clear what, when weakly implied) is the best fit.

3 / 5

Trigger Term Quality

Includes natural user phrases such as "get to know me", "first-run setup", "distill", and "colleague, relationship, or celebrity", which users would plausibly say. A few common variations (e.g. "create a skill", "who am I", "make a skill for someone") are missing, matching anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The niche — turning colleague/relationship/celebrity source material into "reusable Person Profiles for agents" — is distinctive with minimal conflict risk against typical skills. Generic trigger words like "set up my profile" could overlap with profile/configuration skills, so anchor 4 (mostly distinct, minor overlap risk) fits better than anchor 5.

4 / 5

Total

15

/

20

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

titanwings/distilly

Path

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.