CtrlK
BlogDocsLog inGet started
Tessl Logo

regal

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

60

Quality

71%

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

Quality

Content

75%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 concrete, runnable Membrane CLI commands and a clear connection-state workflow. Trimming marketing-style filler and adding output validation would push it higher.

Suggestions

Remove persuasive filler (e.g. "so you can focus on the integration logic rather than auth plumbing", "This is the fastest way") to improve token efficiency.

Add a brief validation/check step for action results before destructive or batch runs to strengthen workflow feedback loops.

Consider moving the proxy flag reference table and Best Practices into a separate reference file to keep SKILL.md a leaner overview.

DimensionReasoningScore

Conciseness

Mostly efficient with executable command blocks, but padded lines like "so you can focus on the integration logic rather than auth plumbing" and "This is the fastest way to get a connection" could be trimmed.

3 / 5

Actionability

Fully executable, copy-paste-ready CLI commands throughout (install, login, connection ensure/get, action list/run, request) plus a concrete proxy-flags table covering the common cases.

5 / 5

Workflow Clarity

Clear install→authenticate→connect→poll-state sequence with explicit state feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED); minor gaps in validating action outputs before destructive runs.

4 / 5

Progressive Disclosure

Well-organized single-file skill with clearly signaled sections and no nested references; at ~110 lines it stays slightly above the under-50-line threshold that would warrant a clean 5.

4 / 5

Total

16

/

20

Passed

Description

67%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 well-formed with both a what and a when clause and a distinct product niche. Its main weakness is thin trigger-term variety and a single action verb across the listed entities.

Suggestions

Add natural trigger variations, e.g. "Use when the user wants to send calls/SMS, manage Regal contacts, or work with Regal pipelines and goals."

Vary the action verbs beyond "Manage" to better signal concrete capabilities (e.g. create, update, query).

Tie the listed entities to the actual Regal objects shown in the body (Company, User, Deal, Task, Call, Email) for consistency.

DimensionReasoningScore

Specificity

Lists several concrete managed entities ("Organizations, Pipelines, Users, Goals, Filters") but relies on a single verb ("Manage"), leaving minor coverage gaps in the range of distinct actions.

4 / 5

Completeness

Explicitly answers both what ("Manage Organizations, Pipelines, Users, Goals, Filters") and when ("Use when the user wants to interact with Regal data"), though the trigger clause is somewhat generic.

4 / 5

Trigger Term Quality

The only natural keyword is the brand name "Regal" repeated in "interact with Regal data"; common variations or synonyms a user might say are missing.

3 / 5

Distinctiveness Conflict Risk

"Regal integration" carves a clear product niche with low conflict risk, though "Regal" as an ordinary word introduces minor ambiguity versus a more unique identifier.

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