credentials

Secure credential management for trading platforms

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/credentials/SKILL.md

Quality

Content

65%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 content is highly actionable with complete executable examples, but it inlines a full API reference that belongs in a separate file and omits validation checkpoints around its destructive credential operations.

Suggestions

Move the bulk TypeScript API reference and platform table into a REFERENCE.md and keep SKILL.md as an overview with one-level-deep links.

Add an explicit validation checkpoint after add/set (e.g. always run /creds test or testCredentials and only proceed on success) before destructive or batch operations.

Trim fluff ("Military-grade encryption") and de-duplicate near-identical chat commands (/creds test vs /creds check).

Dimension	Reasoning	Score
Conciseness	The body is code-dense and assumes competence, but the full TypeScript API reference is inlined (~250 lines) with minor fluff ("Military-grade encryption") and redundant chat commands (/creds test vs /creds check).	3 / 5
Actionability	Fully executable, copy-paste-ready TypeScript examples and concrete chat commands cover the common cases across set/get/delete/test/cooldown/context for multiple platforms.	5 / 5
Workflow Clarity	Destructive operations ("/creds clear", deleteCredentials, deleteAllCredentials) lack validation checkpoints in a sequenced workflow, so workflow_clarity is capped at 3 per the destructive-operations guideline.	3 / 5
Progressive Disclosure	Section headers provide structure, but the bulk API reference is inlined in SKILL.md with no separate reference files, and at >50 lines it does not qualify for the simple-skill exception.	3 / 5
	Total	14 / 20 Passed

Description

41%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 is concise and names a distinct niche, but it lacks concrete actions, natural trigger terms, and any explicit "when to use" guidance.

Suggestions

Add concrete actions, e.g. "Store, encrypt, and rotate API keys and wallet keys for trading platforms".

Include a "Use when..." clause naming natural triggers like API keys, secrets, or specific platforms (Polymarket, Kalshi, Binance).

Add file/extension-style synonyms (e.g. "API credentials", "wallet keys") to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	"Secure credential management for trading platforms" names the domain but uses the generic action "management" rather than concrete operations like store, encrypt, rotate, or revoke.	2 / 5
Completeness	The "what" (secure credential management) is clear, but there is no "Use when..." trigger clause, capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Only "credential" and "trading platforms" appear; the natural phrases users say ("API keys", "secrets", platform names like Polymarket/Kalshi/Binance) are absent.	2 / 5
Distinctiveness Conflict Risk	The "trading platforms" qualifier carves a mostly-distinct niche with only minor overlap risk against generic credential skills.	4 / 5
	Total	11 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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/credentials/SKILL.md
Commit: 715fd4a

Reviewed: 4 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.