CtrlK
BlogDocsLog inGet started
Tessl Logo

nulab

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

58

Quality

68%

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 ./skills/nulab/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 a well-structured, actionable integration guide with executable commands and meaningful validation checkpoints for the connection lifecycle. Its main weaknesses are minor redundancy in the actions section and slightly awkward step numbering rather than substantive gaps.

DimensionReasoningScore

Conciseness

The body is largely efficient with concrete commands and avoids explaining concepts Claude already knows, though the "Popular actions" section repeats the action-list command already shown under "Searching for actions", a minor redundancy that could be trimmed.

4 / 5

Actionability

It provides mostly executable, copy-paste-ready commands (login, connection ensure, action run, request with documented flags), with only minor gaps such as unresolved CONNECTION_ID placeholders and a slightly inconsistent step numbering.

4 / 5

Workflow Clarity

The connect-to-run workflow has a clear sequence with validation checkpoints (polling BUILDING state, READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR branches), though the "Step 2" forward reference and "1b" sub-labeling create a minor sequencing ambiguity.

4 / 5

Progressive Disclosure

No bundle files exist, so the single self-contained SKILL.md is organized into clear, well-signaled sections (install, auth, connecting, searching, running, proxy, best practices) with no nested references, which is good structure with only minor organization gaps.

4 / 5

Total

16

/

20

Passed

Description

61%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 clearly distinct thanks to the named Nulab product and includes an explicit "Use when" trigger, but its capability list is generic ("manage data, records") rather than concrete Nulab-specific actions. Tightening the action list to reference projects, issues, or records would raise specificity and trigger quality.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Nulab operations such as "manage projects, issues, and records" to improve specificity.

Add natural trigger variations users would say, e.g. "Use when working with Backlog issues, Cacoo diagrams, or Typetalk messages" to broaden keyword coverage.

Keep the third-person voice and explicit "Use when" clause, which already anchor the completeness and distinctiveness dimensions.

DimensionReasoningScore

Specificity

The description names the domain ("Nulab integration") but its actions are generic — "Manage data, records, and automate workflows" — rather than concrete Nulab-specific operations like issues or projects, fitting the anchor where the domain is named but actions are minimal or generic.

2 / 5

Completeness

It answers both "what" (manage data, records, automate workflows) and "when" ("Use when the user wants to interact with Nulab data") with an explicit trigger clause, though the "when" could be more specific about Nulab use cases.

4 / 5

Trigger Term Quality

It includes the relevant keyword "Nulab" and an explicit trigger phrase ("Use when the user wants to interact with Nulab data"), but it misses common natural variations such as project management, issues, or tasks that a user would actually say.

3 / 5

Distinctiveness Conflict Risk

"Nulab integration" names a specific product, creating a clear niche with distinct triggers and minimal risk of firing for unrelated skills.

5 / 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.