wwud

Infers user decisions and learns preference rules from approvals and corrections.

1.6k|214|Updated Jun 4, 2025
One-click install
npx skills add https://github.com/Jamailar/RedBox --skill wwud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wwud
Source: https://github.com/Jamailar/RedBox/tree/main/desktop/builtin-skills/wwud
Command: npx skills add https://github.com/Jamailar/RedBox --skill wwud

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

AI assistants often stall at decision points that require user judgment, or make choices that clash with the user's actual taste and operating habits. This Skill models how the current app user would decide, approve, reject, or prioritize work, and turns their corrections into reusable decision rules.

Core Features & Use Cases

  • Decision Inference: Classifies decision points as routine, material, or restricted, then infers the user's likely choice using profiles, session context, and history, returning structured output with decision, confidence, evidence, risk, and fallback.
  • Preference Learning: Converts user approvals, rejections, and corrections into generalized learning events with confidence levels and optional expiry.
  • Role Logic Separation: Distinguishes user logic, creator profile logic, and advisor/member role logic, surfacing conflicts instead of blending them.
  • Use Case: When an automation approval queue item needs a go/no-go call, the Skill reads the user's profile and past approvals, recommends the likely choice with confidence, and escalates if the action is restricted.

Quick Start

Ask the assistant to invoke the wwud skill to decide which of two draft title options you would pick based on your past choices.

Frequently Asked Questions about wwud

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does the skill infer what the user would decide?

It classifies the decision as routine, material, or restricted, then reads the narrowest relevant evidence such as user profiles, creator profiles, session context, and approval history. It returns a structured result with decision, confidence, evidence, risk, and fallback.

How does the skill learn user preferences over time?

It records learning events when the user approves, rejects, or corrects a choice. Each event captures the source, decision, chosen and rejected options, a generalized principle, confidence level, and optional expiry, avoiding turning one-off exceptions into global rules.

Can the skill act on inferred decisions without asking the user?

No. It may decide routine choices at medium or high confidence and material choices only when high confidence and reversible. Restricted actions like publishing, spending, credential changes, or irreversible deletions always require explicit user confirmation.

What evidence sources does the skill use for decisions?

It prioritizes the current user message and task metadata, then session context, user and creator profiles, profile bundles, active advisor or member skills, knowledge files, manuscript state, and automation history. Generic personality guessing is avoided when app-local evidence exists.

When should this skill not be used?

It should not be treated as authorization for high-risk actions, and it should not blend conflicting user, creator, and advisor role logic into vague compromises. When confidence is low and impact is high, it asks one precise question instead of deciding.