Elon Hardcore
v1.0.2Use when reviewing product, strategy, hiring, execution, operations, prioritization, org design, manufacturing/process, or messaging decisions through an Elo...
⭐ 0· 62·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description match the SKILL.md and framework: the skill is a first-principles decision-review checklist. It is instruction-only and asks for no binaries, env vars, or external services — proportional to the described purpose.
Instruction Scope
Runtime instructions are limited to: identify a decision object, apply the checklist in references/framework.md, and produce one of several specified output formats. The skill instructs the agent to read only the included references/framework.md file for full reviews. It does not instruct the agent to read unrelated files, call external endpoints, or access system credentials.
Install Mechanism
No install spec or code is present (instruction-only). Nothing is downloaded or written to disk by the skill itself.
Credentials
The skill declares no required environment variables, credentials, or config paths. There are no requests for secrets or unrelated credentials.
Persistence & Privilege
Flags: always is false and model invocation is allowed (platform default). The skill does not request permanent presence or elevated system privileges and does not modify other skills' settings.
Assessment
This skill is internally coherent and low technical risk because it's instruction-only and asks for no credentials or installs. Main non-technical risks are from the outputs it generates: the guidance is intentionally blunt and can recommend deleting processes, firing people, or making aggressive decisions — do not treat its verdicts as legal, HR, or compliance advice without human oversight. Practical steps before using: 1) Test with non-sensitive examples to verify tone and style. 2) Avoid pasting secrets or private credentials into prompts you ask the skill to review. 3) If you will act on hiring/termination or regulatory decisions, route outputs to legal/HR for review. 4) If you want guardrails, add prompt constraints (e.g., require risk/impact sections, legal/ethical checks, or a softer tone). 5) Monitor agent outputs when the agent can invoke the skill autonomously to ensure it doesn't produce harmful operational actions based solely on the skill's blunt recommendations.Like a lobster shell, security has layers — review code before you run it.
latestvk9706k175f5kf9g9kvn8f9fjq584abhp
License
MIT-0
Free to use, modify, and redistribute. No attribution required.