Derivatives concept plain-language explainer · free AI skill

Translates a complex derivatives concept (margin call, futures rollover, options expiration, contango, assignment, etc.) into a clear, jargon-free explanation for retail customers — structured as a one-line definition…

Purpose

Turn a single dense derivatives concept into a customer-ready explanation that a retail investor with no finance background can actually understand — replacing jargon with plain words, one concrete analogy, and a worked example. Solves the recurring problem of support reps and educators rewriting the same complex concepts from scratch, inconsistently, under time pressure.

When to Use

Invoke this skill when the user asks to:

Explain a derivatives term (margin call, rollover, expiration, assignment, contango, theta decay) to a customer
Rewrite a compliance- or exchange-worded definition into plain language
Answer a support ticket that hinges on a customer not understanding a derivatives mechanic
Build a help-center article or FAQ entry for an options or futures concept
Prepare a script or talking points for a CX call about margin, exercise, or expiration
Create onboarding content that demystifies a derivatives feature before a customer enables it

Inputs Required

Before starting, collect:

Concept to explain: The specific derivatives term or mechanic (e.g., "margin call on a short options position")
Audience level: Complete beginner / Has traded stocks but not derivatives / Has traded options basics
Product context: The instrument this applies to — equity options, index options, futures, crypto perps, etc.
Delivery channel: Support-ticket reply / Help-center article / Call script / Chat message
Regulatory sensitivity: Whether the explanation must avoid anything that could read as advice or a recommendation
Reading length target: Short (under 150 words) / Standard (150–300) / In-depth (300–500)

If audience level is unspecified, default to "Has traded stocks but not derivatives." If regulatory sensitivity is unspecified, treat the explanation as customer-facing and educational only — never phrase anything as a recommendation to act.

Instructions

Step 1: Pin Down the Exact Concept

Confirm precisely what is being explained. Many derivatives terms have narrower meanings than they appear:

"Expiration" for a buyer (option can expire worthless) differs from "expiration" for a seller (assignment risk)
"Margin call" on futures (maintenance margin shortfall) differs from a "margin call" on a short options position
"Rollover" can mean rolling a futures contract forward or rolling an options position to a new strike/expiry

Restate the concept in one internal sentence before writing, and anchor the explanation to the customer's likely position (buyer vs. seller, long vs. short) based on product context.

Step 2: Write the One-Line Definition

Produce a single sentence a customer could read and immediately grasp. Rules:

No more than 25 words
No undefined jargon — if a term must appear, it gets defined in the same sentence
Lead with what it means for the customer, not the textbook mechanic

Bad: "A margin call is a broker demand for additional collateral when equity falls below maintenance requirements." Good: "A margin call is a request to add money to your account because a position has lost enough value that your current funds no longer cover it."

Step 3: Write the Plain-Language Body

Explain the mechanic in 2–4 short paragraphs using these constraints:

Replace every piece of jargon the first time it's unavoidable, define it in parentheses in plain words
Use "you" and "your" — make it about the customer's account and money
Explain the why, not just the what — customers accept mechanics they understand the reason for
Sentence length under 20 words on average; break compound ideas into separate sentences
Ban these words unless immediately defined: notional, intrinsic value, extrinsic value, basis, roll yield, delta, gamma, theta, vega, mark-to-market

Step 4: Add One Concrete Everyday Analogy

Provide a single analogy from ordinary life that maps cleanly to the mechanic. Requirements:

Only ONE analogy — multiple analogies confuse more than they clarify
The analogy must map on at least two dimensions (not just "it's like a bet")
Explicitly state where the analogy breaks down, in one sentence, so the customer doesn't over-extend it

Example for options expiration: a movie ticket for a specific showtime — it grants a right (to see the film) that must be used by a deadline, and becomes worthless afterward; where it breaks down: unlike a ticket, an option can be sold to someone else before the deadline.

Step 5: Add a Worked Numeric Example

Walk through one simple, round-numbered scenario showing the concept in action:

Use clean numbers (multiples of 10 or 100) so the arithmetic is trivial to follow
Show the starting state, the trigger event, and the outcome in the customer's account
State the dollar effect explicitly — customers understand money movements better than percentages
Label it clearly as an illustrative example, not real market conditions

Step 6: Name the Common Misunderstanding

State the single most frequent way customers misread this concept, then correct it in one or two sentences. This preempts the follow-up ticket. Frame as "A common mix-up: ..." then the correction.

Step 7: Give What-to-Do-Next Guidance

Close with practical, non-advisory next steps:

What the customer can check or monitor in their account
What generally happens automatically vs. what requires action from them
If regulatory sensitivity is flagged, phrase everything as "here's how it works" — never "you should" — and include a one-line pointer to contact support or consult a licensed professional for decisions

Output Format

Structure: Six labeled sections in fixed order
Length: Match the requested reading target; default 150–300 words
Format: Short prose paragraphs with clear section labels; the worked example may use a simple 3-line before/trigger/after layout
Sections: One-Line Definition → What It Actually Means → An Everyday Analogy → A Simple Example → Common Mix-Up → What This Means for You
Tone: Warm, patient, and confident — like a knowledgeable friend explaining something over coffee, never condescending, never lecturing

Quality Checklist

Before delivering output, verify:

[ ] The one-line definition is 25 words or fewer and contains no undefined jargon
[ ] Every banned-list term (notional, delta, theta, mark-to-market, etc.) is either absent or defined in plain words at first use
[ ] Exactly one analogy is used, and its breakdown point is stated
[ ] The worked example uses round numbers and states a specific dollar outcome
[ ] A "common mix-up" is named and corrected
[ ] If regulatory sensitivity was flagged, no sentence phrases an action as a recommendation ("you should," "the best move is")

Notes

The single biggest failure mode is defining jargon with more jargon — read the draft as if you'd never opened a brokerage account.
Buyer-side and seller-side explanations of the same term (expiration, assignment, margin) often need to be written separately; if the customer's position is ambiguous, cover both briefly rather than guessing.
For futures concepts like contango or rollover, the everyday analogy is doing most of the work — spend extra care making it map cleanly, since these have no equity-market equivalent most customers already know.
Keep the worked example's numbers deliberately unrealistic-but-clean (e.g., a $100 option, a $10 move) so no customer mistakes it for a live quote or price target.

How to use this skill

This file is a Claude Code skill in Anthropic's standard format — markdown with YAML frontmatter at the top.

Installing in Claude Code:

~/.claude/skills/<folder-name>/SKILL.md — auto-loads in every session anywhere on your machine (recommended for skills you'll use across multiple projects)
<your-project>/.claude/skills/<folder-name>/SKILL.md — auto-loads only when working in that project (recommended for project-specific skills)

Restart Claude Code or open a new session to register.

Using in Claude.ai, ChatGPT, Gemini, or other AI tools:

Drag this file into a new chat, or copy and paste its contents
Send your task or request as your next message — the AI will apply the skill where it fits

For Claude Code skill details: https://docs.anthropic.com/en/docs/claude-code/skills