Individual skill
decision-trees
Use when designing branching logic, eligibility rules, and fallback paths.
plugins/personalization-engine/skills/decision-trees/SKILL.md
Source commit 78e0419f4440bcb43bc80127e174ecf5adef1753
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 10, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 438
- Repository last updated
- Apr 3, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Personalization Decision Trees Skill
## When to Use
- Planning logic for dynamic experiences across web, in-app, email, or sales plays.
- Auditing existing decision flows for complexity, coverage, or compliance gaps.
- Simulating new branches before deploying rule or model updates.
## Framework
1. **Objective Mapping** – tie each node to business KPIs and user intents.
2. **Signal Hierarchy** – prioritize deterministic signals (consent, account tier, lifecycle) before behavioral or predictive ones.
3. **Fallback Design** – ensure every branch has a safe default when data is missing or risk flags appear.
4. **Experiment Hooks** – embed test slots at key decision points with guardrail metrics.
5. **Monitoring** – log path selections, success rates, and anomaly alerts for continuous tuning.
