Name: skillzrun
Rating: 64 (1 reviews)
Author: membranedev

skillzrun

SkillzRun integration. Manage Organizations, Leads, Projects, Pipelines, Users, Goals and more. Use when the user wants to interact with SkillzRun data.

Quality

76%

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/skillzrun/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.

A highly actionable, command-dense skill body that walks through auth, connection state handling, action discovery, execution, and proxying with copy-paste examples. Its weak spots are minor redundancy and an undefined "Step 2" reference in the workflow.

Suggestions

Define or remove the dangling "Step 2" references and renumber the connection steps (1b → 2) so the sequence is unambiguous.

Collapse the repeated action-discovery command in "## Popular actions" since it duplicates "### Searching for actions".

Trim the opening SkillzRun marketing paragraph to one line of relevant context.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands and short explanations, but the opening SkillzRun description paragraph and some repeated action-discovery commands ("## Popular actions" restates the list command) could be trimmed.	4 / 5
Actionability	Nearly every section gives copy-paste-ready commands with concrete flags ("--json", "--wait", "--input '{\"key\": \"value\"}'") and a full proxy-option table, covering the common auth/connect/run/proxy cases.	5 / 5
Workflow Clarity	The connect-to-poll-to-ready state machine is clearly sequenced with a feedback loop (poll after CLIENT_ACTION_REQUIRED), but references to an undefined "Step 2" and the loose "1b" sub-heading leave a minor gap.	4 / 5
Progressive Disclosure	No bundle files exist; the single SKILL.md is well-organized into clear sections (Overview, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with no nested references, though it runs longer than the simple-skill exception.	4 / 5
	Total	17 / 20 Passed

Description

70%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.

A solid, third-person description that states both purpose and an explicit trigger, anchored by a distinctive brand name. Its main weakness is the single generic "Manage" verb and the slightly generic "interact with SkillzRun data" trigger.

Suggestions

Vary the action verbs beyond "Manage" (e.g., "Create and update Leads, move Projects through Pipelines, assign Goals to Users") to lift specificity.

Tighten the "when" clause with concrete trigger phrases (e.g., "Use when the user wants to create or query SkillzRun Leads, Projects, Pipelines, or Goals").

Drop the "and more" hedge — it weakens precision without adding real capability information.

Dimension	Reasoning	Score
Specificity	It names many concrete entities ("Organizations, Leads, Projects, Pipelines, Users, Goals") but applies a single generic verb ("Manage ... and more"), so the actions themselves are not varied or comprehensive.	3 / 5
Completeness	Both halves are present — a clear "what" (manage SkillzRun entities) and an explicit "Use when the user wants to interact with SkillzRun data" trigger — but the "when" is somewhat generic rather than enumerating concrete trigger phrases.	4 / 5
Trigger Term Quality	The brand "SkillzRun" plus the entity nouns (Leads, Projects, Pipelines, Goals) give good keyword coverage a user would naturally say, though no synonyms or extensions are present.	4 / 5
Distinctiveness Conflict Risk	The distinctive "SkillzRun" brand carves a clear niche, though the generic CRM-style entity list (Leads, Pipelines, Users) carries minor overlap risk with general project-management skills.	4 / 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/skillzrun/SKILL.md
Commit: f484c82

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