CtrlK
BlogDocsLog inGet started
Tessl Logo

silverfin

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

65

Quality

79%

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/silverfin/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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 highly actionable with copy-paste CLI commands and a well-sequenced connection state machine, but it lacks validation guidance before destructive action runs and contains minor padding plus a dangling step reference.

Suggestions

Add a validation/verification checkpoint before running potentially destructive or batch Silverfin actions (e.g., dry-run, confirm-with-user, or check outputSchema before mutating accounting records) to lift the workflow_clarity cap.

Fix the dangling 'skip to Step 2' cross-reference — no section is labeled Step 2; either number the workflow steps explicitly or remove the reference.

Trim marketing-style prose in the opening paragraph ('provides real-time insights... streamline collaboration, reporting, and compliance') to improve token efficiency.

DimensionReasoningScore

Conciseness

Quotes lean, executable command blocks (e.g. 'membrane connection ensure "https://www.silverfin.com/" --json') with mostly useful API-state explanations, but the opening 'provides real-time insights... streamline collaboration, reporting, and compliance' is marketing-style padding that could be trimmed, fitting 'efficient; minor instances of over-explanation' rather than the fully-lean level 5.

4 / 5

Actionability

Quotes copy-paste-ready commands throughout — 'npm install -g @membranehq/cli@latest', 'membrane action run <actionId> --connectionId=... --input ...', and a full proxy flag table — covering the common cases with executable, specific examples matching the 'fully executable; copy-paste ready' anchor.

5 / 5

Workflow Clarity

Quotes a clear connect-and-poll sequence with feedback loops ('poll again... to check if the state moved to READY', 'Keep polling until state is no longer BUILDING'), but running arbitrary Silverfin actions on accounting data is a destructive/batch-capable operation with no pre-flight validation guidance, so per the destructive-operation cap workflow_clarity cannot exceed 3.

3 / 5

Progressive Disclosure

Quotes well-organized sections (## Working with Silverfin, ### Connecting, ## Popular actions, ## Best practices) in a single ~160-line file with no bundle files to reference; structure is good with minor organization gaps (the thin 'Popular actions' section repeats the discover command), fitting 'good structure; most content appropriately placed' rather than the clean one-level-reference level 5.

4 / 5

Total

16

/

20

Passed

Description

82%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 cleanly answers both what the skill does and when to use it, anchored on the distinct 'Silverfin' product name. Its only weakness is that the listed actions ('manage data, records, automate workflows') are generic rather than concrete.

DimensionReasoningScore

Specificity

Quotes 'Manage data, records, and automate workflows' and 'interact with Silverfin data' — it names the domain plus 2-3 actions, but the actions are generic ('manage', 'automate') rather than concrete like 'extract' or 'fill', matching the '1-2 concrete actions, not comprehensive' anchor and sitting below the 'several specific actions' level 4.

3 / 5

Completeness

Quotes an explicit what ('Silverfin integration. Manage data, records, and automate workflows.') and an explicit when ('Use when the user wants to interact with Silverfin data.') with a concrete trigger phrase, matching the 'clearly and explicitly answers both what AND when' anchor.

5 / 5

Trigger Term Quality

Quotes 'Silverfin', 'Silverfin data', 'data', 'records', 'workflows' — for a niche proprietary product the name 'Silverfin' is the natural user trigger and is well-captured with a few supporting terms, fitting 'good keyword coverage; a few natural terms missing' rather than the comprehensive-synonym level 5.

4 / 5

Distinctiveness Conflict Risk

Quotes the product-specific trigger 'Silverfin' — a named SaaS niche with distinct triggers and minimal overlap risk with other skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.

5 / 5

Total

17

/

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.