CtrlK
BlogDocsLog inGet started
Tessl Logo

deftship

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

62

Quality

74%

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/deftship/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 body is highly actionable and well structured with concrete commands and a clear state-driven connection workflow, held back only by minor padding in the intro and a couple of inconsistent step references.

DimensionReasoningScore

Conciseness

The body is mostly efficient with copy-paste commands and a tight flags table, but the opening platform description ("Deftship is a shipping management platform that helps businesses streamline...") and phrases like "so you can focus on the integration logic rather than auth plumbing" are mild over-explanation Claude does not need.

4 / 5

Actionability

It provides fully executable, copy-paste-ready commands for every phase (install, login, connection ensure, action list/run, request proxy) with clearly marked placeholders and a flags table covering the common cases.

5 / 5

Workflow Clarity

The connection flow has a clear state-driven sequence with explicit checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop, but the dangling "skip to Step 2" reference and the "1b" heading with no "1a" or labeled "Step 2" are navigation gaps.

4 / 5

Progressive Disclosure

The single ~140-line file is well organized into clearly headed sections with no nested references, though all content (including the detailed connection-state machine and proxy flags table) is inline with no separate reference files for the deeper material.

4 / 5

Total

17

/

20

Passed

Description

66%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 and is highly distinct thanks to the Deftship proper noun, but its action language and trigger vocabulary are generic, limiting specificity and trigger-term quality.

Suggestions

Replace generic verbs ("manage data, records, automate workflows") with concrete Deftship capabilities such as creating shipments, tracking packages, generating quotes, and managing an address book.

Expand the trigger clause with natural user phrases, e.g. "Use when the user wants to create or track shipments, get shipping quotes, or manage Deftship address book entries."

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the Deftship domain with a couple of actions, but the verbs (manage, automate) and nouns (data, records) stay generic rather than listing concrete capabilities like order tracking or shipment creation.

3 / 5

Completeness

Both a "what" (Deftship integration managing data/records and automating workflows) and an explicit "when" ("Use when the user wants to interact with Deftship data") are present, though the "when" could name more concrete triggers.

4 / 5

Trigger Term Quality

The trigger "Use when the user wants to interact with Deftship data" surfaces the core keyword but offers no natural synonyms or variations users might actually say (e.g. shipments, quotes, address book, tracking).

3 / 5

Distinctiveness Conflict Risk

The proper noun "Deftship" plus "Deftship data" gives it a clear, distinct niche with minimal risk of triggering for unrelated skills.

5 / 5

Total

15

/

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.