CtrlK
BlogDocsLog inGet started
Tessl Logo

setup

Verify Daloopa MCP connection and show available skills

54

Quality

60%

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 ./plugins/daloopa/skills/setup/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%

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

The content is a well-sequenced setup walkthrough with a genuine validation and error-recovery loop in Step 2, and it is appropriately organized for a short, reference-free skill. Its weaker spots are mild conversational padding and guidance that tells the model how to narrate rather than giving fully executable steps.

Suggestions

Tighten conversational framing by dropping 'Be conversational and helpful' and converting 'Explain that this skill checks whether...' into a direct instruction, reducing token overhead.

Make the verification step more copy-paste ready by showing the exact discover_companies invocation form expected (e.g. the parameter name and an example payload) rather than only naming the tool and ticker.

For Step 3, briefly state what each example skill actually produces (e.g. 'tearsheet -> saved to reports/tearsheet_AAPL.*') so the guidance is actionable rather than just illustrative prompts.

DimensionReasoningScore

Conciseness

The body is mostly lean and avoids explaining concepts Claude already knows, but conversational framing like 'Be conversational and helpful' and 'Explain that this skill checks whether...' could be tightened, placing it at 'mostly efficient but could be tightened' rather than fully lean.

2 / 3

Actionability

It gives a concrete test (call discover_companies with 'AAPL') and example utterances, but much of the guidance is phrased as 'tell/explain to the user' rather than direct executable steps, and the reporting skills themselves are only illustrated by example prompts, leaving it incomplete rather than copy-paste ready.

2 / 3

Workflow Clarity

The four steps are clearly sequenced, and Step 2 includes an explicit validation checkpoint (the discover_companies test) plus a 'If this fails' feedback loop with concrete recovery actions, matching the clear-sequence-with-validation-and-error-recovery anchor.

3 / 3

Progressive Disclosure

The skill is under 50 lines, needs no external references (none exist), and is organized into clearly labeled Step 1-4 sections, which per the scoring notes lets progressive disclosure score 3 on well-organized sections alone.

3 / 3

Total

10

/

12

Passed

Description

50%

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 concrete domain and a couple of actions, but it lacks any explicit 'when to use' trigger and leans on technical jargon ('MCP connection') over natural user phrasings. Its most impactful gap is the missing trigger guidance, which caps completeness.

Suggestions

Add an explicit 'Use when ...' clause, e.g. 'Use when setting up or troubleshooting the Daloopa MCP connection, or when the user wants to see available Daloopa analysis skills.'

Replace technical phrasing with natural user terms users would actually say, such as 'Daloopa data', 'financial data tools', 'Daloopa setup', or 'connect Daloopa'.

Broaden the action list beyond 'show available skills' to concrete capabilities like 'confirm the Daloopa data and docs MCP servers are reachable' to strengthen specificity and distinctiveness.

DimensionReasoningScore

Specificity

The description names a specific domain ('Daloopa MCP connection') and two actions ('Verify ... and show available skills'), but 'show available skills' is generic and the action set is not comprehensive, fitting the score-2 anchor rather than the multi-action score-3 anchor.

2 / 3

Completeness

It clearly states what the skill does, but provides no 'Use when...' clause or equivalent trigger for when Claude should invoke it; per the judging guidelines a missing explicit trigger caps completeness at 2.

2 / 3

Trigger Term Quality

'Daloopa' is a relevant brand keyword a user might say, but 'MCP connection' is technical jargon and there are no natural user phrasings or common variations, so it sits at 'some relevant keywords but missing common variations' rather than full coverage.

2 / 3

Distinctiveness Conflict Risk

The Daloopa niche is fairly distinct, but the generic 'show available skills' portion could overlap with other onboarding or skill-touring skills, leaving it at 'somewhat specific but could still overlap' rather than a clearly unconflicting niche.

2 / 3

Total

8

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/plugins
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.