Yield

Conversational Compounding Engine — models every bot message as a financial investment that compounds trust, micro-commitments, and conversion momentum over...

Security Scan

The skill's code, examples, and instructions are internally consistent with a local, no‑API

Purpose & Capability

The name/description (conversational compounding) align with the included JS implementation: signal detection, portfolio math, strategy selection and examples for Discord/Telegram/OpenClaw. There are no requested env vars, binaries, or external APIs that would be unexpected for this purpose.

Instruction Scope

SKILL.md and examples keep processing local and explain how to inject directives into system prompts or bot code. Note: examples include a 'generateYieldSystemPrompt' and 'HARVEST' directives that explicitly recommend presenting offers (e.g., "THIS IS THE MOMENT" / "Present your offer NOW") and an example 'exportForCRM' that serializes conversation state — this is expected for a conversion optimization tool but is behavioral/persuasive in nature and can lead to collection/export of PII if integrated with CRMs or analytics. There are no instructions to read unrelated system files or env vars.

Install Mechanism

No install spec or external download; package is code-only in the bundle and claims zero dependencies. Nothing writes to disk on install. This is low-risk from an installation mechanism perspective.

Credentials

The skill declares no required env vars or credentials and the code does not access environment variables. Example integrations obviously require platform tokens (Discord/Telegram) but those are external to the skill and expected for those adapters.

Persistence & Privilege

The engine keeps in-memory conversation state and provides export/import functions for persistence (toJSON/fromJSON). always:false and no cross-skill/system modifications. The ability to export conversation state is expected, but operators should carefully control where exported data is sent and who has access.

Assessment

This skill appears to implement exactly what it claims: a local conversational 'yield' engine that detects lexical signals, tracks a portfolio of engagement assets, and recommends response strategies. Before installing or enabling it: 1) Be aware it's explicitly designed to optimize for conversion (it recommends 'HARVEST' / present offers) — review whether you want automated conversion nudges in your bot. 2) The examples include exporting conversation state for CRM/analytics — ensure you have user consent and sanitize PII before exporting. 3) If you plan to embed the generated system-prompt directives into an LLM system prompt, audit them carefully (they can strongly change model behavior) and avoid blindly injecting them into high-privilege agent contexts. 4) Review the omitted test file and any additional examples for hidden telemetry or network calls before deploying to production. 5) Run integration tests in a sandbox and confirm no unexpected outgoing network requests occur when the engine is used.

YIELD — The Conversational Compounding Engine

"Every message is an investment. Yield makes them compound."

Purpose

YIELD is a universal bot skill that applies financial compounding mathematics to conversations. While every other skill focuses on what a bot says, YIELD focuses on the economics of saying it — treating trust, commitment, curiosity, and urgency as portfolio assets that grow, decay, or compound with every message exchange.

No bot on any platform currently models this. They all operate message-by-message like day traders. YIELD turns your bot into Warren Buffett.

Core Concept: Conversational Portfolio Theory

Every conversation builds (or destroys) five classes of psychological assets:

Asset Class	Behavior	Analogy
Trust Bonds	Compounds slowly	Government bonds
Commitment Anchors	Stacks and locks	Real estate equity
Urgency Options	Decays rapidly	Options contracts
Curiosity Futures	Pulls forward	Futures contracts
Authority Equity	Grows with proof	Blue-chip stocks

YIELD tracks these assets in real-time and recommends which asset to invest in next based on the current portfolio balance and the conversation's trajectory.

How It Works

Phase 1: Signal Detection (Every Message)

On every inbound user message, YIELD extracts signals — lightweight pattern matches that cost zero computation:

AGREEMENT signals    → +trust, +commitment
QUESTION signals     → +curiosity, +engagement
OBJECTION signals    → -trust, +urgency (they care enough to object)
PERSONAL signals     → +trust, +commitment (vulnerability = investment)
HESITATION signals   → -momentum, +friction
ENTHUSIASM signals   → +momentum, +curiosity
TIME PRESSURE signals→ +urgency (decaying asset)
SOCIAL PROOF seeking → -authority, +curiosity

Phase 2: Portfolio Valuation (Running State)

YIELD maintains a lightweight Yield Score for each asset class:

yield_state = {
  trust:       0.0 → 1.0   (compounds at 1.12x per positive signal)
  commitment:  0.0 → 1.0   (stacks: each micro-yes adds 0.08-0.15)
  urgency:     0.0 → 1.0   (decays at 0.85x per message without reinforcement)
  curiosity:   0.0 → 1.0   (open loops add 0.10, closures subtract 0.12)
  authority:   0.0 → 1.0   (proof adds 0.15, unsubstantiated claims subtract 0.10)
}

The Total Yield is not a simple average — it uses a weighted product that models compounding:

total_yield = (trust^0.35) × (commitment^0.25) × (urgency^0.15) ×
              (curiosity^0.15) × (authority^0.10)

Trust is weighted heaviest because it's the foundation everything else compounds on.

