CtrlK
BlogDocsLog inGet started
Tessl Logo

integrations

External data sources, connectors, and custom data streams

56

Quality

39%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./src/skills/bundled/integrations/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

0%

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 critically underdeveloped across all dimensions. It reads as a category label rather than a functional skill description, providing no concrete actions, no trigger guidance, and no distinguishing characteristics that would help Claude select it appropriately from a skill library.

Suggestions

Add specific concrete actions: e.g., 'Connect to REST APIs, query databases, import CSV/JSON files, configure OAuth authentication'

Include an explicit 'Use when...' clause with natural trigger terms: e.g., 'Use when the user mentions API integration, database connection, importing external data, webhooks, or data pipelines'

Narrow the scope to a distinct niche or enumerate specific supported connectors/sources to reduce conflict with other data-related skills

DimensionReasoningScore

Specificity

The description uses vague, abstract language ('external data sources', 'connectors', 'custom data streams') without listing any concrete actions. It doesn't specify what Claude actually does with these things.

1 / 3

Completeness

The description only vaguely hints at 'what' (something about data sources) and completely lacks any 'when' guidance. There is no 'Use when...' clause or equivalent trigger guidance.

1 / 3

Trigger Term Quality

The terms used are technical jargon ('connectors', 'data streams') that users are unlikely to naturally say. Missing common variations like 'API', 'database', 'import data', or specific connector types.

1 / 3

Distinctiveness Conflict Risk

Extremely generic - 'data sources' and 'connectors' could overlap with database skills, API skills, file import skills, ETL skills, and many others. No clear niche is established.

1 / 3

Total

4

/

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 strong API reference skill with excellent actionability and conciseness. The code examples are complete and executable, and the content respects Claude's intelligence. However, it lacks explicit validation workflows for custom source setup and could benefit from progressive disclosure by splitting into multiple focused documents.

Suggestions

Add explicit validation workflow for custom sources: test connection -> verify data schema -> monitor initial fetches -> handle errors before going live

Split into separate files: SKILL.md (overview + quick start), SOURCES.md (built-in source details), CUSTOM.md (webhook/REST/WebSocket setup), EXAMPLES.md (bot integration patterns)

DimensionReasoningScore

Conciseness

The content is lean and efficient, presenting API references and code examples without unnecessary explanation. It assumes Claude understands TypeScript, APIs, and trading concepts without over-explaining.

3 / 3

Actionability

Provides fully executable TypeScript code examples that are copy-paste ready, concrete chat commands, and specific configuration options. Every section includes working code or exact command syntax.

3 / 3

Workflow Clarity

While individual operations are clear, there's no explicit validation workflow for adding custom sources (test connection, verify data format, handle failures). The 'Best Practices' section mentions error handling but doesn't provide a concrete validation sequence.

2 / 3

Progressive Disclosure

Content is well-organized with clear sections, but it's a monolithic document that could benefit from splitting detailed API reference, built-in sources documentation, and bot integration examples into separate files with clear navigation links.

2 / 3

Total

10

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
alsk1992/CloddsBot
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.