Name: rd-station
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

rd-station

RD Station integration. Manage Recordses. Use when the user wants to interact with RD Station data.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/rd-station/SKILL.md

Quality

Content

68%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 throughout and a solid connection-state workflow, but it pads several sections with marketing prose and omits validation steps for the destructive Records operations it advertises. Tightening the prose and adding verify-after-mutate steps would raise conciseness and workflow clarity.

Suggestions

Trim promotional filler ("so you can focus on the integration logic," "This is the fastest way to get a connection") and the RD Station intro paragraph that Claude can infer.

Add validation/verification steps for destructive Records operations (e.g. re-fetch or list a Record after create/update/delete to confirm the change took effect).

Resolve the inconsistent step numbering ("Step 2" is referenced but there is no labeled "Step 1"; section "1b" has no "1a") so the connection workflow sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly commands with brief explanations, but the opening RD Station paragraph and marketing-style lines ("so you can focus on the integration logic rather than auth plumbing," "This is the fastest way to get a connection") are unnecessary padding.	3 / 5
Actionability	It provides copy-paste-ready CLI commands for every stage — install, login, connection ensure/get, action list/run, and proxy requests — with a clear flags table, fully executable as written.	5 / 5
Workflow Clarity	The connection flow has good state-polling checkpoints (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the destructive Records CRUD operations have no validation or verification steps, which caps this at 3 per the destructive-operation guideline.	3 / 5
Progressive Disclosure	No bundle files exist, but the body is well-sectioned into Overview, Authentication, Connecting, Searching, Actions, Proxy, and Best practices; minor inline material (the proxy flags table) could live in a reference but is reasonably placed.	4 / 5
	Total	15 / 20 Passed

Description

61%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 appropriately trigger-aware and clearly scoped to RD Station, but its capability verbs are generic and it contains a misspelling ("Recordses"). Naming concrete operations (create, read, update, delete leads/contacts) and fixing the typo would lift specificity and trigger quality.

Suggestions

Replace the generic "Manage Recordses" with concrete operations, e.g. "Create, read, update, and delete RD Station Records (leads, contacts, opportunities)."

Fix the typo "Recordses" → "Records" and add natural trigger phrases such as "leads," "CRM," or "marketing automation."

Make the "Use when" clause more specific by naming the data types users mention, e.g. "Use when the user wants to manage RD Station leads, contacts, or deals."

Dimension	Reasoning	Score
Specificity	The description names the domain ("RD Station integration") but uses only generic verbs — "Manage Recordses" and "interact with RD Station data" — with no concrete CRUD actions; the misspelled "Recordses" further weakens it.	2 / 5
Completeness	Both a "what" ("Manage Recordses") and an explicit "when" ("Use when the user wants to interact with RD Station data") are present, though the "what" is generic and the "when" could name concrete triggers.	4 / 5
Trigger Term Quality	It surfaces the core brand keyword "RD Station" and the noun "Records," but the term is misspelled and common synonyms (leads, contacts, CRM, marketing automation) are missing.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to the named SaaS platform "RD Station" creates a clear niche with distinct triggers and minimal overlap risk against other skills.	5 / 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/rd-station/SKILL.md
Commit: f484c82

Reviewed: 5 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.