CtrlK
BlogDocsLog inGet started
Tessl Logo

hokodo

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

64

Quality

78%

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/hokodo/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 a strongly actionable, well-structured CLI integration guide with executable commands and a clear connection-state feedback loop. Its weaknesses are minor verbosity and an undefined "Step 2" reference that slightly muddies the workflow.

Suggestions

Define or relabel the "Step 2" target referenced in the connection flow so the sequence is unambiguous.

Trim editorial asides like "so you can focus on the integration logic rather than auth plumbing" to tighten token efficiency.

Consider splitting the proxy request options table and action-reference detail into a reference file to lift progressive disclosure toward 5.

DimensionReasoningScore

Conciseness

The body is mostly efficient with copy-pasteable commands and a useful flag table, but includes minor over-explanation such as "so you can focus on the integration logic rather than auth plumbing" and the slightly redundant "Popular actions" discovery line; it is leaner than a 3 but not the every-token-earns-its-place level of a 5.

4 / 5

Actionability

It provides fully executable, copy-paste-ready membrane commands for install, login, connection ensure/get, action list/run, and proxy requests with a concrete options table covering the common cases.

5 / 5

Workflow Clarity

The connect-then-poll-then-act sequence has an explicit feedback loop (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll), but the "skip to Step 2" reference points to an undefined target and there is no pre-flight validation before running actions, so it stops at 4 rather than 5.

4 / 5

Progressive Disclosure

The skill is a single self-contained file with well-organized section headers and no nested or buried references; since it runs slightly longer than the under-50-line simple-skill case and could split the proxy/action reference detail out, it lands at 4 rather than 5.

4 / 5

Total

17

/

20

Passed

Description

73%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 well-formed with a clear third-person voice, an explicit Use-when trigger, and a highly distinct brand niche. Its main weakness is generic action language ("manage data, records") rather than naming Hokodo's concrete capabilities.

Suggestions

Replace generic verbs with concrete Hokodo capabilities, e.g. 'Create credit applications, manage credit lines, and fetch invoices' to lift specificity.

Add a few natural synonyms/related terms (credit, BNPL, pay-later, invoices) to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

It names the Hokodo domain and lists a few actions ("Manage data, records, and automate workflows"), but the actions are generic verbs rather than concrete capabilities like 'create credit applications' or 'fetch invoices', so it sits at the 3-anchor and not the more concrete 4.

3 / 5

Completeness

It states both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Hokodo data"), but the 'what' is generic so it does not reach the concrete-trigger-phrases level of a 5.

4 / 5

Trigger Term Quality

The natural term a user would say ("Hokodo", "Hokodo data") appears in an explicit "Use when... interact with Hokodo data" trigger, giving good keyword coverage for a niche brand; it falls short of 5 only because no synonyms or related product terms (credit, BNPL, invoices) are included.

4 / 5

Distinctiveness Conflict Risk

The Hokodo brand name is a distinct niche trigger that would not fire for unrelated skills, matching the clear-niche anchor with minimal conflict risk.

5 / 5

Total

16

/

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.