CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

57

Quality

67%

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-claude/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

63%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 highly actionable with novel WordPress 7.0 API examples and a well-sequenced phased workflow, but it is padded by duplicated feature lists and standard structure trees, and it makes no use of progressive disclosure into reference files. Adding explicit validation feedback loops would further strengthen the workflow.

Suggestions

Split the WordPress 7.0 feature reference and the longer code examples (AI connector, Abilities API) into separate reference files (e.g., references/wp7-features.md, references/ai-connectors.md) and link to them from the body.

Deduplicate the 7.0 feature list — describe each feature once in the overview and reference it from phases rather than restating considerations per phase.

Add explicit validate→fix→retry checkpoints for destructive/batch phases (e.g., 'After deployment, run the test suite; on failure, roll back and re-deploy').

DimensionReasoningScore

Conciseness

Much of the WP 7.0 API code is genuinely novel, but the 7.0 features list is duplicated between the overview and each phase, and standard theme/plugin structure trees and generic checklists pad the body.

3 / 5

Actionability

Provides concrete, mostly copy-paste-ready PHP for AI connectors, Abilities API, block registration, and REST routes, with minor gaps like 'labels' => [...] and a stubbed WooCommerce product class.

4 / 5

Workflow Clarity

Eight phases are clearly sequenced with a Quality Gates checkpoint between phases, but explicit validate→fix→retry feedback loops for destructive steps (deployment, DB migrations, security hardening) are absent.

4 / 5

Progressive Disclosure

Good section structure with clear phase headers, but no bundle files exist and the 440-line monolith inlines WP 7.0 reference material and full code examples that belong in separate reference files.

3 / 5

Total

14

/

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.

The description conveys a strong, concrete 'what' with good specificity and a distinct WordPress niche, but it omits an explicit 'when to use' trigger clause, capping completeness at 3. Trigger term coverage is solid but could add common synonyms.

Suggestions

Add a 'Use when...' clause naming the natural trigger phrases (e.g., 'Use when building or hardening WordPress sites, developing themes/plugins, or integrating WooCommerce').

Include common WordPress synonyms and file-level terms (e.g., .php, wp-config.php, wp-content, Gutenberg blocks) to broaden trigger coverage.

Tighten distinctiveness by scoping the trigger to WordPress specifically (e.g., 'Use for WordPress 7.0+ projects') rather than implying general web development.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'theme development, plugin creation, WooCommerce integration, performance optimization, and security hardening' — giving comprehensive coverage of the WordPress dev workflow.

5 / 5

Completeness

Clearly states what the skill covers, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so 'when' is only weakly implied.

3 / 5

Trigger Term Quality

Includes natural terms a user would say ('WordPress', 'WooCommerce', 'theme', 'plugin'), but misses common variations and file-level synonyms like .php or wp-content.

4 / 5

Distinctiveness Conflict Risk

WordPress-specific scope is a clear niche with minimal conflict risk, though as a broad workflow bundle it has minor overlap with related development/ecommerce/security bundles.

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.

Validation14 / 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
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.