CtrlK
BlogDocsLog inGet started
Tessl Logo

supernotes

Supernotes integration. Manage Notes, Users, Groups. Use when the user wants to interact with Supernotes data.

62

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/supernotes/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 body is a well-structured, highly actionable integration guide with concrete commands and a clear workflow including validation via connection-state polling. It is efficient and navigable, with only minor conciseness and step-numbering gaps.

DimensionReasoningScore

Conciseness

The body is mostly lean executable commands with brief, necessary explanations of Membrane-specific concepts (e.g. connection states), though the opening product description and phrases like "so you can focus on the integration logic rather than auth plumbing" could be trimmed.

4 / 5

Actionability

It provides copy-paste ready bash commands for install, login, connection ensure/get, action list/run, and proxy requests with a complete options table, covering the common integration cases.

5 / 5

Workflow Clarity

The install → authenticate → connect → poll-for-ready → search → run sequence is clear with a feedback loop for CLIENT_ACTION_REQUIRED, but the loose "Step 2"/"1b" references without a consistent numbered structure leave a minor gap.

4 / 5

Progressive Disclosure

Content is well organized into clearly headed sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no nested references, though all reference material is inlined in one ~140-line file rather than split out.

4 / 5

Total

17

/

20

Passed

Description

66%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 concise and covers both what and when with a distinct app-specific trigger, but the action verb is generic and the trigger terms lack synonym coverage. It is strong on distinctiveness but middling on specificity and trigger breadth.

Suggestions

Replace the generic verb "Manage" with concrete operations, e.g. "Create, edit, search, and tag Notes; manage Users and Groups."

Add natural trigger synonyms users might say, such as "notes", "flashcards", "cards", or "sync Supernotes" to broaden trigger coverage.

Make the "Use when" clause more specific, e.g. "Use when the user wants to create, find, or organize notes, cards, or tags in Supernotes."

DimensionReasoningScore

Specificity

"Manage Notes, Users, Groups" names the domain and concrete entities to act on, but the single generic verb "Manage" covers only one action type rather than listing multiple specific operations.

3 / 5

Completeness

It states both what ("Manage Notes, Users, Groups") and when ("Use when the user wants to interact with Supernotes data"), matching the anchor where both are present but the trigger could be more specific.

4 / 5

Trigger Term Quality

"Notes, Users, Groups" and "interact with Supernotes data" provide relevant keywords, but common synonyms and variations a user might naturally say (e.g. "flashcards", "sync", file extensions) are missing.

3 / 5

Distinctiveness Conflict Risk

"Supernotes integration" targets a specific named application with a distinct trigger phrase, giving it a clear niche with minimal overlap risk against other skills.

5 / 5

Total

15

/

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.