lab-ordering

Place lab supply orders from member requests — route by request header to Amazon Business, the Pritzker Lab Google Form, or a direct vendor; stage the cart/form and stop for human review before any purchase. Use when the user pastes an order request or asks to order supplies, place an order, or fill the Pritzker form.

Quality

91%

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

Quality

Content

86%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.

A well-structured, concise instruction skill with a clear multi-step workflow, strong validation checkpoints, and clean progressive disclosure to real reference files. The main opportunity is making the per-route execution detail and any validate→fix→retry loops more explicit inline.

Suggestions

Inline the key executable steps for each route (e.g. the Amazon cart/PO-field clicks or the Pritzker form submission-pause flow) rather than relying solely on the reference files, to close the actionability gap.

Add an explicit validate→fix→retry loop for the staging step (e.g. 'if a field fails to populate or stock is unavailable, flag it, re-attempt, then stop for review') to lift workflow clarity to the top anchor.

Surface the natural synonyms (purchase, requisition, restock) that currently live only in the body keywords into the description's trigger clause for stronger trigger-term coverage.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout: steps are terse, it never explains concepts Claude already knows (what a lab order or Amazon is), and every section (golden rules, decision tree, alert) earns its tokens.	5 / 5
Actionability	Concrete guidance throughout (specific config path, header-based decision rules, per-route field placement, login-state checks), but the executable browser-driving details are deferred to the reference files rather than given inline, leaving minor gaps.	4 / 5
Workflow Clarity	Steps 0–6 are clearly sequenced with explicit checkpoints (confirm funding, check login, check in-stock, mandatory stop-and-report) and a golden-rules checklist, but automated validate→fix→retry feedback loops are only partially present (config bootstrap), keeping it just below the top anchor.	4 / 5
Progressive Disclosure	Clear overview with well-signaled one-level-deep references — each route links to its own file and an 'Available resources' section lists all four real bundle files, with detailed content appropriately split out rather than inlined.	5 / 5
	Total	18 / 20 Passed

Description

92%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.

A strong, concrete description that states the workflow's key actions and gives explicit 'Use when...' trigger guidance with natural phrasing. Its only minor gap is a few natural synonyms living in the body rather than the description itself.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions comprehensively — 'route by request header to Amazon Business, the Pritzker Lab Google Form, or a direct vendor; stage the cart/form and stop for human review before any purchase' — naming the domain and three specific routing destinations plus the stop-for-review action.	5 / 5
Completeness	Explicitly answers both what ('Place lab supply orders... route... stage... stop for human review') and when ('Use when the user pastes an order request or asks to order supplies, place an order, or fill the Pritzker form') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural user phrases are present — 'order supplies, place an order, or fill the Pritzker form' — but a few common synonyms (e.g. 'purchase', 'requisition', 'restock') appear only in the body, not the description, so coverage is good rather than comprehensive.	4 / 5
Distinctiveness Conflict Risk	Clear niche (lab supply ordering) with distinct named triggers (Amazon Business, Pritzker Lab Google Form), making overlap with unrelated skills unlikely.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: brunoasm/my_claude_skills
Path: lab_ordering/SKILL.md
Commit: 5bdff99

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