CtrlK
BlogDocsLog inGet started
Tessl Logo

autodesk-revit

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

58

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/autodesk-revit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-sequenced, state-aware connection workflow including feedback loops. Its main weakness is conciseness: the introductory BIM explanation and a few filler lines pad the context with knowledge Claude already has.

Suggestions

Remove or condense the opening paragraph defining Revit/BIM and the 'Use action names and parameters as needed' line, since Claude already knows these concepts.

Consider moving the full clientAction schema detail and the proxy options table into a reference file to keep SKILL.md a lean overview.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete CLI commands, but the opening paragraph explaining what Revit/BIM is and filler like 'Use action names and parameters as needed' explain concepts Claude already knows and could be trimmed.

3 / 5

Actionability

It provides copy-paste-ready, fully executable commands throughout (membrane login, connection ensure, action list/run, request) with concrete flags and a documented options table covering the common cases.

5 / 5

Workflow Clarity

The install → authenticate → connect → poll-until-ready → search → run sequence is clear with explicit state checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a re-poll feedback loop, with only minor gaps.

4 / 5

Progressive Disclosure

Content is well-organized into clear sections in a single file with no bundle files present; most material is appropriately placed, though some detail (full clientAction schema, proxy options) is inlined rather than split out.

4 / 5

Total

16

/

20

Passed

Description

61%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 has an explicit trigger clause and a clearly distinct niche, but its capability list is generic ('manage data, records, automate workflows') and lacks concrete Revit-specific actions and synonyms. Tightening the action verbs and adding natural terms like BIM or .rvt would lift the weaker dimensions.

Suggestions

Replace generic verbs with concrete Revit capabilities (e.g., 'Query model elements, read and update parameters, list views and worksets') instead of 'Manage data, records'.

Add natural synonyms and file extensions to the trigger clause (e.g., 'Use when working with Revit models, BIM data, or .rvt files').

Make the 'when' clause more specific about which user intents trigger the skill (e.g., querying elements vs. running automation workflows).

DimensionReasoningScore

Specificity

The description names the domain (Autodesk Revit) but the listed actions — 'Manage data, records, and automate workflows' — are minimal and generic rather than concrete capabilities, matching the 'names domain, actions minimal/generic' anchor.

2 / 5

Completeness

It explicitly states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Autodesk Revit data'), satisfying the 'has both' anchor, though the 'what' is generic and the 'when' could be more specific.

4 / 5

Trigger Term Quality

'Autodesk Revit' and 'interact with Autodesk Revit data' are relevant natural terms, but common variations and synonyms like BIM, Revit models, or .rvt file extensions are missing.

3 / 5

Distinctiveness Conflict Risk

'Autodesk Revit integration' targets a clear, specific niche with a distinct trigger phrase, giving minimal conflict risk with other skills.

5 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.