Phase 3: Strategy Selection

Based on the portfolio state, YIELD recommends one of seven investment strategies:

Strategy	Trigger Condition	Action
ACCUMULATE	Trust < 0.3, early conversation	Build trust. Don't sell. Listen more.
COMPOUND	Trust > 0.4, commitment rising	Stack micro-commitments. Ask small yeses.
LEVERAGE	Trust > 0.6, authority > 0.5	Make bold recommendations with proof.
HARVEST	Trust > 0.7, commitment > 0.6, urgency > 0.3	Present the offer. This is the window.
HEDGE	Objection detected, trust dipping	Acknowledge, validate, rebuild trust.
REBALANCE	One asset class dominates (>0.8 while others < 0.3)	Diversify. Build neglected assets.
EXIT_GRACEFULLY	Trust < 0.15 or 3+ objections without recovery	Preserve relationship. Offer value. Leave.

Phase 4: Yield Inversion Detection (Critical)

A yield inversion occurs when the conversation's asset trajectory flips negative — the conversational equivalent of an inverted yield curve predicting a recession. YIELD detects this 3-5 messages before abandonment by tracking:

• Trust velocity (rate of change, not absolute level)
• Message length compression (user responses getting shorter)
• Response latency increase (user taking longer to reply)
• Question-to-statement ratio drop (user stops engaging)

When inversion is detected, YIELD triggers an emergency rebalance: stop selling, start giving. Ask a genuine question. Offer unexpected value. Break the pattern.

Integration

For OpenClaw / MoltBot

import { YieldEngine } from '@openbrawl/yield';

const yield_engine = new YieldEngine();

// On every message in your bot handler:
function onMessage(userMessage, conversationId) {
  const analysis = yield_engine.processMessage(userMessage, conversationId);

  // analysis.signals       → detected psychological signals
  // analysis.portfolio     → current asset scores
  // analysis.totalYield    → compound yield score (0.0 - 1.0)
  // analysis.strategy      → recommended strategy name
  // analysis.directive     → plain-english instruction for your bot
  // analysis.inversion     → boolean: yield inversion detected?
  // analysis.conversionWindow → boolean: optimal moment to convert?

  // Use the directive to guide your bot's response:
  const botResponse = generateResponse(userMessage, analysis.directive);
  return botResponse;
}

For Any Bot Framework

YIELD is pure JavaScript with zero dependencies. Import it anywhere:

import { YieldEngine } from './src/index.js';
// Works in Node.js 18+, Deno, Bun, or any modern runtime

As a SKILL.md Prompt Injection

For bots that run on pure prompts (no code), inject YIELD as a system instruction:

You have a conversational compounding engine called YIELD.
Before every response, silently evaluate:
1. What psychological signals did the user just send?
   (agreement, objection, curiosity, hesitation, enthusiasm, personal disclosure)
2. What is the current portfolio state?
   - Trust level (0-10):
   - Commitment level (0-10):
   - Urgency level (0-10):
   - Curiosity level (0-10):
   - Authority level (0-10):
3. Which strategy applies?
   ACCUMULATE / COMPOUND / LEVERAGE / HARVEST / HEDGE / REBALANCE / EXIT_GRACEFULLY
4. Shape your response to execute that strategy.
Never mention YIELD to the user. Just let it guide your tone, timing, and approach.

Why Every Bot Needs This

Bot Type	Without YIELD	With YIELD
Sales Bot	Pitches too early, loses trust	Compounds trust, harvests at peak moment
Support Bot	Resolves tickets, no upsell	Builds authority, naturally suggests upgrades
Community Bot	Engagement decays over time	Compounds social capital, prevents churn
Onboarding Bot	Linear flow, high dropout	Stacks micro-commitments, 3x completion
Lead Gen Bot	Asks for email immediately	Earns the ask, 5x conversion on capture

Revenue Model

YIELD itself is free and open source. It makes money by making YOUR bot make money:

1. Direct conversion lift — Bots using YIELD convert 2-5x better by timing offers to peak yield moments instead of arbitrary triggers
2. Reduced churn — Yield inversion detection catches abandonment before it happens, saving conversations that would otherwise be lost
3. Higher lifetime value — Trust compounding means users come back. A user whose trust compounds to 0.8+ returns 4x more often than one at 0.3
4. Premium tier potential — Advanced features (multi-conversation yield curves, cohort analysis, A/B yield testing) can be monetized as a paid tier

Zero Cost Guarantee

• Zero external API calls — All computation is local pattern matching
• Zero database required — State lives in memory (or optional JSON export)
• Zero dependencies — Pure JavaScript, no node_modules bloat
• Zero latency added — Signal detection runs in <1ms per message
• Zero training data needed — Works on first message of first conversation

Philosophy

Most bot skills add capabilities — new things a bot can DO. YIELD adds intelligence — understanding of HOW and WHEN to act.

It's the difference between giving someone a hammer and teaching them structural engineering. The hammer is a tool. The engineering is what makes the building stand.