CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

identity

User identity, OAuth connections, and device management

43

Quality

54%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/identity/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 skill is a well-organized, mostly executable API reference for an identity service, with concrete commands and TypeScript examples. Its weaknesses are missing validation/confirmation for destructive operations and no progressive disclosure into reference files, leaving a long API surface inlined in SKILL.md.

Suggestions

Add explicit validation/confirmation checkpoints before destructive batch operations (revoke-all, unlink, endAllSessions) to lift workflow_clarity above 3.

Move the bulk CLI command listing and TypeScript API reference into reference files (e.g. references/commands.md, references/api.md) and link to them from SKILL.md to improve progressive disclosure.

Trim redundant inline commentary that restates what the code already shows to push conciseness toward 4-5.

DimensionReasoningScore

Conciseness

The body is mostly efficient command/code reference tables with little padding, but it duplicates concepts already implied by the code (e.g. naming each console.log field) and could be tightened; it sits between the efficient (4) and padded (2) anchors.

3 / 5

Actionability

Commands and TypeScript snippets are concrete and largely copy-paste ready, covering common cases (link, list, revoke, sessions); only minor gaps (no error-handling examples, a few placeholder values) keep it below 5.

4 / 5

Workflow Clarity

The OAuth link flow (getOAuthUrl -> handleOAuthCallback) is sequenced, but destructive/batch operations like 'revoke-all', 'unlink', and 'endAllSessions' have no validation or confirmation checkpoints, so the destructive-ops cap applies.

3 / 5

Progressive Disclosure

Content is organized into clear sections, but a large API reference (CLI commands, full TS API, and several lookup tables) is inlined entirely in SKILL.md with no references/ bundle files present to split it out.

3 / 5

Total

13

/

20

Passed

Description

31%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 correctly identifies the identity/OAuth/device domain but uses only noun-phrase enumeration with no concrete actions and no 'Use when...' trigger guidance. It is readable but below the bar set by the good examples, which pair specific verbs with explicit triggers.

Suggestions

Add concrete verbs, e.g. 'Link and unlink OAuth providers, list and revoke devices, and manage active sessions'.

Add an explicit trigger clause, e.g. 'Use when the user asks about login, OAuth linking, devices, or sessions.'

Add a third-person framing consistent with the good examples to lift specificity and trigger quality.

DimensionReasoningScore

Specificity

The phrase 'User identity, OAuth connections, and device management' names the domain and enumerates three subject areas but states no concrete actions (no verbs beyond the noun phrases), matching the anchor that 'actions are minimal or generic'.

2 / 5

Completeness

A 'what' is weakly present (the domain is named) but there is no 'when' or 'Use when...' trigger clause; the rubric caps completeness at 3 for a missing trigger clause, and here the 'what' is itself vague, placing it at 2.

2 / 5

Trigger Term Quality

It uses generic terms ('identity', 'OAuth connections', 'device management') but lacks the natural phrases a user would say ('login', 'sign in', 'link Google', 'log out', 'revoke device'), offering only a couple of broad keywords.

2 / 5

Distinctiveness Conflict Risk

'User identity, OAuth connections, and device management' is somewhat specific to an auth/identity niche but could overlap with general auth or security skills, matching 'somewhat specific but could still overlap'.

3 / 5

Total

9

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

alsk1992/CloddsBot

Path

src/skills/bundled/identity/SKILL.md

Revision

c930628

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill