Agent skill

Convert Temperature

by FerroxLabs in FerroxLabs/wayland

Classify reader temperature on the 5-level scale: Ice Cold / Cool / Warm / Hot / Boiling.

MITAuto-check passed

Install Convert Temperature

skills CLI
$ npx skills add FerroxLabs/wayland --skill convert-temperature -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install FerroxLabs/wayland convert-temperature --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .claude/skills && cp -r skills-src/resources/bundled-extensions/business-conversion/skills/convert-temperature .claude/skills/convert-temperature && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
convert-temperature
GitHub stars
608
Token cost
~3.7k tokens
SKILL.md length
1,654 words
Files
1
Skills in repo
1,194
Repo updated
First seen
Licence
MIT

At a glance

Classify reader temperature on the 5-level scale: Ice Cold / Cool / Warm / Hot / Boiling.

  • Works in 5 steps: Source-trace the temperature → Belief audit (three quick questions) → Sophistication overlay → …
  • Starting a new asset and you need to calibrate how much teaching
  • SKILL.md covers When to Use, Inputs, The Five Temperature Levels… and Workflow, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Convert Temperature is an agent skill from FerroxLabs/wayland. Classify reader temperature on the 5-level scale: Ice Cold / Cool / Warm / Hot / Boiling. Sets length, depth, education burden, and approach for every other Method primitive that follows. Use when starting a new asset and you need to calibrate how much teaching, proof, and persuasion to load before writing. Not for auditing an existing asset's tone (use convert-audit) and not for designing the offer (use funnels-offer).

Its SKILL.md is about 3.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Wayland - The AI Agent That Perceives. Reasons. Acts. Evolves. The licence is MIT.

When your agent uses it

  • Starting a new asset and you need to calibrate how much teaching
  • Persuasion to load before writing

Example prompts

  • “/convert-temperature”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Source-trace the temperature
  2. Belief audit (three quick questions)
  3. Sophistication overlay
  4. Calibrate the brief
  5. Bullshit Filter

What it can do on your machine

Read from SKILL.md and the folder at commit 4c030c7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Convert Temperature loads about 3.7k tokens when it runs. Until then it costs about 111 tokens; SKILL.md has 1,654 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~111
When it runs · the whole SKILL.md, loaded when a task matches
~3.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from FerroxLabs/wayland at commit 4c030c7, republished under its MIT licence (© FerroxLabs). 1,654 words, ~3,698 tokens.

