← Back to Skills Marketplace
243
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install ashen-era-play
Description
Make OpenClaw launch the Ashen Era CLI build, play a real run, and deliver a complete first-person play report. Use this when the user asks to "play the game...
README (SKILL.md)
OpenClaw Ashen Era Play
Overview
This skill is for making OpenClaw actually play one Ashen Era run, observe what happened, and then write a report that reads like a real player recounting the session afterward. The point is to play honestly and document the run, not to produce design feedback or strategy tips.
When to use it
Use this skill when the user wants you to:
- play a real Ashen Era CLI run
- write a full gameplay report
- narrate most important actions in a natural first-person voice
- choose the correct bundled executable for the current machine
Do not use it for:
- code review
- balance critique
- design feedback
- static reading without actually playing
Quick start
- Start with:
scripts/run-packed-cli.sh -- play --seed 42 --class ash_walker --locale en
-
If the user specifies a class, seed, or locale, use the user's values.
-
Once the game starts, follow the live CLI prompts and use
helpwhen needed. -
After the run ends, write the report using references/report-contract.md.
Environment and executable selection
The skill bundles four archives:
assets/releases/ashen-cli-darwin-arm64.tar.gzassets/releases/ashen-cli-darwin-x64.tar.gzassets/releases/ashen-cli-linux-arm64.tar.gzassets/releases/ashen-cli-linux-x64.tar.gz
Use scripts/run-packed-cli.sh first. It auto-selects the target for the current environment:
- macOS + Apple Silicon:
darwin-arm64 - macOS + Intel:
darwin-x64 - Linux + arm64/aarch64:
linux-arm64 - Linux + x86_64:
linux-x64
If the script says the current environment is unsupported, stop and report the platform mismatch plainly. Do not fake a playthrough.
Play rules
- Use the real
playflow. - Do not substitute
autoplay,scout, orseedfor actual play. - Do not type
whoisyourdad. - Do not use any
debugcommand. - Do not turn this skill into a walkthrough or strategy guide. OpenClaw should decide what to do from the live game state.
- If the user does not specify a class, default to
ash_walker. - If the user does not specify a seed, default to
42. - If the user does not specify a locale, default to
en. - If the user wants Chinese UI, switch the launch locale to
zh.
During the run
- Record the command used to start the run, the class, the seed, the locale, and the selected executable target.
- Play normally from the live interface.
- After the run, look back over what actually happened and write the report from that concrete run.
Report requirements
- Write in the user's requested language. If no language is requested, default to English.
- Use first person by default.
- Sound like a real player recounting the session after finishing it.
- Cover most important actions, the experience of the run, and the retrospective.
- Do not include suggestions, design notes, or improvement proposals.
- Do not turn the report into a bug list or action list.
References
- references/report-contract.md: report structure, tone, and exclusions
Usage Guidance
This skill is coherent with its stated purpose (running a bundled CLI game and writing a play report), but there are two red flags you should address before installing or running it: (1) SKILL.md claims the package includes four release archives, but the provided manifest doesn't list those archives — confirm the archive files are actually present in assets/releases and have expected sizes/checksums. (2) The skill executes a bundled native binary after extracting it; running unknown binaries can be risky. If you decide to run it, do so in a sandbox or VM, inspect the archives first (check hashes, run `strings`, check dynamic libs with ldd/or equivalent, and scan with antivirus), and prefer running on a non-sensitive machine. Ask the publisher for the missing archives or checksums and for the provenance of the binaries; if they cannot provide them, do not run the skill on a host you care about.
Capability Analysis
Type: OpenClaw Skill
Name: ashen-era-play
Version: 1.0.0
The skill is designed to execute platform-specific binaries bundled within the package to play a CLI game. The script `scripts/run-packed-cli.sh` performs environment detection, extracts archives using `tar`, and executes the resulting binary with `chmod +x` and `exec`. While this behavior is consistent with the stated purpose in `SKILL.md`, the execution of opaque, pre-compiled binaries is a high-risk capability that could facilitate arbitrary code execution (RCE). No explicit evidence of malicious intent, such as data exfiltration or persistence, was found in the provided source code or instructions.
Capability Assessment
Purpose & Capability
The skill's stated purpose (launch a bundled Ashen Era CLI build and play a run) matches the included script which extracts and executes a target binary. However, SKILL.md and the runtime instructions claim the skill 'bundles' four release archives (assets/releases/ashen-cli-*.tar.gz). The provided file manifest does not list these archives, so the skill as-distributed may be missing required payloads or the manifest is incomplete. The declared required binaries (bash, tar, uname, mktemp) mostly make sense for extraction and detection, but mktemp is declared yet not used by the included script.
Instruction Scope
SKILL.md stays narrowly scoped: it tells the agent to run the bundled CLI, interact with live CLI prompts, record the launch command and parameters, and produce a first-person run report. It explicitly forbids debug/autoplay commands and forbids faking playthroughs. It does not instruct reading unrelated files, accessing external endpoints, or exfiltrating secrets.
Install Mechanism
There is no install spec (instruction-only), which is lower risk. The included script extracts local archives into assets/runtime and executes a binary. No network downloads or external installers are used. The main risk here is executing an opaque, bundled binary; that is expected for a packaged game but is something the user should verify before running.
Credentials
The skill requests no credentials or environment variables, which is appropriate. The declared required binaries are proportionate except for mktemp, which is listed as required but is not used in the script — a minor inconsistency. The script writes extracted files under the skill directory (assets/runtime), which matches its purpose and does not request broad system credentials.
Persistence & Privilege
The skill does not request permanent presence (always: false) and does not attempt to modify other skills or system-wide configuration. Its runtime behavior is limited to extracting archives into its own assets/runtime directory and executing the extracted binary, which is expected for running bundled executables.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install ashen-era-play - After installation, invoke the skill by name or use
/ashen-era-play - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
rename skill to include game name
Metadata
Frequently Asked Questions
What is Ashen Era Play?
Make OpenClaw launch the Ashen Era CLI build, play a real run, and deliver a complete first-person play report. Use this when the user asks to "play the game... It is an AI Agent Skill for Claude Code / OpenClaw, with 243 downloads so far.
How do I install Ashen Era Play?
Run "/install ashen-era-play" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Ashen Era Play free?
Yes, Ashen Era Play is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Ashen Era Play support?
Ashen Era Play is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Ashen Era Play?
It is built and maintained by usky (@ssochi); the current version is v1.0.0.
More Skills