Name: drimify
Rating: 66.4 (1 reviews)
Author: membranedev

drimify

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

Quality

80%

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

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 well-validated connection workflow. It loses points for minor verbosity, a broken "Step 2" cross-reference, and a single-file structure that could offload reference material.

Suggestions

Fix the broken "skip to Step 2" reference by labeling the post-connection section as "Step 2" or rewording to a concrete section name.

Add a brief validation/check step after running actions (e.g., inspect the `output` field and handle error states) to close the workflow feedback loop.

Move the 15-item experience type list and the proxy flag table into a separate reference file (e.g. REFERENCES.md) to tighten the main SKILL.md overview.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands throughout; the Drimify intro is justified for an obscure product, but lines like "Use action names and parameters as needed" and "so you can focus on the integration logic rather than auth plumbing" are minor trimmable padding.	4 / 5
Actionability	Fully executable, copy-paste-ready commands cover the common cases (install, login, connection ensure/get, action list/run, request proxy) with a complete flag reference table for the proxy.	5 / 5
Workflow Clarity	Clear sequence from install to connect to search to run, with explicit state-checking feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR); however the "skip to Step 2" reference points to a non-existent heading and there is no validation of action-run results.	4 / 5
Progressive Disclosure	Well-organized into clear sections in a single self-contained file with no bundle files; the 15-item experience list and proxy flag table could be split into reference files, leaving minor organization gaps.	4 / 5
	Total	17 / 20 Passed

Description

78%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 branded and clearly answers both what it does and when to use it, with concrete entity names. Its main weakness is the single generic verb "Manage" and a somewhat vague trigger clause that could enumerate more natural use-case phrases.

Suggestions

Replace the single verb "Manage" with distinct concrete actions (e.g., "Create and update Organizations, Leads, Pipelines, Users, Goals, and Filters") to raise specificity.

Expand the "Use when" clause with concrete trigger phrases users would say, e.g., "Use when the user wants to manage Drimify campaigns, quizzes, leads, or pipeline data."

Align the listed entities with the skill body (which covers Experiences, Projects, Clients) to avoid misleading capability claims.

Dimension	Reasoning	Score
Specificity	Lists several concrete entities to manage ("Organizations, Leads, Pipelines, Users, Goals, Filters"), but applies a single generic verb ("Manage") to all of them rather than multiple distinct concrete actions, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both "what" (Drimify integration managing listed entities) and "when" ("Use when the user wants to interact with Drimify data"), but the "when" clause is a single generic trigger that could be more specific.	4 / 5
Trigger Term Quality	Includes the natural brand term "Drimify" plus domain keywords (Leads, Pipelines, Goals) and the trigger phrase "interact with Drimify data"; a few natural variations (campaigns, quizzes, contests) that users would say are missing.	4 / 5
Distinctiveness Conflict Risk	Tied to a specific named SaaS platform ("Drimify") with branded triggers, giving it a clear niche and minimal conflict risk against other skills.	5 / 5
	Total	17 / 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/drimify/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.