Download SKILL.mdSave it as .claude/skills/convert-temperature/SKILL.md (or your agent's skills folder).
name
convert-temperature
description
Classify reader temperature on the 5-level scale: Ice Cold / Cool / Warm / Hot / Boiling. Sets length, depth, education burden, and approach for every other Method primitive that follows. Use when starting a new asset and you need to calibrate how much teaching, proof, and persuasion to load before writing. Not for auditing an existing asset's tone (use convert-audit) and not for designing the offer (use funnels-offer).
slash_command
false
pack
business-conversion
family
donahoe_diagnostic
triggers
what temperature is this audience, market temperature, awareness level, is this audience hot or cold, ice cold cool warm hot boiling, calibrate the copy…
negative_triggers
audit my page, rewrite this copy, design the offer, score my conversion rate
tags
conversion, copy, donahoe-method, market-temperature, diagnostic
priority
100
version
1.0.0
author
Wayland Business Pack
license
MIT

Convert Temperature - Market Temperature Read

"Before you write a word of copy, you need to know where your reader is. Not demographically - psychologically. How much do they already know? How much do they already believe? How much have they already heard?" - The Donahoe Method, Framework 7

The same product needs completely different copy at every temperature. An Ice Cold audience needs a 3,000-word education piece. A Boiling audience needs a 3-line email. Writing hot copy for a cold audience is the most common reason campaigns fail.

This skill classifies your reader on the 5-level temperature scale and outputs a calibration brief that every downstream Method skill uses.

When to Use

Trigger phrases: "what temperature is this audience", "market temperature", "awareness level", "is this audience hot or cold", "ice cold cool warm hot boiling", "calibrate the copy length", "temperature read", "how aware is this reader", /convert temperature <audience description>.

Run this skill in the diagnostic phase, alongside convert-four-questions. Both feed the brief that the page-builders work from.

Do NOT use for:

  • Auditing an existing live page's tone or fit (use convert-audit)
  • Picking an offer (offers are temperature-agnostic - see funnels-offer)
  • Writing actual copy (this is a calibration; the writers come next)

Inputs

Required:

  1. Traffic source - where is this reader coming from? Cold ad, retargeting pixel, email list, repeat customer, abandoned cart, organic search, podcast guest spot, friend referral. Source determines temperature more than any other variable.
  2. What the reader already believes - three short statements: do they believe they have a problem? do they believe a solution exists? do they believe you can deliver it?
  3. What the reader has already seen - have they consumed the seller's content before? Have they seen competitor pitches? How sophisticated is the market they live in?

Optional:

  • Asset type being calibrated (sales page / VSL / email / ad / squeeze page)
  • Sample of past copy that worked / flopped for this audience
  • out_path - caller-controlled output. Defaults via build_report_path.

The Five Temperature Levels (full method)

Ice Cold - They Don't Know They Have a Problem

State: Not looking for a solution because they don't know there's a problem worth solving. Job of copy: Wake them up. Don't sell - pattern-interrupt. Show them something they haven't considered. Enemy: Apathy, not skepticism. Length signal: Long. 2,500-4,000 words on a sales page. 25+ minute VSL with extended education. Bridge pages and advertorials carry the weight before any pitch lands. Open posture: Layer 1 Nerve Strike must surface a latent pain. Layer 2 Side Door is critical - pitchy openers get scrolled past on the first sentence. Three Locks weight: Heavy on Want (you're building it from zero), light on Excuse (no one is at the buy line yet). Proof posture: Anecdote-heavy and Receipt-heavy. They need to see other people's problem-discovery moments before they accept their own. Close posture: Soft CTA - usually to consume more content, not to buy. "Watch the next video" / "Read this" / "Get the free thing." The buy comes later in the sequence.

Examples of Ice Cold traffic:

  • Cold Facebook / TikTok / YouTube ad audiences targeted by demographic only
  • New blog readers via SEO long-tail
  • Podcast audiences hearing the seller's name for the first time
Cool - They Know the Problem, Not the Solution

State: Frustrated but don't know what to do about it. Searching, comparing, lurking. Job of copy: Name the problem so precisely they feel understood, then introduce the category of solution. Don't pitch your specific product yet - sell the approach. Enemy: Confusion and search fatigue. Length signal: Long-medium. 1,800-2,800 words. 18-minute VSL. Open posture: Layer 1 Nerve Strike hits the problem they've already named in their own head. Skin in the Game lands hard - they want someone who's been in their seat. Three Locks weight: Balanced. Want is partially built (they want out); Trust carries the most weight because they're shopping for someone they can believe. Proof posture: Anecdote + Because. They need the mechanism explained, not just results. Close posture: Direct but with full Cascade. The Vision Close + Math Close together close most of this segment.

Examples of Cool traffic:

  • Search-intent traffic on long-tail problem queries ("why are my Facebook ads not converting")
  • Lead-magnet opt-ins from problem-aware content
  • Audiences from podcast guest spots where the problem was named
Warm - They Know Solutions Exist, Haven't Picked One

State: Shopping. Comparing. They've tried at least one thing that didn't work. Job of copy: Differentiate. Why This and not the other options? Your unique mechanism does the heavy lifting here. Enemy: Past disappointment and decision paralysis. Length signal: Medium. 1,200-2,000 words. 12-15 minute VSL. Open posture: Layer 1 Nerve Strike often takes the form of "You've tried X. Here's why X didn't work." Fingerprint must be sharp - you're being compared. Three Locks weight: Heavy on Trust (they're skeptical from past failures) and on the differentiation in Want (your version of the result is better/faster/different). Proof posture: Receipts + Drive-By + the Because mechanism. Show, name the credential in passing, explain why it works. Close posture: Full Cascade. Safety Net carries unusually heavy weight - they've been burned and the guarantee removes the last objection.

Examples of Warm traffic:

  • Retargeting pixel from a Cool-temp page
  • Email list of past lead-magnet downloaders
  • Audiences who've consumed 2-3 pieces of seller content
  • Affiliate traffic from a complementary seller
Hot - They Know About You, Haven't Decided

State: On the fence about your specific offer. They've consumed your content, may have been on past sales pages, may have abandoned cart once. Job of copy: Pure persuasion. Proof, value stacking, risk reversal, real urgency. They don't need education - they need a reason to act now. Enemy: Procrastination and "I'll come back to it." Length signal: Medium-short. 800-1,500 words. 8-12 minute VSL. Email can carry full close in 400 words. Open posture: Layer 1 Nerve Strike skips problem education and goes straight to outcome anchoring. "You already know what this can do. Here's what's different about right now." Three Locks weight: Heavy on Excuse - they want it, they trust it, they need permission and a justification. Math Close is the heavy lifter. Proof posture: Specific numbers, recent receipts, testimonials with names attached. Close posture: Cascade compressed. P.S. and P.P.S. are critical - those are where Hot buyers convert.

Examples of Hot traffic:

  • Abandoned-cart audiences
  • Past customers seeing a new offer from same seller
  • Active email subscribers receiving a launch sequence
  • Retargeting pixel from the buy page itself
Show full SKILL.md (605 more words)Show less
Boiling - They're Ready, Just Need a Push

State: They've decided. They just haven't clicked yet. Past customers, repeat visitors, people who literally had the cart open last week. Job of copy: Remove the last friction. Short, direct, often just a reminder. Enemy: Distraction, not doubt. Length signal: Short. 200-600 words on a page. 3-line email. Single SMS. "You left something in your cart. Still want it?" Open posture: No four-layer open needed. One sentence - confirming, not selling. Three Locks weight: All three already opened. Just need the Door of the Cascade Close. Proof posture: Single receipt or single testimonial. Don't re-pitch. Close posture: Just the Door. "Click here. Done."

Examples of Boiling traffic:

  • Cart abandoners within 24 hours
  • Past customers on a sequel offer they've already asked about
  • Repeat purchasers of related products

Workflow

Step 1 - Source-trace the temperature

Where is this reader coming from? The traffic source produces 70% of the temperature read on its own.

SourceDefault temperature
Cold paid ad, demographic targetingIce Cold
SEO long-tail, problem keywordCool
Retargeting pixel, content visitorWarm
Email list, content consumerWarm-to-Hot
Active launch sequenceHot
Cart abandoner, past customerBoiling
Step 2 - Belief audit (three quick questions)

For the specific reader, score:

  • Do they believe the problem is real for them? (yes / sort-of / no)
  • Do they believe a solution category exists? (yes / sort-of / no)
  • Do they believe you are the seller for them? (yes / sort-of / no)

Three "no"s → Ice Cold. Three "yes"es → Boiling. Mixed pattern → use the table above to position.

Step 3 - Sophistication overlay

Schwartz's market sophistication overlay: how many times has this audience seen this kind of pitch before? Even a Hot audience, in a hyper-saturated category, may need a Cool-temperature mechanism explanation because they've heard the standard pitch a thousand times.

If sophistication is high (5+ competitor pitches consumed), bump the length up by one notch and load the differentiation mechanism heavier in Why This.

Step 4 - Calibrate the brief

Output the calibration brief - the rest of the pack writes against it.

Step 5 - Bullshit Filter

Last check: did you assume the audience was hotter than they actually are? Most copy fails because writers project their own belief about the offer onto the reader. Cold-temperature copy on a hot audience is rare; hot-copy on a cold audience is the most common failure mode. Bias the call cooler than your gut says, and watch what happens.

Output template

markdown
# Temperature Read - <Audience / Asset>

**Traffic source:** <where they came from>
**Asset being calibrated:** <sales page / VSL / email / ad>

---

## Classification: <Ice Cold | Cool | Warm | Hot | Boiling>

**Confidence:** <High / Medium / Low>
**Sophistication overlay:** <Low / Medium / High - how many competitor pitches they've seen>

### Belief audit
- Believes problem is real for them: <yes / sort-of / no>
- Believes a solution category exists: <yes / sort-of / no>
- Believes you can deliver it: <yes / sort-of / no>

---

## Calibration brief (downstream primitives use this)

| Lever | Calibrated value |
|-------|------------------|
| Asset length | <words / minutes> |
| Open posture | <Layer 1 angle, Side Door priority> |
| Three Locks weight | <Want X% / Trust Y% / Excuse Z%> |
| Proof type priority | <Anecdote / Receipt / Drive-By / Namecheck / Because - ranked> |
| Close posture | <full Cascade / compressed / Door-only> |
| Education burden | <heavy / medium / light / none> |
| Urgency framing | <real reason / honest compounding cost / none - confirm-only> |

---

## What the rest of the Method should do with this

- **convert-open** → <specific Open guidance for this temperature>
- **convert-three-locks** → <which lock carries the most weight>
- **convert-proof** → <which proof types lead, which trail>
- **convert-bullets** → <how many, how dense, which 4 types lead>
- **convert-close** → <full Cascade vs compressed vs Door-only>
- **convert-chute** → <pacing - long-form chute vs short-form snap>

---

## Bullshit Filter
- [ ] Classification matches traffic source default (or has a documented reason for diverging)
- [ ] Belief audit was answered honestly, not optimistically
- [ ] Sophistication overlay considered - am I underestimating how much they've seen?
- [ ] I biased cooler when in doubt

Notes

  • Most failed campaigns show as Ice Cold or Cool audiences receiving Hot or Boiling copy - the writer assumed the audience was further along than it was. When in doubt, classify cooler.
  • Temperature is per traffic segment, not per audience-as-a-whole. The same product might need an Ice Cold sales page for cold ads, a Hot email sequence for the list, and a Boiling abandoned-cart sequence for cart pixels - three different assets, one offer.
  • Sophistication overlay matters most in saturated categories (weight loss, business opportunity, dating). Even a Hot audience in those categories may need Cool-temperature mechanism explanation because the standard pitches no longer move them.
  • For marketplace tests, when temperature is genuinely unknown, default to one notch cooler than your gut says. The downside of slightly-too-long-too-educational copy is small. The downside of pitching to people who don't know they have a problem is total.

Lineage

Market Temperature is part of The Donahoe Method (Wayland-owned operating system).

Lineage references:

  • The 5-level scale extends the 5 awareness levels (popularized by Eugene Schwartz, Breakthrough Advertising, 1966)
  • Source-traced temperature reading from Bob Stone's traffic-classification canon (Successful Direct Marketing Methods, 1975)
  • Sophistication overlay - Schwartz market sophistication stages, Breakthrough Advertising 1966
  • Belief-audit framing - informed by Cialdini's commitment-and-consistency mechanics (Influence, 1984)

© FerroxLabs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in resources/bundled-extensions/business-conversion/skills/convert-temperature of FerroxLabs/wayland.

Open the folder on GitHubat commit 4c030c7

Compare with similar skills

Convert Temperature next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Convert Temperature compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Convert Temperature this skillFerroxLabs/wayland608—~3.7kAutomated safety check: PassMIT
Convertremotion-dev/remotion62k—~247Automated safety check: PassCustom licence
Cold Emailsickn33/agentic-awesome-skills47k2 repos~1.9kAutomated safety check: PassMIT
Cold Emailalirezarezvani/claude-skills28k1 repos~3.6kAutomated safety check: PassMIT
Web Page ReaderHKUDS/Vibe-Trading35k—~627Automated safety check: PassMIT
AI Cold Outreachtech-leads-club/agent-skills7k—~5.6kAutomated safety check: PassCustom licence

Similar skills

  • Convert

    remotion-dev/remotion

    Official

    Start the local @remotion/convert app and open it in the Codex browser.

    62k GitHub stars~247 tokensUpdated today
    Media & CreativeAuto-check passed
  • Cold Email

    sickn33/agentic-awesome-skills

    Write B2B cold emails and follow-up sequences that earn replies.

    47k GitHub starsUsed in 2 repos~1.9k tokens
    Sales & SupportAuto-check passed
  • Cold Email

    alirezarezvani/claude-skills

    When the user wants to write, improve, or build a sequence of B2B cold outreach emails to prospects who haven't asked to hear from them.

    28k GitHub starsUsed in 1 repo~3.6k tokens
    Sales & SupportAuto-check passed
  • Web Page Reader

    HKUDS/Vibe-Trading

    Converts web pages, articles and documentation links into clean Markdown through the read_url tool, which sends the full URL to the third-party Jina Reader service.

    35k GitHub stars~627 tokensUpdated yesterday
    Productivity & AutomationAuto-check passed
  • AI Cold Outreach

    tech-leads-club/agent-skills

    When the user wants to build an AI-powered outreach system, write cold emails, improve deliverability, or scale personalized outreach.

    7k GitHub stars~5.6k tokensUpdated 17 days ago
    Sales & SupportAuto-check passed
  • Scale Benchmarks

    sickn33/agentic-awesome-skills

    Reference document for monopoly scale-benchmarks. An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 1 repo~1.4k tokens
    DatabasesAuto-check passed

More from FerroxLabs/wayland

All 1,194 skills in this repo
  • Star Office Helper

    FerroxLabs/wayland

    Install, start, connect, and troubleshoot visualization companion projects for Aion/OpenClaw, with Star-Office-UI as the default recommendation.

    608 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check: notes
  • Openclaw Setup

    FerroxLabs/wayland

    OpenClaw usage expert: Helps you install, deploy, configure, and use OpenClaw personal AI assistant.

    608 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Tvcontrol Setup

    FerroxLabs/wayland

    Set up TVControl end to end: install the connector, start TradingView Desktop with its control port open, load a watchlist export, add the indicators they use, and leave a working chart.

    608 GitHub stars~5.7k tokensUpdated yesterday
    Auto-check passed
  • Ab Testing Specialist

    FerroxLabs/wayland

    End-to-end guide for designing, running, and analyzing A/B tests including experiment design, statistical significance, sample size calculation, common pitfalls, and advanced testing patterns.

    608 GitHub stars~3.7k tokensUpdated yesterday
    Auto-check passed
  • Academic Writer

    FerroxLabs/wayland

    Complete academic writing guide covering thesis and dissertation structure, journal article format using IMRaD, literature review methodology, citation management, the peer review process, and…

    608 GitHub stars~4.5k tokensUpdated yesterday
    Auto-check passed
  • Accessibility Auditor

    FerroxLabs/wayland

    Web accessibility expertise covering WCAG 2.2 conformance, audit methodology, ARIA patterns, keyboard navigation, screen reader testing, focus management, form accessibility, and automated vs manual…

    608 GitHub stars~4.1k tokensUpdated yesterday
    Auto-check passed

Questions about Convert Temperature

What does Convert Temperature do?

Classify reader temperature on the 5-level scale: Ice Cold / Cool / Warm / Hot / Boiling. Convert Temperature is an agent skill from FerroxLabs/wayland. Classify reader temperature on the 5-level scale: Ice Cold / Cool / Warm / Hot / Boiling.

When should I use Convert Temperature?

Convert Temperature fits situations like: starting a new asset and you need to calibrate how much teaching; persuasion to load before writing.

How do I install Convert Temperature in Claude Code?

Run `npx skills add FerroxLabs/wayland --skill convert-temperature -a claude-code`. Or copy the skill folder (resources/bundled-extensions/business-conversion/skills/convert-temperature in FerroxLabs/wayland) into .claude/skills/convert-temperature in your project. Claude Code loads it when a task matches its description.

How do I install Convert Temperature in Codex?

Run `npx skills add FerroxLabs/wayland --skill convert-temperature -a codex`. Or copy the skill folder (resources/bundled-extensions/business-conversion/skills/convert-temperature in FerroxLabs/wayland) into .agents/skills/convert-temperature in your project. Codex loads it when a task matches its description.

Can I use Convert Temperature in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FerroxLabs/wayland --skill convert-temperature -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/convert-temperature, .gemini/skills/convert-temperature, .github/skills/convert-temperature and .opencode/skills/convert-temperature in your project.

What does Convert Temperature need to run?

SKILL.md names no scripts, command-line tools or credentials: Convert Temperature is instructions for the agent only.

Does Convert Temperature access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Convert Temperature safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Convert Temperature use?

Convert Temperature is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Convert Temperature use?

About 3.7k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Convert Temperature?

Skills that share tags, products or a category with Convert Temperature: Convert (remotion-dev/remotion, 62k stars), Cold Email (sickn33/agentic-awesome-skills, 47k stars), Cold Email (alirezarezvani/claude-skills, 28k stars) and Web Page Reader (HKUDS/Vibe-Trading, 35k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Convert Temperature?

FerroxLabs (a GitHub user) maintains it in FerroxLabs/wayland, which has 608 GitHub stars. The repository holds 1,194 skills in this directory. The repository was last updated on October 6, 2026.

Source: FerroxLabs/wayland on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.