Name: strongdm
Rating: 60 (1 reviews)
Author: membranedev

strongdm

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

Quality

70%

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/strongdm/SKILL.md

Quality

Content

78%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 commands and a clear state-machine-driven connection workflow, though it carries minor verbosity and inlines reference-grade material that belongs in a bundled file. Step numbering and an explicit error-recovery loop would further sharpen the workflow.

Suggestions

Move the proxy-request flag table and detailed clientAction state breakdown into a references file (e.g., references/proxy.md) and link to it from SKILL.md to improve progressive disclosure.

Fix the inconsistent step numbering — define an explicit 'Step 2' or relabel '1b.' so the 'skip to Step 2' references resolve.

Add an explicit error-recovery feedback loop (e.g., on CONFIGURATION_ERROR: read error field, correct, re-run connection ensure) to strengthen workflow checkpoints.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable commands with brief, relevant explanations, but the opening paragraph describing what StrongDM is and scattered prose ('Membrane handles authentication... so you can focus on the integration logic') add minor over-explanation that could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready, fully executable commands for install, login, connection setup, action search/run, and proxy requests, with a complete flag table covering the common cases.	5 / 5
Workflow Clarity	The connection flow has a clear sequence with state-based checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but step numbering is inconsistent ('1b.' with an undefined 'Step 2') and there is no explicit error-recovery feedback loop, fitting 'clear sequence with most checkpoints; minor validation gaps'.	4 / 5
Progressive Disclosure	No bundle files exist and the single SKILL.md is well-sectioned, but ~140 lines of inlined CLI reference — including the proxy flag table and detailed clientAction sub-state descriptions — are bulk reference content that would be better split into a separate file, matching 'some structure but content that should be separate is inline'.	3 / 5
	Total	16 / 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 use it with a distinct StrongDM niche, but the capability list is generic and the trigger phrasing lacks concrete scenarios or synonyms. Tightening the action verbs and adding specific trigger situations would lift it.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete StrongDM actions such as granting/revoking access, querying resources, or reviewing audit trails.

Expand the 'Use when...' clause with specific trigger phrases users would say (e.g., 'Use when the user wants to grant or check access to servers, databases, or nodes in StrongDM').

Add common synonyms and the product's typical file/context cues (e.g., 'StrongDM grants', 'SDM resources') to broaden trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the StrongDM domain plus a couple of actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete (no grant/audit/resource specifics), matching the 'names domain and 1-2 concrete actions' anchor.	3 / 5
Completeness	Provides both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with StrongDM data'), but the trigger scenario is somewhat generic rather than concrete, matching the 'both what and when; when could be more specific' anchor.	4 / 5
Trigger Term Quality	Includes the natural keyword 'StrongDM' and the phrase 'interact with StrongDM data', but lacks synonyms or common variations users might say, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The 'StrongDM' niche is distinct and unlikely to trigger for unrelated skills, though the broad 'interact with StrongDM data' phrasing leaves minor overlap risk, fitting 'mostly distinct; minor overlap risk'.	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/strongdm/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.