Name: concord
Rating: 58.4 (1 reviews)
Author: membranedev

concord

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

Quality

67%

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

Quality

Content

68%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 concrete, executable Membrane commands and a solid connection-state workflow, but it is held back by an unnecessary introductory paragraph and a destructive-operations section that lacks verification checkpoints. Removing the padding and adding a verify step before deletes would lift the weakest dimensions.

Suggestions

Add a verification checkpoint before destructive actions, e.g. 'Before running delete-agreement/delete-clause/delete-folder, run the matching get-* action to confirm the target, then confirm with the user before deleting'.

Trim the opening marketing paragraph and either flesh out or remove the cryptic 'Concord Overview' bullet list (Document/Section/Workspace/User/Template), which currently conveys no actionable meaning.

Consider moving the large 'Popular actions' table and the proxy flag reference into a separate reference file to keep SKILL.md a lean overview, improving progressive disclosure for a skill of this length.

Dimension	Reasoning	Score
Conciseness	Mostly efficient operational commands, but the opening paragraph explaining what Concord is ('Concord is a contract management platform. It helps legal, sales, and procurement teams...') and the cryptic 'Concord Overview' bullet list (Document/Section/Workspace/User/Template) add padding Claude does not need.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands for the full lifecycle (install, login, connection ensure, poll, action list/run, request proxy) plus a popular-actions table and flag reference covering the common cases.	5 / 5
Workflow Clarity	The connection flow is well-sequenced with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again feedback loop, but destructive operations in the actions table (delete-agreement, delete-clause, delete-folder) ship with no verify-before-delete checkpoint, invoking the destructive-ops cap.	3 / 5
Progressive Disclosure	Content is organized into clear sections (Install, Authentication, Connecting, Searching, Popular actions, Running, Proxy, Best practices) with everything appropriately inline and navigable; the only gap is the unexplained 'Concord Overview' stub and the absence of any external reference files despite the skill's length.	4 / 5
	Total	15 / 20 Passed

Description

66%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 functional and clearly distinguishes Concord as its niche with an explicit 'Use when' trigger, but its action vocabulary is generic ('data, records, workflows') rather than reflecting Concord's contract-management specifics. It would benefit from concrete contract-domain terms.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with Concord-specific actions such as 'list and create agreements, clauses, folders, and reports'.

Broaden the trigger phrase to include natural terms users say, e.g. 'Use when the user wants to manage Concord contracts, agreements, or clauses'.

Mention the key entities (agreements, clauses, folders, reports) so the trigger aligns with the actions surfaced in the body.

Dimension	Reasoning	Score
Specificity	Names the Concord domain plus a few actions ('Manage data, records, and automate workflows'), but these actions are generic rather than the concrete contract-specific operations (agreements, clauses, folders) the body actually exposes, so coverage is not comprehensive.	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Concord data') are present and explicit, but the trigger could be more specific with concrete contract-related phrases.	4 / 5
Trigger Term Quality	Includes the natural trigger 'Concord' and a usable 'Use when the user wants to interact with Concord data' phrase, but offers few synonyms or varied natural terms a user might actually say (e.g. 'contracts', 'agreements').	3 / 5
Distinctiveness Conflict Risk	'Concord integration' names a specific platform with a distinct trigger ('interact with Concord data'), giving it a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	15 / 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/concord/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.