Name: structurizr
Rating: 53.6 (1 reviews)
Author: membranedev

structurizr

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

Quality

60%

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

Quality

Content

71%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 state machine, but it is held back by an unnecessary product overview, missing error-recovery feedback loops, and a monolithic single-file structure with no progressive disclosure.

Suggestions

Remove or condense the opening 'Structurizr is a modeling tool...' paragraph and the overview taxonomy that Claude already knows, to tighten token efficiency.

Add an explicit validate/retry step for action runs and proxy requests (e.g. check the output/error field and retry with adjusted parameters) to strengthen the workflow feedback loop.

Move the proxy options table and the deep connection-state reference into separate files (e.g. references/proxy.md, references/connection-states.md) with one-level-deep links from SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with ready-to-run commands, but includes some content Claude already knows — the overview paragraph explaining what Structurizr is and who uses it — and minor padding like restating the search command under 'Popular actions'.	3 / 5
Actionability	It provides fully executable, copy-paste-ready membrane CLI commands with concrete flags (--json, --wait, --connectionId, --input) and a clear options table for the proxy, covering the common cases directly.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-driven branching (READY / BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and polling checkpoints, but there is no explicit validate-then-retry feedback loop for failed action runs or proxy errors.	4 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets absent), so everything is inlined in one SKILL.md; the overview taxonomy and API/proxy option table could live in separate referenced files, and there are no one-level-deep references to signal navigation.	3 / 5
	Total	15 / 20 Passed

Description

50%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 anchored to a named product and includes an explicit 'Use when' trigger, but its action language is generic and unrelated to Structurizr's actual modeling/diagramming purpose, undercutting specificity and trigger quality.

Suggestions

Replace generic verbs with Structurizr-specific actions, e.g. 'Create and edit Structurizr workspaces, software systems, containers, and diagram views'.

Add the natural trigger terms users say: 'diagrams', 'software architecture', 'C4 model', 'system context and container views'.

Tie the 'Use when' clause to concrete scenarios, e.g. 'Use when the user wants to model or diagram a software system with Structurizr'.

Dimension	Reasoning	Score
Specificity	It names the domain (Structurizr) but the actions — "Manage data, records, and automate workflows" — are generic and not specific to Structurizr's modeling concepts (workspaces, models, views, diagrams); no concrete Structurizr actions are listed.	2 / 5
Completeness	It states a "what" (manage data, records, automate workflows) and an explicit "when" ("Use when the user wants to interact with Structurizr data"), but the "what" is vague relative to Structurizr's actual modeling purpose, keeping it below 5.	4 / 5
Trigger Term Quality	The only natural trigger phrase is "interact with Structurizr data"; it lacks the natural terms users would say (diagrams, models, software architecture, views) and only repeats the product name.	2 / 5
Distinctiveness Conflict Risk	The Structurizr brand name makes it largely distinct from other skills, though the generic "manage data, records, and automate workflows" phrasing could overlap with broad data-management skills, so it is not a clear niche with minimal conflict.	4 / 5
	Total	12 / 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/structurizr/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.