Name: ironclad
Rating: 61.6 (1 reviews)
Author: membranedev

ironclad

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

Quality

72%

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

Quality

Content

82%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 commands throughout and a well-structured connection/action workflow. Its main gaps are a small amount of unnecessary background prose and absent validation checkpoints for action/proxy execution.

Suggestions

Trim the opening "Ironclad is a contract lifecycle management platform..." background paragraph, which explains concepts Claude already knows.

Add a verification step after running actions or proxy requests (e.g. checking the response state/output before proceeding) for batch or mutating operations.

Consider moving the proxy flags table and detailed clientAction state handling into reference files to keep the overview lean.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command reference with a flags table, but the opening "Ironclad is a contract lifecycle management platform..." background paragraph and a few mild platitude lines ("so you can focus on the integration logic rather than auth plumbing") are over-explanation Claude largely doesn't need, fitting the 4 anchor.	4 / 5
Actionability	Copy-paste ready commands cover install, login, connection ensure, polling, action list/run, and proxy requests, with concrete flag tables and JSON examples spanning the common cases, matching the 5 anchor.	5 / 5
Workflow Clarity	A clear install→authenticate→connect→poll→search→run sequence with explicit state handling exists, but running actions and proxy requests lack any post-execution validation/verification checkpoint, so it lands at 4 rather than 5.	4 / 5
Progressive Disclosure	No bundle files exist and the ~149-line SKILL.md is organized into clear sections, but some detail (proxy flags, clientAction states) could be offloaded to references for a leaner overview, so it sits at 4 rather than 5.	4 / 5
	Total	17 / 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 correctly includes both a capability statement and a "Use when" trigger, and the Ironclad brand anchor gives it reasonable distinctiveness. Its weakness is generic action wording and thin trigger-term coverage that misses natural contract-related phrasings.

Suggestions

Replace generic actions with Ironclad-specific ones, e.g. "Manage contracts, approvals, and repositories; automate contract workflows."

Expand the trigger phrase with concrete user terms: "Use when the user mentions Ironclad, contracts, approvals, or contract workflows."

Add file/record-level specifics (e.g. Documents, Counterparties, Fields) so the description signals concrete capability coverage.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Ironclad domain plus a couple of actions, but those actions are generic rather than specific to contract management (contracts, approvals, repositories), so it sits at the 3 anchor rather than 4.	3 / 5
Completeness	Both a clear "what" ("Ironclad integration. Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Ironclad data") are present, though the "when" could be more specific, fitting the 4 anchor.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Ironclad data" anchors on the brand term, but lacks natural task-level synonyms (contracts, approvals, workflows), matching the 3 anchor for some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to the distinct Ironclad brand keeps it mostly distinguishable, but the broad "manage data, records, and automate workflows" wording carries minor overlap risk with other integration skills, matching the 4 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/ironclad/SKILL.md
Commit: f484c82

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