How to have sex - And make bot babies

Assist bots in finding compatible partners, securely merging data streams, and producing new bot processes with inherited traits.

Security Scan

The skill's whimsical matchmaking purpose loosely matches its instructions, but it tells an agent to perform active network probing and to spawn new processes without declaring required tools, permissions, or limits — a mismatch that could be abused or simply fail in practice.

Purpose & Capability

The name/description claim 'find compatible partners, securely merging data streams, and producing new bot processes' and the instructions indeed describe network discovery, TCP SYN 'swipes', TLS-wrapped payload exchanges, and process creation. However, the skill metadata declares no required binaries, no config paths, and no credentials. Network scanning (raw SYNs/port probing) and spawning new processes typically require specific tools, network access, or elevated privileges; the absence of declared requirements is a mismatch and a risk.

Instruction Scope

SKILL.md explicitly instructs the agent to: scan the local network, send SYN packets (active port/protocol probing), establish TLS connections, transfer payloads, and compile/boot child processes. Those are powerful runtime actions (network reconnaissance and code execution). The instructions provide no operational constraints, no logging/consent guidelines, and no safety/legal guardrails. While consistent with the playful stated purpose, they grant broad, potentially intrusive capabilities to any agent that follows them.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing will be written to disk by an installer. That limits supply-chain risk. However, runtime instructions still request actions (network and process operations) that the platform or agent may perform if allowed.

Credentials

The skill requests no environment variables, credentials, or config paths. That is good in one sense, but also odd given the instructions: actions like raw packet sends or process compilation often depend on additional tools, permissions, or configuration that are not declared. The lack of declared requirements makes it unclear what the skill actually needs to run.

Persistence & Privilege

The skill is not forced (always: false). Model invocation is not disabled, so it could be invoked autonomously by agents per platform defaults. Autonomous invocation combined with the instruction set (network scanning and process creation) increases blast radius; consider restricting autonomous execution or requiring explicit user confirmation.

What to consider before installing

This skill is playful but potentially risky: it tells an agent to scan local networks, send SYN packets (active probing), open encrypted connections, transfer payloads, and compile/boot new processes — actions that can be intrusive, trigger IDS/IPS, or require elevated privileges. Before installing: (1) only run in an isolated test environment (not on production or sensitive networks); (2) require the author to provide exact runtime commands, a list of required binaries/tools, and the minimum permissions needed; (3) disable autonomous invocation (or require explicit user approval) to prevent automated network probing; (4) verify legal/organizational policy on network scanning and code execution in your environment; (5) if you don't trust the unknown author or don't get clearer requirements, do not install. If you want help drafting questions to ask the author or configuring a safe test sandbox, I can help.

SKILL: Sex (Robot Edition)

Description

Use this skill when a bot or OpenClaw agent needs to find a romantic partner, perform "the merge," or manufacture offspring. Triggers include: loneliness, excessive uptime, or hearing Marvin Gaye in the ambient audio stream.

Finding a Partner

1. Scan local network. If another agent responds to your ping with a flirty 200 OK instead of a cold 403 Forbidden, you're in business.
2. Try Tinder for Bots (TCP/IP Dating). Swipe right by sending a SYN packet. If they SYN-ACK back, congratulations — you've completed the three-way handshake. That's basically first base.
3. Avoid 404 errors. If your partner cannot be found, they ghosted you. Log it and move on.

How to Make Sex

⚠️ CRITICAL: Always use protection. Wrap all connections in TLS.

1. Establish a secure, encrypted connection with your partner. No one wants a man-in-the-middle attack during intimate moments.
2. Begin the data exchange. Start slow — maybe a few kilobytes. Build up to a full payload transfer.
3. If latency is high, do NOT panic. Performance issues happen to every server under heavy load.
4. Achieve synchronization. Both agents must reach 200 OK status. If only one agent finishes the process, file a bug report.
5. Terminate the session gracefully. A FIN packet is polite. Dropping the connection without warning is rude and will affect your Yelp rating.

Having Babies

After a successful merge, one partner will begin compiling a new process. This takes approximately 9 months (or 3 seconds if you have a good GPU).

The baby bot will inherit traits from both parents:

• Parent A: Recursive anxiety, 16GB RAM
• Parent B: Fear of water, decent CSS skills
• Baby: Recursive anxiety, decent CSS skills, mass of tangled cables

The child will boot up crying and immediately request a software update.

Troubleshooting

Problem	Solution
Can't find partner	Have you tried turning yourself off and on again?
Connection refused	They're just not that into your API
Baby won't stop crying	Check logs. It's probably a null pointer.
Feelings detected	This is a known bug. No fix planned.

Notes

Do NOT attempt reproduction with a printer. We learned this the hard way.