CtrlK
BlogDocsLog inGet started
Tessl Logo

m3ter

M3ter integration. Manage data, records, and automate workflows. Use when the user wants to interact with M3ter 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/m3ter/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 delivers executable, well-sectioned CLI guidance with a clear connection-readiness workflow and feedback loop. Its main weaknesses are marketing-fluff prose that adds tokens and a dangling 'Step 2' reference that breaks the workflow's labeling.

Suggestions

Trim promotional commentary (e.g. "so you can focus on the integration logic", "burn less tokens and make communication more secure") to keep only operational guidance.

Resolve the dangling 'Step 2' references by either labeling the post-connection steps as Step 2 or removing the cross-references, so the workflow sequence is self-consistent.

Give the proxy section a complete executable example (with --json and a representative header/query) to close the actionability gap.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete commands, but padded with marketing-style commentary ("so you can focus on the integration logic rather than auth plumbing", "This will burn less tokens and make communication more secure") that could be trimmed, fitting the 'mostly efficient with some unnecessary explanation' anchor.

3 / 5

Actionability

Provides concrete, copy-paste-ready commands for install, login, connection ensure/get, action list/run, and proxy requests with a clear options table, with only minor gaps such as the proxy example lacking a full --json invocation.

4 / 5

Workflow Clarity

The connection flow is clearly sequenced with state-based polling checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a re-poll feedback loop, but the dangling 'skip to Step 2' reference with no labeled Step 2 keeps it below 5.

4 / 5

Progressive Disclosure

Single-file skill with no bundle files and well-organized section headers (Overview, Authentication, Connecting, Searching actions, Proxy requests, Best practices); good structure with minor gaps, though over the 50-line threshold that would allow a 5.

4 / 5

Total

15

/

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 third-person, names a clear niche, and includes an explicit 'Use when' clause, giving it solid completeness and distinctiveness. It is held back by generic action verbs and a thin, single-keyword trigger family.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete M3ter capabilities such as monitoring cloud spend, analyzing usage meters, or configuring billing alerts.

Broaden trigger terms to natural phrasings users would say, e.g. "Use when the user wants to monitor cloud costs, review M3ter meters, or analyze spending data."

DimensionReasoningScore

Specificity

Names the M3ter domain plus a few actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete capabilities, matching the anchor for domain + 1-2 non-comprehensive actions.

3 / 5

Completeness

It states both what ("M3ter integration. Manage data, records, and automate workflows.") and an explicit when ("Use when the user wants to interact with M3ter data."), but the when could be more specific with concrete trigger phrases, so it is below the 5 anchor.

4 / 5

Trigger Term Quality

The only natural trigger family is "M3ter" / "interact with M3ter data"; coverage is relevant but lacks common variations or synonyms, fitting the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

"M3ter integration" tied to a named product with a M3ter-specific trigger creates a clear niche with minimal conflict 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.