diff --git a/README.md b/README.md
index ee11182..5bab4ab 100644
--- a/README.md
+++ b/README.md
@@ -1,8 +1,15 @@
-# WordPress API Pro — OpenClaw Skill
+# WordPress API Pro — Claude Code & OpenClaw Skill
 
 [![CI](https://github.com/Digitizers/wordpress-api-pro/actions/workflows/ci.yml/badge.svg)](https://github.com/Digitizers/wordpress-api-pro/actions/workflows/ci.yml)
+![Claude Code Skill](https://img.shields.io/badge/Claude_Code-Skill-d97757)
+![OpenClaw Skill](https://img.shields.io/badge/OpenClaw-Skill-purple)
+![WordPress](https://img.shields.io/badge/WordPress-REST_API-21759b)
+![License: MIT--0](https://img.shields.io/badge/License-MIT--0-green)
+![Version](https://img.shields.io/badge/version-3.7.0-blue)
 
-WordPress REST API integration skill for OpenClaw. Manage posts, pages, media, WooCommerce products, Elementor content, SEO metadata, ACF, JetEngine fields, and multi-site workflows programmatically — with explicit safety boundaries for agentic use.
+A production-grade **Claude Code & OpenClaw skill** for managing WordPress content via the REST API — posts, pages, media, WooCommerce, Elementor, SEO meta, ACF, JetEngine — with explicit safety boundaries for agentic use.
+
+This is not just a tool reference. It is an operational playbook for managing WordPress content responsibly: posts, pages, media, WooCommerce products, Elementor content, SEO metadata, and custom fields — with drafts-first, dry-run, and explicit-approval guardrails on every write.
 
 ## Features
 
diff --git a/wordpress-api-pro/SKILL.md b/wordpress-api-pro/SKILL.md
index b6517fc..9c26090 100644
--- a/wordpress-api-pro/SKILL.md
+++ b/wordpress-api-pro/SKILL.md
@@ -3,7 +3,7 @@ name: wordpress-api-pro
 version: 3.7.0
 license: MIT-0
 description: |
-  WordPress REST API integration for managing posts, pages, media, WooCommerce products, Elementor content, SEO meta, ACF, and JetEngine fields.
+  Production-grade WordPress REST API integration for managing posts, pages, media, WooCommerce products, Elementor content, SEO meta, ACF, and JetEngine fields.
   Use when you need to retrieve, draft, create, or update WordPress content programmatically on sites where the user has provided explicit credentials.
   For any operation that writes to a live site, get explicit user approval for the target site, post/product IDs, and final action before executing.
   Prefer drafts first. Run batch operations in dry-run mode first; use --execute only after review. Remote URL media downloads and local file reads are restricted by safety boundaries.