CtrlK
BlogDocsLog inGet started
Tessl Logo

woo-guard

Review generated or changed WooCommerce code — extensions, payment and shipping integrations, checkout customizations, and order/product logic — before it ships. Best used reactively after an agent writes, edits, or reviews code touching WooCommerce APIs: wc_get_order, wc_get_orders, wc_get_product, WC() cart or session, woocommerce_* hooks, Store API endpoints, payment gateways, order or product meta, HPOS, subscriptions, or bookings. Use on 'review this Woo plugin', 'is this HPOS compatible', or after tasks like 'write a WooCommerce extension', 'add a checkout field', 'hook into the order flow', or 'update stock'. Enforces HPOS-safe order access, CRUD over direct meta, feature-compatibility declarations, server-side checkout validation, money-handling discipline, and hooks over template overrides. DO NOT USE for WordPress code without WooCommerce APIs (use wp-guard), generic code review (use clean-code-guard), test review (use test-guard), or store configuration and admin-screen questions.

80

Quality

100%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplary guard-pass skill body: tight, actionable, with explicit validation checkpoints and well-structured reference offloading. It adds only what Claude would not already know and provides concrete executable guidance throughout.

DimensionReasoningScore

Conciseness

Lean and high-signal — assumes Claude's competence, names exact APIs and forbidden patterns without explaining what WooCommerce or CRUD is. The brief motivational intro is tightly bound to the rules rather than padded filler.

3 / 3

Actionability

Fully executable guidance: exact function calls (wc_get_order, FeaturesUtil::declare_compatibility), exact validation hooks (woocommerce_checkout_process), forbidden-pattern lists, and a copy-paste grep-based self-check.

3 / 3

Workflow Clarity

Clear sequencing across three modes plus a 4-step project-adapt pre-flight, and an 8-step self-check validation checkpoint with an explicit feedback loop ('If any answer is wrong, fix it before showing the user').

3 / 3

Progressive Disclosure

Body is an overview that offloads detail to four real one-level-deep references, each signaled inline and listed with a one-line description; all referenced paths exist as verified bundle files.

3 / 3

Total

12

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 high-quality description: third-person voice, concrete capability list, explicit reactive-use triggers, and a clear negative boundary. It fully answers what the skill does and when to invoke it without verbosity.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and enforcement behaviors — 'extensions, payment and shipping integrations, checkout customizations, and order/product logic' plus 'Enforces HPOS-safe order access, CRUD over direct meta, feature-compatibility declarations'. Beyond a domain-plus-some-actions level 2.

3 / 3

Completeness

Explicitly answers both what (review/enforce list) and when ('Best used reactively after an agent writes, edits, or reviews code...', 'Use on...') with explicit trigger phrasings, plus a DO NOT USE boundary.

3 / 3

Trigger Term Quality

Strong natural-term coverage users would actually say: 'review this Woo plugin', 'is this HPOS compatible', 'add a checkout field', 'hook into the order flow', 'update stock', alongside concrete API tokens like wc_get_order and woocommerce_* hooks.

3 / 3

Distinctiveness Conflict Risk

Clear WooCommerce-code-review niche with distinct triggers and an explicit negative boundary steering away WordPress-only, generic, and test-review work to other guards.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
amElnagdy/guard-skills
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.