Name: slope
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

slope

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

Quality

68%

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

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 content is highly actionable with executable Membrane CLI commands and a validated connection workflow. It loses points on a marketing-style intro and on workflow labeling (broken Step 2/1b references) rather than on substance.

Suggestions

Trim the marketing intro to one technical sentence about what Slope is, removing the KPIs/growth/insights fluff.

Fix the broken step references: label an explicit "1. Install & authenticate", "2. Connect", "3. Discover & run actions" sequence instead of dangling "Step 2" and "1b" references.

Either populate "Popular actions" with a few real Slope action examples or relabel it as part of the discovery flow to avoid promising content it does not deliver.

Dimension	Reasoning	Score
Conciseness	The intro ("It helps finance and sales teams track key performance indicators... optimize their sales performance and gain better financial insights") is marketing fluff Claude does not need, and phrases like "so you can focus on the integration logic rather than auth plumbing" pad otherwise tight command reference.	3 / 5
Actionability	The body is dominated by copy-paste-ready commands (install, login, connection ensure, poll with --wait, action list/run, request proxy) plus a flags table, covering the common cases end-to-end.	5 / 5
Workflow Clarity	The connection flow has a clear sequence with a feedback loop (poll --wait, check READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, re-poll after action), but "skip to Step 2" and "#### 1b" reference unlabeled steps, and running actions has no pre-flight validation for destructive calls.	4 / 5
Progressive Disclosure	No bundle files exist, so all content is inline, but the single SKILL.md is well-sectioned (Overview, Install, Auth, Connecting, Searching, Running, Proxy, Best practices) with a clear overview; minor gaps are the redundant "Popular actions" section and inline reference material (clientAction states, proxy flags).	4 / 5
	Total	16 / 20 Passed

Description

62%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 and provides an explicit Use-when trigger plus a named app, giving it solid completeness and distinctiveness. Its weakness is generic action language and thin trigger-term coverage that lacks natural synonyms.

Suggestions

Replace generic actions with concrete Slope capabilities (e.g. "query revenue and sales KPIs, pull customer records, trigger workflow automations").

Broaden the Use-when clause with natural synonyms users say, such as "Use when the user wants to analyze Slope revenue, pull sales records, or automate Slope workflows."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Slope domain and lists a few actions, but they are generic verbs rather than concrete Slope-specific capabilities, so it stops short of comprehensive coverage.	3 / 5
Completeness	It has both a "what" ("Manage data, records, and automate workflows") and an explicit "Use when..." clause ("Use when the user wants to interact with Slope data"), but the "what" is generic rather than concrete, so it is not a 5.	4 / 5
Trigger Term Quality	The only trigger is "interact with Slope data"; while "data, records, workflows" appear, it misses natural variations and synonyms a user would say (e.g. revenue, sales, analytics, pull records).	3 / 5
Distinctiveness Conflict Risk	Naming the specific app Slope and tying the trigger to Slope data gives it a clear niche with minimal conflict, though the generic "manage data/records/workflows" framing overlaps slightly with other integration skills.	4 / 5
	Total	14 / 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/slope/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.