CtrlK
BlogDocsLog inGet started
Tessl Logo

fena

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

60

Quality

70%

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/fena/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 delivers concrete, executable Membrane CLI guidance with a clear connection workflow and well-organized sections; it would benefit from tighter prose and a couple of explicit verification steps.

Suggestions

Trim explanatory prose like "This skill uses the Membrane CLI to interact with Fena. Membrane handles authentication and credentials refresh automatically" to the essential facts.

Add an explicit verification step after running actions, e.g. checking the `output` field or status before proceeding.

Flesh out the Overview section's action tree or remove the placeholder line "Use action names and parameters as needed."

DimensionReasoningScore

Conciseness

The body is mostly efficient with executable commands and little padding, though sentences like "This skill uses the Membrane CLI to interact with Fena" and the thin Overview tree could be trimmed slightly.

4 / 5

Actionability

Concrete `membrane` commands with flags and JSON examples are given throughout for install, auth, connection, search, and proxying, with only minor placeholder gaps (e.g. CONNECTION_ID usage).

4 / 5

Workflow Clarity

The connection flow has a clear sequence with explicit state handling (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a retry-after-action loop, though output validation checkpoints are not emphasized.

4 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections with no nested references and no unnecessary external files, matching a good single-file structure appropriate for this skill's scope.

4 / 5

Total

16

/

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 the skill does and when to use it, anchored to a distinct named product, but its action vocabulary is generic and it lacks richer natural trigger terms.

Suggestions

Replace generic verbs like "Manage data" and "automate workflows" with concrete Fena actions such as tracking income, expenses, and invoices.

Broaden trigger terms to include natural phrases users would say, e.g. "income", "expenses", "invoices", or "financial records".

Make the "when" clause more specific, e.g. "Use when the user wants to manage income, expenses, or invoices in Fena."

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the domain and a couple of actions, but "manage data" and "automate workflows" are generic rather than comprehensive concrete capabilities.

3 / 5

Completeness

Both a "what" (manage data, records, automate workflows) and an explicit "when" ("Use when the user wants to interact with Fena data") are present, though the trigger is somewhat generic rather than fully concrete.

4 / 5

Trigger Term Quality

"Use when the user wants to interact with Fena data" provides a trigger clause, but the keywords are limited to "Fena data" with no natural synonyms like income, expenses, or invoices.

3 / 5

Distinctiveness Conflict Risk

Tied to a named product (Fena) with an explicit Fena trigger, giving it a clear niche with minimal overlap risk against other 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.