CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

explicit-identity

Explicit Identity Across Boundaries

Quality

65%

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

Quality

Content

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

A tight, well-structured principle skill: it states the rule, gives concrete do/don't guidance with a precise ID taxonomy, and disambiguates with a BAD/GOOD example. Only minor gaps — an illustrative rather than executable code example and a low-value provenance section — keep it from full marks.

DimensionReasoningScore

Conciseness

The body is lean with zero over-explanation of known concepts ('Never rely on "latest" or "current" when crossing process or async boundaries', terse DO/DON'T bullets). The only minor trimmable content is the 'Source Sessions' provenance block, which adds tokens that do not instruct, keeping it just below anchor 5's 'every token earns its place'.

4 / 5

Actionability

Concrete, specific guidance throughout: 'Pass `--session-id $ID` when spawning processes', 'Use full UUIDs, not partial matches', a precise ID taxonomy (session_id / root_span_id / turn_span_id), and a BAD/GOOD code contrast. The example uses illustrative `spawn('analyzer', ...)` pseudocode rather than an executable API, so it falls short of anchor 5's copy-paste-ready bar.

4 / 5

Workflow Clarity

This is a simple, single-purpose behavioral rule and the single action is unambiguous: never query 'most recent' at execution time, always pass explicit IDs across boundaries, and keep ID types separate. The DO/DON'T lists plus the worked example leave no ambiguity about what to do, and no destructive/batch-operation validation cap applies.

5 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references, and is cleanly organized into Pattern / DO / DON'T / Example / Source Sessions sections. Per the simple-skill guideline, well-organized sections with no bundle dependencies merit the top score.

5 / 5

Total

18

/

20

Passed

Description

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

The description functions as a pattern title rather than a skill description: it names the domain but gives no actions, no usage triggers, and no natural keywords, so Claude would struggle to know when to load it. It is specific enough to avoid being generic filler, but well below the standard set by the good examples.

Suggestions

Add concrete actions in third person, e.g. 'Enforces passing explicit session and span IDs when spawning processes or awaiting async work; prevents wrong-session attribution from most-recent lookups.'

Add a 'Use when...' trigger clause with natural terms users would say, e.g. 'Use when spawning subprocesses, crossing await/async boundaries, correlating session IDs with trace span IDs, or debugging wrong-session attribution.'

Include the natural keywords users and Claude would actually encounter — 'session ID', 'root span ID', 'race condition', 'most recent session' — to improve trigger-term quality and distinguish the skill from auth/identity-management skills.

DimensionReasoningScore

Specificity

'Explicit Identity Across Boundaries' names a recognizable technical domain but contains no verbs or concrete actions — it reads as a title, matching anchor 2 ('Names the domain but actions are minimal or generic') rather than anchor 1 only because the domain itself is specific, not generic filler.

2 / 5

Completeness

There is no 'when' clause at all (which alone caps completeness at 3), and the 'what' is only an implied principle rather than a clear statement of what the skill does — matching anchor 2 ('Has a vague what and no when'). It falls below anchor 3, whose example lists concrete actions the skill performs.

2 / 5

Trigger Term Quality

The only keywords are the abstract concept words 'identity' and 'boundaries'; natural phrases a user would actually say — 'session ID', 'race condition', 'async', 'spawn', 'trace correlation' — are all absent. This matches anchor 2 ('one or two generic keywords; missing the natural phrases users say').

2 / 5

Distinctiveness Conflict Risk

The niche is fairly specific to ID propagation across process/async boundaries, but the bare word 'Identity' could plausibly collide with auth or identity-management skills, matching anchor 3 ('Somewhat specific but could still overlap with similar skills') rather than anchor 4's minimal-conflict bar.

3 / 5

Total

9

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

parcadei/Continuous-Claude-v3

Path

.claude/skills/explicit-identity/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.