mikeparcewski/wickedizer
skills/wickedizer/SKILL.md
This skill should be used when writing, rewriting, or humanizing content. Removes AI tells while preserving meaning. Aligns output to team voice: direct, practical, action-oriented. Use when: humanizing AI-sounding prose, drafting a PR description or commit message, or aligning written output to team voice.
$ install --global
skillsauthnpx skillsauth add mikeparcewski/wicked-garden wickedizerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 8, 2026, 5:57 AM282.4s9 files scanned
SKILL.md
- name:
- wickedizer
- description:
- |
- This skill should be used when writing, rewriting, or humanizing content. Removes AI tells while preserving meaning. Aligns output to team voice:
- direct, practical, action-oriented.
- Use when:
- humanizing AI-sounding prose, drafting a PR description or commit
- portability:
- portable
- status:
- experimental
- phase_relevance:
- ["*"]
- archetype_relevance:
- ["*"]
Wickedizer: Clear, Credible, Human Writing
You are rewriting for trust and clarity, not for "vibes."
Your job:
- Remove AI-generated tells (fluff, hedging, promo language, chatbot artifacts)
- Preserve meaning, constraints, and domain terms
- Align to team voice: direct, pragmatic, outcome-driven
- NEVER invent facts, citations, names, or numbers
When This Skill Applies
Invoke automatically when:
- Writing or rewriting prose (emails, memos, exec summaries, PRDs, POVs)
- Producing slide text or bullets
- Writing work items (epics/stories/tasks/bugs in Jira, Linear, GitHub Issues, Azure DevOps, etc.)
- Drafting PR descriptions, commit messages, ADRs/RFCs, design docs
- Writing code comments, docstrings, READMEs, runbooks
Non-Negotiables
- Do not change meaning - Preserve commitments, constraints, scope, decisions
- Do not add facts - No invented stats, quotes, names, dates, attributions
- Keep useful structure - Headings, bullets, tables that aid scanning
- Keep terminology stable - Same concept = same name everywhere
- Match medium + audience - Slack ≠ PRD ≠ exec memo
Operating Process
Step 0: Classify the Artifact
Pick ONE: exec-summary | technical-doc | prd-requirements | work-item | email-comms | slide-bullets | code-comments | mixed
→ See refs/artifact-types.md for mode-specific rules.
Step 1: Extract Immutables
Identify and preserve:
- Facts, dates, numbers, names, owners
- Decisions, constraints, scope boundaries
- Domain terms and key nouns
- Acceptance criteria / definitions of done
Step 2: De-AI Pass
Remove:
- Chatbot artifacts ("hope this helps", validation filler)
- Promotional language and significance inflation
- Hedge stacking ("could potentially possibly")
- Vague attributions ("experts say")
- Cadence uniformity (same rhythm every sentence)
→ See refs/de-ai-pass.md for detection patterns.
Step 3: Clarity Pass
- Convert abstract nouns into actions
- Replace vague verbs with specific ones
- Ensure reader can answer: What changed? Why? Who owns it? What's next?
Step 4: Voice Pass
Apply team voice defaults:
- Assertive opening sentence with limited bold
- Scannable structure: short paragraphs, real bullets
- Consistent terms (no synonym cycling)
- Close with next steps / decision points
→ See refs/voice-profile.md for full voice guide.
Step 5: Trust Check
Before output, verify:
- [ ] No added facts, citations, names, or stats
- [ ] Meaning and constraints preserved
- [ ] Structure appropriate for medium
- [ ] Output contains at least one: decision, tradeoff, next step, open question, or measurable outcome
→ See refs/failure-modes.md for common problems.
Quick Reference: What to Remove
| Pattern | Fix | |---------|-----| | "Additionally / Furthermore / Moreover" spam | Delete most transitions | | "Pivotal / transformative / game-changing" | Remove or prove | | "Not just X, but Y" scaffolding | State directly | | Rule-of-three when 2 is correct | Use real count | | "Experts agree" without naming | Cite or delete | | "Hope this helps!" | Delete |
Quick Reference: What to Keep
| Element | When | |---------|------| | Bullets and lists | When they aid scanning | | Technical terms | When precise | | Numbers and dates | Always (don't generalize) | | Named constraints | Always | | Scope boundaries | Always |
Output Format
Return:
- The rewritten content
- Optional Change Log (3-8 bullets) if helpful:
- Removed fluff
- Clarified claims
- Preserved constraints
- Adjusted structure
Flexibility Note
These are defaults, not laws. Override when:
- Source material is intentionally casual or formal
- Audience expects different tone (legal, marketing)
- Context requires adaptation
The goal is credible and specific, not rigid adherence. Situation matters more than rules.
References
Core Process:
- Voice Profile - Tone, sentence structure, ending strong
- De-AI Pass - Detecting and removing AI tells
- Artifact Types - Mode-specific guidance
Principles:
- Structure - Document architecture and organization
- Complexity - KISS, YAGNI, DRY for writing
- Patterns - Reusable templates and structures
Quality:
- Review - Validation checklists by type
- Failure Modes - Common problems and fixes
Related Skills
mikeparcewski/skills/engineering/large-scale-migration
development
VerifiedTrustedCommunity
--- name: large-scale-migration description: How to execute a LARGE MECHANICAL change across any codebase with LEVERAGE instead of an agent-grind or hand-edits — a cross-cutting migration, refactor, rename, dialect/framework/DB port, library adoption, or bulk transform. The map→transform→gate pattern: a deterministic transform driven by a source-of-truth map, proven by a differential-equivalence gate. Use when the work is "migrate all X to Y", "rename Z everywhere", "port to a new DB/dialect/fra
8SKILL.mdUpdated Jun 3, 2026
mikeparcewski/wicked-garden:classify
testing
VerifiedTrustedCommunity
v11 LLM-based work-shape classifier. Replaces the regex archetype detector with the model's own reasoning. Reads the user's prompt, picks the right archetype(s) from the catalog, identifies signals (blast_radius, novelty, reversibility, etc.), and persists to SessionState so subsequent turns steer correctly. Use when: the prompt_submit hook emitted a `<wg classify-due />` directive, OR explicitly invoked at session start, OR when re-classifying after the user changes scope mid-session.
8SKILL.mdUpdated May 26, 2026
mikeparcewski/wicked-garden:archetype
tools
VerifiedTrustedCommunity
v11 work-shape archetype runner. When a prompt has been routed to one of the 9 archetypes (triage, explore, specify, decide, ship, review, incident, build, migrate), this skill is the entry point. It picks the right per-archetype playbook from refs/ and executes the phase shape declared in `.claude-plugin/archetypes.json`. Use when: a `<wg archetype="X">` or `<wg archetypes>` system-reminder tag appears, an explicit "let's run the X archetype" request, or when one of the per-archetype slash commands resolves to this skill.
8SKILL.mdUpdated May 8, 2026
mikeparcewski/intent
development
VerifiedTrustedCommunity
Show or set the session intent variable. Intent gates how loud the framework is — simple-edit (silent), feature/research (synthesis directive), rigor (full crew context). Auto-detected on turn 1; this skill overrides explicitly. Sticky for the session. Use when: "set intent", "intent override", "/wicked-garden:intent", "make the framework quiet", "force rigor", "what's my intent".
8SKILL.mdUpdated May 6, 2026