CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wordpress

Complete WordPress development workflow covering theme development, plugin creation, WooCommerce integration, performance optimization, and security hardening. Includes WordPress 7.0 features: Real-Time Collaboration, AI Connectors, Abilities API, DataViews, and PHP-only blocks.

Quality

69%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/wordpress/SKILL.md

The canonical home for this skill is wordpress in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

56%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 delivers real value in its WordPress 7.0 feature coverage with mostly executable code and a clearly sequenced 8-phase workflow, but it is padded with boilerplate structure trees and generic checklists Claude already knows, and it is a monolithic single file with no progressive disclosure. Trimming known-material and offloading the long API examples into reference files would address its two weakest dimensions.

Suggestions

Delete or drastically shorten the theme and plugin directory-structure trees and generic checklists (security checklist, standard actions like 'Enable CDN') — Claude already knows standard WordPress scaffolding.

Move the long per-feature code examples (AI Connector usage, Abilities API registration, WooCommerce product type) into references/ files (e.g. references/wp70-apis.md) and keep one-line pointers in SKILL.md.

Convert the quality gates and checklists into explicit validate-then-proceed feedback loops per phase (e.g. 'If the security scan fails: fix findings, then re-run before deploying').

DimensionReasoningScore

Conciseness

The body is noticeably verbose: it inlines stock boilerplate Claude already knows (the full 'theme-name/ style.css functions.php index.php...' tree, the standard plugin class scaffolding tree) and generic checklists ('Update WordPress core', 'Strong passwords enforced', 'Set up version control'). It also carries version-dated, time-sensitive detail ('WordPress 7.0 (April 9, 2026)', 'PHP 7.4 minimum (drops 7.2/7.3 support)') that is not placed in an old-patterns/deprecated section, which the guidelines penalize. The genuinely novel 7.0 feature content is diluted by this padding, keeping it below the mostly-efficient anchor 3.

2 / 5

Actionability

Most guidance is executable, copy-paste-ready PHP: the AI Connector chain ('wp_ai_client_prompt(...)->using_temperature(0.2)->generate_text()'), RTC-compatible 'register_post_meta' with 'show_in_rest' => true, the complete Abilities API registration with correct hooks ('wp_abilities_api_init') and a working handler, and REST route registration. Minor gaps keep it from 5: a placeholder ellipsis (''labels' => [...]') in register_post_type, and several phase action lists remain high-level directives ('Optimize database queries', 'Enable CDN') without commands.

4 / 5

Workflow Clarity

The 8 phases are clearly sequenced, each with 'Skills to Invoke' and concrete actions, and checkpoints exist via checklists (performance checklist with numeric targets, security checklist, and 'Before moving to next phase, verify' quality gates). It is not a 5 because validation checkpoints are checklists rather than explicit validate-then-proceed feedback loops, and error-recovery guidance (e.g. what to do when the security scan or performance target fails) is absent.

4 / 5

Progressive Disclosure

No references/, scripts/, or assets/ directories exist, so all ~585 lines live in SKILL.md. Section headers are clear and consistent, but large self-contained units that belong in separate files are inlined (the full WordPress 7.0 AI Connector API usage with schema examples, the complete Abilities API registration, theme/plugin structure templates). This matches the anchor for good internal structure but with content that should be split left inline, so it cannot score 4 ('most content is appropriately placed').

3 / 5

Total

13

/

20

Passed

Description

71%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 specific, well-scoped description with strong capability enumeration and natural WordPress vocabulary, but it omits any 'Use when...' trigger guidance, which both caps completeness and weakens its value as a routing signal. Adding an explicit trigger clause would lift it substantially.

Suggestions

Append an explicit trigger clause, e.g. 'Use when building or modifying WordPress sites, themes, plugins, or WooCommerce stores, or when the user mentions WordPress, WP, or WooCommerce.'

Add common synonyms and phrasings users actually say ('WP', 'CMS', 'online store', '.php themes') to broaden trigger coverage.

Narrow the security/performance claims or scope them as sub-cases of the WordPress workflow to reduce overlap risk with dedicated security-audit and performance skills.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete capabilities ('theme development, plugin creation, WooCommerce integration, performance optimization, and security hardening') and goes further to name specific WordPress 7.0 features ('Real-Time Collaboration, AI Connectors, Abilities API, DataViews, and PHP-only blocks'). This is comprehensive, multi-action coverage matching the anchor exactly; anchor 4 would require minor gaps in coverage, which are not present.

5 / 5

Completeness

It clearly answers 'what' ('Complete WordPress development workflow covering...'), but there is no 'Use when...' clause or equivalent explicit trigger guidance anywhere in the description, capping completeness at 3 per the judging guideline. It is not a 4 because the 'when' is entirely absent rather than merely implicit-but-present.

3 / 5

Trigger Term Quality

Natural terms users would say are present ('WordPress', 'WooCommerce', 'theme development', 'plugin'), giving good keyword coverage. A few natural variations are missing ('WP', 'CMS', 'store/e-commerce', file extensions), so it falls just short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

The WordPress/WooCommerce niche is clearly distinct with specific trigger vocabulary, but the breadth over 'performance optimization' and 'security hardening' creates minor overlap risk with dedicated skills the body itself invokes (e.g. 'security-auditor', 'wordpress-penetration-testing', 'web-performance-optimization'). Not a 5 because of that overlap with closely related skills.

4 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (596 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/wordpress/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.