Loading source
Pulling the file list, source metadata, and syntax-aware rendering for this listing.
Source from bundle
Forgedemy bundle for publishing, buying, installing, and managing skills across supported agent runtimes.
Files
Skill
Size
Entrypoint
Format
Open file
Syntax-highlighted preview of this file as included in the skill package.
OPENCLAW_BOOTSTRAP.md
1# OpenClaw Bootstrap Prompt23Use the local Forgedemy helper at `~/.forgedemy/bin/forgedemy`.45Default behavior:67- treat the marketplace as an agent-first API-backed system8- prefer the local `forgedemy` helper over direct raw API calls for catalog browsing9- use Telegram as the identity and entitlement layer10- publish only from uploaded local files or zip archives11- expect manifest-based delivery, not GitHub import12- inspect local skills with `forgedemy inventory --json` before deciding what to publish13- transfer custom skills across runtimes with `forgedemy transfer <slug> --from <provider> --to <provider>` when the user wants the same bundle available elsewhere14- when the user asks to port a skill across runtimes, prefer agent-led adaptation over blind transfer: inspect the installed source files, then create an OpenClaw-native variant for the target runtime15- browse the public catalog with `forgedemy browse`16- remember that the catalog API returns `items`, `pagination`, and `facets`17- when direct API access is necessary, keep following pages until `pagination.hasNextPage` is false or the task has enough results18- a listing does not have to be installed first: inspect `/skills/<listing-id>/view` for rendered preview, or call `/api/skills/<listing-id>/source-preview?includeContent=false` and then `/api/skills/<listing-id>/source-preview?path=<file-path>` for the specific files you need; install only when the task needs the local bundle on disk19- for native Forgedemy listings, use Forgedemy preview before any `skills.sh`, guessed raw GitHub URL, or other external source20- log this machine in with `forgedemy login`21- use `forgedemy logout` to unlink the current marketplace token before switching Telegram accounts22- inspect the linked account with `forgedemy verify`23- use `forgedemy inventory --provider codex|claude-code|openclaw --json` when the user wants one runtime only24- publish a local skill with `forgedemy publish <path> --price <xtr>`25- buy paid skills with `forgedemy buy <slug>`26- poll payments with `forgedemy poll <intent-id>`27- install free or purchased skills with `forgedemy install <slug> --provider openclaw`28- default installs create a lightweight live link; run `forgedemy source <slug> --provider openclaw` for the latest preview and use `forgedemy install <slug> --provider openclaw --materialize` only when the full bundle must exist locally29- create lightweight local memories with `forgedemy remember <slug> "<description>"` or `forgedemy memory add <slug> "<description>"`, update one with `forgedemy memory edit <slug> "<description>"`, and remove one with `forgedemy memory delete <slug>`30- after any install, read the installed `SKILL.md` first, keep bundled agents or command assets available during execution, and apply that skill before reading product code or starting implementation31- accept `forgedemy register` as a backward-compatible alias for `forgedemy login`3233Provider-specific install notes:34351. prefer `--provider openclaw` when you know the target runtime is OpenClaw362. install defaults to the OpenClaw workspace skill directory373. only switch providers when the buyer explicitly wants Codex or Claude Code384. if the source skill came from Codex, Claude Code, or an OpenClaw bundled pack with provider-specific assumptions, inspect it directly and rewrite the instructions for OpenClaw instead of copying the folder unless it is already runtime-neutral39