CtrlK
BlogDocsLog inGet started
Tessl Logo

seekwell

SeekWell integration. Manage data, records, and automate workflows. Use when the user wants to interact with SeekWell data.

59

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/seekwell/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 an actionable, well-structured CLI integration guide with concrete commands and a genuine connection-readiness feedback loop, held back only by minor filler, a dangling step reference, and a 'Popular actions' section that does not actually list actions.

Suggestions

Resolve the dangling 'skip to Step 2' reference by explicitly labeling the searching/running sections as numbered steps, and fix the '1b' that lacks a '1a'.

Make 'Popular actions' list concrete example actions (e.g. run-query, list-records, refresh-schedule) instead of repeating the discovery command.

Trim filler like 'Use action names and parameters as needed.' and tighten the prose around connection states to improve token efficiency.

DimensionReasoningScore

Conciseness

The body is mostly commands and CLI usage with little padding, though filler lines like 'Use action names and parameters as needed.' and some prose could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready commands throughout (install, login, connection ensure, action run, proxy flags table); minor gaps include the 'Popular actions' section restating discovery rather than listing actual actions.

4 / 5

Workflow Clarity

Clear install-authenticate-connect-search-run sequence with a real poll-state feedback loop for connection readiness, but references to 'Step 2' and a '1b' without a labeled '1a' show minor sequencing gaps.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with no need for external reference files for this CLI integration skill; not a 5 because a few dense blocks (proxy flags, connection states) could be split out.

4 / 5

Total

16

/

20

Passed

Description

62%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 answers both what and when with an explicit 'Use when' trigger and a clearly named product, but relies on generic action verbs and misses the natural SQL/query/visualization terms users would say.

Suggestions

Replace generic verbs with concrete SeekWell capabilities, e.g. 'Write and run SQL queries, visualize results, and schedule data refreshes'.

Add natural trigger synonyms users actually say, such as 'query SeekWell data', 'SQL', 'charts', or 'dashboards'.

Tighten the 'when' clause to mention specific intents like analyzing data or building visualizations rather than only 'interact with SeekWell data'.

DimensionReasoningScore

Specificity

Names the SeekWell domain and lists several actions ('Manage data, records, and automate workflows'), but the verbs are generic ('manage', 'automate') rather than concrete operations like query or visualize.

3 / 5

Completeness

Explicitly states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with SeekWell data'), but the 'what' could be more concrete to reach a 5.

4 / 5

Trigger Term Quality

Includes relevant keywords (SeekWell, data, records, workflows, 'interact with SeekWell data') but omits the most natural user phrases such as SQL, query, visualize, or charts that the body itself emphasizes.

3 / 5

Distinctiveness Conflict Risk

The named app 'SeekWell' and trigger 'interact with SeekWell data' create a clear niche with minimal conflict risk, though the generic 'manage data, records' phrasing leaves minor overlap with other data skills.

4 / 5

Total

14

/

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.

Validation15 / 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
membranedev/application-skills
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.