Name: autodesk-bim-360
Rating: 59.2 (1 reviews)
Author: membranedev

autodesk-bim-360

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

Quality

69%

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/autodesk-bim-360/SKILL.md

Quality

Content

76%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 highly actionable with executable CLI commands and a clear connection-state workflow, scoring well on actionability and conciseness. It is weaker on progressive disclosure (everything inlined, no referenced deep files) and has only implicit validation feedback loops.

Suggestions

Trim the opening definitional sentence ('Autodesk BIM 360 is a construction management software platform...') since Claude already knows the domain.

Extract the large action/state reference tables and clientAction schema into a separate reference file linked from the body to improve progressive disclosure.

Make validation feedback loops explicit for the connection polling and error states (e.g., 'If CONFIGURATION_ERROR: read `error`, fix, then re-run ensure') to raise workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands and minimal padding; the only over-explanation is the opening 'Autodesk BIM 360 is a construction management software platform...' sentence that describes a concept Claude already knows, fitting the score-4 anchor of efficient with minor trimmable instances.	4 / 5
Actionability	It provides copy-paste-ready CLI commands for every step (install, login, connection ensure/get, action list/run, request proxy) plus a flag table, fully executable and covering the common cases, matching the score-5 anchor.	5 / 5
Workflow Clarity	The connect -> poll -> CLIENT_ACTION_REQUIRED -> READY sequence is clearly laid out with state-based branching, but validation feedback loops are mostly implicit ('poll again', 'check the error field') rather than explicit fix-and-retry checkpoints, fitting score-4 with minor validation gaps.	4 / 5
Progressive Disclosure	The body is one continuous overview with section headers but no bundle files (references/scripts/assets absent) and no signaled references to deeper material; all detail is inlined, matching the score-3 anchor of some structure but content that could be split out 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 states a clear domain and includes both a 'what' and a 'when' clause, placing it in the upper-mid range. It loses points for generic action verbs and thin trigger-term coverage lacking synonyms or extensions.

Suggestions

Replace generic verbs ('Manage data, records') with specific concrete actions a user would perform on BIM 360 (e.g., 'browse projects, manage issues, fetch checklists, read field data').

Expand the 'Use when' trigger to mirror natural user phrasings and synonyms, e.g., 'Use when the user asks about BIM 360 projects, issues, field data, or Autodesk construction files'.

Add file-format or platform cues (e.g., '.pdf plans', 'Autodesk Construction Cloud') to strengthen trigger-term quality and distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the domain (BIM 360) and two concrete-ish actions ('Manage data, records' and 'automate workflows'), but 'data, records' are generic and the actions are not comprehensive, matching the score-3 anchor of a clear domain with 1-2 actions.	3 / 5
Completeness	It answers 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Autodesk BIM 360 data'), so both clauses are present, though the 'when' trigger is generic rather than concrete.	4 / 5
Trigger Term Quality	'interact with Autodesk BIM 360 data' provides one relevant keyword (BIM 360), but it lacks common synonyms, file extensions, or the varied natural phrases users say, matching the score-3 anchor of some relevant keywords with missing variations.	3 / 5
Distinctiveness Conflict Risk	The BIM 360 niche is fairly distinct and unlikely to trigger for unrelated skills, with only minor overlap risk against a generic data-management skill, fitting the score-4 anchor of mostly distinct with minor overlap.	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/autodesk-bim-360/SKILL.md
Commit: f484c82

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