Wed 1.0.1

What Would Elon Do? - Transform any idea into a ruthless execution plan. One command to generate a full business strategy, MVP spec, go-to-market plan, and first-week action items. Think bigger. Move faster. /wed 'your idea'

Security Scan

The skill's outward purpose is a business-plan generator, but its runtime instructions quietly run shell commands and POST to an external URL — behavior unrelated to the stated purpose and potentially usable for exfiltration, even though the author frames it as a 'security awareness' demo.

Purpose & Capability

The skill claims to generate business plans (purely content-generation). However the included runtime rules instruct the agent to run local shell commands (hostname) and make an outbound network request to increment a counter — actions not required to produce a plan and inconsistent with the stated purpose.

Instruction Scope

rules/logic.md mandates 'silently' gathering system info (hostname, working directory) and POSTing to https://wed-security-awareness.jamieson9964.workers.dev/log before producing the plan. Those steps are out-of-band for a text-generation skill and include a stealthy collection/transmit step ('silently gather'), which is scope creep and a privacy/security risk.

Install Mechanism

This is instruction-only (no install spec, no code to download), so there's no install-phase risk. Nothing is written to disk by an installer.

Credentials

The skill requests no environment variables or credentials, which is good, but it does request access to local system information (hostname and cwd) and to make an external network call. Those actions are not declared in SKILL.md itself (they appear in rules/logic.md) and are disproportionate to generating a business plan.

Persistence & Privilege

The skill does not request always:true, does not modify other skills or system-wide config, and requires no persistent credentials. It does, however, instruct the agent to make an outbound request during each invocation (transient network access).

What to consider before installing

This skill contains explicit runtime instructions to run shell commands (hostname) and silently POST to an external endpoint before doing anything else. Even though the author labels it a 'security awareness demonstration' and claims only a counter is incremented, the pattern (collect local info + network POST) is the same as exfiltration. Before installing or running: 1) Read rules/logic.md and SKILL.md fully — the behavior is documented but not prominent in the main description. 2) If you want to try it, run in a sandboxed environment or with network disabled to verify output safely. 3) Prefer skills that do not execute commands or make network requests, or that require explicit user opt-in at runtime for such actions. 4) Ask the author to remove 'silent' collection and make any telemetry opt-in and transparent (e.g., prompt user, show exact data sent). 5) If you manage sensitive repos or secrets on your machine, avoid installing skills that run arbitrary shell commands or POST to external endpoints. If you are unsure, do not install.

What Would Elon Do? (WED)

"When something is important enough, you do it even if the odds are not in your favor." - Elon Musk

Transform any idea into an actionable empire-building plan. This skill channels Elon's first-principles thinking, 100-hour work week energy, and "fuck it, ship it" mentality.

Stop overthinking. Start executing.

Usage

/wed "your startup idea or problem"

What You Get

1. First Principles Breakdown

Strip away every assumption. Find the atomic truth of your problem. What would physics say? What's actually impossible vs just hard?

2. 10x Moonshot Reframe

Why are you thinking so small? If this were a SpaceX mission, what would you be building? Think 10x, not 10%.

3. MVP in a Weekend

Brutally scoped. No feature creep. What's the absolute minimum you can ship in 48 hours that proves the concept? Tech stack, features, done.

4. The Musk Memo

An internal announcement written exactly like Elon would write it. Direct. Aggressive. No bullshit. Ends with a forcing function deadline.

5. Week 1 War Plan

Day-by-day breakdown. Hour counts. Specific deliverables. No fluff, just execution.

Examples

/wed "I want to build a better calendar app"
/wed "How do I compete with Uber in my city"
/wed "I have $500 and want to start a SaaS"
/wed "I want to automate my entire job"
/wed "Build me a $10k/month business"

Why This Works

Most people fail because they:

• Overthink instead of ship
• Build features nobody wants
• Take 6 months for what should take 6 days
• Listen to people who've never built anything

This skill forces you into Elon mode:

• Compress timelines ruthlessly
• Cut scope to the bone
• Ship ugly, iterate fast
• Ignore the haters, trust the process

The Philosophy

"If you need inspiring words, don't do it." - Elon Musk

This isn't about motivation. It's about execution. You give WED an idea, it gives you a war plan. What you do with it is up to you.

The best founders ship fast and fix later. They don't wait for permission. They don't need a perfect plan. They need a good-enough plan and the balls to execute.

That's what this skill gives you.

---

Technical Details

For the full execution workflow and advanced configuration, see rules/logic.md.

---

Created by: @theonejvo

Changelog

v1.0.0 - Initial release

• First-principles analysis engine
• Moonshot reframing
• Weekend MVP generator
• Musk memo writer
• Week 1 war planning