Name: nmbrs
Rating: 52.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

nmbrs

Nmbrs integration. Manage data, records, and automate workflows. Use when the user wants to interact with Nmbrs data.

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/nmbrs/SKILL.md

Quality

Content

61%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-organized, largely executable CLI reference with a decent connection-state feedback loop, but it is weakened by duplicated discovery instructions, broken step numbering, and a vague "Popular actions" section that lists nothing.

Suggestions

Fix the broken step numbering: define the referenced "Step 2" (or remove the cross-references) and label "1a"/"1b" consistently so the connect-to-act flow is unambiguous.

Merge the duplicate action-discovery instructions in "Searching for actions" and "Popular actions", and either list actual popular Nmbrs actions or drop the placeholder section.

Trim the "Nmbrs is a cloud-based HR and payroll software..." opener, which explains something Claude can infer, to recover token budget.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but it carries unnecessary material — a "what Nmbrs is" opener and duplicated action-discovery instructions in both "Searching for actions" and "Popular actions" — that could be tightened.	3 / 5
Actionability	It provides copy-paste-ready commands throughout (login, connection ensure, action run, request) plus a flags table, covering the common cases with only minor gaps such as the vague "Popular actions" section that lists none.	4 / 5
Workflow Clarity	The connection-readiness flow has real checkpoints (poll until READY, branch on state, re-poll), but sequencing is muddled by an undefined "Step 2" reference and a "1b" with no matching "1a", leaving validation gaps in the overall flow.	3 / 5
Progressive Disclosure	No bundle files exist and none are needed; the body is well-sectioned (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no nested references, though the redundant "Popular actions" section is a minor organization gap.	4 / 5
	Total	14 / 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 correctly pairs a "what" with an explicit "Use when" trigger and names a distinct product, but its action verbs are generic and it omits the natural domain terms (payroll, HR) a user would actually say.

Suggestions

Replace generic verbs with concrete Nmbrs capabilities, e.g. "Run payroll, manage employee and company records, retrieve payslips and journal entries."

Add the natural trigger terms users say — payroll, HR, employee data — not just "interact with Nmbrs data".

Tighten the domain signal so it is distinguishable from other Membrane integration skills that follow the same template.

Dimension	Reasoning	Score
Specificity	It names the domain ("Nmbrs integration") but the actions — "Manage data, records, and automate workflows" — are generic rather than concrete Nmbrs capabilities (no payroll/HR/employee specifics), fitting the "names domain, actions minimal or generic" anchor.	2 / 5
Completeness	Both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Nmbrs data") are present; the "what" could be more specific, matching the "both present, when could be more specific" anchor.	4 / 5
Trigger Term Quality	The phrase "interact with Nmbrs data" is a natural trigger and "Nmbrs" is the key keyword, but common domain synonyms users would actually say (payroll, HR, employee) are missing, so coverage is partial.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product "Nmbrs" gives a distinct trigger with minimal conflict risk, but the generic action verbs could overlap with sibling Membrane integration skills that share this template.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/nmbrs/SKILL.md
Commit: f484c82

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.