Name: procore
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

procore

Procore integration. Manage Projects, Users, Roles, Organizations. Use when the user wants to interact with Procore data.

Quality

66%

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

Quality

Content

60%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 skill delivers highly actionable, executable CLI guidance with a clear connection workflow and validation feedback loops. Its major weakness is the massive inlined, duplicated entity catalog that bloats the token budget and should be split into a reference file.

Suggestions

Move the ~280-line entity catalog into a separate references file (e.g., references/entities.md) and replace it in SKILL.md with a one-line pointer plus a short representative sample, eliminating the duplicated 'Resource Resource ...' padding.

Clean up or remove the auto-generated 'Resource Resource Resource X' duplications entirely, as they are pure noise.

Tighten the opening paragraph ('Procore is a construction management software platform...') since Claude already knows the domain; keep only what is specific to this integration.

Enumerate the connection steps explicitly (Step 1, Step 2...) and fix the dangling 'skip to Step 2' reference so the workflow sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose due to a ~280-line auto-generated entity list (including nonsensical duplications like 'Resource Resource Resource Owner') that is heavily padded, although the surrounding CLI guidance is efficient; this fits the noticeably-verbose anchor rather than the severely-padded score-1 because real actionable content coexists.	2 / 5
Actionability	Provides copy-paste-ready, fully executable commands throughout ('npm install -g @membranehq/cli@latest', 'membrane connection ensure', 'membrane action run ... --input', 'membrane request') with flags, JSON examples, and a popular-actions table covering common cases.	5 / 5
Workflow Clarity	The connect→poll-until-ready→handle-clientAction→search→run→proxy sequence has explicit validation checkpoints and a state-based feedback loop, but step numbering is loose (it references a 'Step 2' that is not cleanly enumerated), placing it just below the score-5 anchor.	4 / 5
Progressive Disclosure	No bundle files exist and the entire 280-line entity catalog is inlined in SKILL.md despite clearly belonging in a separate reference file; section headers provide minimal structure, matching the 'content that clearly belongs in separate files is inlined' anchor rather than a fully monolithic wall.	2 / 5
	Total	13 / 20 Passed

Description

73%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 cleanly states a niche domain and includes an explicit 'Use when' trigger clause, with strong distinctiveness. Its main weakness is specificity, leaning on the generic verb 'Manage' over a richer action vocabulary.

Suggestions

Replace the single generic verb 'Manage' with several distinct concrete actions (e.g., 'List, create, update, and query Projects, Users, Roles, and Organizations') to raise specificity.

Add a couple of natural trigger phrasings users might say (e.g., 'Procore projects', 'construction RFIs/submittals') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the Procore domain and several concrete entities ('Manage Projects, Users, Roles, Organizations'), but relies on a single generic verb 'Manage' rather than enumerating distinct actions, so it is not comprehensive like the score-4 anchor.	3 / 5
Completeness	Both 'what' (Procore integration managing Projects/Users/Roles/Organizations) and an explicit 'when' ('Use when the user wants to interact with Procore data') are present, but the 'what' is terse and could be more specific, so it sits below the fully concrete score-5 anchor.	4 / 5
Trigger Term Quality	Includes natural user-facing terms ('Procore', 'Procore data', 'interact with Procore') with an explicit trigger clause, though a few common synonyms or phrasings are missing, matching the good-but-incomplete anchor.	4 / 5
Distinctiveness Conflict Risk	Procore is a specific construction-management niche with distinct triggers ('Procore', 'Procore data'), giving it a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	16 / 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/procore/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.