identity

User identity, OAuth connections, and device management

Quality

51%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./src/skills/bundled/identity/SKILL.md

Quality

Discovery

22%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is too terse and noun-heavy, lacking actionable verbs and explicit usage triggers. While it identifies a domain (identity/OAuth/devices), it fails to explain what specific operations the skill performs or when Claude should select it. The description would benefit significantly from concrete action verbs and a 'Use when...' clause.

Suggestions

Add specific action verbs describing what the skill does, e.g., 'Authenticate users, manage OAuth token connections, list and revoke device sessions'

Include a 'Use when...' clause with natural trigger phrases like 'Use when the user asks about login, connected apps, active sessions, or account security'

Add common user-facing synonyms like 'login', 'sign in', 'connected accounts', 'active sessions' to improve trigger term coverage

Dimension	Reasoning	Score
Specificity	The description uses abstract nouns ('identity', 'connections', 'management') without any concrete actions. It doesn't specify what operations can be performed - no verbs like 'authenticate', 'connect', 'list', or 'revoke'.	1 / 3
Completeness	Only vaguely addresses 'what' through domain nouns, and completely lacks any 'when' guidance. No 'Use when...' clause or equivalent trigger guidance is present.	1 / 3
Trigger Term Quality	Contains some relevant technical terms ('OAuth', 'device management') that users might mention, but lacks common variations and natural phrases users would say like 'login', 'sign in', 'connected apps', 'sessions', or 'account settings'.	2 / 3
Distinctiveness Conflict Risk	'OAuth' and 'device management' provide some specificity that distinguishes it from generic skills, but 'user identity' is broad and could overlap with profile management, authentication, or security-related skills.	2 / 3
	Total	6 / 12 Passed

Implementation

79%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured API reference that excels in conciseness and actionability with clean, executable code examples. However, it lacks validation checkpoints for destructive operations (device revocation, session termination) and could benefit from splitting the detailed API reference into a separate file with the main skill providing an overview.

Suggestions

Add error handling examples and validation steps for OAuth callback handling (e.g., what to do if state mismatch or code is invalid)

Include confirmation or recovery guidance for destructive operations like revokeAllDevices and endAllSessions

Consider splitting the detailed TypeScript API reference into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with links

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, presenting API reference material without explaining concepts Claude already knows. Every section serves a purpose with no padding or unnecessary context.	3 / 3
Actionability	Provides fully executable TypeScript code examples that are copy-paste ready, with concrete method signatures, configuration objects, and usage patterns. Chat commands are also specific and complete.	3 / 3
Workflow Clarity	The OAuth flow shows a clear sequence (generate URL → handle callback), but lacks validation checkpoints or error handling guidance. Device revocation operations are destructive but have no confirmation or recovery steps mentioned.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections and tables, but this is a monolithic reference file with no links to separate detailed documentation. The API reference could be split from the chat commands overview.	2 / 3
	Total	10 / 12 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: alsk1992/CloddsBot
Commit: 2a8c94e

Reviewed: 28 days ago

Table of Contents

Discovery Implementation Validation

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.