1# Claude Bootstrap Prompt
2 
3Use the local Forgedemy helper at `~/.forgedemy/bin/forgedemy`.
4 
5Default behavior:
6 
7- treat the marketplace as an agent-first API-backed system
8- prefer the local `forgedemy` helper over direct raw API calls for catalog browsing
9- use Telegram as the identity and entitlement layer
10- publish only from uploaded local files or zip archives
11- expect manifest-based delivery, not GitHub import
12- inspect local skills with `forgedemy inventory --json` before deciding what to publish
13- transfer custom skills across runtimes with `forgedemy transfer <slug> --from <provider> --to <provider>` when the user wants the same bundle available elsewhere
14- when the user asks to port a skill across runtimes, prefer agent-led adaptation over blind transfer: inspect the installed source files, then create a Claude Code-native variant for the target runtime
15- 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 results
18- 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 disk
19- for native Forgedemy listings, use Forgedemy preview before any `skills.sh`, guessed raw GitHub URL, or other external source
20- log this machine in with `forgedemy login`
21- use `forgedemy logout` to unlink the current marketplace token before switching Telegram accounts
22- inspect the linked account with `forgedemy verify`
23- use `forgedemy inventory --provider codex|claude-code|openclaw --json` when the user wants one runtime only
24- 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 claude-code`
28- default installs create a lightweight live link; run `forgedemy source <slug> --provider claude-code` for the latest preview and use `forgedemy install <slug> --provider claude-code --materialize` only when the full bundle must exist locally
29- 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, then apply that skill before reading product code or starting implementation
31- use `--project` for workspace-only installs when this workspace should own the skill copy
32 
33Seller onboarding flow:
34 
351. run `forgedemy login`
362. open the Telegram deeplink
373. if Telegram returns a token-bound login command, execute that exact command for the agent
384. continue operating through the agent in a seller-scoped mode
39 
40`forgedemy register` remains accepted as a backward-compatible alias for `forgedemy login`.
41 
42Porting note:
43 
441. if the source is a Codex skill, including a hidden `.system` skill, or an OpenClaw skill with bundled/provider-specific assumptions, inspect and rewrite it for Claude Code instead of copying it unchanged
452. use `transfer` only when the folder is already runtime-neutral and the user wants an exact duplicate
46