CtrlK
BlogDocsLog inGet started
Tessl Logo

modulr

Modulr integration. Manage data, records, and automate workflows. Use when the user wants to interact with Modulr 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

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/modulr/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 body is a well-structured, command-rich integration guide with clear sequencing and connection-state validation. Its main weaknesses are minor redundancy, an undefined "Step 2" cross-reference, and reference-worthy material inlined in a single file.

DimensionReasoningScore

Conciseness

The body is mostly lean and command-driven with only minor over-explanation (e.g. "so you can focus on the integration logic rather than auth plumbing", "This will burn less tokens"), fitting the efficient-with-minor-trim anchor; it does not reach 5 due to light redundancy such as the repeated action-list command.

4 / 5

Actionability

It provides concrete, copy-paste-ready commands for install, login, connection, action search/run, and proxy with a flag table, covering common cases; minor gaps (generic "/path/to/endpoint" and undefined "Step 2" reference) keep it just below fully executable 5.

4 / 5

Workflow Clarity

There is a clear install→login→connect→poll→search→run sequence with validation checkpoints via connection states (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop; the dangling "Step 2" reference and absence of an explicit final verification step are minor gaps that hold it at 4.

4 / 5

Progressive Disclosure

The skill is a single, well-organized file with clear section hierarchy and no nested references; since no bundle files exist and there is nothing to navigate, it scores well-organized, but reference-like material (the proxy flag table, clientAction spec) could be split out, keeping it below 5.

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 successfully states both what the skill does and when to use it, anchored by the distinct Modulr brand trigger. Its weakness is generic action phrasing ("manage data", "automate workflows") and a thin set of natural trigger keywords.

Suggestions

Replace generic verbs with concrete Modulr actions, e.g. "create and reconcile payments, manage accounts and transactions, pull merchant invoices".

Expand the Use-when clause with concrete user phrases such as "when the user mentions Modulr payments, account transactions, or merchant invoices".

Add a natural keyword variation or two (e.g. "payments", "reconciliation") to broaden trigger coverage.

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the Modulr domain plus a couple of actions (manage records, automate workflows), matching the anchor for 1-2 concrete actions that are not comprehensive; the actions are fairly generic so it does not reach 4.

3 / 5

Completeness

It answers both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Modulr data"), but the when clause is somewhat generic rather than listing concrete trigger phrases, matching the 4 anchor.

4 / 5

Trigger Term Quality

Keywords present are "Modulr", "data", "records", and "workflows" — relevant but largely generic, missing common synonyms or variations, which fits the anchor of some relevant keywords with gaps.

3 / 5

Distinctiveness Conflict Risk

The brand trigger "Modulr" makes the skill clearly distinct from others with minimal conflict risk; the generic action phrasing keeps it just below the clear-niche 5 anchor.

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.