Name: replicate
Rating: 52.8 (1 reviews)
Author: membranedev

replicate

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

Quality

59%

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/replicate/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 action-dense with executable CLI commands and a useful flag table, but it carries unnecessary conceptual preamble, references an unlabeled "Step 2," and lacks validation checkpoints before destructive proxy requests. Structure is good for a single-file skill with no external bundles.

Suggestions

Remove the introductory paragraph explaining what Replicate is and the vague "Replicate Overview" filler; assume Claude knows the platform.

Label the post-connection steps explicitly (e.g. "## Step 2: Discover and run actions") so the "skip to Step 2" reference resolves.

Add a validation/verification checkpoint before destructive proxy requests (POST/PUT/DELETE), e.g. confirming the target id or running a dry-run GET first.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient code blocks and a flag table, but the opening paragraph explaining what Replicate is ("a platform for running machine learning models in the cloud...") and the thin "Replicate Overview" bullet filler ("Use action names and parameters as needed") are unnecessary explanation Claude already knows, matching the score-3 anchor of mostly efficient with some over-explanation.	3 / 5
Actionability	The body provides copy-paste-ready commands for install, login, connection ensure, action list/run, and request, plus a full flag table, but placeholders (CONNECTION_ID, QUERY, actionId) and a redundant second `action list` example leave minor gaps, matching the score-4 anchor of mostly executable guidance with minor gaps.	4 / 5
Workflow Clarity	A rough sequence exists (install → login → connection ensure → poll state → search → run) with state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED), but the "skip to Step 2" reference has no labeled Step 2 and there are no validation/verification steps before destructive proxy operations (POST/DELETE), which caps the score at 3 per the destructive-operation guideline.	3 / 5
Progressive Disclosure	The content is a single well-organized file with clear section headers and no nested or buried references (no bundle files exist), but minor organization gaps like the redundant action-list sections and the thin Overview section keep it just below the score-5 anchor.	4 / 5
	Total	14 / 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 includes an explicit "Use when" trigger and names the Replicate niche, but its action language is generic ("manage data, records, and automate workflows") rather than concrete Replicate capabilities, and it omits the natural terms users actually say for Replicate (models, predictions, images).

Suggestions

Replace generic actions with concrete Replicate capabilities, e.g. "Run machine learning models, generate predictions, and manage model deployments on Replicate."

Expand the trigger clause with natural user phrasings: "Use when the user wants to run models on Replicate, generate predictions or images, or deploy/manage ML models."

Add file-extension or platform-specific keywords (predictions, model versions, deployments) to improve distinctiveness and trigger coverage.

Dimension	Reasoning	Score
Specificity	The phrase "Manage data, records, and automate workflows" names the Replicate domain but the actions are generic (manage, automate) rather than concrete Replicate-specific operations like running models or predictions, matching the score-2 anchor of minimal/generic actions.	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 Replicate data"), but the "when" could be more specific, matching the score-4 anchor of both present with room for greater explicitness.	4 / 5
Trigger Term Quality	"Replicate" and "data" are relevant keywords and the "Use when... interact with Replicate data" clause gives a natural trigger, but common variations users would actually say (models, predictions, generate images, run ML) are missing, matching the score-3 anchor of some relevant keywords missing common synonyms.	3 / 5
Distinctiveness Conflict Risk	"Replicate integration" anchored to the named Replicate platform is a mostly distinct niche with minimal conflict risk, though the generic "manage data, records, automate workflows" phrasing creates minor overlap with other integration skills, matching the score-4 anchor.	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/replicate/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.