CtrlK
BlogDocsLog inGet started
Tessl Logo

survser

Survser integration. Manage Organizations. Use when the user wants to interact with Survser data.

57

Quality

66%

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/survser/SKILL.md
SKILL.md
Quality
Evals
Security

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 content is highly actionable with concrete, executable Membrane CLI commands and a solid connection-state workflow. Its main weaknesses are the dangling "Step 2" references and a slightly verbose intro.

Suggestions

Resolve the undefined "Step 2" references by either labeling the workflow steps (1a/1b/2) or rewording to point at the actual "Running actions" section.

Trim the introductory exposition about Membrane handling authentication, since the same point is made under Best practices.

Consider moving the proxy flag table and detailed clientAction fields into a references file to keep SKILL.md a tighter overview.

DimensionReasoningScore

Conciseness

The body is mostly lean executable commands with minimal padding, though lines like "This skill uses the Membrane CLI... Membrane handles authentication..." are mild over-explanation that could be trimmed.

4 / 5

Actionability

It provides copy-paste ready commands throughout—login, connection ensure, action list/run with JSON input, and a proxy options table—covering the common cases fully.

5 / 5

Workflow Clarity

The connection flow has a clear state-based feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED with re-polling), but it twice references an undefined "Step 2", a minor sequencing gap.

4 / 5

Progressive Disclosure

The single file is well-organized with clear section headers and no nested references, though the proxy options table and detailed connection states could arguably move to a separate reference file.

4 / 5

Total

17

/

20

Passed

Description

50%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 an explicit Use-when trigger and names the Survser platform, but the capability statement is thin and it lacks natural survey/feedback trigger terms. It is adequate but not comprehensive.

Suggestions

Expand the capability list beyond "Manage Organizations" to concrete actions like create surveys, distribute surveys, and analyze responses.

Add natural trigger terms users would actually say, such as "surveys", "feedback", "responses", or "questionnaires", alongside "Survser data".

Tighten the Use-when clause to reference survey-specific scenarios (e.g., when the user wants to create or analyze surveys) for sharper triggering.

DimensionReasoningScore

Specificity

"Manage Organizations" names the domain but offers only a single, generic action with no concrete capability list, fitting the 'names the domain but actions are minimal or generic' anchor.

2 / 5

Completeness

It states both a what ("Manage Organizations") and an explicit when ("Use when the user wants to interact with Survser data"), matching 'has both what and when; when could be more specific'.

4 / 5

Trigger Term Quality

The only trigger keyword is "Survser data"; natural user phrases such as surveys, feedback, or responses are absent, leaving just one or two generic keywords.

2 / 5

Distinctiveness Conflict Risk

The named Survser platform gives it a clear niche with low conflict risk, but the generic "interact with Survser data" phrasing leaves minor overlap risk with other data-integration skills.

4 / 5

Total

12

/

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.