Name: financialforce
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

financialforce

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

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/financialforce/SKILL.md

Quality

Content

61%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 well-structured and highly actionable with concrete executable CLI commands and a strong connection-state feedback loop, but it pads the context with a trivial Dimension 1-20 list and background Claude already knows, and lacks validation checkpoints before destructive action runs or proxy writes. Conciseness and workflow clarity are the weakest dimensions.

Suggestions

Collapse the 'Dimension 1' to 'Dimension 20' bullets into a single line (e.g., 'Dimension 1-20') and trim the ERP/NetSuite intro paragraph that Claude already knows.

Add a validation checkpoint before mutating actions or proxy POST/PUT/DELETE calls (e.g., confirm non-destructive intent or list-then-run) so destructive/batch operations have a feedback loop.

Include one fully worked end-to-end example with real connection id, action id, and --input JSON to bridge the placeholder commands into a copy-paste-ready flow.

Dimension	Reasoning	Score
Conciseness	The CLI command sections are lean and efficient, but the inlined 'Dimension 1' through 'Dimension 20' list (20 near-identical bullets) and the ERP/NetSuite intro that Claude already knows are padding that could be tightened, matching 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands across the full workflow (install, login, connection ensure, action list/run, request proxy) plus a complete flags table, but commands rely on placeholders (CONNECTION_ID, actionId, QUERY) and 'Use action names and parameters as needed' is vague, leaving minor gaps versus fully executable coverage.	4 / 5
Workflow Clarity	The connection-readiness flow has explicit state branching and a poll-again feedback loop, but running mutating actions and proxy POST/PUT/DELETE calls are destructive-capable operations with no validation checkpoint, which per the rubric caps workflow clarity at 3.	3 / 5
Progressive Disclosure	The single-file skill is organized into clear, well-labeled sections with no nested or broken references, but the ~65-object reference list is inlined in the overview rather than split out, leaving a minor organization gap that fits 'good structure; most content appropriately placed'.	4 / 5
	Total	14 / 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 is distinct and explicitly answers both what and when, but its action verbs are generic and its trigger coverage relies almost entirely on the product name without synonyms or concrete FinancialForce scenarios. Specificity and trigger-term quality are the weakest dimensions.

Suggestions

Replace the generic verb 'Manage data, records' with concrete FinancialForce actions (e.g., 'create and post invoices, track projects and timecards, record journal entries').

Expand the 'Use when' clause with concrete trigger phrases beyond the product name (e.g., 'Use when the user mentions FinancialForce invoices, billing, ERP accounting, or Salesforce-based financials').

Name 1-2 FinancialForce-specific objects (invoices, journal entries, timecards) in the description to raise specificity and reinforce distinctiveness.

Dimension	Reasoning	Score
Specificity	It names the domain ('FinancialForce integration') and 2-3 actions ('Manage data, records, and automate workflows'), but the verb 'Manage' is generic and the actions are not concrete, matching the anchor that names a domain with 1-2 actions but is not comprehensive.	3 / 5
Completeness	It has a clear 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with FinancialForce data'), but the trigger clause could be more specific with concrete FinancialForce scenarios, matching the 'has both what and when; when could be more explicit' anchor.	4 / 5
Trigger Term Quality	'FinancialForce' is a strong specific natural keyword, but the only supporting terms ('data', 'records') are generic and common variations (ERP, invoicing, billing, Salesforce financials) are missing, fitting 'some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	FinancialForce is a specific named product, so the trigger term carves a clear niche with minimal conflict risk against other skills; this matches the 'clear niche with distinct triggers; minimal conflict risk' anchor.	5 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/financialforce/SKILL.md
Commit: f484c82

Reviewed: ~19 hours ago

Table of Contents

Discovery Implementation Validation

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.