SKILLEMALL.ai

BD BlogForge — End-to-End Blog Post Generator

A comprehensive AI-powered blog post generator that creates SEO-optimized, human-sounding content and optionally publishes directly to Medium, WordPress, or Ghost. Supports Anthropic Claude, OpenAI GPT, and local Ollama models. Includes built-in readability analysis, humanization post-processing, and multi-platform publishing.

ClawHub Agent Skills author: Shadow Rose v1.0.3 MIT-0 6 files body ≈ 2 226 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process D 39/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

GeneratorWordPressAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
87/100
safety, quality, tests
Safety 60%
100
Quality 40%
67
Run on models
none yet
Process rating
D
39/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "env"

Process rating: all ten parameters 39/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 16 mutating operations with no state check
  • 40Consistency. Frontmatter name (BlogForge — End-to-End Blog Post Generator) differs from the folder (blog-forge)
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 100Steps. 32 steps
  • 100Execution cost. Instruction body is 2226 tokens

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +3Description length 328: enough signal without eating the budget
  • +4Structure: 17 headings
  • +3Step-by-step instructions: 32 items
  • +4Has examples (8 code blocks)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.

External checks

ClawHub: suspicious
This blog-writing skill mostly matches its stated purpose, but it should be reviewed because it advertises AI-detection evasion and can create drafts on connected publishing accounts.
LLM: suspicious (high) · VirusTotal: · 29 May 2026