CtrlK
BlogDocsLog inGet started
Tessl Logo

mason

Mason integration. Manage data, records, and automate workflows. Use when the user wants to interact with Mason 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/mason/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 content is a well-structured, highly actionable guide with concrete CLI commands, clear connection-state feedback loops, and good section organization, held back only by minor prose padding, a thin "Popular actions" section, and inconsistent step numbering.

DimensionReasoningScore

Conciseness

The body is dominated by concrete, copy-pasteable commands with only minor over-explanation (the platform intro paragraph, "so you can focus on the integration logic rather than auth plumbing", and "This is the fastest way to get a connection"), fitting the anchor for efficient content with trimmable asides.

4 / 5

Actionability

It provides executable commands for install, login, connection ensure/get, action list/run, and proxy requests with a full flags table; the "Popular actions" heading promises examples but only instructs discovery, a minor gap keeping it below fully copy-paste-ready coverage.

4 / 5

Workflow Clarity

A clear sequence (Install → Authenticate → Connect → poll/handle client action → search → run) is present with feedback loops (poll until READY, re-poll after the user acts), but step numbering is inconsistent ("Step 2" is referenced without a clearly labeled Step 1), a minor clarity gap.

4 / 5

Progressive Disclosure

No bundle files exist; the single ~140-line SKILL.md is well-organized with clear section headers and appropriately inlined content, but its length exceeds the simple-skill threshold and it offers no one-level-deep references, so it stops short of the top anchor.

4 / 5

Total

16

/

20

Passed

Description

57%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 answers both what and when with an explicit trigger clause and leans on a distinct brand term, but its capability verbs are generic rather than concrete and its trigger keywords lack synonyms or file-extension variations.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete actions, e.g. "Create and edit Mason projects, documents, and pages; apply templates and brand kits; automate record workflows."

Expand the trigger clause with natural variations users might say, e.g. "Use when the user wants to build or edit Mason projects, pages, or templates, or automate workflows over Mason records."

Mention concrete Mason objects (projects, documents, pages, templates, brand kits) in the description so it is distinguishable from generic data/automation skills.

DimensionReasoningScore

Specificity

Names the Mason domain and lists three actions ("Manage data, records, and automate workflows"), but the verbs are generic ("manage") rather than concrete operations, matching the anchor for minimal/generic actions and falling below the anchor requiring concrete actions.

2 / 5

Completeness

Both 'what' ("Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with Mason data") are present; the 'Use when' clause satisfies the trigger-guidance requirement, but the 'what' is generic enough to keep it below a 5.

4 / 5

Trigger Term Quality

"Mason" is a specific brand keyword and "data", "records", "workflows" are relevant, but common variations and synonyms are missing, fitting the anchor for some relevant keywords without full coverage.

3 / 5

Distinctiveness Conflict Risk

The "Mason" brand term gives it a clear niche with mostly distinct triggers, but the generic "manage data, records, automate workflows" phrasing creates minor overlap risk with other data/automation skills.

4 / 5

Total

13

/

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.