Name: demandbase
Rating: 55.2 (1 reviews)
Author: membranedev

demandbase

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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

63%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 skill is highly actionable, with executable CLI commands and a clear, well-checkpointed connection workflow. Its weaknesses are a padding marketing intro, a redundant and empty "Popular actions" section, and a monolithic structure that does not split reference material into bundled files.

Suggestions

Cut the opening "Demandbase is a B2B marketing and sales platform..." paragraph, which states background Claude already knows.

Either populate the "Popular actions" section with actual commonly-used actions or remove it to eliminate redundancy with the search guidance.

Move the entity-type list and proxy flag reference into a bundled reference file and link to it, so the overview stays lean and progressive disclosure improves.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands, but the opening "Demandbase is a B2B marketing and sales platform..." paragraph explains background Claude does not need, and the "Popular actions" section redundantly repeats the action-list command without listing actions, fitting the mostly-efficient-with-some-unnecessary-explanation anchor.	3 / 5
Actionability	It provides concrete, copy-paste-ready bash commands for install, login, connection setup, action search/run, and proxy requests with real flags, with only minor gaps such as the "Popular actions" heading not actually listing popular actions.	4 / 5
Workflow Clarity	The install→login→connection→search→run sequence is clear, and connection setup includes an explicit polling feedback loop (BUILDING→READY, CLIENT_ACTION_REQUIRED→re-poll), though action execution lacks result/error validation, matching the clear-sequence-with-minor-validation-gaps anchor.	4 / 5
Progressive Disclosure	The 173-line body has clear section headers but is monolithic: the 21-item entity list and the proxy flag table are inlined with no references to separate files, and no bundle files exist, fitting the some-structure-but-could-be-better-organized anchor.	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 cleanly states what the skill does and when to invoke it, anchored to a distinct named platform. Its weakness is generic action verbs and limited trigger-term variation, which keep specificity and trigger quality at mid-range.

Suggestions

Replace generic verbs ("manage data, records") with concrete DemandBase capabilities such as "query account lists, contacts, and activities" to lift specificity.

Expand the trigger clause with natural user phrasings, e.g. "Use when the user wants to pull DemandBase accounts, contacts, or intent data."

Name a few DemandBase objects users commonly request (accounts, contacts, opportunities) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the DemandBase domain with a couple of actions, but the actions ("manage data", "manage records", "automate workflows") are generic rather than concrete, matching the anchor that names a domain and 1-2 actions without being comprehensive.	3 / 5
Completeness	Both halves are present — the what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with DemandBase data"), but the when clause is fairly generic and could be more specific, matching the anchor with both present but a less-than-explicit when.	4 / 5
Trigger Term Quality	The phrase "interact with DemandBase data" surfaces the core natural keyword ("DemandBase") plus "data"/"records", but it lacks common variations or synonyms, fitting the anchor for some relevant keywords with missing variations.	3 / 5
Distinctiveness Conflict Risk	"DemandBase integration" and the DemandBase-specific trigger give it a clear named niche with low conflict risk, though the generic "manage data, records" wording leaves minor overlap with other data-management skills, fitting the mostly-distinct anchor.	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/demandbase/SKILL.md
Commit: f484c82

Reviewed: 4 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.