CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

purchasing

Create approved purchase orders with the create-purchase-order tool

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./libraries/typescript/packages/server/examples/skills-over-mcp/skills/purchasing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 admirably concise and gives a clear, sequenced workflow with an approval checkpoint, but it is held back by a missing code example and a broken reference to a nonexistent templates file. Fixing the broken link and adding a concrete call example would materially raise the score.

Suggestions

Create the missing `templates/purchase-order.md` file (or correct the path) so the referenced template link resolves.

Add a short executable example of the `create-purchase-order` call showing the SKU and quantity arguments.

Add an explicit verification step after order creation (e.g. confirm the returned order ID against the template) to strengthen the workflow's feedback loop.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it states only the necessary steps with no padding or explanation of concepts Claude already knows, matching the lean-and-efficient anchor.

5 / 5

Actionability

It gives concrete guidance ("call `create-purchase-order` with the SKU and requested quantity") naming the tool and exact arguments, but lacks a copy-paste code example or call signature, leaving a minor gap.

4 / 5

Workflow Clarity

A clear sequence is present (read policy → obtain approval → call tool → confirm with template) with an explicit approval checkpoint and a clarification feedback loop referenced in the policy, though output verification is only implicit.

4 / 5

Progressive Disclosure

Structure is good with one-level-deep references, but `templates/purchase-order.md` is referenced and the templates directory does not exist, so navigation is impaired by a broken link.

3 / 5

Total

16

/

20

Passed

Description

53%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 concise, third-person, and names a concrete action with a specific tool, but it lacks any explicit "when to use" trigger guidance and only covers a single action. Adding a Use-when clause and a couple of natural trigger phrases would lift completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to create or approve a purchase order, request procurement, or order supplies."

Include natural synonyms/variations such as "PO", "procurement", or "requisition" to broaden trigger-term coverage.

Mention additional concrete actions if any exist (e.g. checking status, canceling) to improve specificity beyond the single create action.

DimensionReasoningScore

Specificity

Names the domain (purchase orders) and one concrete action ("Create approved purchase orders") but offers only a single action with no comprehensive coverage, matching the 1-2 concrete actions anchor.

3 / 5

Completeness

It clearly states what the skill does (create approved purchase orders) but includes no "Use when..." clause or equivalent trigger guidance, so completeness is capped at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

"purchase orders" is a natural term a user would say, but only that single phrase appears with no synonyms or variations, matching the some-relevant-keywords anchor.

3 / 5

Distinctiveness Conflict Risk

"Create approved purchase orders with the create-purchase-order tool" carves a clear niche with a named tool, with only minor overlap risk against generic ordering skills.

4 / 5

Total

13

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

mcp-use/mcp-use

Path

libraries/typescript/packages/server/examples/skills-over-mcp/skills/purchasing/SKILL.md

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.