CtrlK
BlogDocsLog inGet started
Tessl Logo

crowddev

Crowd.dev integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with Crowd.dev data.

62

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/crowddev/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 well-structured and highly actionable with concrete Membrane CLI commands and a useful action table, and is reasonably concise. Its main weakness is workflow clarity: destructive and batch operations (delete/update by IDs) ship with no validation or verification checkpoints, capping that dimension.

Suggestions

Add a validation/verification checkpoint before destructive and batch actions (e.g., confirm IDs via a get/list query, run deletes with --dry-run or against a single ID first, and verify the result) so destructive workflows clear the workflow_clarity cap.

Trim the opening platform-marketing paragraph ('Crowd.dev is a community growth platform that helps companies...') to a one-line orientation, since Claude does not need the audience/use-case detail to execute the skill.

Consider moving the Popular actions table into a references/ file referenced one level deep from SKILL.md to tighten the overview and lift progressive_disclosure.

DimensionReasoningScore

Conciseness

The body is mostly command- and table-driven and efficient, but the opening paragraph explaining what Crowd.dev is and who uses it ('helps companies understand, engage, and grow their developer communities... used by developer relations teams...') is over-explanation that could be trimmed, fitting 'efficient; minor instances of over-explanation'.

4 / 5

Actionability

Provides concrete, copy-paste-ready commands (npm install, membrane login, membrane search/connect/action list/action run/request) with flags and a Popular actions table of real action IDs, matching 'mostly executable guidance; concrete commands with minor gaps'; placeholders like CONNECTION_ID and the vague 'Use action names and parameters as needed' prevent a 5.

4 / 5

Workflow Clarity

A clear sequence exists (install → login → connect → list actions → run/proxy), but the skill exposes destructive and batch operations ('Delete Organizations', 'Delete Members', 'Update Organization') with no validation, confirmation, or verify-result checkpoints; per the rubric cap, missing validation for destructive/batch operations caps this at 3.

3 / 5

Progressive Disclosure

Content is organized into well-signaled sections (Install, Setup, Connecting, Searching, Popular actions, Running, Proxy, Best practices) with no nested references, matching 'good structure; most content appropriately placed; minor organization gaps'; the inline ~18-row action table is bulk content that could live in a separate reference file, holding it below 5.

4 / 5

Total

15

/

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 clearly states what the skill does and when to use it, with a distinct Crowd.dev niche and good keyword coverage. It is held back from top marks by the generic 'Manage' verb, the vague 'and more', and a single non-enumerated trigger phrase.

DimensionReasoningScore

Specificity

Names the domain and several concrete entity types ('Manage Persons, Organizations, Deals, Leads, Projects, Activities') matching the 'lists several specific actions; minor gaps' anchor, but the single generic verb 'Manage' and the vague 'and more' keep it below comprehensive coverage.

4 / 5

Completeness

Explicitly answers both what ('Crowd.dev integration. Manage...') and when ('Use when the user wants to interact with Crowd.dev data'), but the single 'when' phrase is generic rather than enumerating concrete triggers, fitting 'has both what and when; when could be more specific' rather than a 5.

4 / 5

Trigger Term Quality

Good keyword coverage with the platform name 'Crowd.dev' plus natural entity terms ('Organizations, Deals, Leads'), matching the 'good keyword coverage; a few natural terms missing' anchor; it lacks synonyms and Crowd.dev's actual 'Members' term (written as 'Persons').

4 / 5

Distinctiveness Conflict Risk

Scoped to a single named platform ('Crowd.dev integration') with distinct triggers, giving a clear niche and minimal conflict risk with other skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.