Name: badger-maps
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

badger-maps

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

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/badger-maps/SKILL.md

Quality

Content

65%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 highly actionable with executable CLI commands and a well-sequenced connection workflow including state feedback loops. Its main gaps are the absence of validation guidance around destructive actions (capping workflow clarity) and no progressive disclosure via separate reference files.

Suggestions

Add an explicit validation/confirmation checkpoint before destructive actions like 'Delete Account' (e.g. verify the target ID and confirm with the user before running delete-* actions).

Move the Popular actions catalog and proxy flag reference into a separate reference file and link to it from the body to improve progressive disclosure.

Trim the introductory paragraph and 'auth plumbing' prose that explain context Claude can already infer.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable commands and brief prose, but includes unnecessary padding such as the opening 'Badger Maps is a route optimization and CRM app... Field sales reps and teams use it to improve efficiency and close more deals' and 'so you can focus on the integration logic rather than auth plumbing'. Not a 4 because several sentences explain context Claude could infer; not a 2 because the bulk is lean command reference.	3 / 5
Actionability	Provides copy-paste-ready, executable commands for every phase (install, login, connection ensure, action list/run, request proxy) with flag tables covering common cases. Not below 5 because the examples are concrete and complete for the typical workflow; placeholders like CONNECTION_ID are standard and clearly marked.	5 / 5
Workflow Clarity	The connection flow is well sequenced with state-based checkpoints and a feedback loop (poll again after CLIENT_ACTION_REQUIRED), but the skill exposes destructive operations ('Delete Account') with no validation/verification step before running. Per the destructive-operations cap, this limits the score to 3; it cannot rise to 4 without a confirm/verify checkpoint around destructive actions.	3 / 5
Progressive Disclosure	The body is organized into clear sections, but no bundle files exist and no external references are signaled; content that could live in a separate file (the Popular actions table, proxy flag reference) is inlined. Not a 2 because section structure is reasonable; not a 4 because there are no one-level-deep references and the action catalog is inline.	3 / 5
	Total	14 / 20 Passed

Description

62%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 specific niche, and includes both a 'what' and a 'Use when' trigger, which is solid. Its weakness is generic action language and thin natural trigger terms that limit specificity and trigger-term quality.

Suggestions

Replace generic verbs with concrete Badger Maps actions, e.g. 'Plan sales routes, manage customer accounts and check-ins, and track leads'.

Add natural trigger phrases users would say, e.g. 'Use when the user wants to plan field-sales routes, manage Badger Maps accounts or check-ins, or work with leads'.

Mention key entity terms (routes, check-ins, accounts, leads) so the description surfaces for those requests.

Dimension	Reasoning	Score
Specificity	Names the domain (Badger Maps) and a couple of actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete; not comprehensive. It is not a 2 because it does name multiple action areas, and not a 4 because none of the actions are specific (no extract/create/route-level verbs).	3 / 5
Completeness	Explicitly answers both 'what' ('Badger Maps integration. Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Badger Maps data'). Not a 5 because the 'when' trigger is generic ('interact with Badger Maps data') rather than concrete trigger phrases; not a 3 because both halves are present.	4 / 5
Trigger Term Quality	Includes 'Badger Maps' and 'data' as relevant keywords with an explicit 'Use when' clause, but misses common natural variations a user would say (routes, check-ins, accounts, leads, field sales). Not a 2 because the trigger phrase is present and domain-relevant; not a 4 because natural synonyms and entity terms are largely absent.	3 / 5
Distinctiveness Conflict Risk	The 'Badger Maps' niche is specific and unlikely to trigger for unrelated skills, giving minimal conflict risk. Not a 5 because the generic 'manage data, records, and automate workflows' phrasing could overlap with other CRM/data skills; not a 3 because the named app makes it mostly distinct.	4 / 5
	Total	14 / 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/badger-maps/SKILL.md
Commit: f484c82

Reviewed: ~1 hour 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.