Wicked Evolutions Knowledge Docs

Overview

This SKILL produces agent definition posts for knowledge.wickedevolutions.com. Each agent post follows the same structure: identity badges, a description of the agent’s role, a table of its operating lanes and key abilities, permission constraints, behavioral rules, any course prerequisites, a structured output format, and hand-picked related items.

The template (single-post.html) provides the page header, sidebar, breadcrumb, title, excerpt, category/tags, related query, post navigation, TOC rail, and footer. Content provides everything inside wp:post-content.

Data Requirements

Every agent post needs these fields before the build call. Collect them first — the build is a single ability call, so all data must be ready.

Block Map

The block map is the blueprint. It shows exactly how Gutenberg blocks nest, which attributes use preset slugs, and which use inline styles. Read it before writing any markup.

AGENT POST — 8 SECTIONS
═══════════════════════════════════════════

SECTION 1 — Badges
└── Group (section wrapper)
    └── Group (flex row, wrap, blockGap 8px)
        └── N× Paragraph (badge chip)
            preset: backgroundColor, textColor
            inline: fontSize 11px, textTransform, letterSpacing,
                    fontWeight 600, padding 4px/10px, radius 4px

SECTION 2 — Agent Description
└── Group (section wrapper)
    ├── Heading H2          preset: fontSize "large"
    └── Paragraph           preset: textColor "secondary", fontSize "medium"

SECTION 3 — Lanes
└── Group (section wrapper)
    ├── Heading H2
    ├── Paragraph           intro text
    └── Table               3×3 (Lane | Focus | Key Abilities)
        preset: fontSize "small"
        inline: hasFixedLayout
        <strong> for lane names · <code> for ability names

SECTION 4 — Permission Level
└── Group (section wrapper)
    ├── Heading H2
    ├── Paragraph           bold constraint statement
    └── Group (callout)
        preset: backgroundColor "green-tint"
        inline: border-left 3px green
        └── Paragraph       "Why read-only?" explanation

SECTION 5 — Behavioral Rules
└── Group (section wrapper)
    ├── Heading H2
    └── List (unordered)    7 items
        preset: textColor "secondary", fontSize "small"

SECTION 6 — Course Requirement
└── Group (section wrapper)
    ├── Heading H2
    ├── Paragraph           requirement statement
    └── Group (card)        green-tint/green-border, compact
        ├── Paragraph       linked title
        └── Paragraph       description

SECTION 7 — Output Format
└── Group (section wrapper)
    ├── Heading H2
    ├── Paragraph           intro text
    └── Code                structured report template

SECTION 8 — Related
└── Group (section wrapper)
    ├── Heading H2
    └── Columns (2) × 2 rows
        └── 4× compact glass card (title + description)

Badge Chip Patterns

Three color variants cover the badge use cases. Each is a Paragraph block with preset background/text colors and inline typography:

Build Log

Proven on the Diagnostician agent (post 225, knowledge.wickedevolutions.com). One ability call produced the complete post.

Block Type Counts

Preset vs Inline Tally

Duplicating to Other Agents

The block structure stays identical — only text content changes. Badge color variants should match the agent’s characteristics.

1. Duplicate the base post — Use content/duplicate on post 225, or create a new post with the same block structure via content-create.
2. Swap the content — Change: title, excerpt, badges (different permission/type/lane), description, lanes table, permission level, behavioral rules, output format, related items.
3. Assign taxonomy — Set the correct category and tags via taxonomies/assign-to-content.

Related