ClawHub
Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

WordPress Article Publisher

v1.0.0

Automates the creation and publishing of articles on WordPress sites from provided content, streamlining blog and news post workflows.

⭐ 0· 79·0 current·0 all-time
by@hsyhph

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for hsyhph/wp-article-publisher.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "WordPress Article Publisher" (hsyhph/wp-article-publisher) from ClawHub.
Skill page: https://clawhub.ai/hsyhph/wp-article-publisher
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install wp-article-publisher

ClawHub CLI

Package manager switcher

npx clawhub@latest install wp-article-publisher
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
high confidence
!
Purpose & Capability
The name/description promise automated publishing to WordPress, but the package provides no implementation details, no API/endpoint, and does not declare any WordPress credentials or required binaries — something that would normally be necessary for this purpose.
!
Instruction Scope
SKILL.md is a generic, unfinished template with TODOs rather than runtime instructions. It does not describe how the agent should obtain site URLs, authenticate, or perform publishing; its vagueness grants broad, undefined discretion and makes the skill non-functional as-is.
✓
Install Mechanism
No install spec and no code files are included, so nothing will be downloaded or written to disk by the skill installer.
!
Credentials
A WordPress publisher would normally require at least site URL and credentials (API key, application password, OAuth tokens, or username/password). The skill declares no required env vars or primary credential — either it is non-functional or expects ad-hoc credential entry, which is disproportionate and unclear.
✓
Persistence & Privilege
The skill is not marked always:true and uses default invocation settings; it does not request persistent system-wide privileges.
Scan Findings in Context
[no-regex-findings] unexpected: The regex scanner found nothing (because there are no code files). For a WordPress publishing skill, you'd expect patterns referencing HTTP calls, wordpress/api, wp-json, or credential env names — their absence supports the conclusion that the skill is incomplete.
What to consider before installing
This skill is incomplete and currently just a template: it does not explain how or where it will publish, nor does it declare the credentials it would need. Do not rely on it until the author provides concrete implementation details. Before installing or using it, ask the developer to provide: (1) the exact publishing mechanism (REST API, XML-RPC, application passwords, or OAuth), (2) the required environment variables or credential flow, (3) the minimum permissions required (avoid admin-level credentials), (4) concrete examples of requests/responses or code snippets, and (5) whether any external code will be downloaded during install. If you must test, do so in a sandbox WordPress site with least-privilege credentials and review any added code or install steps before providing real site credentials.

Like a lobster shell, security has layers — review code before you run it.

latestvk97chthnv6btaza4b9bbcx7bd183wr08
79downloads
0stars
1versions
Updated 4w ago
v1.0.0
MIT-0
@hsyhph
latest
Download

Wp Article Publisher

Overview

[TODO: 1-2 sentences explaining what this skill enables]

Structuring This Skill

[TODO: Choose the structure that best fits this skill's purpose. Common patterns:

1. Workflow-Based (best for sequential processes)

  • Works well when there are clear step-by-step procedures
  • Example: DOCX skill with "Workflow Decision Tree" -> "Reading" -> "Creating" -> "Editing"
  • Structure: ## Overview -> ## Workflow Decision Tree -> ## Step 1 -> ## Step 2...

2. Task-Based (best for tool collections)

  • Works well when the skill offers different operations/capabilities
  • Example: PDF skill with "Quick Start" -> "Merge PDFs" -> "Split PDFs" -> "Extract Text"
  • Structure: ## Overview -> ## Quick Start -> ## Task Category 1 -> ## Task Category 2...

3. Reference/Guidelines (best for standards or specifications)

  • Works well for brand guidelines, coding standards, or requirements
  • Example: Brand styling with "Brand Guidelines" -> "Colors" -> "Typography" -> "Features"
  • Structure: ## Overview -> ## Guidelines -> ## Specifications -> ## Usage...

4. Capabilities-Based (best for integrated systems)

  • Works well when the skill provides multiple interrelated features
  • Example: Product Management with "Core Capabilities" -> numbered capability list
  • Structure: ## Overview -> ## Core Capabilities -> ### 1. Feature -> ### 2. Feature...

Patterns can be mixed and matched as needed. Most skills combine patterns (e.g., start with task-based, add workflow for complex operations).

Delete this entire "Structuring This Skill" section when done - it's just guidance.]

[TODO: Replace with the first main section based on chosen structure]

[TODO: Add content here. See examples in existing skills:

  • Code samples for technical skills
  • Decision trees for complex workflows
  • Concrete examples with realistic user requests
  • References to scripts/templates/references as needed]

Resources (optional)

Create only the resource directories this skill actually needs. Delete this section if no resources are required.

scripts/

Executable code (Python/Bash/etc.) that can be run directly to perform specific operations.

Examples from other skills:

  • PDF skill: fill_fillable_fields.py, extract_form_field_info.py - utilities for PDF manipulation
  • DOCX skill: document.py, utilities.py - Python modules for document processing

Appropriate for: Python scripts, shell scripts, or any executable code that performs automation, data processing, or specific operations.

Note: Scripts may be executed without loading into context, but can still be read by Codex for patching or environment adjustments.

references/

Documentation and reference material intended to be loaded into context to inform Codex's process and thinking.

Examples from other skills:

  • Product management: communication.md, context_building.md - detailed workflow guides
  • BigQuery: API reference documentation and query examples
  • Finance: Schema documentation, company policies

Appropriate for: In-depth documentation, API references, database schemas, comprehensive guides, or any detailed information that Codex should reference while working.

assets/

Files not intended to be loaded into context, but rather used within the output Codex produces.

Examples from other skills:

  • Brand styling: PowerPoint template files (.pptx), logo files
  • Frontend builder: HTML/React boilerplate project directories
  • Typography: Font files (.ttf, .woff2)

Appropriate for: Templates, boilerplate code, document templates, images, icons, fonts, or any files meant to be copied or used in the final output.

Not every skill requires all three types of resources.

Comments

Loading comments...