Name: spiff
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

spiff

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

Quality

62%

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/spiff/SKILL.md

Quality

Content

67%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 content is a well-structured, actionable integration guide with concrete Membrane CLI commands and state-driven connection handling. Its main weaknesses are an unnecessary marketing intro, placeholder-driven action examples, and a couple of minor structural/numbering inconsistencies.

Suggestions

Remove or condense the marketing paragraph about what Spiff is and who uses it; assume Claude knows or can infer the product context.

Add one or two concrete Spiff action examples (e.g., a real intent like 'list commission plans' with sample output) instead of relying on the QUERY/CONNECTION_ID placeholders.

Fix the broken 'skip to Step 2' reference and the '1b' sub-numbering so the connection-readiness sequence is internally consistent.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command documentation, but the opening paragraph describing what Spiff is and who uses it ("helps sales teams and finance departments... used by companies of all sizes") is marketing fluff Claude does not need, fitting the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	It provides many copy-pasteable concrete commands (install, login, connection ensure, action run, request) plus a flags table, but the 'Popular actions' section relies on placeholders (CONNECTION_ID, QUERY) and offers no real Spiff-specific action examples, leaving a minor gap.	4 / 5
Workflow Clarity	There is a clear sequence (install → authenticate → connect → wait/poll → search → run) with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-after-action feedback loop, but the 'skip to Step 2' reference points to no labeled Step 2 and the '1b' numbering is inconsistent, leaving minor gaps.	4 / 5
Progressive Disclosure	The single SKILL.md is organized into clear, well-labeled sections (Overview, Working with Spiff, Authentication, Connecting, Searching, Popular actions, Best practices) with no nested or buried references, though the 'Searching for actions' and 'Popular actions' sections overlap and could be consolidated.	4 / 5
	Total	15 / 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 third-person, concise, and includes an explicit 'Use when' clause with the named platform, but its capability verbs are generic rather than concrete commission-management actions. It is solid but leaves the 'what' underspecified.

Suggestions

Replace generic verbs with concrete Spiff capabilities, e.g. 'Calculate commissions, track sales performance, manage commission plans and records.'

Expand the 'when' clause with concrete triggers like 'Use when the user mentions commissions, sales performance, payout calculations, or Spiff.'

Add natural synonyms and file/resource terms (commission plans, quotas, payouts) to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	It names the Spiff domain but the listed actions — "Manage data, records, and automate workflows" — are generic rather than concrete commission-specific operations, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It has both a 'what' ("Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with Spiff data"), but the 'when' trigger is somewhat generic and could be more specific, fitting just below the 5 anchor.	4 / 5
Trigger Term Quality	It includes the natural product name "Spiff" and phrases like "interact with Spiff data," but "data, records, workflows" are generic and it misses common synonyms or concrete commission-related terms a user would say.	3 / 5
Distinctiveness Conflict Risk	The named platform "Spiff" and the Spiff-specific trigger give it a clear niche with minimal conflict risk, though the generic capability verbs ("manage data, records") create minor overlap with other integration/data skills.	4 / 5
	Total	13 / 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/spiff/SKILL.md
Commit: f484c82

Reviewed: 4 days 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.