CtrlK
BlogDocsLog inGet started
Tessl Logo

funding-options

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

57

Quality

66%

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/funding-options/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 highly actionable, well-structured CLI integration guide with strong command coverage and a clear connection workflow including state-based feedback loops, slightly held back by minor redundancy and a brief concept-explanation intro.

DimensionReasoningScore

Conciseness

Most of the body is efficient concrete CLI commands, but the introductory paragraph explaining what Funding Options is, the redundant 'Popular actions' section that repeats the action-list command, and filler like 'Use action names and parameters as needed' are unnecessary explanation that could be trimmed.

3 / 5

Actionability

It provides fully executable, copy-paste-ready commands for every common case — install, login, connection ensure, state polling, action list, action run with JSON input, and proxy requests with a complete flag table — covering the integration workflow comprehensively.

5 / 5

Workflow Clarity

The connect-to-ready flow is clearly sequenced with explicit state-based validation checkpoints and feedback loops ('poll again', 'keep polling until state is no longer BUILDING'), but the action-running and proxy steps lack any verification of their results, leaving a minor validation gap.

4 / 5

Progressive Disclosure

The single self-contained file is well-organized with clear section headers and no broken or deeply nested references; keeping everything inline is appropriate for a runtime-discovery CLI skill, though it offers no one-level-deep references to warrant a 5.

4 / 5

Total

16

/

20

Passed

Description

57%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 functional with an explicit 'Use when' trigger and a clearly named platform, but its capability description relies on generic verbs ('manage', 'automate') rather than concrete Funding Options actions, limiting specificity and trigger coverage.

Suggestions

Replace generic verbs with concrete Funding Options actions, e.g. 'Search and compare funding options, retrieve option details, and run financing calculations'.

Add natural synonyms users say — 'loans, lines of credit, business financing, funding options' — to the trigger clause.

Tighten the 'what' to list 2-3 specific operations so the description reads as Funding Options-specific rather than templated boilerplate.

DimensionReasoningScore

Specificity

The description names the domain ('Funding Options integration') but its actions are generic — 'Manage data, records, and automate workflows' uses abstract verbs rather than concrete operations like compare, calculate, or retrieve, matching the 'names the domain but actions are minimal or generic' anchor.

2 / 5

Completeness

Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Funding Options data') are present; the when clause is explicit so it clears the missing-trigger cap, but the what is too generic to reach a 5.

4 / 5

Trigger Term Quality

It includes the relevant platform keyword and the natural phrase 'interact with Funding Options data', but misses common synonyms and variations users would say such as financing, loans, lines of credit, or business funding, fitting 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

The named platform 'Funding Options' and its data-specific trigger make it mostly distinct with minimal conflict risk, though the boilerplate 'Manage data, records, and automate workflows' phrasing could overlap with sibling Membrane integration skills.

4 / 5

Total

13

/

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.