Name: resci-retention-science
Rating: 62.4 (1 reviews)
Author: membranedev

resci-retention-science

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

Quality

74%

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/resci-retention-science/SKILL.md

Quality

Content

82%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 executable commands and a clear connection workflow, well-organized into sections. Minor verbosity and a dangling 'Step 2' reference keep conciseness and workflow_clarity at 4 rather than 5.

Suggestions

Trim marketing-style filler such as 'so you can focus on the integration logic rather than auth plumbing' and 'This is the fastest way to get a connection'.

Resolve the dangling 'Step 2' reference by labeling an explicit numbered step sequence (e.g. 1. Ensure connection, 2. Wait for READY, 3. Search actions, 4. Run action).

Tighten the 'Best practices' bullets to drop buzzword phrasing like 'burn less tokens' in favor of concrete guidance.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean command examples and a flag table, with only minor over-explanation such as 'so you can focus on the integration logic rather than auth plumbing' and 'This is the fastest way to get a connection'; the niche-platform intro is justified context, so this fits anchor 4 rather than the more padded anchor 3.	4 / 5
Actionability	Provides copy-paste-ready commands for install, login, connection ensure/get, action list/run, and request, plus a concrete flag table, fully covering common cases as in the 'fully executable, copy-paste ready' anchor.	5 / 5
Workflow Clarity	The connection flow is sequenced with explicit state checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a re-poll feedback loop, but the dangling 'Step 2' reference and loosely numbered sub-steps leave minor validation gaps; fits anchor 4 rather than 5.	4 / 5
Progressive Disclosure	Single well-sectioned file with no nested references and content appropriately contained in one place; at ~138 lines it exceeds the simple-skill threshold, so it scores 4 ('good structure, most content appropriately placed') rather than 5 which requires split reference files.	4 / 5
	Total	17 / 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 third-person, covers both what and when, and is clearly tied to a specific platform. Its main weakness is generic action verbs and thin trigger-term coverage, which cap specificity and trigger_term_quality at 3.

Suggestions

Replace generic verbs with concrete actions, e.g. 'query customer attributes, fetch email campaign records, and trigger automated workflows' instead of 'Manage data, records, and automate workflows'.

Add natural trigger phrases and synonyms users would say, such as 'Retention Science', 'ReSci', 'customer churn reports', or 'retention campaigns'.

Sharpen the 'when' clause with concrete triggers, e.g. 'Use when the user wants to query Retention Science customer data, review email campaigns, or automate retention workflows.'

Dimension	Reasoning	Score
Specificity	Names the Retention Science domain and a few actions ("Manage data, records, and automate workflows") but the verbs are generic ("manage") rather than concrete, fitting the 'names domain and 1-2 concrete actions, not comprehensive' anchor; not a 4 because the actions lack specificity.	3 / 5
Completeness	Explicitly states both what it does ("Manage data, records, and automate workflows") and when to use it ("Use when the user wants to interact with Retention Science data"), but the 'when' clause is somewhat generic; fits anchor 4 rather than 5 which requires concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes relevant terms ("Retention Science", "Retention Science data") but misses common variations or synonyms a user might naturally say, matching the 'some relevant keywords but missing common variations' anchor; not a 4 due to thin keyword coverage.	3 / 5
Distinctiveness Conflict Risk	Names a specific third-party platform (Retention Science) giving it a clear niche with distinct triggers and minimal overlap with other skills, matching the 'clear niche with distinct triggers' 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/resci-retention-science/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.