Name: devrev
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

devrev

DevRev integration. Manage Organizations, Pipelines, Users, Goals, Filters. Use when the user wants to interact with DevRev data.

Quality

61%

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/devrev/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 content is highly actionable with concrete CLI commands and a solid connection state-machine, but it mixes in marketing fluff and leaves the top-level workflow sequence implicitly ordered. Structure is clean for a single-file skill.

Suggestions

Remove marketing filler (e.g., "so you can focus on the integration logic rather than auth plumbing", "burn less tokens and make communication more secure") to improve conciseness.

Number the end-to-end onboarding flow (install → login → connect → wait for READY → search actions → run) and fix the dangling "Step 2" reference so the sequence is explicit.

Consider moving the Popular actions reference table into a separate reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes marketing-style padding ("focus on the integration logic rather than auth plumbing", "burn less tokens and make communication more secure") that could be trimmed.	3 / 5
Actionability	Concrete, copy-paste bash commands are given throughout (install, login, connection ensure, action list/run, request) with a flags table and JSON input examples; minor gaps remain around placeholders like CONNECTION_ID and <actionId>.	4 / 5
Workflow Clarity	The connection-readiness polling loop (READY / BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) is a good checkpoint, but the macro onboarding sequence is not crisply numbered and references a "Step 2" with no labeled Step 1 or Step 2.	3 / 5
Progressive Disclosure	The single-file guide is well organized with clear section headers and no nested references; the long Popular actions table inlined is a minor organization gap but appropriate for an integration overview.	4 / 5
	Total	14 / 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 clearly targeted to a specific product and includes an explicit trigger clause, but it relies on one generic verb ("Manage") for several objects and lacks richer natural trigger phrasing. It is solid but not exemplary.

Suggestions

Replace the single verb "Manage" with concrete actions (e.g., "List, create, and update Organizations, Pipelines, Users, Goals, and Filters") to lift specificity.

Expand the trigger clause with natural phrasings users would say (e.g., "Use when the user wants to query or update DevRev organizations, users, work items, or conversations").

Mention the most common DevRev entities users reference (e.g., issues, work items, conversations) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the DevRev domain plus concrete objects ("Manage Organizations, Pipelines, Users, Goals, Filters"), but the single generic verb "Manage" covers what would be several distinct actions, so it is not comprehensive.	3 / 5
Completeness	It answers both "what" ("Manage Organizations, Pipelines, Users, Goals, Filters") and "when" (explicit "Use when..." clause), but the trigger could be more specific and enumerate more concrete phrasings.	4 / 5
Trigger Term Quality	Relevant keywords appear ("DevRev", "Organizations", "Pipelines", "Users", "Goals", "Filters") with a usable trigger phrase ("Use when the user wants to interact with DevRev data"), but common natural variations or synonyms are missing.	3 / 5
Distinctiveness Conflict Risk	The "DevRev integration" niche is clearly distinct and unlikely to fire for unrelated skills, though generic object names like Users and Goals carry minor overlap with other CRM-style 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/devrev/SKILL.md
Commit: f484c82

Reviewed: ~18 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.