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

tenderly

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

Quality

69%

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

Quality

Content

76%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 copy-paste-ready Membrane CLI commands and a clearly sequenced connection workflow including polling and state recovery. The main weakness is the absence of validation/verification steps before executing mutating actions or proxy requests, which caps workflow clarity, and some inlined reference material that could be split out.

Suggestions

Add explicit validation checkpoints before destructive/batch operations: after `membrane action run` and `membrane request` with POST/PUT/DELETE, instruct Claude to inspect the `output`/response for errors and confirm success before proceeding.

Move the proxy flag reference table and the action schema field list into a one-level-deep reference file (e.g. REFERENCE.md) and link to it from the body.

Trim the opening Tenderly marketing paragraph ('It helps developers identify and resolve issues...') to keep the body token-lean.

Dimension	Reasoning	Score
Conciseness	Largely lean with direct CLI commands and a flag table, though the opening Tenderly explainer and phrases like 'so you can focus on the integration logic rather than auth plumbing' add minor over-explanation that could be trimmed.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure, --wait polling, action run with --input, proxy request with full flag table) covering the common integration cases.	5 / 5
Workflow Clarity	The install→auth→connect→search→run→proxy flow is sequenced with state-branching and a poll-retry loop, but mutating action runs and proxy POST/PUT/DELETE calls lack explicit verification/validation checkpoints, so the destructive-batch cap of 3 applies.	3 / 5
Progressive Disclosure	Single SKILL.md with clear section headers and no bundle files present; well-organized overall, though reference-style material (the proxy flag table, action schema fields) is inlined rather than split into a one-level-deep reference.	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 correctly includes a 'Use when...' trigger and anchors itself to the Tenderly brand, but the capability description is generic ('manage data, records, automate workflows') rather than naming concrete Tenderly actions like simulation, forks, or transactions. Tightening the action list and adding natural trigger terms would lift specificity and trigger-term quality.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete Tenderly actions such as 'run simulations, fork transactions, and inspect contracts'.

Expand the 'Use when' clause with natural user phrases: 'Use when the user wants to run Tenderly simulations, debug transactions, or fork an Ethereum network.'

Add Tenderly-specific synonyms (simulation, transaction, fork, contract) so the trigger matches how users actually phrase these requests.

Dimension	Reasoning	Score
Specificity	Names the Tenderly domain and a couple actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete like 'Extract text... fill forms', matching the anchor for domain plus 1-2 non-comprehensive actions.	3 / 5
Completeness	Provides both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Tenderly data'), but the what is vague and the when is generic, matching both-present-but-could-be-more-specific.	4 / 5
Trigger Term Quality	Includes the product name 'Tenderly' twice ('interact with Tenderly data') but lacks natural synonyms users would say (simulation, fork, transactions, contracts), matching some-relevant-keywords-but-missing-variations.	3 / 5
Distinctiveness Conflict Risk	The 'Tenderly' brand name anchors it to a clear niche, but the generic verb phrasing ('Manage data, records, and automate workflows') leaves minor overlap with other data-management 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/tenderly/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.